GRACE · Module 12 · Closeout and Debriefing

Module Home › Module Overview

1The problem

The project that was never closed

You’re the Project Manager. The client has moved in, and the last punchlist item is complete. Half your team started on a new project on Monday. The rest start next week.

It’s easy to feel that this project is finished.

Before you move on, ask one question. If Admin archived this project today, would the firm have the complete record? Would anyone know what the team learned, or what to do differently next time?

Keep your answer. Section 5 returns to it.

Closeout has two jobs. The first is to meet the remaining obligations to the contract, the money and the client. The second is to make the experience useful to the next project. Module 12 teaches both. You close the project across five areas. You lead a short debrief at the end of each phase and a full debrief at closeout.

Closeout uses records you already keep. The debrief reads the success statement from Module 7, the final numbers from Module 9, the change log from Module 10, and the QC Forms from Module 11.

Recall, before you go on

From memory. Which record from kickoff states what the project must achieve? Which records show what happened after that?

The success statement, written at kickoff in Module 7. After that, the plan from Module 5, the final numbers from the Module 9 monthly review, the change log from Module 10, and the QC Forms from Module 11. In Module 11, the Storyteller completes the A3 at closeout and you review it. Module 12 puts the debrief action into that A3.

By the end of Module 12, you’ll be able to:

✓Check a project against the five areas, name every item still open, and leave the archive request until the checklist is complete.
✓State who performs each closeout step and what the Project Manager confirms.
✓Lead a debrief with the five questions, at a phase end and at closeout, against the project records.
✓End a debrief with an action, an owner and a date, send it to the right person, and check at the next review that it happened.

2The gap

Nobody owns the last steps

Some closeout steps move because someone outside the team needs them. The contractor wants Substantial Completion, so the punchlist walk happens. The owner wants to move in, so the G704 gets issued.

Nobody outside the team asks for the project record, the client’s feedback or the lesson. Those steps wait until someone owns them.

Your own cohort found this at Onsite 1. Twenty groups sorted 44 Project Manager responsibilities by the size of the gap and the cost when the step is missed. Here are the 9 closeout responsibilities, with the firm rank out of 44.

Card	Responsibility	Firm rank	Groups that flagged it, of 20
41	Complete lessons learned and transfer knowledge to the team	4	19
38	Obtain final client feedback, measured as relationship health	9	15
45	Archive project records and store project emails in Centerline	23	19
43	Finalize the Project A3 and conduct the post occupancy or project review	25	18
46	Request the Centerline archive zip and validate deliverables against the original scope	29	20
44	Complete financial closeout and resolve AR	33	9
40	Identify future opportunities and cultivate the repeat client	36	2
39	Create and complete the punchlist, manage Substantial Completion, warranties, final payment	40	3
42	Review closeout submittals, O&M manuals, warranties, record drawings, and start the G704	43	1

Two results stand out. Lessons learned is the 4th largest gap in the firm. Every group flagged the archive request. The steps the contractor and the owner push, the punchlist and the closeout submittals, rank 40 and 43. The gaps are in the steps that nobody outside the team pushes.

Eight ways closeout breaks

Each one is ordinary, and each one has a cause you can fix.

The team moves on. The team starts the next project, and people assume someone else is handling the remaining work.
Archiving early. The archive zip goes in while project email is still in personal inboxes. After the zip, nobody can add to the project in Centerline.
Debriefing from memory. Nobody brings the records. One difficult moment dominates the discussion.
Writing the lesson down and changing nothing. Everyone agrees on a lesson, records it, and returns to work the same way.
Leaving the money open. Hours stay unbilled after the last invoice, and nobody compares the final cost to the plan.
Closing without the client. Nobody asks for feedback or thanks the client, and the relationship stops with the last invoice.
The blame review. The debrief looks for who made the mistake. People stop explaining what happened.
Waiting too long. The debrief happens weeks after the team disperses, and only memory is left.

Who owns closeout

As Project Manager, you own closeout, with support from other parties. Admin helps issue closeout documents and archives files. Accounting follows receivables. The Storyteller finalizes the A3. Your responsibility is to confirm that each part is complete.

Closing the project deserves the same deliberate attention you give to starting it.

3The frame

Contract, money, client, lesson, record

Think about closeout as covering five areas: the contract, the money, the client, the lesson, and the record.

The five areas. The same five areas run through the checklist, the readiness check and the Quick Reference.

Much of this work can happen at the same time. Three rules set the order.

