Post-Project Review & Continuous Improvement for General Contracting

Obtain the final job cost report, control budget, and approved change order summaries from accounting or the ERP system. Confirm that all costs and revenues have been posted or that remaining accruals are understood. Save copies in a dedicated “Post-Project Review” folder.

Organize the data to show base scope versus change order work, and separate major cost categories (general conditions, sitework, structure, envelope, interiors, MEP). Ensure that large one-off costs or owner-driven changes are identified so they don’t distort base performance.

For each major cost category, calculate variance to budget in dollars and percentage. Highlight areas with significant overruns or underruns, such as specific trades, general conditions, or allowances. Note whether variances were driven by quantity changes, rate changes, productivity, or scope creep.

For large variances, review supporting details such as change logs, buyout notes, and field reports. Determine whether issues stemmed from estimating assumptions, scope gaps, subcontractor performance, or site conditions. Write short notes capturing these factors for discussion in the review meeting.

Prepare a simple one- or two-page financial summary with charts or tables showing budget vs. actual by major category, total margin, and key drivers of variance. Use plain language to explain what went well and what did not. Bring this summary to the post-project review meeting as a reference.

Retrieve the original baseline schedule, any approved updates, and the final as-built schedule. Confirm that key milestones such as start, major turnovers, and substantial completion are clearly shown. Save schedules in the post-project review folder.

List major milestones (permit received, structure topped out, dry-in, MEP rough-in complete, finishes complete, substantial completion, occupancy) and record both planned and actual dates. Calculate slippage or gains in days for each milestone.

Using schedule narratives, meeting minutes, and delay logs, identify the major events that delayed or accelerated the project. Note what recovery actions were taken (overtime, resequencing, adding crews) and whether they were effective. Distinguish between owner-caused, weather-caused, and contractor-caused delays.

For selected scopes such as framing, drywall, concrete, or MEP rough-in, compare planned productivity (units per day or week) to actual performance where data is available. Use field logs, daily reports, or quantity tracking sheets as inputs. Note where productivity consistently lagged or exceeded plan.

Create a one-page schedule summary that shows milestone variance, main delay drivers, key recovery actions, and noteworthy production issues. Include a few bullet points on what should be done differently next time in planning or trade coordination. Bring this summary to the review meeting.

List the stakeholders whose views matter: owner’s representative, key users or tenants, architect, and possibly major consultants or landlord. Confirm contact info from your stakeholder list and decide whether feedback will be collected via survey, interview, or both.

Develop a simple set of questions covering communication, responsiveness, schedule, quality, coordination, and overall satisfaction. Include at least one open-ended question asking what went well and what could be improved. Keep it short enough that busy people will respond.

Email the survey with a brief explanation of why you are asking and how the information will be used. For key stakeholders, also propose a short phone or video call to discuss their experience. Make it clear you are looking for honest, constructive input.

During calls, ask your prepared questions and then probe lightly where they raise issues or praise. Listen more than you talk, and avoid becoming defensive. Write down specific examples, including where your team handled things well and where stakeholders were frustrated.

Combine survey responses and interview notes into a concise summary. Highlight recurring themes—both positive and negative—and pull out direct quotes (without names if sensitive) that illustrate key points. Include this summary in the post-project review materials.

List project team members who should provide input: project manager, superintendent, assistant supers, project engineer, project accountant, and safety lead. Also identify key subcontractors whose performance and insight matter most on similar future jobs.

Create a short list of questions focused on what worked well, what didn’t, and what should change next time. Cover preconstruction, buyout, coordination, schedule planning, RFIs/submittals, quality controls, safety, and client communication. Share this guide ahead of time so people can think.

Schedule short sessions with each internal participant and with representatives from key subs. Encourage blunt honesty and focus on specific examples rather than general complaints. Take notes on both problem areas and successful practices.

Review your notes and highlight issues that multiple people mention, such as recurring detail problems, unrealistic durations, or effective meeting structures. Extract specific suggestions for changes to processes, templates, or trade selection. Avoid dismissing ideas just because they differ from past practice.

Create a one- to two-page summary of feedback themes, organized by topic (precon, field coordination, quality, safety, client). Include concrete examples and proposed changes where available. Bring this summary to the post-project review meeting as a discussion driver.

Decide what you want out of the meeting: top lessons, priority issues, and specific improvement actions. Invite the project manager, superintendent, preconstruction lead, project accountant, quality/safety rep, and a representative from leadership. Optionally include a trusted key sub for part of the discussion.

Create an agenda that covers financial performance, schedule, quality/safety, client feedback, internal/trade feedback, and improvement opportunities. Allocate time blocks so no single topic consumes the entire meeting. Send the agenda and pre-read summaries at least a day in advance.

At the meeting, briefly present the financial summary, schedule performance, client/stakeholder feedback, and internal/trade feedback. Keep presentations short and focused on “what happened” rather than long storytelling. Encourage questions to clarify facts before moving to solutions.

Guide the group to identify the handful of most important lessons from the project. Ask what should be repeated on future jobs and what must change. Keep the conversation grounded in specific examples and avoid general complaining or finger-pointing.

As ideas emerge, write down potential actions on a shared screen or board: process changes, template updates, standard detail revisions, training topics, or trade lineup adjustments. Note which area of the business each action belongs to (precon, field ops, QC, safety, client service).

