Name the next action, the current version and the evidence required on return. Include what has already been checked and which decisions remain open. Give the recipient the material and authority needed to complete that task.
“Finish the funnel” leaves too much to infer. Editing copy, connecting a workflow, reviewing a preview and publishing a page are different tasks. State the outcome you are handing over and the check that will establish completion.
This guide provides an original team process and a fictional example. The roles below are work responsibilities, not claims about roles or permissions available inside ClickFunnels AI or any other product.
Write the next action in one sentence
Use this pattern:
Please [specific action] using [current material], within [scope of changes]. Return [result and evidence] by [agreed date or next milestone].
For example: “Please replace the preview's workshop description with the reviewed copy, keep the request flow unchanged, and return the updated preview with a note of the sections you changed.”
That sentence gives an editor a concrete task. If the task also includes publication, say which destination and version may be published and who has that authority. If the next action is a review, state which decision the reviewer is expected to make.
Identify the current artifacts
List one current version of each needed artifact. Include the brief, reviewed copy, approved images, preview, workflow notes, test results and intended public destination where relevant. The recipient should be able to locate the material without reconstructing the project history.
| Artifact | What the recipient needs to know |
|---|---|
| Brief or decision record | Which version describes the agreed offer and scope |
| Copy and images | Which material is current, and whether important conditions remain unresolved |
| Editable project | Where the work lives and how the recipient obtains appropriate access |
| Preview | Which version it represents and what can be inspected there |
| Workflow notes | The intended destination or owner for the visitor's next action |
| Evidence | What was checked, in which environment and on which version |
| Public destination | The intended host and path, plus whether that actual destination has been verified |
Label old drafts as superseded so the recipient can distinguish them. Use the team's normal access process for accounts or restricted files; the handoff should point to that process rather than contain passwords or secret keys.
Separate the work state from its evidence
Use plain descriptions such as drafted, implemented in preview, checked in preview, published, or public destination checked. Add the version and date to each observation.
Those labels answer different questions. A preview can show the new copy. A workflow check can show where a permitted test request went. A public check can show what an anonymous visitor actually receives at the intended address. Keep the evidence tied to the particular result it supports.
For a verbal check, record the actual observation and what remains uninspected. “Looks ready” does not identify a test result. After a page change, mark any earlier observations that need to be checked again.
A fictional handoff for a workshop enquiry page
Imagine a ceramics studio preparing a private-group workshop enquiry page. The copy has been reviewed and a preview exists, but the coordinator has not yet confirmed the destination for incoming requests. All people and work states in this example are invented.
The next task is to prepare the preview for a focused review. It does not include sending a campaign or publishing the page.
Scroll horizontally to compare all columns.
| Responsibility | Fictional owner | Next action | Evidence to return |
|---|---|---|---|
| Offer and conditions | Studio manager | Confirm the workshop description and the statement that an enquiry does not reserve a date | Decision recorded against the current copy |
| Page edits | Page builder | Apply the reviewed text and supplied images to the named preview | Updated preview and a short change list |
| Request handling | Event coordinator | Identify the actual request destination and person responsible for replies | Destination and owner recorded; later workflow check still required |
| Review | Operations teammate | Compare the updated preview with the agreed copy and record unresolved differences | Review notes tied to that preview version |
| Publication decision | Studio manager | Decide whether the required work and evidence are complete before authorizing the intended destination | Explicit release decision naming the version and destination |
The builder can act on the page copy while the coordinator settles the request destination. The handoff makes that dependency visible. It should not ask the builder to invent a reply address or mark request delivery complete because the preview shows a confirmation message.
Include the decisions that constrain the work
For the fictional project, the decision notes could be:
- The offer is an enquiry about a private workshop; it does not reserve a date.
- Use the manager's reviewed workshop description and the three supplied images.
- The builder may change page wording and image placement within that scope.
- Request routing is unresolved and belongs to the coordinator.
- The current task ends with an updated preview and review notes.
- Publication and campaign distribution are separate next actions owned by the manager.
These boundaries reflect this fictional assignment. Your own handoff should state the authority already agreed for your team. Do not invent a new approval step when the relevant person already has permission to complete the work.
Write a handoff message the recipient can use
Here is a fictional message based on that project:
Please apply the reviewed workshop copy and the three supplied images to the current enquiry-page preview. Keep the offer as a request for availability, with no confirmed-booking language.
The materials list identifies the current copy and preview. Return the updated preview, the sections changed and any differences you could not resolve.
The event coordinator still needs to confirm the request destination. Record that dependency; do not mark delivery checked until the actual destination and permitted test are complete. This assignment ends at preview review. The studio manager owns the later publication decision.
In a real handoff, replace the references with actual current links and name the people responsible. A useful message should not require the recipient to search an entire conversation for the right file.
Ask the recipient to confirm the next action
Ask for a short reply naming the task, the version to use and any missing access or decision. That gives both people a concrete point to correct before work starts.
Compare the returned work with the requested outcome. Record the new version, received evidence and unresolved dependencies. Update those details before the next handoff. An old “ready” message may describe a different version or set of assumptions.
Use the project handoff worksheet
The funnel project handoff worksheet includes the task, artifact inventory, responsibility table, evidence record and return notes. It can be used for an editor, builder, reviewer or project owner without assuming a particular collaboration feature.
For a ClickFunnels AI project, consult the agent guide for its workflow and access requirements. Verify the actual account and product permissions separately; assigning a responsibility in this worksheet does not grant access or publish anything.
Common questions
Can one person own several responsibilities?
Yes. Name that person wherever needed. The useful distinction is which task and decision they own, not how many people appear in the table.
What if a dependency is still unresolved?
Name it, its owner and the work it blocks. Other clearly scoped work can continue when it does not depend on that decision. Keep the unresolved item in the returned handoff until it is settled.
How much evidence should the handoff include?
Enough to support the specific state being claimed. A copy edit may need the changed preview and comparison notes. A delivery claim needs evidence from the actual delivery path. Label what has not been checked so the next person can act accurately.