Back to SOZ
Example only · no client data.
Sample handoff record
A client asks for more work.
See who checks the request, who decides, and where the next step is written.
Check availability
Signed scope
Named owner
Approval point
Recorded next action
One request
A client asks for another pricing page.
The agreed work is one responsive landing page. No one promises the extra page until the delivery lead approves it.
- 01 Receive Acknowledge the request.
- 02 Check scope Check the agreed page.
- 03 Record the change Write down the change.
- 04 Get approval Send it for approval.
Scope change
The extra work waits for approval.
Signed scope
One responsive landing page
New request
Add a second pricing-page version
Status
Needs approval
Request
Reply without promising extra work.
The operator can acknowledge the request and check the agreed work. Because the request adds a page, they stop there until approval.
Next reply
“Received. I’m checking this against the signed scope before confirming the next step.”
Decision record
The next decision is written down.
- Context
- After sign-off on one responsive landing page.
- Request
- Add a second pricing-page version.
- What was agreed
- Signed deliverables · one responsive landing page.
- Who records it
- The delivery lead records the request.
- Approval
- The delivery lead approves before anyone promises the extra page.
- Status
- Needs approval
- Next action
- Acknowledge the request and compare it with the signed scope.
- Stop when
- The request changes the agreed deliverable.
- Record in
- Project record → Scope changes.
Operator test
Can someone else use the record?
Four checks show whether the team can use the record without the founder.
- 01Find the signed scope.
- 02Restate the new request.
- 03Name the approval point.
- 04Record the next action.