Lessons Learned Register

A lessons learned register is a structured project document that records significant events — positive or negative — that occurred during a project, together with the root cause of each event, its impact on cost, schedule, quality or safety, and a concrete recommendation for how to handle the same situation better on future projects. It is the primary mechanism for transferring knowledge from one project team to the next.

A useful entry captures six things: the project phase in which the event occurred, the category it belongs to, a clear description of what happened and why it matters, the root cause that allowed it to happen, the impact it had on the project, and a specific and actionable recommendation that a future project team could follow. Vague entries such as "improve communication" without describing what broke down and exactly what to do instead have little practical value.

High means the event had a material effect on project outcome — a safety incident, a significant cost overrun, a major schedule delay, or a contractual dispute. Medium means the effect was notable but manageable. Low means the impact was minor and the lesson is worth recording as a prompt for good practice rather than a warning about a serious risk.

Lessons should be recorded as they occur, not accumulated for a closeout workshop. By the time a project reaches closeout, the team that experienced an event in the execution phase may have moved on, and the specific detail is already fading. Recording a lesson within days of the event produces a far more accurate and useful entry than reconstructing it six months later. The register should be reviewed at each phase gate and presented to the client at practical completion.

Root cause analysis is the process of identifying the underlying reason an event occurred, rather than describing only what happened. A foundation that required redesign is a symptom; the root cause might be that the geotechnical investigation scope was set before the alignment was finalised and never reviewed afterward. Capturing the root cause is what makes a lesson actionable — without it, a recommendation can only say "do better next time", which gives a future team nothing concrete to act on.

At the start of a new project, search the organisation's lesson register for entries relevant to the contract type, location, client and technical scope. High-severity closed lessons should be translated into specific actions in the project execution plan. Lessons that are still Open should be tracked as actions and assigned to named responsible parties with a target close-out date.

Use Save Register (.json) to download a file that preserves the complete register and can be reloaded later. Use Export Table (.csv) to download the visible rows in a format that opens in Excel. Use Generate Status Report (PDF) to open a formatted A3-landscape print preview — save it as PDF from the browser's print dialog to produce a document suitable for client submission or review meetings.

No. The register runs entirely in your browser. There is no account, no server component, and no data leaves your machine. Projects are saved as JSON files you download yourself, the CSV export goes to your own device, and the autosave option writes only to your own browser's local storage. Nothing is transmitted externally.