Post Project Review for General Contracting

Export the final job cost report from your accounting system, including cost by cost code, committed costs, and total spend. Retrieve the original project budget or baseline estimate so you have a “before and after” comparison.

Group cost codes into major categories (for example, sitework, structure, interiors, MEP, general conditions). For each category, calculate budget, actual cost, and variance in both dollars and percentage.

Highlight the categories and specific cost codes with the biggest overruns and underruns. Make note of any patterns, such as consistent underruns in one trade and overruns in another.

List all approved change orders, their values, and any associated costs. Calculate approximate gross margin on change work to see whether changes helped, hurt, or maintained overall project margin.

Confirm total revenue billed (including changes) versus total job cost to determine actual margin. Compare this to your original target margin and note the size of the gap, whether positive or negative.

Create a one- to two-page summary with charts or tables that show budget vs. actual, major variances, and final margin. This summary will be used during the review meeting to guide discussion.

Gather the original baseline schedule (or first approved schedule) and the final as-built schedule. If you used look-ahead schedules or phase pull plans, collect representative samples as well.

Compare planned start and completion dates to actual start and completion dates. Note the overall days or weeks ahead or behind schedule and whether substantial completion and final completion were achieved on time.

List major milestones such as structure complete, dry-in, MEP rough-in, inspections, and finishes. For each, document planned date, actual date, and variance so you can see where the project first started to slip or recover time.

Look at documented delays (weather, design changes, late decisions, late materials) and how the team responded. Note which recovery strategies worked (added crews, resequencing) and which created new problems.

Ask field staff for observations on production rates—where trades moved faster than expected and where they struggled. These insights help refine future schedule logic and durations.

Summarize your findings in a short document or slide with timelines, milestone variance charts, and bullet points describing major schedule drivers. This will guide schedule-related discussion during the review.

Decide which areas you want client feedback on, such as communication, responsiveness, change management, cleanliness, safety perception, and overall satisfaction. Make a short list so the survey stays focused.

Create a survey with a mix of rating-scale questions and open-ended questions. Alternatively, build an interview guide if you plan to gather feedback by phone or meeting instead of a form.

Identify 2–4 key client stakeholders (project manager, facilities lead, end-user representative) and invite them to provide feedback. Explain that the goal is to learn and improve, not to argue project details.

Send the survey link or conduct the interviews and record responses accurately. Avoid defending or explaining during feedback—just listen and capture what is said.

Group feedback into themes (for example, “strong communication early, weaker at end,” “issues with change order clarity”). Pull out specific quotes that illustrate each theme without using names in the review.

Create a one-page summary showing key scores (if using ratings), major positives, and main improvement areas. Use neutral language so the team can absorb the feedback without getting defensive.

List the project manager, superintendent, project engineer, foremen from key trades, and any coordinators who played a major role. These are the people whose perspectives you want captured.

Prepare a short form or set of questions asking what went well, what went poorly, which processes helped, and where they felt friction (for example, submittals, RFIs, scheduling, change orders). Include space for specific examples.

Send the template to participants with a clear due date and explain how the information will be used. Emphasize that the goal is improving systems, not assigning blame.

For key roles like the superintendent and project manager, schedule short one-on-one conversations to dig deeper into their written responses. Ask for concrete examples of problems and ideas for improvement.

Collect all responses and group them into themes such as “preconstruction handoff,” “procurement timing,” “field coordination,” and “documentation.” Note where multiple people mention the same issue.

From the themes, select the most impactful improvement opportunities that appear across roles or trades. Prepare a brief summary of each to bring into the review meeting.

Clarify that the purpose of the meeting is to understand project performance and agree on improvements, not to assign blame. Invite the project manager, superintendent, estimator, key office and field staff, and a representative from leadership if appropriate.

Send out financial summary, schedule performance snapshot, client feedback summary, and internal feedback themes at least one day before the meeting. Ask participants to review and think about top 2–3 changes they would recommend.

Plan an agenda that covers financials, schedule, client experience, internal process issues, and improvement ideas. Allocate time for each segment and build in a few minutes at the end to prioritize actions.

During the meeting, guide the conversation so everyone has a chance to speak and side conversations are limited. When disagreement arises, focus on facts and processes, not personal opinions about individuals.

Assign someone to take notes on a shared screen or visible board so everyone can see what is being recorded. Make sure decisions and action items are captured with clear owners and due dates.

At the end, summarize major insights and list the agreed action items. Confirm who is responsible for each action and how progress will be tracked after the meeting.

