Source
Which proposal, contract, message, invoice, or delivery record supports this action?
Template
A short readiness report for checking delivery, approval, open issues, and payment terms before sending the final invoice.
Use it when
These templates are deliberately plain. The value comes from pairing the message with the source records that support it.
# Invoice readiness report
Project: [project name]
Invoice: [invoice number]
Delivery:
- Deliverables sent: [yes/no]
- Source record: [file/message/date]
Approval:
- Approval found: [yes/no/partial]
- Source record: [file/message/date]
Open issues:
- Scope change unresolved: [yes/no]
- Delivery concern unresolved: [yes/no]
Payment terms:
- Invoice trigger: [delivery/approval/date]
- Due date: [date]
Decision:
- Ready to invoice: [yes/no/confirm first]
- Confirmation message needed: [message]
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.