Skip to guide
ClickFunnels AI

Plan the walkthrough · 7 min read

Plan a short walkthrough video someone can follow

Turn one useful task into a recording plan with a fictional storyboard, spoken visual details, caption and transcript work, and a reusable worksheet.

ClickFunnels AI planning guide · Published

A useful walkthrough has a visible finish. Someone should be able to name the task it explains and the output they are working toward.

Write that finish before recording your screen. Then plan what the viewer must see, what the narration must explain and what information must remain available without playing the video.

This guide assumes you have already chosen a walkthrough as a useful format. It produces a storyboard and a review plan. The example, worksheet and proposed narration are fictional; no video has been recorded or tested.

Give the recording one task

Imagine a tutor sharing a workshop-kit checklist. The walkthrough will explain how a participant marks each item provided, bring or ask using the tutor's event notes.

The finished output is a completed sample checklist with one unresolved question. It is not a workshop booking, a shopping order or proof that the participant has packed anything.

For your own recording, write four lines:

  • Who needs the explanation?
  • What do they need in front of them?
  • What decision or action will the recording explain?
  • What will remain unfinished afterward?

Keep unrelated work outside the recording. This example does not teach workshop registration, travel planning or how to use every feature of an editing application. A short recording can still be incomplete if it omits the input needed for its central task.

Prepare the example before the camera

The fictional event note says that paper is provided, participants should bring a pencil, and apron availability is unspecified. The checklist contains those three items and a blank decision beside each.

Scroll horizontally to compare all columns.

Item Information supplied in the example Result to explain
Paper Tutor provides it Provided
Pencil Participant brings it Bring
Apron Event note does not say Ask the tutor

Keep this input note beside the storyboard. It lets a reviewer trace the decisions without guessing what happened off screen.

Use invented sample information when real customer details are unnecessary. Inspect the intended capture area for names, notifications and unrelated browser tabs. If the recording depends on a real product screen, identify the actual product, workspace and version before capture. A drawn mockup must be labeled as a mockup.

Do not insert a success screen to bridge a missing action. If a task cannot be performed, the recording plan should say where the demonstration stops.

Write the visual action and spoken meaning together

The storyboard below is an original planning example. The four scenes have no promised duration. Read them aloud and allow time to follow the visible actions before deciding the final edit length.

Scroll horizontally to compare all columns.

Scene Planned visual action Proposed spoken text
S01 — Set the task Show the blank checklist and fictional event note “This sample checklist has paper, pencil and apron rows. Use the event note to mark each item provided, bring or ask.”
S02 — Resolve known items Mark paper Provided and pencil Bring “The note says paper is provided, so mark paper Provided. It asks participants to bring a pencil, so mark pencil Bring.”
S03 — Preserve the unknown Mark apron Ask; add a question below “The note does not say whether an apron is available. Mark apron Ask. Write: Should I bring an apron?”
S04 — Show the finish Display all three decisions and the unresolved question “The sample now says paper Provided, pencil Bring and apron Ask. Check the apron question with the tutor before treating the packing plan as complete.”

The narration names the row, evidence and resulting decision. “Click here, then choose this” would leave important meaning dependent on the cursor.

W3C describes integrating necessary visual information into the main narration when planning instructional video. Use that approach where it fits, then inspect the recording for details the script missed. W3C: Description of Visual Information.

Leave time to read the question in S03. If a close-up hides the event note, make sure its relevant wording is still explained. A viewer should not need to infer a rule from a fleeting highlight or color alone.

Plan captions and a useful text version

Decide who will prepare captions, review the spoken explanation and maintain a separate text version. Include these tasks before booking recording time. W3C's planning guidance covers captions, descriptive transcripts and player support as distinct parts of media accessibility. W3C: Planning Audio and Video Media.

For this example, the planned text version contains the input note, the four narration sections and the resulting three-row checklist. That preserves the task even when the reader does not play the video.

The storyboard is a useful starting document, but it is not a transcript of an unmade recording. After recording, reconcile the text with what was actually said and shown. If an unscripted correction changes the apron decision, update the corresponding text rather than leaving two contradictory instructions.

Review captions against the final audio for wording, timing and meaningful sounds. Keep them clear of information the viewer needs to read. A draft caption file or an automatic output still needs inspection in the actual player.