The contract, the money and the client run together. Start each one when the punchlist walk supports it.
The final debrief needs the results in hand. That means the final invoice sent, unbilled at $0, the final cost recorded against the plan, and any client feedback. An open receivable does not hold up the debrief. Accounting keeps following it under the AR Guide.
The archive zip is last. Nothing can be added after it. The Storyteller writes the debrief action into the A3 before you ask for the zip.

Area	What complete means	Who performs	You confirm
Contract	Punchlist closed. G704 issued. Closeout submittals and record drawings in. Final pay application certified. Closeout documents sent. Delivered work checked against the agreed scope.	PM, Admin, project team, contractor	Each step is done, and no scope item is open.
Money	Final invoice sent. Unbilled at $0. Final cost recorded against the plan. Last receivable followed.	PM, Accounting	Unbilled is $0, and Accounting has confirmed the receivable status.
Client	Feedback requested, any response recorded, client thanked in person or by phone.	PM, PIC	The conversation happened, and the response is recorded.
Lesson	Project debrief held before the team disperses.	PM leads, project team attends	At least one action with an owner and a date, sent to the person who can act on it.
Record	Project email in Centerline. Bluebeam sessions archived. A3 final with the debrief action. Then the archive zip.	Every team member, Storyteller, Admin	Nothing is left to add before the zip.

The Grace Closeout Checklist lists all 17 steps, who performs each one, what you confirm, and the source of each step.

Contract, money and client

The contract. The AIA Form G704 establishes the date of Substantial Completion. Other contract dates depend on it. Submit the request in Milo when the punchlist walk supports it, so Admin can issue the G704. Then check the delivered work against the agreed scope, including the approved changes in your Module 10 change log, and resolve any open item.

The money. Issue the final invoice, bring unbilled to zero, and record the final cost against the plan. The debrief reads those final numbers. Keep following the last receivable with the AR Guide from Module 3.

The client. Speak with the client while the experience is fresh. Ask for feedback, record the response, and thank them personally, by phone or in person. The conversation tells you how the client experienced the project, and it keeps the relationship open after this project ends.

The readiness check

The record closes last. Each team member moves project email into Centerline. The team archives its Bluebeam sessions. The Storyteller puts the debrief action in the A3, and you check the A3 for accuracy. Then confirm readiness across all five areas.

The readiness check. The same five questions close the Grace Closeout Checklist.

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

4The method

Five questions, against the records

The debrief should produce specific actions, with owners and dates. Following through on those actions is what makes the lesson useful.

Hold a short debrief, about 20 minutes, at the end of each phase. You can apply what you learn while the project is still underway. At closeout, allow about an hour for the full review, before the team disperses.

When the team debriefs. A phase debrief at each phase end, and the project debrief at closeout. Use the Phase Debrief form and the Project Debrief form.

Bring the records

A debrief from memory gives the loudest memory the most weight. Bring these 6 records into the room.

Success statement · Plan · Final numbers · Change log · QC Forms · Client feedback

At a phase debrief, bring the phase versions: the phase plan, the phase numbers from BST, the change log, and the QC Form for the phase.

Begin with the actions from the last debrief. Ask the owner of each action to show what changed in the work. Then lead the team through the five questions.

The five questions

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. Establish the target before judging the result. If people worked toward different targets, record that. It is the first finding.
2. What happened?	Memory keeps the loudest and most recent moments.	Walk through the records in order: dates, costs, decisions and changes. Establish the facts before you discuss causes. Where the records don’t settle a difference, write the difference down.
3. What went well, and why?	When the team knows why something worked, it can repeat it on purpose.	Name the practice behind the result. If someone says, “We communicated well,” ask what they actually did. Perhaps a decision was documented and sent to the client the same day. The next team can use that.
4. What went wrong, and why?	It looks for causes the team can act on.	Examine the steps, tools and decisions, and the time, people and skills available. Keep asking what contributed until the team knows what it could change. Invite other views before you give your own. Talk about what people did and the conditions they faced.
5. What will we do next time?	It turns the discussion into action.	Choose at least one action. It can correct a problem or repeat something that worked. Name the owner and set a date.

Question 4 has one rule, and the reason for it matters. When people expect blame, they’re less likely to explain what happened, and the review becomes less useful.

Where the action goes

A personal actionPut it into your next plan.

A team actionAssign it to the person responsible.

A firm standardSend it to the person who owns that standard.

Record and share the final debrief’s lessons so they inform the next project’s approach. At the next debrief, each owner shows what changed in the work.

Why the time is worth it

Research supports making time for this. A review of 46 samples found that people who debriefed performed about 20 to 25 percent better than comparison groups, on average across the studies. That is why the team debriefs at every phase end and at closeout.

