How to check a document before sending it to a client
Client-facing QA: scope alignment, numbers, attachments, obligations, and tone risks—then reconcile a Proof Report as a team before delivery. Not a substitute for relationship judgment or privileged review.
Last updated 2026-05-14
Pre-send
Read it like an outsider would
Client delivery is a trust event—reconcile issues as a team before the file leaves.
Scope match
Deliverables and assumptions align with the engagement story.Numbers
Pricing tables match narrative obligations.Attachments
Referenced files exist and are current.
Checklist
Pre-client send checklist
- Scope, deliverables, timelines, and assumptions match the engagement narrative.
- Pricing tables, discounts, and totals match the body text and any SOW references.
- Attachments referenced actually exist and are the latest versions.
- Names, logos, and customer examples are permitted for external use.
- Risk language is intentional (no accidental guarantees).
How Recensa helps
Confidence before send
Use a Document Check to generate an issue ledger and Proof Report, and attach supporting files when the client packet should align to a prior statement of work or policy excerpt. You still own relationship risk and final wording.
Related