GRACE · Module 12 · Quick Reference · Closeout and Debriefing

Module Home › Quick Reference

What you need to know

If Admin archived this project today, would the firm have the complete record?

You own closeout. Admin, Accounting and the Storyteller perform steps. You confirm that each one is complete.

The debrief produces an action with an owner and a date. Following through on that action is what makes the lesson useful.

The five areas. Contract, money and client run at the same time. The final debrief needs their results. The record closes last.

What to do

Seven actions, from the punchlist walk to the archive request.

Submit the Substantial Completion request in Milo when the punchlist walk supports it, so Admin can issue the G704.
Check the delivered work against the agreed scope, including the approved changes in your change log, and resolve any open item.
Issue the final invoice, bring unbilled to zero, and record the final cost against the plan. Follow the last receivable with the AR Guide.
Ask the client for feedback, record the response, and thank them by phone or in person.
Hold a short debrief at the end of each phase and the full debrief at closeout, before the team disperses, with the records in the room.
End every debrief with at least one action, an owner and a date. Open the next debrief with those actions.
Run the readiness check across all five areas before you ask Admin for the archive zip.

What to watch out for

Seven warning signs. Each one means a closeout step has no owner.

A team that has moved to the next project while closeout items are still open and nobody owns them.
Project email still in personal inboxes after the punchlist is complete.
A debrief with no records in the room.
One difficult moment that dominates the discussion.
A lesson that is written down and changes nothing.
“We communicated well,” said with nothing specific behind it.
A final invoice that leaves hours unbilled.

What to avoid

Seven habits that seem efficient and leave closeout open.

Requesting the archive zip before the checklist is complete. Nothing can be added after it.
Waiting for the last receivable to be paid before you hold the debrief. The team disperses.
Debriefing from memory.
Assigning blame in the debrief. People stop explaining what happened.
Offering your own view of a cause before others have spoken.
Closing the project without asking the client for feedback.
Leaving the debrief action in the notes and out of the A3.

The five areas

Who performs each part, what you confirm, and the question you answer yes to before the archive request.

Area	Who performs	You confirm	Yes when
Contract	PM, Admin, project team, contractor	Punchlist closed, G704 issued, closeout submittals and record drawings in, final pay application certified, closeout documents sent, work checked against the agreed scope.	The contract steps are complete and the delivered work matches the agreed scope.
Money	PM, Accounting	Final invoice sent, unbilled at $0, final cost recorded against the plan, last receivable followed with the AR Guide.	The final invoice is sent, unbilled is zero, and Accounting has confirmed the receivable status.
Client	PM, PIC	Feedback requested, response recorded, client thanked by phone or in person.	The client was asked for feedback and thanked, with any response recorded.
Lesson	PM leads, project team attends	Project debrief held before the team disperses. Last debrief’s actions checked.	The debrief action has an owner and a date.
Record	Every team member, Storyteller, Admin	Email in Centerline, Bluebeam sessions archived, A3 final with the debrief action and checked by you.	The email, Bluebeam sessions and A3 are complete. Then ask for the zip.

Contract, money and client run together, from the punchlist walk.
The final debrief needs the results in hand: final invoice sent, unbilled at $0, final cost recorded, and any client feedback. An open receivable does not hold it up.
The archive zip is last. The Storyteller writes the debrief action into the A3 before it.

The five questions

Bring the records: success statement, plan, final numbers, change log, QC Forms and client feedback. Open with the actions from the last debrief.

Question	Why it exists	The conversation it should produce
1 · What were we trying to do?	A result only means something against a target.	Read the success statement and the plan. Agree on the target before you judge the result.
2 · What happened?	Memory keeps the loudest moments.	Walk the records in order: dates, costs, decisions, changes. Facts before causes. Write down differences the records don’t settle.
3 · What went well, and why?	The team can repeat what it understands.	Name the practice. “We communicated well” gets the follow up question: what did you actually do?
4 · What went wrong, and why?	It looks for causes the team can act on.	Steps, tools, decisions, time, people, skills. Other views first. What people did and the conditions they faced.
5 · What will we do next time?	It turns the discussion into action.	At least one action, an owner and a date. Correct a problem or repeat what worked.

Personal action: into your next plan. Team action: to the person responsible. Firm standard: to the person who owns it.

Phase debrief and project debrief

	Phase debrief	Project debrief
When	End of each phase	Closeout, before the team disperses
Time	About 20 minutes	About an hour
Records	Phase plan, phase numbers from BST, change log, QC Form for the phase	Success statement, plan, final numbers, change log, QC Forms, client feedback
Output	One action for the next phase, and the last debrief’s actions checked	At least one action, routed by level, each with an owner, a date and a check
Form	Phase Debrief form, 1 page	Project Debrief form, 2 pages

When to escalate

A receivable past 90 days brings in the Practice Leader. Past 120 days, Executive Leadership reviews it. Follow the Module 3 AR Guide.

Before the archive

Resolve outstanding checklist requirements before asking Admin to create the archive zip.