How to Build a Post-Project Field Debrief That Changes Future Designs

What a Post-Project Field Debrief Actually Is (and How It Differs From a POE)

A post-project field debrief is a structured team review held after a project's substantial completion that captures what the project taught the firm. A post-occupancy evaluation (POE) is a separate study that measures how the finished building actually performs in use— typically 12 to 18 months after move-in, per AIA practitioners¹. Both matter. They are not the same activity, and conflating them is the most common reason firms have neither.

A debrief reviews the project. A POE reviews the building. Most firms do neither, claim both, and learn from neither.

The Royal Institute of British Architects codified the loop in its Plan for Use Guide. RIBA² writes that "Plan for Use embeds a basic level of POE and lesson learning into every project as a standard component of architectural practice." But the same guide notes that on most projects, the design team has no Stage 7 duties unless explicitly contracted— meaning the learning loop is optional by default.

The British Building Services Research and Information Association frames the same loop differently. BSRIA's Soft Landings Framework³ (2018 revision) breaks the work into six phases: inception and briefing; design; construction; pre-handover; initial aftercare; and extended aftercare with POE. BSRIA describes the goal in plain language— "a strategy adopted to ensure the transition from construction to occupation is 'bump-free' and that operational performance is optimised."

The same firm typically benefits from both: an immediate debrief at substantial completion (process) and a POE 12 to 18 months out (performance). Why this matters in dollars: the industry that doesn't do this loses billions to rework and decades to flat productivity.

The Cost of Skipping the Debrief

The UK Get It Right Initiative (GIRI) estimates rework at 21% of project value when indirect costs are counted— roughly £21 billion per year across UK construction⁷. McKinsey Global Institute's 2017 Reinventing Construction report⁶ found that construction productivity has grown at only 1% per year over the past two decades, compared with 2.8% in the overall economy. The same McKinsey report found that 98% of megaprojects suffer cost overruns of more than 30%. A 90-minute debrief is cheap insurance against those numbers.

The data the industry actually carries:

• 1% per year — construction productivity growth over two decades (McKinsey, 2017⁶)
• 2.8% per year — productivity growth in the overall economy over the same period⁶
• 98% — share of megaprojects exceeding cost by more than 30%⁶
• 77% — share of megaprojects at least 40% late⁶
• 21% — GIRI's best estimate of rework as a percentage of UK project value, indirect costs included⁷

The closeout-stage numbers are just as ugly. The Construction Management Association of America⁸ reports the biggest closeout challenges as completing work on time (38%), lack of parts and/or materials (33%), and delayed change order resolution (29%). These are exactly the issues a structured debrief surfaces while inputs are still fresh.

If a 90-minute debrief shaves even half a percent off rework on the next project, the time is recovered many times over. For firms weighing this against the hidden costs of AI implementation projects, the math is hard to argue with.

With the cost on the table, here's the agenda.

A 90-Minute Field Debrief Agenda That Doesn't Waste Anyone's Time

A 90-minute post-project field debrief, structured around the Lean Construction Institute's Plus/Delta spine, produces three to five specific changes the firm will actually adopt. The agenda is six segments: framing (5 min), goal versus actual (15 min), design decisions to revisit (20 min), field findings (20 min), Plus/Delta close (15 min), and assignment of owners (15 min).

The Lean Construction Institute (LCI), the source body for Plus/Delta, defines the practice⁴ as "a continuous improvement discussion performed at the end of a meeting, project or event used to evaluate the session or activity." Plus asks what produced value. Delta asks what could change to improve. LCI is direct on why the format earns its place on the calendar: "Valuable insights may go unspoken without regularly scheduled opportunities to share them."

AIA Contract Documents⁵ positions lessons learned "as part of the overall construction/commissioning process" rather than as a separate ceremony. In practical terms, the debrief belongs inside closeout, not outside it.

Four artifacts survive the meeting:

• Goal-versus-actual one-pager — owned by the Project Architect
• Three-design-decisions list — owned by Project Architect plus Construction Manager
• Plus/Delta minutes — owned by the Facilitator
• Owner/Destination matrix — owned by the Facilitator, published within five business days

