Fulfillment Handoff SOP Template
Fortunes Fortuna

Purpose
Use this SOP when accepted or paid work needs to move into delivery with a clear owner, required inputs, evidence links, completion checks, and post-delivery follow-up.

Start Conditions
1. Accepted scope is recorded and approved by the owner.
2. Payment, deposit, or owner-approved start condition is clear.
3. Delivery owner, due date, and customer contact are assigned.
4. Required customer inputs and access boundaries are written before work starts.

Required Fields
- Accepted scope
- Delivery owner
- Due date
- Customer contact
- Required customer inputs
- Access notes and access removal date
- Delivery checklist
- Delivery status
- Evidence links
- Handoff notes
- Completion date
- Customer confirmation
- Post-delivery follow-up date
- Close reason when cancelled, replaced, or no longer active

Suggested Statuses
- Ready for handoff: scope and start condition are accepted, but delivery has not started.
- Waiting on input: delivery depends on customer files, answers, access, or owner approval.
- In delivery: delivery owner is actively completing the approved checklist.
- Review needed: work is ready for owner or customer review before final handoff.
- Delivered: handoff notes, evidence links, and completion confirmation are recorded.
- Closed: delivery is accepted, cancelled, replaced, or no longer active.

Access Rules
- Request the minimum customer access needed for the approved scope.
- Use owner-approved accounts and sharing methods only.
- Do not ask for passwords, wallet seeds, private keys, exchange credentials, or unrelated customer secrets.
- Record what access is needed, who owns it, and when it should be removed.

Completion Proof
Record:
1. delivered file links,
2. customer-visible outputs,
3. screenshots or notes that do not expose secrets,
4. owner handoff notes,
5. customer confirmation or review status,
6. next review or follow-up date.

Boundary
- This SOP tracks delivery; it does not grant access or start work.
- Do not start work outside accepted scope.
- Do not store passwords, private keys, seed phrases, wallet files, exchange credentials, or customer secrets.
- Do not handle funds or customer wallets.
- Remove or hand back access when delivery no longer needs it.

Related resources:
- https://fortunesfortuna.com/resources/fulfillment-handoff-checklist.csv
- https://fortunesfortuna.com/resources/invoice-payment-sop.html
- https://fortunesfortuna.com/services/revenue-workflow-build.html