Consulting Project Closeout Template
Four documents and three sheets that request acceptance against the SOW's own criteria and gate the final invoice on it.
Free download · No account needed
Deliverable Acceptance Tracker · Ashcombe Consulting · Delray Point Utilities billing operations redesign · 29 Sep 2026
The fourth deliverable got no reply at all. SOW 7.3 already says what that means.
| Deliverable | SOW 4.1 | Window Closes | Outcome |
|---|---|---|---|
| Current State Diagnostic | (a) | 17 Aug | Accepted 6 Aug |
| Target Operating Model | (b) | 31 Aug | Accepted 20 Aug |
| Implementation Roadmap | (c) | 14 Sep | Cond. accepted, cured 11 Sep |
| Training and Enablement Guide | (d) | 28 Sep | Deemed accepted 28 Sep |
| Final Findings Presentation | (e) | 5 Oct | Accepted 23 Sep |
Nobody at the client ever replied to the fourth deliverable. SOW Section 7.3 already states what a closed window with no response means, so it never sits as an open question.
That one dated line releases the last $5,250 of the holdback without either side arguing over whether it was "really" accepted.
Search consulting project closeout template and the shape is consistent. Get a written sign-off confirming the client accepts every deliverable against the statement of work, reconcile the budget and settle outstanding invoices, run a structured lessons-learned session, and archive the files. Every serious guide in the category covers all four, and a signature line sits on the acceptance form itself. None of them name the ordinary way that signature never actually arrives.
This pack's Acceptance Request quotes the SOW's own deliverable clause and its review-window clause in the same letter. That dates the response clock from a specific written request, not a delivery date nobody logged. FAR 46.101 defines acceptance and conditional acceptance in the same terms most commercial SOWs borrow. When the window closes with no reply, the tracker marks that row deemed accepted on the closing date, not left open. The final invoice reconciles only once every row reads one of those four outcomes.
Ashcombe Consulting's operations redesign for Delray Point Utilities carries five deliverables and a $26,250 holdback released in five $5,250 shares. Four clear by written response inside their review windows. The fifth, a training and enablement guide, draws no reply at all, and its window closes 28 September, the date SOW 7.3 deems it accepted. The Follow-on Proposal for the integration gap that redesign surfaced goes out the same week, dated from the last acceptance request rather than from when that final invoice actually clears 30 days later.
What's in the pack
Acceptance Request
Quotes the SOW's own deliverable clause and review-window clause in the same letter, dating the response clock from a specific written request rather than a verbal delivery nobody logged.
Deliverable Acceptance Tracker
Every deliverable against its own SOW clause, the date acceptance was requested, and the date deemed acceptance takes effect if the client never replies.
Final Invoice Note
Reconciles the holdback share by share against the tracker, on top of the progress billing the workplan already invoiced during delivery, naming any share released by deemed acceptance rather than a reply.
Outstanding Item Register
Everything still open that isn't a deliverable, aged in days with a named owner and a dollar value, for whatever the standing escalation path hasn't already resolved by closeout.
Data Destruction Confirmation
Every category of client data or system access the engagement touched, returned or destroyed by a named method and confirmed by a named person. NIST's own sanitization guidance ties the method to the data's sensitivity, not a status of 'deleted.'
Follow-on Proposal
Dated from the last acceptance request, not from whenever the final invoice happens to clear, so the finding behind it is still fresh with the same team.
Closeout Report
The one document reconciling acceptance, the invoice, outstanding items and data return, the same week the client's own capability assessment closes out separately.
How it works
- 1
Open in River, or take it blank
Edit with AI installs the pack as a private Space and starts the tracker. Download gives you the Word documents and CSV sheets free, no account.
- 2
Send the signed SOW and what's shipped
The section naming every deliverable's acceptance criterion, the section covering the review window, and which deliverables already went out, ideally after a deliverable review caught what needed catching first.
- 3
Request acceptance, then let the clock run
Every request quotes the SOW's own clause. A window that closes with no reply gets marked deemed accepted on that date instead of left open indefinitely.
- 4
Reconcile, return, and propose what's next
The final invoice bills against accepted and deemed-accepted rows, client data gets returned or destroyed by a named method, and the follow-on proposal goes out dated from the last request, not from whenever payment clears.
Frequently asked questions
Is this project closeout template free?
Yes. Download gives the whole pack with no account and no email: four Word documents and three CSV sheets, opening natively in Word, Pages, Google Docs, Excel, Numbers and Sheets, with a PDF option on the documents via ?format=pdf. Edit with AI creates a free account and installs the same pack as a private Space, filled in from your SOW and delivery record.
What format are the downloaded files?
The four documents (Acceptance Request, Final Invoice Note, Follow-on Proposal and Closeout Report) download as Word .docx files, and the three sheets as CSV, all zipped together. Everything opens natively in Word, Pages, Google Docs, Excel, Numbers and Sheets, with a PDF option via ?format=pdf.
How is this different from a standard project closeout checklist?
Most closeout checklists ask for a signed acceptance and a lessons-learned session, then trust the signature actually arrives. This pack's Acceptance Request quotes the SOW's own clause and starts a dated review window. A client who never replies doesn't leave the deliverable in limbo, because a SOW 7.3-style clause deems it accepted once that window closes.
What happens if the client never responds to a formal acceptance request?
Nothing waits on a reply that may never come. The Acceptance Request states the SOW's review-window clause and the date it closes, so once that date passes with no written response, the tracker marks the deliverable deemed accepted and the invoice bills its holdback share. On the worked example, that dated line releases $5,250 that a silent inbox would otherwise have held open indefinitely.
How is this different from the engagement retrospective template?
That pack prices the next proposal off what this one actually took, task type by task type, and the two commonly run back to back. This one comes first: acceptance, the final invoice and data return all have to close before there's a clean estimate-versus-actual number to retrospect on, since a deliverable still under dispute has no final effort figure yet.
Why does the follow-on proposal go out before the final invoice is even paid?
Because the finding it's built on has a shelf life the payment clock doesn't respect. This pack dates the Follow-on Proposal from the last acceptance request, not from when payment clears under net-30 terms, a gap of a month on the worked example. The team that lived with the gap is still assembled on the earlier date, and likely reassigned by the later one.
Close it on the SOW's own clock, not on hope
Take the Word documents and CSV sheets blank, or send River the signed SOW and get the acceptance clock running today.
Edit with AI