A post-project lessons-learned review is a structured meeting held after a commercial roofing project to evaluate what worked well, what caused problems, and what should be done differently on future projects. The goal is not to assign blame. It is to capture practical knowledge while the project is still fresh so the property owner, facility team, contractor, and project professionals can improve future roofing work.
For Florida commercial roofing projects, the review can be especially useful because weather, permitting, building operations, material availability, and storm conditions can significantly affect project performance.
When Should the Review Take Place?
The review should generally occur after substantial completion or final closeout, when the project team has enough information to evaluate the entire process.
It is usually better to schedule the meeting soon after completion rather than waiting several months. Important details about scheduling decisions, weather delays, material issues, communication problems, and field conditions become harder to remember over time.
The team should also review relevant project records before the meeting, including daily reports, schedules, inspection reports, change orders, photographs, safety records, and punch lists.
Who Should Participate?
The appropriate participants depend on the size of the project. A typical review may include:
-
Property owner or owner’s representative
-
Property or facility manager
-
Roofing superintendent or foreman
-
General contractor, if applicable
-
Architect, engineer, or roofing consultant
-
Project manager or construction manager
-
Other key participants who were directly involved
The group should be small enough to have a productive discussion but broad enough to capture perspectives from both construction and building operations.
What Should Be Reviewed?
The discussion should cover the complete project lifecycle rather than focusing only on installation.
Planning and Pre-Construction
Ask whether the scope was clear, whether existing conditions were properly investigated, whether the schedule was realistic, and whether responsibilities were clearly assigned.
Scheduling
Review whether the project finished on time and what caused significant delays.
For Florida projects, weather-related delays should be evaluated separately from contractor productivity issues so the team can distinguish unavoidable conditions from preventable scheduling problems.
Communication
Evaluate how effectively information moved between the owner, contractor, property manager, consultants, and building occupants.
Questions may include:
-
Were changes communicated quickly?
-
Did decision-makers receive enough information?
-
Were daily reports useful?
-
Were problems escalated appropriately?
Quality Control
Review inspection findings, deficiencies, corrective work, testing, manufacturer inspections, and warranty closeout.
The team should identify recurring quality problems and determine whether they resulted from unclear specifications, installation practices, supervision, materials, or communication.
Safety
Evaluate incidents, near misses, access issues, fall protection, material handling, and other safety concerns.
The purpose is to identify ways to improve future projects rather than simply document whether an incident occurred.
Building Operations
For occupied properties, review whether the contractor successfully coordinated access, noise, deliveries, rooftop equipment, tenants, security, and building systems.
How Should Lessons Be Documented?
The review should produce a concise written record. Each important lesson should identify:
Issue → Cause → Impact → What worked → Recommended change → Responsible party
For example, if repeated rain delays affected production, the recommendation might involve earlier weather monitoring, improved temporary protection, or more flexible scheduling.
Not every observation needs to become a formal action item. Focus on lessons that can materially improve future projects.
What Should Happen After the Meeting?
The lessons-learned document should be distributed to the appropriate project and facilities personnel. Action items should have an owner and, when appropriate, a target completion date.
The most valuable lessons should also be incorporated into future roofing specifications, contractor selection criteria, pre-construction checklists, maintenance procedures, and project-management standards.
Best Practice for Florida Roofing Projects
A post-project lessons-learned review should answer three basic questions:
-
What went well?
-
What did not go well, and why?
-
What will we change on the next project?
The strongest reviews use objective project evidence rather than opinions alone. Daily reports, weather records, inspection documentation, photographs, schedules, change orders, and warranty records can help the team identify the actual causes of problems.
For Florida commercial property owners, this process can turn one completed reroof into a source of better knowledge for future projects. A well-documented lessons-learned review can improve planning, communication, quality control, safety, scheduling, and building operations while reducing the likelihood of repeating the same mistakes on the next roofing project.
Related Questions
- What is a pre-installation conference with the manufacturer?
- What daily reporting should a roofing contractor provide?
- What training should be provided to facility staff after a reroof?
- How are as-built roof plans prepared and delivered?
- How often are these testing standards updated?
- What should be included in an operations and maintenance manual for a new roof?
