Should an Engineering Firm Document Lessons Learned From Its Mistakes?

Short Answer

Yes, most firms benefit from some process to document lessons learned, even though the concern about litigation risk is understandable. A record that explains what a firm changed after a problem generally differs from a record that admits fault on a specific project.

For many firms, the bigger risk is recurring problems that never get fixed because the knowledge stays informal and leaves when experienced people do. This is a risk-management question, not a legal one. A firm with specific litigation concerns should talk to counsel about how to structure its records.

What engineers said about repeating the same mistakes

A Reddit discussion among civil engineers asked a simple question: what mistake does your company keep making? The responses described organizational patterns rather than one-off errors. Several themes came up:

• Knowledge stays informal. One commenter said their company rarely documented mistakes or ran meaningful lessons-learned reviews, because employees worried the firm could face a written record later. Older employees would recognize a repeated problem, say something like “we did this on X too,” fix it, and move on. Newer employees never heard about it.
• The fix depends on the size of the failure. A few commenters said teams struggle to act on lessons unless the problem caused a major loss. If the team resolved it quickly, management had little incentive to spend money preventing a repeat.
• Specific technical examples came up. One commenter described roads over clay subgrade failing repeatedly when crews milled off too much existing pavement before resurfacing, which led to change orders for road repairs. Another described specifications copied from a previous project without review. In one case, a lift station in Oklahoma had specifications that still referred to New York, and the set reportedly reached issued-for-construction status that way.
• Commenters also blamed staffing and structure. They pointed to project managers asked to draft, design, and manage all at once, and to a lack of succession planning.

These are anonymous comments and personal experience, not verified guidance, and the specific examples above are as described by commenters, not confirmed facts.

Does documenting a mistake create legal risk?

This is a legal question, and the answer depends on the jurisdiction, the type of document, and how the firm creates it. Records created in the ordinary course of business can generally become discoverable in litigation. These include project files, meeting notes, and internal process changes.

Some organizations use specific processes and legal review to reduce that exposure for certain safety or quality assessments. Firms should confirm with counsel whether that applies to their lessons-learned process rather than assume it does.

Hardcover can speak to the risk-management and insurance side. That means how a firm's documentation habits, or the lack of them, tend to play out during underwriting and during a claim.

How does a lessons-learned process affect professional liability underwriting?

Underwriters ask about a firm's quality control procedures, and the answers can affect how they view the firm at renewal. A firm that can describe a real process for catching and fixing recurring problems, even briefly, looks different from one where the same mistake keeps happening because nobody wrote it down. Our article on why your professional liability application matters at renewal covers how underwriters use these answers.

A documented process doesn't need to read like an admission of fault. A useful version usually separates the general lesson from the specific project. For example, a note that the firm checks its specification template for project-specific references before reuse describes a process change. It doesn't describe what went wrong on a particular job.

How does the absence of documentation show up in a claim?

When a claim arises from a mistake that has happened before at the firm, one question tends to come up: did the firm know about the pattern, and what did it do about it? A firm with no record of the prior instances or the fix must rely on memory. That can be harder to work with than a clear, factual record, especially if the people involved have since left.

Our article on whether an engineer's emails can create professional liability problems makes a similar point about documentation generally. Informal or missing records often make reconstructing events after a claim more difficult.

Prior knowledge of a recurring issue can also come up on an application. Applications commonly ask about known circumstances that could lead to a claim, and the firm's history of addressing a known pattern can be part of that picture.

What a lessons-learned process can look like without adding risk

A few habits came up across the discussion and tend to hold up well from a risk-management perspective:

• Separate the general lesson from the specific project narrative. Record what changed in the process, not a detailed account of what went wrong and who was involved.
• Put lessons where new staff will actually see them, since several commenters described knowledge that stayed with senior employees.
• Review templates and go-by specifications for project-specific details before reuse, since outdated or mismatched language often carries forward.
• Decide with firm leadership, and counsel where appropriate, what level of detail belongs in an internal lessons-learned record versus a project file.
• Revisit the list periodically rather than only after a major failure, since several commenters said smaller recurring problems rarely get attention until something bigger happens.

None of these guarantee an outcome in a dispute. Firms generally describe them as good practice because they reduce the chance of a repeat and give the firm something concrete to point to later.

Example

A civil firm has resurfaced several roads over clay subgrade over the years. More than one project needed a change order after the remaining pavement failed under construction traffic. No one wrote this down as a pattern, and each project treated it as a one-off problem.

A new project manager, unaware of the earlier issues, mills the same amount of pavement on a similar road. The same failure happens again. The owner asks why the firm didn't account for it, given its experience with the same soil conditions in the area.

A short internal note describing the pattern, plus a design standard for minimum remaining pavement thickness over that subgrade, would have let the new PM catch the problem before bidding. Without one, the firm has to explain after the fact why prior experience didn't shape the design.

What to check

• Does your firm have any process for recording recurring problems, even an informal one?
• Where does that record live, and would a new employee actually see it?
• Does the record describe process changes, or does it read like a narrative of what went wrong on a specific project?
• Has your firm discussed with counsel how to structure these records for your jurisdiction?
• Does your renewal application ask about quality control procedures, and does your answer reflect what actually happens?
• Does your team review templates and specifications for project-specific content before reuse?

Hardcover insight

The Reddit thread describes something we see across firms of different sizes. The knowledge of what went wrong usually exists somewhere in the organization, but it doesn't travel. That gap matters most at the two moments a firm can least afford it: when a new employee repeats an old mistake, and when an underwriter or a claim asks what the firm knew and what it did about it.

A lessons-learned process doesn't need to be sophisticated to be useful. A short, factual, process-focused record serves a firm better than no record at all, and the firm can review it with counsel if it has specific concerns.

Related Questions

Can a lessons-learned document be used against a firm in a lawsuit?

It depends on how the firm creates the document, what it says, and the jurisdiction. This is a legal question, so firms with specific concerns should ask counsel how to structure their process.

Does quality control history affect a professional liability renewal?

It can. Underwriters commonly ask about QA/QC procedures, and the firm's answers may affect underwriting. Practices vary by carrier.

What's the difference between a lessons-learned note and a claim admission?

A lessons-learned note generally describes a process change going forward. A claim admission concedes fault for a specific incident. Firms concerned about this distinction should ask counsel how to draft internal records.

Should a firm document a mistake that never became a claim?

Many firms find it useful for preventing a repeat, separate from any insurance reporting question. Whether the firm should also report a specific incident to a carrier is a different question tied to the policy's notice provisions.

More on This Topic

Can a Civil Engineering Mistake Become a Professional Liability Claim?

A small civil engineering error can create a much larger project loss. Here is how professional liability insurance may respond

Can an Engineer's Emails Create Professional Liability Problems?

Worried a routine email could come back to haunt you in a professional liability claim? Here's how project documentation actually gets used when a claim happens, and what habits reduce that risk.

Why Your Professional Liability Application Matters at Renewal

Think your professional liability application is just a formality? Here's why what you report each year can shape your premium, and why

Author:

Hardcover Editorial Team

Reviewed by:

Hardcover Insurance Team

Last reviewed:

September 22, 2026

This article is educational and does not provide legal advice or determine whether a specific claim is covered. Policy terms, exclusions, underwriting requirements, and applicable law vary. Consult your insurance professional and qualified legal counsel regarding your circumstances.

Source discussion:

insurance for Owner's Rep?