Roles matter as much as timing. The Facilitator is not the project manager— whoever ran the project cannot also facilitate the review of it. The conflict is structural, not personal. When the debrief is paired with the 12-to-18-month POE, a building operator joins for the second pass.

Who needs to be in the room— because the wrong attendee list will sabotage the agenda before it starts.

Who Needs to Be in the Room

Five voices belong in a field debrief: the project architect, the construction manager, a designer who worked the project but isn't the architect of record, an owner-side representative when the relationship allows, and— for the paired 12-to-18-month POE— a building operator or end-user. Without the construction-side voice, the debrief becomes design-team self-justification. Without an owner-side voice, the findings will not survive contact with the next client conversation.

• Project Architect. Owns goal-versus-actual; one person responsible for the one-pager that anchors the session.
• Construction Manager. Owns field findings the design team didn't see. Without this voice, half the lessons walk out the door with the trade contractors.
• Project Designer / Job Captain. The person who drew the details, not just the principal of record.
• Owner-side Representative. When the relationship allows. Page architecture firm reports approximately 90% of its work comes from repeat clients¹.
• Building Operator / End-User. For the paired 12-to-18-month POE only. Surfaces actual-use issues no document captures.
• Facilitator. Not the project manager. Non-negotiable. Conflict of interest will neuter the conversation before it starts.

BSRIA's Soft Landings framework³ makes the cross-stakeholder principle explicit. When to hold it— and why one debrief is rarely enough.

When to Hold the Debrief (Two Timings, Both Cited)

Most firms benefit from two debriefs, not one. The first runs within 30 days of substantial completion and captures process and team learnings while the project is fresh. The second runs 12 to 18 months after occupancy— the standard AIA post-occupancy survey window¹— and captures how the building actually performs once it has been lived in.

The first debrief is the closeout debrief. Inputs are fresh and teams haven't dispersed. The CMAA closeout pain points⁸ (38% completion, 33% materials, 29% change orders) land exactly here. Capture the lessons before the team moves on, or accept that they'll be relearned on the next project.

The second debrief is the building-performance review. Inputs include sensor data, occupant surveys, and FM staff feedback. This is where POE methodology overlaps with the debrief format— the team reviews not just how it built the project but how the building has performed in use.

A firm that can't spare 90 minutes still has options. Granger Construction¹¹ runs Plus/Delta in the final 10 minutes of weekly meetings. The discipline scales down. What it can't do is disappear and still produce learning.

And now the hardest part— making any of this matter on the next project.

How to Make Findings Actually Change the Next Project's Design

Every finding from a field debrief needs an owner and one of three destinations, or it dies in a binder. The three destinations are: (1) a firm-level design standard that gets updated for every future project; (2) a project-template detail or specification that propagates automatically; or (3) a checklist item that lands in the next project's Stage 0 or schematic-design brief. Without an owner and a named destination, the binder wins.

This is the structural fix, not the cultural one. Most debriefs produce notes that nobody reads. The fix isn't a better culture of follow-through. The fix is assigning every Delta to a person with a deadline and a destination.

Page architecture firm reports approximately 90% of its work comes from repeat clients, a metric the firm credits in part to its post-occupancy evaluation services¹. Evaluations of completed emergency-care centers directly shaped the design of a sixth center— sizing of specific areas adjusted based on end-user feedback¹. That's what the binder-problem solution looks like in practice: a documented finding from one project changing the program of the next.

Planman¹⁰ frames the destination question the same way for UK architectural practice: post-project review outputs feed straight into the next project's Stage 0/1 brief, or the learning loop is decorative. Tracking whether destinations actually receive their findings is the same discipline behind how to measure AI implementation success— measure loop closure, not activity.

One honest constraint: not every finding can be acted on. Some are project-specific (client program, code constraints, fixed budget) and cannot become a firm-level standard. Distinguish firm-level standards the firm controls from project-specific decisions the client controls. The first is yours. The second is information for the next conversation.

