Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
Case Retrospective and Playbook Candidate
A reusable retrospective format for turning a completed client project into a future workflow pattern.
Use it when
Start from a clear structure, then check the facts.
These templates are deliberately plain. The value comes from pairing the message with the source records that support it.
playbooks
Case Retrospective and Playbook Candidate
# Case retrospective and playbook candidate
Project: [project name]
Client type: [type]
Outcome: [result]
Important records:
- Agreement:
- Approval:
- Scope change:
- Delivery:
- Invoice/payment:
What worked:
- [pattern]
What should not be reused:
- [condition]
Reusable playbook:
- Trigger:
- Required evidence:
- Suggested action:
- Blocking conditions:Before sending
Review the evidence first.
Status
Is the project confirmed, unclear, overdue, or blocked by a missing record?
Tone
Does the message fit the client relationship and the current state of the work?
Related
Continue with the matching workflow.
FAQ
Who should use Case Retrospective and Playbook Candidate?
Independent professionals and small teams who need a calm, source-aware starting point before sending a client message.
Should I copy it exactly?
Use it as a structure, then adjust the facts, tone, and relationship context before sending.
What should I check first?
Check the relevant approval, scope, delivery, invoice, or payment record before using the template.
Early access
Bring this template into real client work.
Early access helps us test these workflows against actual project records.