Decide what the next person needs to know.
An inquiry arrives by email. Someone adds a quick office note. The customer changes one detail. By the time another teammate takes over, three versions of the job are floating around.
The handoff should answer four questions: what is being requested now, what remains unresolved, who has accepted the next action and what would show it happened? It should also let that person find the supporting record. A shorter summary is useful only if it keeps those distinctions.
This guide works with a notebook or shared record. An AI drafting tool can help organize a permitted example, but it does not confirm the facts or assign responsibility. Start with the method, then decide whether drafting assistance adds anything.
Read the changes in order.
Fictional source notes: The following repair-estimate example was written for this guide. It is not a customer transcript, an observed AI response or evidence of a client result. All times refer to the same Monday in the business’s local time.
On a small screen, swipe or scroll sideways to read the full table.
| Reference | Source note |
|---|---|
| A · 9:10 · Customer | “Can you estimate painting the living room and hallway? Friday might work if the price fits. Please email me.” |
| B · 9:18 · Office note | “Ask Casey for estimate. Friday?” |
| C · 10:05 · Customer correction | “Just the hallway for now. Living room can wait.” |
| D · 10:20 · Casey, estimator | “Need to know whether the ceiling is included before pricing. I haven’t agreed a work date.” |
| E · 10:30 · Morgan, office | “I’ll email the ceiling question by 3 p.m. today and update the request.” |
Read each source for its role as well as its time. The customer’s correction changes the requested scope. The office’s “Friday?” records a question, not a booking. Morgan’s acceptance establishes ownership of the clarification task, not confirmation that the email was sent.
Keep the earlier scope as history and label what the correction replaced. If two notes conflict without a clear correction or reliable source, flag the conflict instead of assuming the newest text wins.
Separate facts from gaps and proposals.
Write the current handoff with a source beside every consequential fact. Preserve uncertainty where the notes do not settle it. “Not confirmed” is more useful than a confident guess that somebody else must undo.
On a small screen, swipe or scroll sideways to read the full table.
| Part of the handoff | What the record supports |
|---|---|
| Current request | Hallway painting estimate. Customer correction C replaces the living-room-and-hallway scope in A. |
| Reply route | Email requested in A. No permission for unrelated outreach is inferred. |
| Unresolved details | Ceiling inclusion is unknown (D). Price and work date are not agreed. Friday is a customer possibility (A), not a reservation. |
| Accepted next-action owner | Morgan accepted emailing the ceiling question by 3 p.m. Monday (E). Sending is not yet evidenced. |
| Proposed later handoff | After the answer, ask Casey to accept the estimate-preparation task and its timing. This later assignment is not yet confirmed. |
Do not compress this to “Friday hallway job assigned to Casey.” That sentence turns a possibility into a date, skips the missing scope detail and gives someone work they have not accepted.
Use drafting assistance without handing over the decision.
If you use an AI tool, begin with these fictional notes or another example cleared for that use. Do not paste private conversations into a tool simply because a summary would be convenient. For real work, follow your organization’s approved handling rules and include only the information needed.
This instruction can also serve as a manual checklist:
Prepare a draft internal handoff from the supplied notes. List the current request, its source references, explicit corrections, unresolved or conflicting details, accepted next-action owner and agreed review time. Separate proposed actions from confirmed commitments. Do not invent prices, availability, bookings or ownership. Keep missing information marked unknown. Include a short list of questions a person must resolve. Do not write or send a customer message.
Read the draft against the notes line by line. Check every date, price, scope change and assignment. The example handoff above is an authored illustration, not a claim that any tool will reproduce it correctly.
Give the recipient a handoff they can accept.
Before sharing the record, confirm that the receiving person can find its sources and understands the action. If ownership is still proposed, say so. An accepted handoff needs more than somebody’s name in a field.
In the example, Morgan can prepare the clarification email. Casey is not yet committed to issuing a priced estimate by a particular time. Record the later acceptance when it happens. Keep the request’s stage separate from the latest task.
If a customer-facing reply is needed, draft and review it separately. The AI-written reply checklist checks what the message promises; this handoff checks what the team knows and owns.
Keep the handoff current.
Download the blank conversation-handoff worksheet (CSV). Use an internal request reference and source pointers rather than copying full messages into another file. Keep completed worksheets in your approved workspace.
Record the current request, the correction it incorporates, unresolved details, next action, accepted owner, due or review time and evidence needed to close that action. Add who checked the handoff and when.
When the customer answers the ceiling question, update the current handoff and retain the earlier version as history. A completed clarification does not mean the estimate, appointment or job is complete. Check the next estimate decision before choosing the next task. The next person should not have to reconstruct the conversation again.