None of this works if people can't say what actually happened. The next problem is psychological— but the framing matters.

Psychological Safety on a Construction Team (Without Going Soft)

A field debrief surfaces honest findings only if the team trusts that the conversation is about the process, not the person. Norman Kerth's Retrospective Prime Directive⁹— "Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand"— is the operational expression of that trust. Lean Construction calls the same principle "Respect for People." Construction culture tends to bristle at "psychological safety" language; both of these framings land harder.

"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." — Norman Kerth, Project Retrospectives (2001)

Kerth's framing is operational, not therapeutic. It tells the team what the room is for. Read it aloud at the start of every debrief. Separate person from process. That's the rule.

The LCI parallel is real. Plus/Delta facilitators are expected⁴ to foster "an environment that promotes a Respect for People." Same idea, native vocabulary.

Harvard's Amy Edmondson found that psychological safety is the single most consistent predictor of high-performing teams (Google's Project Aristotle replicated the finding in software)⁹. The principle is cross-industry; the language adapts. If your firm is also wrestling with how AI affects firm-wide change management, the same principle applies— change without trust doesn't stick.

What about the part where AI helps— because for a firm trying to make findings stick across years and staff turnover, the binder problem is also a search problem.

Where AI Helps the Debrief Loop (the Search Problem Inside the Binder Problem)

The binder problem is partly discipline and partly search. Most firms have a decade of debrief notes nobody can find when the next project starts. This is where AI helps— not by replacing the debrief, but by making three years of past findings searchable from inside the project Stage 0 brief.

What AI doesn't do here: replace the human conversation. The debrief itself is irreducibly human— the trust, the framing, the in-room judgment of what a field finding means for a specific design choice.

What AI does well:

• Indexes debrief notes, lessons-learned documents, and POE reports so a project architect can ask "what did we learn about emergency-department triage layouts on past projects" and get a citable answer with sources.
• Drafts the Stage 0 checklist for an incoming project by surfacing the relevant subset of firm-standard updates from prior debriefs.
• Auto-summarizes verbatim Plus/Delta minutes into the owner/destination matrix, so the Facilitator's 75-to-90-minute segment becomes review-and-confirm rather than transcription.

There's a gate. This requires a centralized, searchable knowledge base— not SharePoint folders by project. The same discipline that solves the binder problem (owners and destinations) is what makes the AI integration possible. Without the structure underneath, the AI has nothing useful to index.

Discipline first, technology second. A firm that wants to implement this without buying enterprise software has options; the discipline matters more than the platform. If mapping the right tools onto your closeout process feels like a project on its own, AI implementation services for AEC firms is exactly the kind of work we do— and it extends our guide to AI workflow automation for knowledge-base work specifically.

Five questions a principal will ask before running their firm's first structured debrief.

Frequently Asked Questions

What is the difference between a post-project debrief and a post-occupancy evaluation?

A debrief reviews the team and project process; a POE measures how the finished building actually performs in use. The first is run by the project team within 30 days of substantial completion; the second is typically run 12 to 18 months after move-in, per AIA practice¹. Most firms benefit from both— they are not interchangeable, and RIBA's Plan for Use Guide² treats them as complementary parts of the same loop.

What is Plus/Delta in construction?

Plus/Delta is a short retrospective format from the Lean Construction Institute⁴. At the end of a meeting or project, the team answers two questions: Plus— what produced value, and Delta— what could we change to improve. LCI recommends running it in the final 10 minutes of meetings, which means a firm without 90 minutes for a closeout debrief still has 10 minutes at the end of a weekly project meeting.

When should you hold a construction debrief?

Most firms benefit from two debriefs: one within 30 days of substantial completion to capture process learnings while inputs are fresh, and a second 12 to 18 months post-occupancy aligned with the AIA POE survey window¹. The first captures team and process; the second captures building performance. CMAA closeout data⁸ shows that completion timing (38%), materials (33%), and change orders (29%) are exactly the issues the first debrief is positioned to capture.

How much does construction rework cost?