A second review, of 61 studies, found the strongest effects when teams reviewed their own work against objective records. That is why your team runs its own debrief, led by you, with the records in the room.

A field study found that soldiers who debriefed on successes and failures improved more than soldiers who debriefed on failures only. That is why question 3 gets the same time as question 4.

Oakhaven at closeout

Oakhaven is 30 days past Substantial Completion, and the client has moved in. The plan set profit at 19.3 percent. The final numbers show 16.0 percent. That is above the 15 percent floor and below the plan. Most of the difference came from the Design Development overrun you saw in Module 9, when senior staff spent extra hours on the estimate reconciliation. The rest came from the volume of RFIs during construction.

The Project Manager runs the checklist. Here is what it shows.

On the checklist	Status
Contract
Punchlist: 43 items at the walk	3 items open
AIA G704	Issued 30 days ago
Closeout submittals	All in except the roofing warranty
Record drawings	Complete
Money
Last invoice	41 days old, unpaid
Unbilled	$8,400 of CA hours
Final numbers	Recorded, 16.0 percent against 19.3 planned
Client
Final client feedback	Not requested
Lesson
Project Debrief	Not held. Half the team starts another project next week.
Record
Project email	2 months of DD email in one team member’s inbox
Bluebeam sessions	Archived
Project A3	Storyteller draft, PM check pending

Practice

What is still open?

Take the five areas one at a time. Pick the answer that a Project Manager who owns closeout would give.

Area 1 of 5 · Contract
3 of 43 punchlist items are open. The G704 was issued 30 days ago. Every closeout submittal is in except the roofing warranty. The record drawings are complete. Is the contract area complete?

Contract, 2 items openNo. Track the 3 punchlist items to complete in Centerline, and follow the roofing warranty until it is received and reviewed. The G704 sets the date of Substantial Completion. The punchlist and the closeout submittals still have to close.

Look againThe G704 sets the date of Substantial Completion, and other contract dates count from it. It does not close the punchlist or the closeout submittals.

Look againThe contractor performs the punchlist work. You confirm that every item is closed. Until then, the item stays on your checklist.
Area 2 of 5 · Money
The last invoice is 41 days old and unpaid. $8,400 of CA hours are unbilled. The final numbers are recorded, 16.0 percent against 19.3 planned. What is the next step?

Money, 2 items openSend the final invoice with the $8,400 so unbilled returns to $0. Keep following the 41 day invoice with the AR Guide. Once the final invoice goes out, the debrief has the results it needs.

Look againAn open receivable does not hold up the debrief or the rest of closeout. Accounting keeps following it under the AR Guide.

Look again$8,400 is still unbilled. The final invoice goes out with it, and unbilled returns to $0.
Area 3 of 5 · Client
Nobody has asked the client for feedback. The client moved in a month ago and has not raised a concern. What do you do?

Client, 1 item openCall the client this week. Ask for feedback, record the response, and thank them personally. Speak with the client while the experience is fresh.

Look againSilence tells you nothing about how the client experienced the project. Ask, record the response, and thank them by phone or in person.

Look againThe invoice follows the AR Guide on its own track. The feedback is most useful while the experience is fresh.
Area 4 of 5 · Lesson
The Project Debrief has not been held. Half the team starts another project next week. When do you hold it?

Lesson, 1 item openSend the final invoice first, then hold the debrief this week, while the team is still together, with the records in the room. The debrief needs the results in hand and the team in the room. This week has both.

Look againThe numbers the debrief needs are in hand once the final invoice goes out. If you wait for payment, the team disperses and the debrief runs on memory.

Look againLessons by email skip the conversation. Nobody compares views against the records, and nobody leaves with an action, an owner and a date.
Area 5 of 5 · Record
Two months of DD email are in one team member’s inbox. The Bluebeam sessions are archived. The A3 is a Storyteller draft you have not checked. Admin asks whether to create the archive zip. What do you say?

Record, 2 items openNot yet. The email goes into Centerline. After the debrief, the Storyteller adds the debrief action to the A3 and I check it. Then I ask for the zip. The archive zip is last.

Look againAfter the zip, the project is no longer accessible in Centerline. Nothing can be added afterward.

Look againThe A3 is final when it carries the debrief action and you have checked it for accuracy. Both happen before the zip.

Oakhaven, 8 items open across the five areas

Contract, 2: the 3 punchlist items and the roofing warranty.
Money, 2: the $8,400 unbilled and the 41 day invoice.
Client, 1: feedback not requested.
Lesson, 1: the debrief.
Record, 2: the email and the A3.

