Who Is Responsible When a Senior Engineer Fails to Review a Junior Engineer’s Design?

Short Answer

When a senior engineer fails to review a junior engineer's design, responsibility generally lands on the firm and the licensed engineer who was supposed to check and seal the work. The junior engineer who raised concerns and followed instructions usually carries less of it.

This is a firm-level QC failure more than an individual mistake. On the insurance side, the firm's professional liability policy usually responds if the redesign or the underlying error leads to a claim. The firm's review practices can also affect how underwriters view it at renewal.

What engineers said about a senior engineer who didn't review the work

A widely discussed Reddit thread described a junior structural engineer working on a multi-story CMU building under a senior engineer. The junior told the senior directly that they had little experience with complex CMU design and did not feel confident starting the project. The senior still gave minimal guidance, so the junior did most of the design. The senior only glanced at the work after it had gone into the drawings.

The design looked fine until construction started. Then RFIs began arriving, problems surfaced, and the firm ran extensive checks. The result was a full redesign at significant cost to the company. The senior engineer quit partway through, which left the junior holding the project.

What commenters focused on

Commenters focused less on the junior's mistakes and more on what went wrong above them:

• Responsibility sits with the reviewer, not the junior. Several commenters noted that the junior had already flagged their inexperience, so the senior’s job was to check and guide the work. One commenter put real weight on the person who sealed the drawings. They said sealing structural work without adequate review raises serious professional concerns given the stakes.
• This reads as a QC failure, not a personal one. One commenter walked through the sequence of events. An inexperienced junior disclosed their inexperience and received minimal guidance. No meaningful review followed, and the drawings went to construction. RFIs exposed the problems, and an expensive redesign followed. The commenter concluded that the company was paying for its own QC failure.
• A second reviewer should have caught this. Multiple commenters said complex structural drawings should never go out without a second set of eyes, whoever designed them.
• Documentation came up repeatedly. Commenters asked whether the junior had emails or messages showing they flagged their inexperience and the lack of review. More than one warned that without that record, the junior could take the blame.
• Similar stories were common. One commenter described inheriting a project barely a year out of school. A peer review caught a seismic loading error in a spreadsheet after the crew had poured the foundations. The correction took about six weeks, cost the company a large sum, and led to a lawsuit and a lost client.

Treat these as anonymous comments and personal accounts, not verified guidance.

Does the junior engineer carry any responsibility?

That is ultimately a legal question that depends on licensing rules, the firm's structure, and the facts. One distinction came up repeatedly in the discussion: competence is task-specific. A junior engineer can be fully competent at their usual work and still lack the experience to handle a complex design independently. Review procedures exist for exactly that situation.

A junior who disclosed their inexperience and did the work as directed stands in a very different position from one who concealed a problem or ignored instructions. Firms and individuals concerned about how others might view a specific situation should raise it with counsel rather than rely on general guidance.

Why does responsibility usually center on the reviewing engineer?

The engineer who reviews and seals a design generally takes professional responsibility for it, including work a supervised employee prepared. State licensing rules on direct supervision vary, but the underlying expectation stays consistent. A stamp should reflect a real review, not a signature added after the drawings are finished.

When that review doesn't happen, the firm loses one of its main safeguards against exactly this kind of problem. Our article on what happens after stamping someone else's design and an error gets through covers this scenario from the stamping engineer's side in more detail.

How does professional liability respond when a QC failure like this leads to a claim?

A claim can come from the redesign cost, a contractor's added expense, or an owner's loss. A few points shape how the firm's policy responds.

Who the claim targets. Someone typically directs a claim like this at the firm, since the firm holds the contract and the policy. The firm's policy commonly insures employees acting within their duties, including the junior engineer, though definitions vary by carrier.

The firm's own redesign cost. Policies generally treat time spent fixing the firm's own design as a business cost. Many limit or exclude coverage for redoing services.

Third-party damages. A contractor or owner may suffer added costs, delay, or other losses from the design problems. The policy is generally designed to respond to claims for those damages, subject to the limit, deductible, and exclusions.

