Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
Safe AI Client Message Review Checklist
A checklist for reviewing AI-written client messages against real project context before sending.
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.
ai client work
Safe AI Client Message Review Checklist
# Safe AI client message review
Draft purpose: [approval / scope / invoice / payment / follow-up]
Before sending, confirm:
- The client name and project are correct
- The message does not invent approval
- Scope claims match the agreement
- Delivery claims match source records
- Invoice status and due date are correct
- Open issues are not ignored
- Tone fits the relationship
Missing context:
- [record needed]
Decision:
- Send as-is
- Edit first
- Do not send yetBefore 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 Safe AI Client Message Review Checklist?
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.