This plan does not certify accessibility. The finished media, text alternatives, player and page need their own checks in the intended setting.

Keep the edit honest

Remove waiting time when it adds nothing to the explanation, but preserve the meaning of the sequence. State an omitted wait when its duration or outcome matters to the task.

In this example, it is reasonable to cut a pause between marking two worksheet rows. It would be misleading to cut from “Ask the tutor” to a resolved answer that nobody supplied. The unresolved question is part of the useful finish.

Keep a record of the source recording, edits and any changed instructions. A replacement screenshot should not imply that the recorded action produced it. A staged explanation can teach a process without claiming a customer completed it independently.

Review the finished package against the plan

Before publishing, give a reviewer the intended task, actual video, final text version and checklist. Ask them to record what they checked, against which version, and what remains unresolved.

Use four checks for this example:

  1. R01 — Sequence: the input note and three decisions agree across the recording and text.
  2. R02 — Visual meaning: important row names, decisions and the unknown apron state are explained in audio.
  3. R03 — Text alternatives: captions match the final recording, and the separate text contains the complete example.
  4. R04 — Placement: the actual page exposes the video, text and usable playback controls as intended.

All four remain NOT RUN in the supplied worksheet. Planning a check is not a passing result. A reviewer finding “apron supplied” in one version should return that specific mismatch for correction.

Use the walkthrough-video planning worksheet for the filled storyboard and a blank production record. Assign the recording, text review and page checks to actual people when the work is scheduled.

For a ClickFunnels AI project, bring the approved material and unresolved requirements into the workflow described at /agents. The worksheet does not grant builder access, establish a video-hosting feature, generate captions, publish a page or verify delivery. Finish the plan with a specific next task: prepare the sample, record it or resolve a missing input.

About

Todd Dickerson is the technical co-founder of ClickFunnels. His focus here is helping business owners turn a funnel idea into clear instructions, understand the choices involved in an AI-assisted build, and check the result before sharing it.

Choose your first funnel goal: a guide download, webinar registration, or service enquiry

Plan a service quote request form: what to ask before the first reply

Plan webinar registration details people can use

Write one clear promise for a funnel page

Choose an AI build or an existing template for one funnel task

Estimate the work and costs of a small funnel launch

Choose the right ClickFunnels product and AI connection

Prepare a funnel project handoff a teammate can act on

Prepare test cases for a funnel without using real customer data

Read funnel results with the right counts and denominators

Prepare an existing page for an AI-assisted rebuild

Evaluate a funnel template before adapting it

Choose evidence that supports your funnel promise

Assign the next step before collecting a lead

Plan a signup confirmation page that matches what happened

Turn real prospect questions into a useful offer FAQ

Choose a lead-magnet format your buyer can actually use

Check what volunteers understand on your funnel page

Estimate the break-even point for a funnel change

Check that a campaign and its funnel page promise the same thing

Check a funnel's keyboard path before inviting visitors

Plan campaign links you can distinguish in a report

Write useful text alternatives for your funnel images

Prepare a useful help request when a funnel task gets stuck

Write funnel links that explain where they lead

Write form errors that help someone finish

Plan page titles and descriptions that match your funnel

Plan when your enquiry funnel should pause and reopen

Help buyers compare two service options by what they need

Check your funnel at narrow widths and browser zoom

Plan a manual recovery path for an unavailable download

Turn a service enquiry into a scope you can confirm

Plan an enquiry attachment request before adding an upload

Choose one first traffic channel from evidence you already have

Plan a review step before someone sends an enquiry

Decide whether two audiences need separate offer pages

Plan what a funnel-page comparison can actually tell you

Prepare a funnel translation brief that preserves the offer

Explore a buyer's decision without guessing from clicks

Update a shared lead magnet without losing track of old copies

Plan a small funnel pilot with a clear stop-or-continue decision

Explain what a service price covers before the enquiry

Plan a useful fallback when an embedded tool cannot load

Organize a long offer page around the reader's next question

Prepare a worksheet people can complete on paper

Plan image crops that keep the important details visible

Review repeated enquiries before treating them as duplicates

Retire an offer page without misleading returning visitors

Plan motion controls before adding animation to a funnel

Choose form controls that fit the answer you need

Plan help for someone who cannot complete your enquiry form

Prepare a lead-magnet brief and launch checks