Do what you promised.
Write the result, collect inputs, do the visible steps, and hand off the work clearly.
Mission outcome
At the end of this manual, you will have:
- One fulfillment checklist.
- One customer handoff note.
- One revision boundary rule.
- One QA and proof-capture checklist.
- One feedback loop.
- One repeatable SOP update.
- One delivery safety lock.
Stop reinventing delivery.
Use one checklist for scope, QA, revisions, proof, feedback, and follow-up.
Build review-only delivery ops.
Let AI prepare checklists, drafts, QA notes, and SOP files while humans approve quality and customer-facing actions.
Fulfillment checklist
Promise, inputs, work blocks, QA, handoff, feedback, and SOP update.
Revision boundary
A plain rule that separates fixing the agreed deliverable from new scope.
Proof + SOP loop
Capture permissioned proof and turn repeated work into safer templates.
Promise rule
If the promise is fuzzy, delivery will be messy.
Before delivery starts, write the result, included scope, excluded scope, customer inputs, review point, and done condition in one plain sentence.
10-year-old mode
Delivery means doing what you said.
We promised this result. We need these inputs. We will do these steps. A human checks the work before the customer sees it.
From Guide 06
Bridge an approved customer promise into delivery.
Use the Guide 06 → Guide 07 Delivery Bridge when a proposal snapshot or customer commitment is ready to become work. The pack turns the approved promise into a fulfillment checklist, customer handoff note, revision boundary, proof-capture request, and SOP update — without sending, publishing, deploying, changing live systems, or using private data without approval.
Proposal to promise
Confirm the source signal, approved next step, exact result, scope, inputs, review point, and done condition.
Checklist before tools
Break the job into visible work blocks and QA checks before AI drafts, compares, or prepares handoff notes.
Customer-facing only after approval
Draft the note and proof request locally; a person approves recipients, claims, privacy, boundaries, and timing.
Fulfillment checklist
Seven lanes make delivery visible.
What was approved?
Result, scope, boundary, timeline, and done condition.
What do we need?
Customer materials, examples, notes, access, and constraints.
What are the steps?
The smallest visible blocks from kickoff to handoff.
What must be checked?
Truth, links, claims, privacy, math, design, and usability.
How will they use it?
What changed, how to review, and what comes next.
What happened?
Approved, revision, objection, follow-up, or no next step.
What can repeat?
Permissioned proof, anonymized lesson, template, or SOP update.
Customer promise
What exact result did we agree to deliver?
Inputs needed
What files, notes, examples, decisions, or access are required?
Work blocks
What are the 3–7 visible steps from start to handoff?
QA checks
What must be true before the customer sees it?
Revision boundary
What is included, and what becomes new scope?
Proof / SOP lesson
What can be reused with permission and private details removed?
Intermediate workflow
Make every delivery teach the next one.
Restate the promise
Confirm result, inputs, boundary, timeline, and review point.
Work in visible blocks
Move from inputs to draft to QA to handoff.
Review before customer view
Check truth, privacy, claims, links, and scope.
Capture proof and SOP
Save feedback, permission, reusable steps, and next improvement.
Advanced workflow
Build review-only delivery ops.
Create statuses for kickoff, waiting on inputs, in progress, QA, customer review, revision, approved, proof captured, and SOP updated. Give AI only named draft actions: summarize brief, make checklist, draft handoff, check scope, flag missing inputs, draft FAQ, and create local SOP file.
Safe AI delivery loop
AI prepares delivery work. Humans own quality.
ReadApproved brief, inputs, scope, and constraints.
PrepareChecklist, work plan, QA notes, handoff draft, SOP draft.
CheckCompare finished work against promise, privacy, and claims.
ApproveHuman reviews before customer contact, publish, deploy, or live changes.
QA before handoff
Seven checks before the customer sees it.
- The delivered work matches the approved promise.
- Scope boundaries are still clear.
- Links, files, forms, calculations, and instructions were checked.
- Private data is protected.
- Claims are truthful and do not imply guaranteed results.
- A human approved the handoff note.
- Follow-up and revision expectations are clear.
Revision boundary
A revision fixes the agreed deliverable. New scope changes the promise.
Type
Included revision
New scope
Content
Clarify confusing wording or correct a mistake.
New audience, offer, page, campaign, or guide.
Inputs
Add missing information that was already approved.
New customer data, platform, or business decision.
Automation
Fix the checklist or local draft instructions.
Live account changes, deployment, credentials, sending, or integrations.
Handoff note
Make the customer feel oriented, not abandoned.
What we built
Restate the approved artifact and result in plain language.
How to use it
Give the first action, review path, and owner instructions.
What is included
Name the revision boundary so fixes do not become scope creep.
What proof helps
Ask for feedback, quote permission, or anonymized result only after real use.
Route-complete pack
Turn delivery into proof and a better system.
After a delivery is handed off, use the Guide 07 Route-Complete Proof Loop to capture a delivery retro, proof-permission card, SOP update, offer improvement log, and next customer/content route. It keeps every public proof claim, quote, screenshot, logo, customer name, metric, send, post, and live-system action behind human approval.
What happened?
Save the real lesson: what worked, what blocked delivery, what needed approval, and what should repeat.
What can be shown?
Separate anonymous lessons, permission-pending proof, approved proof, and claims that must stay unused.
What improves?
Update the SOP, tighten the offer, and draft the next useful FAQ, post, guide section, or customer-system note.
Do not do this
Do not let delivery create risk.
- No fake proof or invented testimonials.
- No live customer changes without approval.
- No silent scope creep.
- No sending files or messages automatically.
- No using private details or credentials in AI tools casually.
Do this instead
Turn good work into a system.
- Save the promise and inputs.
- QA against the promise.
- Hand off with clear next steps.
- Capture feedback and permission.
- Update the SOP after delivery.
- Use the lesson to improve the next offer.
Ready to deliver?
You are ready when the promise, inputs, QA, handoff, revision boundary, and human approval gate are visible.
Ready. Begin Manual 07.
Delivery quality is human-owned.
AI may summarize, organize, compare, draft, check, anonymize draft notes, remind, and create local files. Human approval is required before sending, publishing, deploying, contacting people, changing live customer systems, deleting records, accepting terms/contracts, entering credentials, or using private payment/tax/legal/KYC/identity details.
- Never invent results, testimonials, screenshots, logos, customer quotes, or revenue.
- Never publish proof without permission and private-detail removal.