Hand an agreed customer scope to delivery
Turn an agreed customer scope into a linked delivery task with enough detail for its owner to accept the work.
Hand an agreed customer scope to delivery
Turn an agreed customer scope into a linked delivery task with enough detail for its owner to accept the work.
Before you start: Have the customer’s current agreed scope, target date, acceptance criteria and exclusions. Identify the CRM enquiry, destination Board and person who should own delivery.
Steps
1. Open the exact enquiry in the intended CRM space. Read the current scope and customer decision. A lead stage, deal amount or expected close date is not the customer’s agreement to the deliverable.
2. Inspect Linked Work for the intended production task. If it already exists, skip steps 3–4 and open that task for the brief check in step 5. Do not create a second task merely because an earlier discovery task is complete.
3. Select Add task on the lead. Choose the intended Board and give the task an action-based title for the agreed output. Preserve the generated source description so the CRM relationship remains clear.
4. Use Backlog for work not yet started. Set the agreed Due Date through the calendar and OK, and inspect Assign Members for the intended owner. Select Create Task once. Reopen it from the lead’s Linked Work and check the retained Board, source, date and assignee.
5. In Comments → Write a comment, put the current agreed brief: output and version, required inputs, inclusions, exclusions, target date and acceptance checks. Include the relevant customer decision reference. If the same complete brief is already present, use it; otherwise submit the new comment with the visible send arrow.
6. Reopen the task and read the complete brief. Check that the delivery owner can identify what to produce without reconstructing the sales discussion. Keep a customer decision date separate from the task’s delivery deadline.
7. Send the intended owner a concise handoff through your normal connected communication route. For Inbox, use Compose, check From/To and the full message, and include the CRM source, Board task locator and agreed scope version. Select Send only when the intended recipient and content are correct.
8. The receiving owner opens the actual source and task, checks the inputs, timing and capacity, and confirms responsibility or identifies the missing information. Record the resulting decision on the task, without claiming that sending the handoff itself establishes acceptance.
9. Check the task’s saved assignee and date after the handoff. Use Update Task only for an intended change. Leave production incomplete until the output is actually produced and reviewed.
Expected result
The delivery task is linked to the customer enquiry and contains the agreed scope, with ownership confirmed or a specific unresolved handoff issue.
Common pitfalls
- Discovery completion is not delivery completion. Keep the preparation task and production task distinct.
- A later draft scope does not replace the customer’s agreed version automatically. Resolve changes before delivery proceeds.
- If the intended owner is unavailable in the picker, resolve that assignment rather than selecting an unrelated person.
Continue learning
In this series: Customer enquiry to delivery — guide 2 of 3.
Turn what you learned into the way the team works.
Mark this lesson complete once the workflow exists in your workspace—not simply when you reach the bottom.