<aside> 📋 Frequency: Trigger-Based | Time: 60 min | Trigger: When a deliverable is due within 5 business days

</aside>

Deliverables produced without a process get delivered late, half-finished, or misaligned to what the client actually needs — and you discover that misalignment on the call when it's too late to fix it. This SOP structures the production window: from confirming the scope through drafting, reviewing, and preparing for client presentation, so nothing goes out the door without a quality pass.

Prerequisites

• The deliverable's scope confirmed against the SOW — know exactly what "done" means before you start producing
• All client inputs required to build the deliverable collected and accessible (data, decisions, approvals from prior sessions)
• At least 2 hours of focused production time blocked before the due date — not the morning it's due

Procedure

1. Open the client's SOW and locate the deliverable definition. Confirm the exact format, scope, and success criteria. If the original SOW language is vague, check your session notes for any clarifications the client gave.
2. Run the Deliverable Draft Builder skill with the deliverable type, client context, engagement phase, and any relevant prior session outputs as input. Review the draft output in full before editing.
3. Edit the draft against the SOW scope. Every section should map to something the client agreed to. Remove anything that exceeds scope — scope creep in deliverables trains clients to expect more than they're paying for.
4. Run a self-review pass: Does this deliverable answer the client's stated problem? Is every recommendation actionable with their current resources? If no to either, revise before moving on.
5. Run the Client Presentation Prep skill with the finalized deliverable as input. Output: a presentation structure, the two or three key messages to anchor on, and anticipated client questions with your prepared responses.
6. Send the deliverable to the client at least 24 hours before the review session, with a one-sentence framing of what you want them to come prepared to discuss. If the review is the same day as delivery, you've started this SOP too late.

Expected Outcome

You'll have a finalized deliverable scoped exactly to the SOW, a presentation structure for the review session, and a list of anticipated client questions with prepared responses. The client receives the deliverable at least 24 hours before review.

<aside> ⚠️ Common mistakes:

— Building the deliverable from memory instead of the SOW — what you remember the client wanting and what they actually agreed to pay for diverge over a long engagement. The SOW is the reference. Use it every time.

— Skipping the presentation prep step to save time — the deliverable is half the job. How you present it determines whether the client acts on it or shelves it. Showing up without a framing narrative turns a solid deliverable into a confused conversation.

</aside>

<aside> 📋 Frequency: Trigger-Based | Time: 60 min | Trigger: When a deliverable is due within 5 business days

</aside>

Deliverables produced without a process get delivered late, half-finished, or misaligned to what the client actually needs — and you discover that misalignment on the call when it's too late to fix it. This SOP structures the production window: from confirming the scope through drafting, reviewing, and preparing for client presentation, so nothing goes out the door without a quality pass.

Prerequisites

• The deliverable's scope confirmed against the SOW — know exactly what "done" means before you start producing