Use or create a template with sections for project overview, key successes, key issues, root causes, and recommended changes. This keeps documentation consistent across projects.

Write a short description of the project type, size, complexity, and any unique factors (for example, occupied renovation, fast-track schedule). This context helps future readers understand why certain issues appeared.

Identify 3–7 things that went particularly well and briefly explain why (for example, “early procurement of long-lead equipment prevented delays”). Focus on actions and decisions that can be repeated on future jobs.

Describe the most significant problems that affected cost, schedule, quality, or client satisfaction. Include their approximate impact (for example, “two-week delay,” “added $50,000 cost”) without over-precision.

For each major issue, provide a brief explanation of why it happened in terms of process, information, or resourcing. Avoid blaming individuals; instead, focus on what in the system allowed it to occur.

Write one to three sentences per issue describing what should change to prevent it or reduce its impact next time. These recommendations will feed into more specific action items later.

From your lessons learned list, pick the handful of issues with the largest impact on cost, schedule, quality, or client satisfaction. Limit yourself to a manageable number (for example, three to five) so analysis stays focused.

For each selected issue, involve the project staff and trades who were directly involved. They often know details that are not visible in reports or high-level summaries.

Write a concise problem statement for each issue, including what happened, when, and how it affected the project. Make sure everyone agrees on this description before you look for causes.

Ask “why” repeatedly (often five times or more) to move beyond immediate triggers (for example, “late submittal”) to underlying causes (for example, “unclear submittal priority list” or “unrealistic review durations”). Document each level of cause as you go.

Look for causes related to process (missing steps, unclear ownership), communication (poor handoffs, incomplete information), or planning (unrealistic durations, missing scope). These are the levers you can actually adjust on future projects.

Write a brief summary of root causes for each issue and review it with the involved team members. Adjust if they feel something important is missing or misrepresented.

Look at your lessons learned and root cause summaries to identify potential changes to processes (for example, preconstruction handoff), templates (for example, RFI forms), tools, or training.

With the project manager and perhaps operations leadership, rank each potential change in terms of impact on future projects and effort required to implement. Focus on high-impact, reasonable-effort items first.

Rewrite each selected change as a specific action, such as “revise preconstruction checklist to include long-lead item review” or “create standard client kickoff agenda template.” Avoid vague actions like “improve communication.”

For every action, name a single person who is responsible for making it happen (for example, operations manager, preconstruction manager, project controls lead). Make sure they understand and accept the responsibility.

Agree on a due date for each action that fits around ongoing workload but keeps momentum (for example, 30–60 days for most changes). Note any dependencies, such as needing leadership approval.

Enter all actions, owners, and due dates into a shared tracking sheet or task system that leaders review regularly. This keeps improvements visible until they are completed.

From your financial and production analysis, pick out items that should change how you price work (for example, labor productivity, typical contingency for certain trades, typical change order margins).

Schedule a discussion with the people responsible for estimates and preconstruction planning. Share specific examples of where original assumptions were too aggressive, too conservative, or simply wrong.

Based on the conversation, update unit pricing, crew productivity factors, or contingency percentages in your estimating system for similar project types. Document why changes were made for future reference.

If certain activities consistently took longer or shorter than planned, adjust durations or logic in your standard schedules. Similarly, update preconstruction or kickoff checklists to include steps that proved important on this project.

Incorporate lessons about client communication or change management into standard email templates, meeting agendas, or change order forms. Small wording changes can greatly improve clarity next time.

Record what was updated and why in a short note and share it with project managers, estimators, and preconstruction staff. This builds trust that post-project reviews actually lead to real improvements.

From your lessons learned and action list, select a handful of points that will matter on other projects—especially patterns, new best practices, and major pitfalls to avoid.

Decide how to share: short write-up in an internal newsletter, segment in a project manager meeting, a quick toolbox talk topic, or a short slide deck for operations meetings. Different audiences may need different formats.

For each key learning, write a short explanation of the situation, what was done, and what you recommend others do in similar circumstances. Focus on clear “do this / avoid this” guidance.

Share not only problems but also things that worked very well—such as a particularly effective kickoff process or a new way of sequencing work. This encourages copying good practices, not just avoiding bad ones.

Present the lessons in the relevant meetings or send them out through agreed communication channels. Keep the tone constructive and practical, not negative or overly detailed.

Save the final lessons learned document and any summary slides in a central, easy-to-find location (for example, a “Project Lessons” folder). Tell teams where to find them so they can reference them when planning similar jobs.