Choose one page and one thing you are unsure people understand. Can they explain what the offer includes? Do they know whether the button requests information or books an appointment?
A small comprehension check helps you hear those interpretations before polishing more copy. You will leave with observations tied to a page version, a decision about what to clarify and a question to check again.
This exercise examines meaning. It does not test whether a form saves, prove demand or measure a change in sales. The workshop, participants and notes below are fictional. They are not coaching conversations or results from a ClickFunnels AI project.
Write the question you want the session to answer
Start with a decision the page asks a visitor to make. Write the meaning you intend in a private moderator note. Keep that note out of the participant's view so it does not supply the answer.
For this exercise, imagine an online Product Photo Planning Workshop. Its fictional scope is a live group session about making a shot list using products the attendee already has. It does not include taking or editing their photographs.
The page has a Request workshop details button. The intended next step is a request for information, with no place reserved by that request. Those are assumptions for the fictional offer, not claims about a configured workflow.
The research question is: Can a likely attendee distinguish planning help from a photography service, and a details request from a booking? That is narrow enough to guide a useful conversation.
GOV.UK's moderated usability guidance recommends agreeing the research question and using realistic tasks that do not reveal the answer. This exercise applies that principle to one page's meaning.
Invite people whose context fits the question
Look for volunteers who resemble likely readers in the relevant way. For the fictional workshop, that means people preparing product photographs who can discuss what they need help with. Someone who wrote the page already knows more than a first-time reader.
Keep the invitation clear: what they will review, the approximate time, whether anyone else will observe and how you will use their notes. Participation should be voluntary. Explain that they may skip a question or stop, and get agreement before any recording. A written note may be sufficient for this small exercise.
Ask about access arrangements and let participants use a suitable device or assistive setup. GOV.UK's introduction to user research stresses including people with different needs and avoiding research arrangements that exclude them.
A convenient group of colleagues or friends can help expose confusing wording. Record that limitation if their context differs from the intended audience. Do not turn their agreement into a claim about all prospective buyers.
Prepare a version people can inspect without submitting
Use an identified draft, printout or suitable prototype. Record its version and date. For this check, use a copy with real submissions, purchases and notifications disabled; if that cannot be established, use a static document and ask participants to point to the action they would take.
Explain what is interactive and where the exercise stops. Do not ask for personal contact details or let an ordinary comprehension session become an accidental signup. A screenshot can support a wording check, but cannot establish keyboard, screen-reader or live interaction behavior. Note what the chosen material allows you to observe.
Keep the same version for a round of sessions. If you change it midway, record a new version and separate the notes.
Use neutral prompts and leave room for an answer
Open with a short explanation: you are checking the page, and unclear wording is useful to discover. Give the participant time to read or explore it in their usual way.
| Prompt | What to listen for |
|---|---|
| “In your own words, what is being offered here?” | Their interpretation of the scope |
| “What would you expect to have or be able to do afterward?” | The output they believe the offer provides |
| “What would you do next if you wanted to find out more?” | Where they look and which action they choose |
| “What do you expect after taking that action?” | Whether they expect information, a reservation or something else |
| “What on the page led you to that answer?” | The text or visual cue behind the interpretation |
These are suggested prompts to adapt, not a scored examination. Ask one at a time. Avoid correcting an answer while you are still trying to understand it.
If someone says “I think they do the photos,” ask what led them there. “You understand this is only planning, right?” teaches the desired answer. GOV.UK's interview guidance recommends open, neutral questions and follow-ups that clarify what someone means.
If a participant asks for help, first ask what they would normally look for. If you explain something, mark the point in your notes. An interpretation after an explanation is different from an interpretation based on the page alone.
Separate the observation from your explanation
Record what you heard or saw, then write your interpretation separately. GOV.UK's research analysis guidance makes this distinction before moving from observations to findings and actions.
Here are three invented observations from separate fictional sessions on version A. They are paraphrases, not quotations from actual people.
Scroll horizontally to compare all columns.
| Observation | Possible explanation to investigate | Proposed response |
|---|---|---|
| V01 expected edited photos and pointed to “Get your product photos ready” | The headline may imply a finished photography service | Specify that the session produces a shot list; clarify who takes the photos |
| V02 expected a reserved place after pointing to “Request workshop details” | Nearby “Save your spot” text may contradict the button | Remove the inconsistent phrase and explain the information-request step |
| V03 described planning a shot list but could not find what to bring | Preparation information may be missing or hard to find | Add the required materials beside the session details |
These notes suggest edits worth checking. They do not prove that the headline caused every misunderstanding. A participant's prior experience, the task instructions or another part of the page could also matter.
Choose an edit and check the meaning again
Prioritize a mismatch that could change someone's decision: believing a service includes work it does not, for example. Write the observation IDs, proposed change, reason and any fact the offer owner must settle first.
For version B of the fictional page, one proposal is “Plan a shot list for your product photos.” Add that attendees take and edit their own photos. Keep that wording only if it matches the actual offer. If the business has not decided the scope, clarify the offer before rewriting around it.
Check the revised version with relevant readers again. Record whether they have seen version A; prior exposure may affect their interpretation. Preserve contradictory observations instead of declaring the issue solved because one person now understands it.
Report the scope plainly: which page version, which reader contexts, what was observed and what remains uncertain. This small exercise supplies qualitative evidence for revision. It does not estimate an audience-wide success rate or establish a conversion improvement.
Finish a session plan you can reuse
Use the comprehension-check worksheet. It contains a moderator plan, the fictional example, blank observation records and a revision-and-recheck log. Use participant codes and keep only the context needed to interpret the session; store agreed notes in an appropriate restricted location.
For a ClickFunnels AI project, bring the wording decisions and unresolved questions into your brief alongside the agent guide, subject to its workflow and access requirements. This plan does not grant builder access or verify submission, booking, delivery or publication. Complete one check of meaning, then give the clearest mismatch a specific next step.