The UK Get It Right Initiative estimates rework at 21% of project value when indirect costs are included— roughly £21 billion per year across UK construction⁷. McKinsey Global Institute separately reports⁶ that 98% of megaprojects suffer cost overruns of more than 30% and construction productivity has grown only 1% per year over two decades. No US industry-body figure of comparable authority exists; GIRI's figure is UK-specific and inclusive of indirect costs.

Who should attend a project field debrief?

The project architect, construction manager, the project designer or job captain (not just the principal of record), an owner-side representative when the relationship allows, and— for the paired 12-to-18-month POE— a building operator or end-user¹. The facilitator should not be the project manager; conflict of interest is structural, not personal. BSRIA's Soft Landings framework³ treats cross-stakeholder attendance as foundational to the loop.

And one final note on the second debrief— the one the serious firms run.

The Second Debrief, and How to Start Small

The serious firms run two debriefs per project: one within 30 days of substantial completion, and one 12 to 18 months after occupancy. The first captures process. The second captures performance. Together they are what builds a firm's future in construction: a documented, owned, searchable record of what every project taught the firm— captured in structure, carried forward by discipline.

Start small if 90 minutes feels impossible. Plus/Delta scales down— a firm can begin with 10 minutes at the end of every weekly project meeting (Granger's adoption pattern¹¹). Build the muscle on weekly cadence, then graduate to the 90-minute closeout. Then add the paired 12-to-18-month POE.

The senior-leader argument is repeat-client retention. Page reports approximately 90% of its work comes from repeat clients and frames POE as a service differentiator, not a profit center¹. The ROI lives in the relationship and in the design knowledge the firm carries from one project to the next— compounding across projects, not booking against a single closeout.

If your firm is building the discipline— and especially the searchable knowledge layer that makes findings compound across years and staff turnover— Dan Cumberland Labs helps AEC firms put the systems in place. What builds a firm's future in construction is a documented, owned, searchable record of what every project taught the firm— captured in structure, carried forward by discipline.

⚠️ EVERYTHING BELOW IS PIPELINE METADATA — NOT PUBLISHED

References

1. American Institute of Architects, "Post-occupancy services can improve your future design offerings. Here's how." (2024) — https://www.aia.org/aia-architect/article/post-occupancy-services-can-improve-your-future-design-offerings-heres-how
2. Royal Institute of British Architects, "Plan for Use Guide" (2021) — https://www.riba.org/media/54tn0pr2/plan-for-use-guide-2021.pdf
3. Building Services Research and Information Association (BSRIA), "Soft Landings Framework: About Soft Landings" (2018) — https://www.bsria.com/uk/consultancy/project-improvement/soft-landings/about-soft-landings/soft-landings-approach/
4. Lean Construction Institute, "Plus/Delta" (2024) — https://leanconstruction.org/lean-topics/plus-delta/
5. AIA Contract Documents, "Construction Contract Closeout: Best Practices & Lessons Learned" (2024) — https://learn.aiacontracts.com/articles/construction-contract-closeout-lessons-learned-and-best-practices/
6. McKinsey Global Institute, "Reinventing construction through a productivity revolution" (February 2017) — https://www.mckinsey.com/capabilities/operations/our-insights/reinventing-construction-through-a-productivity-revolution
7. Get It Right Initiative, "Literature Review: Financial and Economic Impact of Error" (2016) — https://getitright.uk.com/reports/literature-review/chapter/financial-and-economic-impact-of-error
8. Construction Management Association of America, "Nail Your Construction Project Closeout Every Time With These Tips" (2023) — https://www.cmaanet.org/sites/default/files/resource/Project%20Closeout.pdf
9. Opensource.com (Red Hat), "The psychology behind a blameless retrospective" (April 2019) — https://opensource.com/article/19/4/psychology-behind-blameless-retrospective
10. Planman, "Project Post-Mortems and Retrospective Reviews in UK Architecture" (2024) — https://www.planman.app/blog/architects/project-post-mortems-reviews/
11. Granger Construction, "Lean: How the Plus/Delta process helps continuous improvement" — https://www.grangerconstruction.com/lean-plus-delta-process/