FUNNEL-PAGE COMPREHENSION WORKSHEET Companion to: Check what volunteers understand on your funnel page ClickFunnels AI | Planning resource Purpose: Observe what a reader thinks one page offers and what happens next. This is not a functional test, conversion experiment or proof of demand. All filled example records below are fictional. No sessions have been run. PART 1 — MODERATOR PLAN (DO NOT SHOW THE INTENDED ANSWERS TO PARTICIPANTS) Page title: Version/date and location of the reviewed copy: Material: Static document / Printout / Suitable prototype / Other Research question (one uncertain meaning): Decision the visitor is trying to make: Intended meaning, with source in the current offer: Unsettled business facts to resolve before the session: Relevant reader context: Where volunteers will come from: How this group differs from the intended audience: Access arrangements, device and assistive setup needed: Approximate time stated in invitation: Moderator: Observer/note-taker, if any: Consent and notes plan: - Explain purpose, observers, notes and any proposed recording in advance. - Explain that participation is voluntary; questions may be skipped or stopped. - Obtain agreement before starting; obtain agreement before any recording. - Decide where agreed notes are kept, who can access them and when to remove them. - Use participant codes; omit unnecessary names, emails and private details. Agreed process/reference: Recording: None / Separately agreed Restricted notes location and access: Retention/removal plan: Action boundary: What is interactive: Where the exercise stops: How real submissions, purchases and notifications are prevented: If prevention cannot be established, use a static copy and point-only tasks. What this material cannot establish (for example, live keyboard behavior): PART 2 — SHORT DISCUSSION GUIDE Opening suggestion, adapt to the agreed process: "We are checking whether this draft makes sense. Unclear wording is useful for us to find. You can skip a question or stop. Please look through the page as you normally would. We will stop before submitting or buying anything." Confirm notes/observers/recording arrangements and any access needs. Allow time to inspect the page without explaining its intended meaning. Suggested prompts, one at a time: 1. In your own words, what is being offered here? 2. What would you expect to have or be able to do afterward? 3. What would you do next if you wanted to find out more? 4. What do you expect after taking that action? 5. What on the page led you to that answer? Useful follow-up: Ask the reader to explain an unclear answer in more detail. Avoid: Supplying the intended answer in the question or correcting too early. If you give help: Record when and what; distinguish answers before/after help. At the end: Invite final questions, thank the participant and explain next steps. PART 3 — FICTIONAL FILLED EXAMPLE Page: Product Photo Planning Workshop, version A. Scope: A live group session creating a shot list for products attendees have. Not included: Taking or editing their photographs. Button: Request workshop details. Intended next step: Information request; no place reserved by this request. Research question: Can likely readers distinguish planning from photography, and requesting details from booking? Setup: Static draft; no live submissions. All records below are invented. V01 observation (fictional paraphrase): Expected edited photos and pointed to "Get your product photos ready." Interpretation: Headline may imply a finished photography service. Other possible influence: Prior expectations or another page section. Proposed action: Specify shot-list output and who takes/edits the photos. V02 observation (fictional paraphrase): Expected a reserved place after pointing to "Request workshop details." Interpretation: Nearby "Save your spot" text may contradict the button. Proposed action: Remove the inconsistent phrase; explain the request step. V03 observation (fictional paraphrase): Described shot-list planning but could not find what to bring. Interpretation: Required materials may be missing or hard to find. Proposed action: Add preparation details beside session information. Version B proposal: "Plan a shot list for your product photos." Supporting clarification: Attendees take and edit their own photographs. Fact to verify before real use: This must match the actual agreed workshop scope. Recheck status: Not run. No misunderstanding rate or improvement claimed. PART 4 — BLANK OBSERVATION RECORD (COPY PER OBSERVATION) Observation ID: Session date: Participant code and relevant context: Page version and material/device: Previous exposure to this page or an earlier version: Prompt or task: What was said/done: Record type: Faithful paraphrase / Exact wording recorded with agreement Page wording/element the participant pointed to: Help or explanation supplied, with timing (or none): Intended meaning: Difference, if any: Possible explanation (separate from observation): Alternative explanation or unresolved question: Evidence not collected / limitation: PART 5 — REVISION DECISION Decision ID: Observation IDs supporting the decision: Which visitor decision could be affected: Current wording/location: Proposed change: Reason: Business fact/source that must be checked first: Owner: Action: Revise / Clarify offer / Research further / Keep with reason Reason for keeping, if applicable: New version identifier: PART 6 — RECHECK AND BOUNDED REPORT New version/date: Question to check again: Relevant reader contexts included: Prior-exposure status recorded for each participant: What was observed: Contradictory observations: Help supplied: What remains uncertain: Next decision/owner: Suggested reporting structure: "On [version], participants with [relevant contexts] interpreted [specific element] as [observed meaning]. We propose [change] because [reason]. We have not established [remaining uncertainty]. The next check is [question]." Do not describe this small volunteer exercise as an audience-wide success rate, sales-demand validation, accessibility certification or conversion improvement. USE BOUNDARY For CFAI workflow and access requirements: https://www.clickfunnels.ai/agents This plan does not grant builder access, send requests, book places, configure delivery, test a backend or publish a page. BACKGROUND GUIDANCE Moderated tasks: https://www.gov.uk/service-manual/user-research/using-moderated-usability-testing Inclusive research: https://www.gov.uk/service-manual/user-research/how-user-research-improves-service-design Neutral questions: https://www.gov.uk/service-manual/user-research/using-in-depth-interviews Observation and interpretation: https://www.gov.uk/service-manual/user-research/analyse-a-research-session The workshop scenario, observation records and decision log are original editorial exercises, not actual participant evidence.