Defense costs. Many policies include a duty to defend. The policy form determines whether defense costs reduce the limit and whether the deductible applies to them. A claim like this can require a real defense before anyone decides who bears responsibility.

Claims-made timing. Most professional liability policies are claims-made and reported. Coverage therefore depends on when someone makes and reports the claim, plus the retroactive date. The firm's policy generally still responds if the senior engineer who reviewed the work has left. The departure can complicate the facts the firm needs to reconstruct.

Policy terms, exclusions, and underwriting vary by carrier, and coverage always depends on the actual facts and the policy in force.

Does a QC failure like this affect underwriting at renewal?

Often, yes. Underwriters commonly ask how a firm reviews complex or unfamiliar work. They also ask whether junior staff receive meaningful oversight and whether a second qualified engineer checks work before sealing.

A firm that has absorbed an expensive redesign from a review gap should expect those questions at renewal. Our article on why your professional liability application matters at renewal explains how firms should think through those answers.

Example

A structural firm assigns a junior engineer to a multi-story masonry building. The junior tells their supervisor they have never designed anything this complex. The supervisor, busy with other projects, gives brief direction and reviews the calculations after they enter the drawings.

Construction begins, and the contractor's RFIs start surfacing inconsistencies in the lateral system. The firm pulls in another senior engineer to check the design. That engineer finds several errors serious enough to require redesigning major portions of the structure. The added engineering time and the contractor's cost to rework installed elements become a dispute involving the firm and owner.

The firm reports the matter to its carrier. The carrier's questions focus on what the original reviewing engineer actually checked. They also cover what the firm's QC procedure required. Records showing the junior engineer raised concerns before the design went out matter too.

The firm's own cost to fix its design likely counts as a business expense rather than a covered loss. Whether the policy responds to the owner's added costs depends on the policy wording, the contract, and the facts.

What to check

• Does your firm have a written QC procedure for complex or unfamiliar work, and does the team follow it?
• Does a second qualified engineer review structural calculations before they go into construction drawings?
• Are junior staff’s disclosures about their experience level documented anywhere?
• Does your policy define employees, including junior staff, as insureds?
• What is your retroactive date, and how does the policy treat claims tied to a departed employee’s work?
• Does the policy limit coverage for redoing the firm’s own design work?
• What are your limit, deductible, and the policy’s treatment of defense costs?

Hardcover insight

This situation tends to repeat the same pattern. A firm hands an inexperienced engineer complex work, the engineer flags the mismatch honestly, and the reviewer offers a light check instead of real supervision. The gaps surface once the design reaches construction. The firm then faces the cost of the fix and the harder question of what its review process actually caught.

Two things make a real difference here. First, a genuine second review catches problems while they're still cheap to fix, unlike a glance after the drawings are done. Second, a habit of documenting when junior staff flag their limitations protects everyone. It gives the firm an accurate record of what it knew and when. That record matters far more during a claim or renewal conversation than anyone's memory of a hallway conversation.

Related Questions

Is a junior engineer personally liable if a senior engineer didn't review their work?

That depends on licensing rules, the firm's structure, and the facts. Firms and individuals with specific concerns should speak with counsel rather than rely on general guidance.

Does professional liability insurance cover the cost of redesigning a flawed structure?

Generally, the policy treats a firm's own cost to redo its design work as a business expense. Third-party damages from the error more likely fall under the policy, subject to its terms.

What happens to a claim if the engineer responsible for reviewing the work has left the company?

The firm's policy generally still responds to a claim, since it covers the firm rather than any one individual. The departure can make gathering facts and documentation harder.

Should a junior engineer document that they raised concerns about a project?

Many engineers in the discussion said yes. A written record can clarify what was known and by whom if the project runs into problems later. This is a practical recommendation, not a legal one.

More on This Topic

What Happens After Stamping Someone Else’s Design and an Error Gets Through?

When a designer's error gets past the engineer who stamped the drawings, responsibility rarely stays with one person.

If You Stamp Engineering Drawings, What Liability Are You Actually Taking On?

If you're a PE starting to stamp engineering drawings, your insurance depends on how you work, who employs you, and whether you

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?