Lessons Learned Register

Phase: Closing | Audience: Internal | Project: WEB-2026-01 Corporate Website Development

Understand it first

In simple words: The Lessons Learned Register records what went well and what should be done differently next time, captured during the project, not only at the end.

Think of it like: After a family trip you note: 'book trains earlier next time; the homestay was great, use it again.'

When is it created?	Throughout the project; reviewed at closure
Who prepares it?	Project Manager with the team
Who approves or uses it?	Shared with the PMO
What happens next?	Used to improve future projects

How it connects to other documents

Many lessons come from the Issue Log and Risk Register.
L1 explains the cost problem seen in the EVM tracker.
Summarised in the Project Closure Report.

The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: Lessons captured throughout the project, not just at the end. Reviewed at the closure meeting and shared with the PMO.

Item	Detail
Document no.	WEB-2026-01/LL
Version	1.0
Date	30 Oct 2026
Owner	Project Manager
Audience	Internal
Phase	Closing

1. Register

ID	Category	What happened	Effect	Recommendation	Type
L1	Stakeholders	MD saw the home design only in round 2 and asked for a new layout	20 extra designer hours; cost went Red	Get senior approvers to review wireframes, not just final designs	Improve
L2	Client content	Services content came 3 weeks late	Placeholder text, rework risk	Make content due before design starts; include it in the payment milestone	Improve
L3	Estimation	Design estimate had no buffer for senior feedback	Overrun in the first month	Add 15% to design estimates when the approver is not in weekly calls	Improve
L4	Technical	Staging server blocked outgoing email	Form testing delayed	Check email capability when choosing hosting	Improve
L5	Commercial	30% advance before starting work	No cash risk in month 1	Keep the advance clause as standard	Went well
L6	Change control	Careers page request routed through a CR from day one	₹12,000 extra revenue; no scope creep	Explain the change process in every kickoff	Went well

WEB-2026-01/LL · v1.0 · Internal. Bracketed items such as [Client Name] are placeholders.

Key takeaways

Record both successes and problems.
Each lesson needs a clear recommendation.
Capture lessons when they happen, not months later.

Common mistakes to avoid

Blaming people instead of improving processes.
Writing lessons nobody reads.
Only recording negatives.

Next lesson: 39. Project Closure Report