Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
A short approval request you can send when a client has reviewed work but the approval signal is still informal.
Use it when
These templates are deliberately plain. The value comes from pairing the message with the source records that support it.
Subject: Approval confirmation for [deliverable]
Hi [Client name],
Thanks for reviewing [deliverable].
Before I move to [next step], can you confirm that [specific deliverable / direction] is approved?
For clarity, I have the approved item as:
- Deliverable: [deliverable]
- Version/date: [version or date]
- Next step after approval: [next action]
Please reply with "approved" or any final notes I should address first.
Thanks,
[Your name]
Before sending
Which proposal, contract, message, invoice, or delivery record supports this action?
Is the project confirmed, unclear, overdue, or blocked by a missing record?
Does the message fit the client relationship and the current state of the work?
Related
Independent professionals and small teams who need a calm, source-aware starting point before sending a client message.
Use it as a structure, then adjust the facts, tone, and relationship context before sending.
Check the relevant approval, scope, delivery, invoice, or payment record before using the template.
Early access
Early access helps us test these workflows against actual project records.