Before ending, review the list of potential actions and ask the group to prioritize. Confirm which items will move forward, who will own each, and expected timeframes for follow-up. Thank participants and explain how outcomes will be shared and tracked.

Set up a simple template with sections for project overview, financial summary, schedule summary, quality/safety notes, client feedback, internal/trade feedback, key successes, and key issues. Include space for “recommendations for future projects.”

Using notes from the review meeting and prior summaries, draft concise bullet points under each section of the template. Describe successes (for example, effective phasing strategy) and issues (for example, underpriced scope) in plain language, with enough context to be useful later.

Where possible, tie lessons to specific events, metrics, or locations (for example, “Level 3 overhead MEP coordination”). Include short explanations of why something worked or failed. Avoid vague statements like “communication could be better” without details.

Share the draft lessons-learned document with the project manager and a senior leader who knows the job. Ask them to confirm accuracy and add any missing key points. Adjust wording where needed to be factual and constructive, not personal.

Once approved, save the lessons-learned document in a central repository where preconstruction, operations, and estimating can easily access it. Tag or name it clearly with client, project type, and year so it is easy to find when similar opportunities arise.

From the lessons-learned document, choose a handful of high-impact problems: large cost overruns, major delays, repeated quality failures, or serious safety incidents. Limit the list so you can analyze each one properly rather than skimming many superficially.

For each selected issue, collect relevant RFIs, daily reports, emails, photos, and schedule snapshots. Build a simple timeline showing when the problem first appeared, what actions were taken, and how it affected cost, time, or client satisfaction.

For each problem, ask “why” repeatedly until you reach underlying causes that are actionable, such as process gaps, unclear standards, missing training, or misaligned incentives. Write down each “why” step so it’s clear how you reached the conclusion.

Sort root causes into those the company can influence (planning, staffing, standard details, trade selection) and those it cannot fully control (extreme weather, owner decisions). Focus most improvement effort on controllable causes while still acknowledging external factors.

Summarize each issue with its main root causes and potential countermeasures. Keep explanations short but specific. Use this document as an input to deciding which process, template, or standard updates to implement.

From the review meeting, lessons-learned document, and root cause analysis, list all potential improvement actions: process changes, new checklists, training modules, changes to trade lineups, or updates to preconstruction workflows. Combine duplicates and remove items that are not realistically actionable.

For each action, assess potential impact on future cost, schedule, quality, or safety, and estimate the effort required to implement. Use a simple high/medium/low scale. Focus on high-impact, medium-effort items first and deprioritize low-impact, high-effort items.

For every chosen action, assign one person (not a committee) who is accountable for driving it. This might be someone from estimating, operations, safety, quality, or corporate services. Confirm with them that they understand and accept ownership.

Agree on when each action should be completed and what “done” looks like (for example, “new drywall QC checklist piloted on next two projects” or “updated precon risk review form issued”). Write these into the action log alongside owners.

Distribute the improvement action list to leadership and affected departments. Decide where progress will be reviewed (for example, monthly operations meetings) and how status will be updated. Store the log in a shared location and keep it current until actions are fully implemented.

From financial and schedule analyses, list areas where actuals differed significantly from bid assumptions: production rates, subcontractor performance, material pricing, general conditions, or level of contingency. Decide which of these should influence standard estimating data versus being treated as one-off anomalies.

Meet with the estimating manager or lead estimator to review these items. Share concrete examples from the job, including quantities, durations, and trade performance. Explain how current assumptions led to overruns or how certain strategies produced savings.

Translate findings into proposed changes: updated unit rates, revised crew assumptions, different contingency percentages for certain work types, or adjustments in preferred subcontractor lists. Be as specific as possible rather than suggesting vague “be more conservative” guidance.

With estimating, apply proposed changes to a recent or upcoming project estimate to see how much the total would shift. Check that the new assumptions seem reasonable in the context of market competition and company margin targets.

Once agreed, have estimating update their databases, templates, and checklists. Document what changed and why, referencing the project as an example. Encourage estimators to review the project’s lessons-learned document when pricing similar work in the future.

From the lessons-learned document and improvement actions, pick a small number of items most relevant company-wide: for example, a new detail standard, a better way to structure OACs, or a recurring trade risk. Avoid overwhelming people with too many points.

Decide how to communicate: short write-up in an internal newsletter, a segment in operations or estimating meetings, a brief lunch-and-learn, or a page added to your internal playbook. Use channels that the intended audience already pays attention to.

Write concise explanations of each lesson, focused on what others should do differently. Include a brief description of the situation, what went wrong or right, and the new standard or recommendation. Avoid naming or blaming individuals; focus on systems and practices.

Present the lessons in the chosen forums. Encourage questions and discussion about how they apply to other projects or clients. Be honest about trade-offs and where the company is still experimenting with new approaches.

Save presentation slides, write-ups, and updated standards in a shared knowledge location, such as an intranet or SOP repository. Tag them by project type and discipline so people can find them when working on similar jobs.

Periodically, check whether these shared lessons are being referenced or incorporated into planning and SOPs. Refresh or retire items as practices evolve. Use feedback from future projects to refine how you communicate lessons learned.