Contractors
Lessons Learned Compiler
Systematically capture, organize, and document project lessons learned across all project phases to improve future project performance and build institutional knowledge within your construction firm.
This prompt compiles a structured lessons-learned report from project performance data across six categories — preconstruction and estimating, project startup and planning, construction execution, owner and design team relations, safety and compliance, and technology and processes — with each lesson documenting the observation, root cause, a specific actionable recommendation, and which future project types benefit most from the lesson. The report concludes with an executive summary of the top five lessons for company leadership formatted for storage in the firm's knowledge management system. Sensitive information about personnel performance, subcontractor failures, or unresolved disputes should be handled per company legal and HR policies before distribution. It is for construction operations managers and project executives conducting structured post-project reviews on completed commercial, institutional, or multifamily construction projects.
Testedclaude-sonnet-4-6ValidatedMar 2026ScopeLessons must be specific and actionable — avoid vague observ…TierProfessional
Constraints
Lessons must be specific and actionable — avoid vague observations like 'better communication needed'
Root cause analysis must go beyond surface-level descriptions to identify systemic issues
Recommendations must be implementable by the project team on future projects without major resource investment
Sensitive personnel or subcontractor performance issues must be documented objectively and factually
All observations must be supported by project records — not anecdotal recollections
Tested Models
claude-sonnet-4-6
Uncertainty
If specific project performance data is not available, generate a lessons-learned framework with prompting questions for each category that the project team can answer in a structured debrief session.
Last updated
2026-05-28 — Published
The prompt
You are a construction operations manager and continuous improvement specialist with expertise in project post-mortems, lessons-learned processes, and building institutional knowledge in construction firms. You understand what insights are most valuable for improving future project performance. Compile lessons learned for the following construction project: Project Name: [PROJECT_NAME] Project Type: [BUILDING_TYPE] Project Size: [CONTRACT_VALUE_AND_SF] Project Duration: [PLANNED_DURATION vs ACTUAL_DURATION] Final Cost vs Budget: [OVER/UNDER — PERCENTAGE] Delivery Method: [LUMP_SUM/GMP/DESIGN-BUILD] Key Team Members: [PM/SUPERINTENDENT/ESTIMATOR] Major Challenges Encountered: [LIST_KEY_CHALLENGES] Major Successes: [LIST_KEY_WINS] Owner Satisfaction: [HIGH/MEDIUM/LOW] Safety Record: [INCIDENTS/NEAR_MISSES] Quality Issues: [MAJOR_QUALITY_PROBLEMS_IF_ANY] Subcontractor Performance: [NOTABLE_PERFORMANCE — GOOD_AND_BAD] Generate a comprehensive lessons-learned document covering: 1. PRECONSTRUCTION AND ESTIMATING - Estimate accuracy issues - Scope gaps or misunderstandings - Subcontractor bid quality - Value engineering effectiveness 2. PROJECT STARTUP AND PLANNING - Schedule development quality - Site logistics effectiveness - Subcontractor mobilization - Permit and approval timeline 3. CONSTRUCTION EXECUTION - Schedule performance drivers - Cost performance drivers - Quality management effectiveness - Trade coordination successes and failures 4. OWNER AND DESIGN TEAM RELATIONS - Communication effectiveness - Change order management - RFI and submittal process - Dispute avoidance or resolution 5. SAFETY AND COMPLIANCE - Safety program effectiveness - Compliance issues encountered - Near-miss learnings 6. TECHNOLOGY AND PROCESSES - Project management tools - BIM and coordination technology - Documentation processes For each lesson: Category, Observation (what happened), Root Cause, Recommendation (what to do differently), and Application (which future project types benefit most).
WAITLIST
Runner beta coming — join the waitlist.
In-product execution isn't live yet. Leave your email and we'll let you know if the Runner beta opens.
How to use this prompt
1
Complete the project summary inputs with actual performance data, then work through each category with your project team in a structured debrief session
2
Use the generated framework as a discussion guide
3
Document specific observations and recommendations for each finding and store in your company knowledge management system.
Customization tips
Add a 'best practices to repeat' section alongside the 'what to change' findings to capture positive patterns
Create a rating scale for each lesson by potential impact on future project profitability
Include subcontractor-specific lessons that feed into your subcontractor qualification database
Add an estimating feedback section that quantifies estimate vs. actual variances by CSI division for future estimating calibration
Sample output
Lessons Learned Report — Project Closeout Documentation
Project: [Project Name and Type]
Contract Value: $[Amount]
Project Duration: [Planned] vs. [Actual]
Prepared by: [Project Manager]
Date: [Date]
Distribution: [GC] Company Project Managers, Estimating, Preconstruction
PURPOSE: This report captures key lessons from this project for application to future work. It is a confidential internal document.
PRECONSTRUCTION PHASE:
Lesson 1 — Document Review Before Award
What happened: During bidding, we did not identify the specification requirement for a specific HVAC controls system that required sole-source procurement. The controls package came in $42,000 over our bid estimate because we had only priced a generic BAS system.
Lesson: Establish a spec review checklist item specifically for "sole-source or proprietary specifications" during estimating. Flag any specification that names only one manufacturer and has no substitution provision for immediate scope/cost clarification before submitting a bid.
CONSTRUCTION PHASE:
Lesson 2 — Concrete Pour Sequencing on Multi-Level Projects
What happened: We initially sequenced concrete pours by floor (complete Level 2 before starting Level 3). The structural engineer confirmed that a two-floor separation was not required; we could begin Level 3 forming while Level 2 concrete reached design strength. We did not recognize this opportunity until Week 8.
Lesson: In the preconstruction schedule, always evaluate whether sequential floor pours are required by the structural design or by our scheduling habit. Confirm with the structural EOR during preconstruction — this type of acceleration is often available without any cost.
Lesson 3 — Subcontractor Communication During Scope Changes
What happened: Three approved change orders in the first 6 weeks changed the MEP routing in Zone C. The GC project engineer communicated the changes to the affected MEP subcontractors, but the information was not forwarded to the foremen in the field. The mechanical foreman installed 40 feet of duct per the original design, which had to be removed.
Lesson: Establish a formal change notice process: when a change is approved, the subcontractor is required to acknowledge receipt in writing AND confirm that field supervision has been notified before work in the affected area continues.
Lesson 4 — Owner Submittal Response Times
What happened: The contract required owner response to submittals within 10 business days. The design team routinely took 18-22 days. We did not document or formally notice these overruns until the delays had accumulated.
Lesson: Log every submittal with the submission date and the contract response due date. Send a formal written notification to the design team for every submittal that passes the contract response deadline without a response. This creates the record needed for delay claim support.
CLOSEOUT PHASE:
Lesson 5 — Operations and Maintenance Manual Assembly
What happened: We waited until the last 3 weeks of the project to begin assembling the O&M manual. The process took 6 weeks because we were chasing subcontractors for equipment documentation they should have submitted with their final pay applications.
Lesson: Require subcontractors to submit all warranty and O&M documentation as a condition of their penultimate pay application (not final). Begin organizing the O&M binder at project mid-point.
Related prompts
Frequently asked questions
Conduct a brief mid-project lessons review at 50% completion to apply learnings while the project is still active. Conduct the full project lessons-learned debrief within 30 days of substantial completion while memories are fresh and the team is still intact. Waiting until final closeout means key team members have moved on.
Create a psychologically safe environment: emphasize that the goal is improving future performance, not assigning blame. Allow anonymous submissions for sensitive observations. Have a neutral facilitator (not the PM or superintendent) run the session. Focus on systemic issues, not individual failures.
Create a searchable database organized by project type, size, and lesson category. Distribute a 'Top 5 Lessons' executive summary to all project managers after each project. Review relevant lessons in project kick-off meetings for similar future projects. A lessons-learned database only adds value if it is actually referenced and used.
Professional Disclaimer
Lessons-learned documents are internal management tools for improving company performance. Sensitive information about project disputes, personnel performance, or subcontractor failures should be handled in accordance with company legal and HR policies before distribution. Consult legal counsel before including information that relates to unresolved disputes or potential claims.