Make the delivery easy to identify
Start with the client, project, delivery title and version. Use a name both teams recognize. A delivery record should make it obvious which milestone is being reviewed, even when someone opens it weeks later.
- Client and project name
- A specific delivery title
- Version number and a short delivery summary
Put the work and its scope together
Collect the review links in one place. Describe what each link contains and make sure the client can access it. Record agreed additions or reductions alongside the original scope, so the delivery amount has a clear explanation.
- Described links to the review build or documents
- Agreed scope changes and their amounts
- Currency and the total value of this delivery
Choose the person who can give a decision
Send the review to a named person who can approve the work or explain the changes needed. Make the decision request specific to the version you sent. In Handoff, the reviewer verifies the invited mailbox before accessing the pack.
- A named reviewer and their correct email
- A clear request to approve or request changes
- A decision recorded against the exact delivery version
Make a change request actionable
A useful change request explains what needs attention. Keep that feedback with the delivery record. When the work changes, publish a revision and ask for a fresh decision rather than carrying an old approval forward.
- A written explanation of requested changes
- A new published version when the delivery changes
- Fresh client review for the current version
Collect the details needed for invoicing
Approval can be one part of readiness. Your team may still need a billing contact, delivery confirmation or a purchase-order reference. Set the requirements for the delivery, then check the missing items before telling the team it is ready.
- The billing contact for this client
- Confirmation that delivery is complete
- A purchase-order reference when this delivery requires one
Keep a record of the finish
Preserve the agreed version, the client’s decision and the billing-readiness record. Handoff can export a frozen PDF receipt with its exact source attached as JSON. Use that record alongside your invoicing tools; readiness is not a tax invoice or evidence of payment.
- Published version and decision history
- An observed readiness record
- The receipt and a next action for your invoicing workflow
Turn the checklist into a shared workflow.
Try publishing a delivery, inviting a reviewer and collecting billing details in Handoff.
Create your workspace