The final project report to management: six pages that say what happened and why
Management asks how the completed project went. The team has a thick closeout folder and a celebratory photo, but the final margin, late finish and unresolved trade issue are explained in separate conversations. The company has no concise record of what it should repeat or change.
Write the final project report as six focused parts: checked results against the baseline, significant changes and causes, client and consultant relationships, trade and supplier performance, lessons and recommendations, and appropriate people-development follow-up. Aim for six useful pages rather than a complete correspondence archive. Use the financial closing review for the numbers and label unresolved items. Management should understand what happened, why it happened and what action follows.
Give each part one management purpose
- Start with the checked result. Show the agreed scope, budget and schedule baseline beside the final position. Include the safety and quality records appropriate to the company’s reporting process, with references and unresolved items identified rather than unsupported success claims.
- Explain the significant changes. Select the changes that affected the result and distinguish their causes. Connect scope decisions, access, procurement or delivery issues with the evidence instead of presenting a long chronology with no explanation.
- Describe the working relationships. Record what helped or hindered decisions with the client and consultants. Use specific communication or release examples, and separate a factual event from an interpretation about someone’s motives.
- Assess trades and suppliers fairly. Compare delivery with the agreed scope and expectations using checked records. Note circumstances, corrective action and unresolved disagreements. Avoid a simple favourable or unfavourable label unsupported by examples.
- Turn lessons into recommendations. Identify what the company should repeat, revise or investigate on a comparable project. Give each recommendation a responsible function and a follow-up route, including the estimating review where relevant.
- Handle people follow-up appropriately. Record team-development recommendations through the company’s authorized private process. Keep sensitive personal information out of broadly distributed project reporting and identify who receives the required follow-up.
Common mistakes
- Using the last forecast as a final actual result without reconciliation.
- Listing events without explaining their effect or the evidence.
- Making vague recommendations with no receiving owner.
- Putting sensitive personnel material in a report shared beyond its authorized audience.
Checklist
A final report worth keeping
- Checked results beside the original baseline.
- Significant causes with supporting references.
- Balanced relationship and delivery observations.
- Specific recommendations and receiving owners.
- Private people follow-up handled through the proper route.
Check your understanding
A proposed lesson says “avoid this supplier,” but the record includes a changed delivery date and an unresolved dispute. How should the report handle it?
