Project Delivery
Purpose
This SOP defines the engagement lifecycle, milestones, check-ins, handover, and scope change process. It ensures predictable delivery and clear governance when scope or timeline shifts.
Scope
| Context |
Applies to |
| All engagements |
Growth system, funnel, web, automation, analytics, social |
Definitions
| Term |
Definition |
| Milestone |
A named deliverable or checkpoint with date |
| Check-in |
Regular status meeting (weekly, bi-weekly) |
| Change request |
Formal request to add or remove scope |
| Handover |
Transition of deliverables to client or next phase |
Engagement Lifecycle
Intake → Kickoff → Discovery → Execute → Check-ins → Milestones → Handover → Close
| Phase |
Purpose |
| Intake |
Contract, access, kickoff prep |
| Kickoff |
Align scope, roles, process |
| Discovery |
Map current state; agree priorities |
| Execute |
Deliver per SOW |
| Check-ins |
Status, blockers, next steps |
| Milestones |
Formal deliverables; sign-off |
| Handover |
Transfer knowledge, assets |
| Close |
Offboard; retrospective |
Milestones
| Element |
Action |
| Define |
Per SOW; clear deliverable, date |
| Track |
In shared doc or project tool |
| Sign-off |
Client approves before next phase |
| Change |
Via change request only |
Check-ins
| Cadence |
Purpose |
| Weekly |
Status, blockers, next week |
| Bi-weekly |
For longer engagements |
| Ad-hoc |
When blocking issue arises |
| Format |
Agenda |
| 15–30 min |
What’s done; what’s next; blockers |
Scope Change
Change request process
- Request — Client or Project Lead identifies need for scope change.
- Assess — Impact on timeline, cost, resources.
- Propose — Revised SOW or addendum; pricing if applicable.
- Decide — Client approves; document.
- Execute — Update plan; communicate.
Decision rights
| Change type |
Owner |
| Minor (e.g. extra round of revisions) |
Project Lead + Client |
| Major (new deliverable, timeline shift) |
Client Lead + Client |
| Contract change |
Per Frameworks & Principles escalation |
Handover
| Step |
Action |
| 1 |
Compile deliverables; assets; access |
| 2 |
Walkthrough with client |
| 3 |
Document runbooks or how-tos |
| 4 |
Transfer access; revoke ours |
| 5 |
Close shared spaces; archive |
Roles & Responsibilities (RACI)
| Deliverable |
Project Lead |
Client Lead |
Client |
| Drive execution |
R |
A |
I |
| Check-ins |
R |
I |
R |
| Milestone sign-off |
R |
A |
A |
| Change request |
R |
A |
A |
| Handover |
R |
A |
I |
Escalation
| Trigger |
Action |
| Missed milestone |
Document cause; propose recovery; escalate if client impact |
| Scope creep (informal) |
Redirect to change request |
| Blocker from client |
Escalate per Frameworks & Principles |
Version & Approval
| Field |
Value |
| Last updated |
February 2025 |
| Approver |
— |