Run the same check on your own project with the Grace Closeout Checklist.

The Oakhaven debrief

The team sends the final invoice and holds the debrief the same week, with the records in the room. Here is what the five questions produced.

Question	What the team found
1. What were we trying to do?	The client’s three targets from kickoff: a great final project, dispatch never goes dark, and no surprises before City Council. The plan set profit at 19.3 percent.
2. What happened?	Final profit 16.0 percent. The DD hours ran over on the estimate reconciliation. CA carried a high volume of RFIs. The client got an update 5 working days before every council meeting.
3. What went well, and why?	No surprises before City Council. The practice behind it: a client update 5 working days before each council meeting, set at kickoff as an Experience Point with a named owner.
4. What went wrong, and why?	The DD overrun. The cause the team can act on: the plan had no task or hours for the estimate reconciliation, so senior staff did that work inside other tasks.
5. What will we do next time?	Your turn. Pick the action that meets the standard.

Practice

Which action meets the standard?

Three answers to question 5 from the Oakhaven debrief. Pick the one the next team can act on.

Question 5 · What will we do next time?
The cause: the plan had no task or hours for the estimate reconciliation. Which action do you write on the form?

This one meets the standardAn action, an owner, a date and a check. It is a personal action, so it goes into the PM’s next plan.

Look againNo owner and no date, and the work is undefined. The next team cannot act on it.

Look againThis one has an owner and an action. Nothing says when, and nobody will check whether it happened.

The standard

An action, an owner, a date, sent to the person who can act on it, and checked at the next review.

If someone says, “We communicated well,” ask what they actually did.

5Transfer

Put it to work

Return to the archive question. The firm should have a complete project record and a useful action with someone responsible for it. Your job is to bring the remaining work to that point.

This week

Run the checklist on your project closest to closeout.
Schedule a debrief for the end of your current phase.
Complete your Academy reflection on the Phase Debrief form and bring it to Onsite 2.

For the live session on Thursday, October 22. Bring one record from a recent phase: the phase plan, the change log or the QC Form. You will use it to practice a debrief.

Debrief your Academy

You’ve reached the end of the Academy’s virtual phase. Use the same five questions to examine your own progress.

What were you trying to do? Read the 3 goals you set at Onsite 1, what each one is tied to, and the proof for each.
What happened? Look at your project records from the months since then: plans, change logs, invoices and QC Forms.
What went well, and why? Identify your strongest result and the practice that helped produce it.
What went wrong, and why? Examine the goal that needs the most attention, and what got in the way.
What will you do next time? Choose one action you can carry forward, set a date, and check the evidence at your monthly review.

An action you can check

“I need to bill more often” leaves the work undefined. “I’ll review the prebill on the 25th of every month, starting this month” tells you what to do and when.

Write it on the Phase Debrief form, Academy reflection (PDF or Word). Bring the completed form to Onsite 2.

Challenge, from memory

Name the five areas and what you confirm in each. Then name the five debrief questions.

Contract: each step is done and no scope item is open. Money: unbilled is $0 and Accounting has confirmed the receivable status. Client: the client was asked for feedback and thanked, and the response is recorded. Lesson: the debrief action has an owner and a date. Record: email, Bluebeam sessions and A3 are complete, then the archive zip. The questions: What were we trying to do? What happened? What went well, and why? What went wrong, and why? What will we do next time?

Next. The Quick Reference is your job aid. Print it. The Grace Closeout Checklist is the tool you run on the project.

Then Onsite 2. You apply all 12 modules to one case and practice using them together. Wednesday, November 4, Phoenix. Thursday, November 5, Dallas. Tuesday, November 10, New Orleans. Wednesday, November 11, Orlando. Thursday, November 12, Nashville. 9:00 AM to 4:00 PM local time.

Sources for this page. Tannenbaum, S. I., and Cerasoli, C. P. (2013). Do team and individual debriefs enhance performance? A meta analysis. Human Factors, 55(1), 231 to 245. Keiser, N. L., and Arthur, W., Jr. (2021). A meta analysis of the effectiveness of the after action review (or debrief) and factors that influence its effectiveness. Journal of Applied Psychology, 106(7), 1007 to 1032. Ellis, S., and Davidi, I. (2005). After event reviews: Drawing lessons from successful and failed experience. Journal of Applied Psychology, 90(5), 857 to 871.

Closeout steps: Grace Milo, Close Out and Closeout pages. Card ranks: Onsite 1 responsibility card sort, cards 38 to 46, Phase 5 Closeout.