Guide

Construction lessons learned register: a practical guide

A lessons learned register is only useful if the next crew actually sees the lesson in time. Here's a practical way to run one on construction projects. What to capture, how to store it, and how to make sure it gets reused on the next job.

What is a lessons learned register?

A lessons learned register is a running log of the things a project team wishes they had known earlier. A wall that leaked, a detail that turned out to be ambiguous, an access sequence that cost two weeks. On construction projects it usually lives across a mix of site diaries, defect trackers, close-out reports and someone's inbox. The register's job is to pull those signals into one place so they can be reused, not just archived.

What to capture in each entry

• The job and location. Which project, which trade, which part of the works.
• What happened. One or two sentences in plain language. The actual event, not the polished version.
• Root cause. Why it happened, at the level of the design or the sequence. Not just "the sub was slow".
• The lesson. The specific thing to do differently next time. This is the part that has to survive to the next job.
• Scope link. Which trade or scope line this lesson should surface against next time.
• Cost or time impact. A rough number if you have one. It's what makes people care.

A simple lessons learned template

If you're starting from scratch, a template with the fields above in a shared spreadsheet is enough for the first few months. Keep the entry short, one screen, and require the scope link. Without that link, the register turns into a reading list nobody opens.

Capture on site, in about 30 seconds

The barrier to a useful register isn't the format. It's the friction of logging. Site engineers won't stop and write a paragraph. Give them a fast path: dictate the event, tag the trade, tag the scope line, done. Anything longer than a minute quietly stops happening after the first busy week.

The reuse problem

Most construction lessons learned registers fail at reuse, not capture. The register exists, but the team on the next job has no way to see the relevant past lesson at the moment they hit the same problem. By the time someone remembers to search, the decision has already been made.

The fix is to surface the lesson inline, against the exact scope line it relates to, so the next crew sees it without searching. That's what Margin is built to do.

From register to next job

A working loop looks like this: engineer logs the lesson on the job against a scope line → the lesson lands in the company register → next time anyone opens that same scope line on a new project, the lesson appears next to it. The same mistake stops happening twice.