A review screen should let someone inspect the answers they intend to send and correct a mistake. Showing a summary is only part of that job. The change action, return path and final submission need a clear plan too.
Use this exercise when an enquiry has several steps or choices that affect later questions. Finish with a review map: the values shown, the edits allowed, dependent questions and evidence needed to check the final send. A short, straightforward form may not need a separate review screen; assess the actual task before adding another step.
The window-display enquiry below is fictional. Its screens and behaviors are requirements, not an implemented or tested ClickFunnels AI form.
Identify the commitment that has not happened yet
Write the action the visitor is reviewing: “Send an enquiry about a window-display consultation,” for example. Reviewing those answers does not book a visit, produce an estimate or establish that the business received the enquiry.
The GOV.UK check-answers pattern describes letting people inspect and change information before they finish a transaction. Apply that interaction principle to your enquiry. Government declarations and claimed error-reduction benefits are not promises this plan establishes.
Use a heading such as Check your display enquiry before sending. The final button in this fictional journey is Send my display enquiry. A change link edits an answer; it must not silently perform that final action.
Draft saving, if it exists, is separate from sending. Do not promise that progress is stored merely because someone reached the review screen. Record the actual persistence behavior as an implementation question.
Build a summary from the relevant answers
Imagine a studio offering an initial discussion about a shop's window display. The fictional form asks for a reply address, discussion format and topic. A shop town is required only when the visitor requests a visit. An additional note is optional.
The proposed first review looks like this:
Scroll horizontally to compare all columns.
| Review label | Fictional value shown | Change action |
|---|---|---|
| Reply address | The address the visitor supplied | Change reply address |
| Discussion format | Visit my shop | Change discussion format |
| Shop town | Brookford | Change shop town |
| Topic | Seasonal window layout | Change topic |
| Additional note | Not provided | Add or change additional note |
Use recognizable labels and the current answer, not an internal code. The optional blank note is distinguishable from a value that failed to load. “Not provided” is appropriate only when the process knows the visitor left that optional answer blank.
Keep the summary limited to relevant information. It does not need extra personal data merely to look like a receipt. Any field requiring special handling needs an explicit display rule; do not assume every collected value belongs on this screen.
Define the change-and-return path
Take Change topic. In the plan, it opens the existing topic question with the current answer available. After an acceptable edit, the visitor returns to review and sees the new topic. The unrelated reply address and discussion format remain as entered.
GOV.UK's pattern describes retaining existing answers, offering change links and returning to the review after an edit. Those are requirements to check, not behaviors supplied by a plain-text worksheet.
Give each repeated change action enough context to distinguish it. Someone using a keyboard or assistive technology should be able to identify which answer they are changing. Record the intended label, destination and return point. The implementer still needs to verify actual associations, focus behavior and announcements in the rendered journey.
If the edit is incomplete, keep the relevant correction within that question. Do not return to a confident summary with a value the process has already rejected. Field-error wording has its own plan; this review map records when the answer is ready to return.
Follow changes that affect other questions
A change to Discussion format is more complicated than editing a topic. It can change which information is needed.
If the fictional visitor switches from Visit my shop to Video call, Shop town is no longer required for this enquiry. The review should no longer present it as a relevant answer. What happens to a previously entered town behind the scenes is a separate data-handling decision. Hiding a row does not prove deletion.
If the visitor switches from Video call to Visit my shop, the town becomes required. Ask the newly relevant question before returning to a complete review. Do not carry on with an unexplained blank or invent the town from another answer.
The same principle applies to any answer that reveals more questions. Mark those dependencies in the worksheet so the builder does not treat every change link as an isolated text edit.
Prepare four checks before implementation
These are expected cases, not test results. Use safe fictional inputs and an authorized environment when carrying them out.
Scroll horizontally to compare all columns.
| Case | Starting situation and change | Expected review result |
|---|---|---|
| V01 | Edit Topic from Seasonal window layout to Display lighting discussion | New topic appears; unrelated relevant answers remain as entered |
| V02 | Change Visit my shop to Video call | Shop town is no longer required or shown as a relevant answer |
| V03 | Change Video call to Visit my shop when no town is available | Ask for the required town before returning to a complete review |
| V04 | Review context is unavailable or expired | Explain the known state and supported recovery; do not invent answers or imply the enquiry was sent |
V02 and V03 are separate cases. Do not assume V03 can reuse the town from V02. The plan deliberately starts V03 without one.
Keep each case NOT RUN until someone performs it. Record the starting answers, action, returned values, visible message and evidence. If recovery in V04 is not specified, leave it unresolved. A “Start again” instruction needs a known effect on the existing attempt, especially when its submission state is uncertain.
Check the final send separately
The final send must use the reviewed, relevant answers. Compare the resulting enquiry with the latest review state in a permitted check. Seeing the updated topic on screen does not establish that the receiving record used it.
Record receipt separately from later work. A saved enquiry is not a booked consultation. A confirmation screen should describe only the result the process has established; an unknown submission result needs its own handling.
Also inspect the path that reaches review without valid context. An old bookmark or direct address should not manufacture a completed enquiry. Keep this requirement in the implementation brief rather than assuming navigation alone proves the state.
Finish the review map
The enquiry review worksheet contains the fictional summary, V01–V04 and blank change/dependency records. Choose one question whose edit affects another answer and map that path first.
For a ClickFunnels AI project, use the map alongside the agent guide, subject to its workflow and access requirements. The worksheet grants no builder access and establishes no draft-saving, conditional-form or submission capability. It gives the implementer a specific behavior to confirm before the review step is used.