Post-Project Debrief
How to capture lessons from residential HPWH modelling projects.
Residential projects can look routine, but they often surface useful lessons about testing gaps, model naming, certification timing, control settings, scheme forms, and client communication. The debrief turns those lessons into reusable process improvements.
When to run a debrief
Run a debrief within 2 weeks of final submission confirmation, or sooner if the project had a difficult handover.
Debriefs are mandatory for projects with:
- Multiple models or model variants
- Testing or certification delays
- Gate A or Gate B findings that required rework
- Scheme RFIs or portal rejections
- Scope changes after quotation
- Client communication issues
Debrief structure
Use this structure:
- Project summary
- Testing and certification
- Documentation intake
- Modelling and Gate A review
- Audit file preparation and Gate B review
- Submission and scheme administrator feedback
- Client communication
- Lessons learned and KMS updates
Prompt template
Generate a structured post-project debrief report for this EnergyAE residential HPWH modelling project.
PROJECT DETAILS
Project code: {AExxx}
Client: {Client}
Product range / models: {Models}
Schemes: {CER / VEU / ESS}
EAE team lead: {Name}
SEARCH SCOPE
Search project emails, Teams messages, Monday.com notes, and project files using:
- Project code
- Client name
- Model names
- Brand name
- Testing lab / certification body contacts
REPORT STRUCTURE
1. PROJECT SUMMARY
2. TESTING AND CERTIFICATION
3. DOCUMENTATION INTAKE
4. MODELLING AND GATE A
5. AUDIT FILE PREPARATION AND GATE B
6. SUBMISSION AND RFIS
7. CLIENT COMMUNICATION
8. LESSONS LEARNED AND KMS UPDATE TASKS
For each lesson, identify the KMS page in /kms/09-residential-modelling/ that should be updated.Exit gate
The debrief is complete when the team lead has reviewed it, KMS update tasks are assigned, and the director has signed off closeout.