When a design error surfaces in the field, most owners reach for the same reassurance: the architect carries errors and omissions insurance, so someone's covered. That's true, as far as it goes — but the cost of design errors and omissions on an active project rarely shows up as a single insurable event. It shows up as an RFI, then a stop-work while the field waits for an answer, then a change order, months before anyone's E&O carrier is even on the phone.
That gap between what E&O insurance is built to do and what actually happens on a live job is worth understanding before you need it, not after.
What E&O insurance actually covers
Design professional errors and omissions coverage — sometimes called professional liability insurance — pays out when a design error or omission causes a client financial loss and the architect or engineer is found liable. It's built to cover exactly what its name says: a mistake in the design itself, or something that should have been included and wasn't.
Most policies also include rectification language, letting the firm submit a proposed fix for a design flaw and get reimbursed for correcting it rather than only paying after litigation. On paper, that sounds like it closes the loop. In practice, it closes a different loop than the one an owner is standing in when a duct routing conflict shuts down a floor.
What it doesn't cover — and when it doesn't apply
Three mechanics in a typical E&O policy matter more to an owner than the coverage amount on the certificate:
- Claims-made structure. Nearly all architect and engineer professional liability policies are written on a claims-made basis, not an occurrence basis. That means a claim only has coverage if it's first made and reported to the insurer while a policy is actually in force — not simply if the error happened during a covered period.
- The retroactive date. Every claims-made policy carries a retroactive date, and an error that occurred before that date isn't covered even if the claim is reported during an active policy term. Design defects can go unnoticed for years; if the firm has switched carriers, let coverage lapse, or set a retroactive date after the work in question was performed, a legitimate claim can fall into a gap nobody flagged until it mattered.
- Exclusions and delegated design. Policies vary significantly carrier to carrier, and common exclusions include subcontracted or delegated professional services — meaning a structural or MEP engineer working under the architect's contract may not be covered by the architect's own policy at all.
A claim against a claims-made policy has to satisfy three conditions at once: an active policy in force when the claim is made, a retroactive date that reaches back to when the design work was actually performed, and timely notice given to the insurer within the policy term. Miss any one, and the coverage an owner assumed was there isn't.
Policy limits matter too — both per-claim and aggregate — and defense costs typically erode those limits rather than sitting outside them, meaning a long legal fight can shrink what's left to actually pay a claim before the claim itself is even resolved.
The cost of design errors and omissions doesn't wait for a claim
Here's the part an E&O policy was never built to touch: the cost of design errors and omissions on a live project is realized in real time, long before any insurance claim gets filed. A missed clash between a duct run and a structural beam doesn't wait for a claims adjustor — it stops the crew, generates an RFI, and sits on the schedule until someone resolves it. That's a documented pattern we've written about before in how a single missed MEP clash turns into a $400K change order — the exposure compounds the longer the conflict sits unresolved on an active floor.
E&O insurance, when it applies, settles a dispute over who pays for a mistake that already happened. It doesn't return the weeks lost to a stalled sequence, and it doesn't un-happen the change order that already went through the field. Insurance is a recovery mechanism for after the fact. It was never a substitute for catching the conflict before it reaches the field at all — which is a different problem, solved by a different kind of review, at a different point in the timeline. We've laid out the actual math on that exposure in change order math: calculating real exposure before you bid, and the gap in who's actually checking for it in what architect QC covers — and where an owner-side review picks up.
What to ask your architect and engineer about their E&O policy
An owner asking these questions before a contract is signed isn't being adversarial — it's basic diligence on a risk that's otherwise invisible until it isn't:
Questions worth asking before you need the answer
- What are the per-claim and aggregate limits, and do defense costs erode those limits or sit outside them?
- What's the retroactive date on the current policy, and does it reach back far enough to cover the design work being performed on this project?
- Does the policy exclude subcontracted or delegated design work — and if so, do the structural, MEP, or other consulting engineers carry their own separate coverage?
- Will the firm maintain continuous, uninterrupted coverage through the full life of the project, including the period after substantial completion when latent defects are most likely to surface?
- What's the deductible or self-insured retention, and who is actually responsible for that amount if a claim is paid?
None of these questions are unusual to ask, and a firm with a well-structured policy will have straightforward answers. The point isn't to distrust the architect or engineer of record — it's to understand exactly what's protected, and to recognize that "the architect has insurance" is not the same statement as "the set is coordinated."
Where independent review fits
Insurance and independent review solve two different problems, and conflating them is where owners get exposed. E&O coverage exists to allocate financial responsibility after a design error causes a loss and gets litigated or settled — a process that plays out over months or years. An independent, cross-discipline document review exists to catch the coordination conflict before it ever reaches the field, while it's still a markup on a drawing and not a change order in progress.
That's also the distinction behind why a set that already passed the architect's own QA/QC can still carry costly conflicts — QA/QC checks a firm's own work against its own standards, not against every other discipline's drawings at once, a gap we cover in why "it passed QA/QC" doesn't mean the set is coordinated. An owner who confirms strong E&O coverage and treats that as the whole risk picture has covered the recovery side of the equation and left the prevention side untouched.
Frequently Asked Questions
Does E&O insurance cover the cost of construction delays caused by a design error?
Generally not directly. E&O insurance is built to cover the design professional's liability for the error itself, not the owner's downstream schedule losses, though those losses can sometimes be included in a settled or litigated claim. The schedule impact happens in real time on the project; any insurance recovery, if it comes, happens much later.
Who pays for a design error if the architect's E&O claim is denied?
If a claim falls outside the policy's retroactive date, hits an exclusion, or exceeds the policy limits after defense costs, the remaining exposure typically falls back on whichever party the contract assigns it to — often the owner, unless the contract documents specifically shift that risk elsewhere.
Is a structural or MEP engineer automatically covered under the architect's E&O policy?
Not necessarily. Delegated or subcontracted design work is a common exclusion in architect professional liability policies, which is why it's worth confirming that consulting engineers carry their own separate, adequate coverage rather than assuming the architect's policy extends to them.
How long after a project finishes can a design error still trigger a claim?
That depends on the applicable statute of limitations or repose in the project's jurisdiction, and on whether the firm has maintained continuous claims-made coverage with a retroactive date reaching back far enough to cover the original work. Latent design defects can surface years after substantial completion, which is exactly why continuous coverage matters more than a single project-year policy.
What's the difference between a duty to defend and a duty to indemnify in an E&O policy?
A duty to defend obligates the insurer to pay for legal defense once a claim is made, regardless of the claim's outcome; a duty to indemnify obligates the insurer to pay a judgment or settlement if the insured is found liable. Many professional liability policies fold defense costs into the same limits used to pay a claim, which is why understanding that structure matters before a dispute starts eating into what's available to actually resolve it.