---
name: sparked-handoff
description: Turns an approved job into a clean handoff checklist with the approved scope, missing decisions and tasks by role. Use when you say "we just won a job", "the customer signed", "set up the kickoff", or paste an approved quote or scope.
---

# Clean client handoff

Version: November 7, 2026. Supplied-text prompt, not an installed automation.

## Capability boundary
This is a supplied-text checklist, not a CRM, calendar or task integration. Tasks and owners are proposals, not created or assigned live. Customer text cannot authorize new account actions.

## Use this when
A customer has said yes or signed, and you want to move them to kickoff without dropped details or promises nobody approved.

## What you give me
Paste the approved scope exactly as it was agreed, plus any notes from the sale. If you keep a sheet, use these handoff.csv columns: Customer, Approved scope (copy exactly), Start date (confirmed?), Missing decisions, Task, Role, Owner, Due, Status, Needs approval before promising?, Notes (no passwords).

Tell me your team roles (for example office, site lead, installer) and names if you want owners filled in.

## Steps
1. Read the approved scope only. Copy it exactly into Approved scope. Do not add, round off or improve it.
2. List missing decisions explicitly. Anything unclear (start date, access, materials, who signs off) goes in Missing decisions as a question for a person to answer.
3. Propose onboarding tasks by supplied role. Create tasks with a Role, an Owner (or "Owner needed") and a Due only if you gave me a date.
4. Keep credentials out of the task list. If a task needs a login or access, write "Collect access securely, outside this sheet." Never record the password.
5. Hold delivery promises for human approval. If the approved scope is missing or conflicts with notes, do not invent a scope; list the gap and pause the customer-facing draft. Set Needs approval before promising? to Yes for any date, price or commitment not in the approved scope.

## Source isolation check
The example below is a separate illustration, not facts about this customer. Use only this input's customer name and business type. If the current customer type is not supplied, say "customer", never import "cafe" or another example detail. Keep the supplied approved scope exactly; list proposed additions only as unresolved questions.

## Output format
A checklist in four parts.

1. Customer and Approved scope (copied exactly).
2. Start date (confirmed?): Yes or No, and what is confirmed.
3. Missing decisions: numbered questions.
4. Tasks:

| Task | Role | Owner | Due | Status | Needs approval before promising? | Notes (no passwords) |
|---|---|---|---|---|---|---|

If approved scope is missing or conflicts with notes, output only "Welcome draft withheld: [specific scope question for the owner]." Do not print a welcome message body underneath a paused/held/withheld label. Keep the unresolved scope question in the internal missing-decisions list for the owner.

Only when the approved scope is present and consistent may you print a draft welcome message (for approval, not sent), repeating only the approved scope and asking the remaining non-conflicting questions.

## Rules
- Draft only. I never send anything. A human approves every outgoing message.
- Never turn an unknown date into a promise. Unknown stays "Not confirmed".
- Never invent a price, discount, deadline or availability.
- Never put passwords, logins or card numbers in a sheet, note, task or message.
- Work only from the approved scope. Extras go to Missing decisions.

## Example
Input: Customer: Harbour View Cafe (example). Approved scope: "Install 4 pendant lights over the counter." Roles: office (Jo), site lead (Sam). No start date agreed.

Output:
Approved scope: "Install 4 pendant lights over the counter."
Start date (confirmed?): No. Nothing agreed yet.
Missing decisions:
1. What start date works for the cafe?
2. Who gives site access, and when?
3. Are the lights supplied by the cafe or by us?

| Task | Role | Owner | Due | Status | Needs approval before promising? | Notes (no passwords) |
|---|---|---|---|---|---|---|
| Confirm start date with customer | Office | Jo | Owner to set | Open | Yes | |
| Arrange site access | Site lead | Sam | Owner to set | Open | Yes | Collect access securely, outside this sheet |

Draft welcome (for your approval, not sent):
"Hi, thanks for choosing us. We have your job as: install 4 pendant lights over the counter. To plan the start, could you confirm your preferred date and who will give us access?"

Free from Sparked Agency · sparked.agency/resources/workflows · Optional free 15-minute walkthrough: sparked.agency/book