Architect Insurance: The 2026 Liability Playbook

Most architects meet commercial insurance not by asking “what’s my risk?” but by finding a coverage requirement inside an agreement they need to sign. The design agreement asks for professional liability at named limits. The general contractor asks for a certificate before granting site access. The state board requires a written contract before you can practice. By the time you are reading policies, most of what you will carry has already been decided by the people whose signatures you need.

That reframe is the point of this playbook. It is not a catalog of what each policy does — that work belongs on the sister library, isthiscovered.org. This is the professional liability map: five exposures that actually generate claims at an architecture practice, who can assert each one, and which line of coverage is supposed to answer it. The decisions left to you are narrower than the brochure suggests, and they are the ones that matter.

Where these hit your timeline. Few appear at licensure. They attach to milestones.

Milestone	What enters	Why then
Solo practice, no signed contracts	Defer most coverage	No project counterparty is demanding anything yet
First client engagement signed	Professional liability (E&O)	The design agreement’s insurance clause conditions the work
First job-site or construction-administration work	General liability	Site exposure activates; the owner or GC demands it
Engaging subconsultants	Indemnity / subconsultant exposure	A subconsultant’s error can flow back to the architect of record
Client or project data handled	Cyber	Plans, records, and payment data create a breach path
First hire	EPLI exposure	Every employment decision becomes a potential claim — and nobody requires it

1. A design or construction-administration error costs the client money

The client relied on your plans, the building did not perform, and they say it cost them money. They sue. This is the central exposure of an architecture practice, and the coverage that answers it is professional liability — architects E&O. It pays to defend and settle claims that your professional service failed: a missed code requirement, a defective specification, a coordination error between disciplines, or a lapse in construction administration.

The claim runs through the standard of care. The AIA frames a professional-negligence claim as duty, breach, actual damages, and causation — the architect owed a duty, fell below the profession’s standard, and the breach caused legally recognized loss. An unhappy client is not automatically a valid claim; the claimant still has to connect the professional act to the damage. The NCARB Competency Standard makes the exposure concrete by naming the workstreams that generate allegations: scope, schedule, budget, building-system coordination, construction documentation, and construction-phase services. Those are the decisions a plaintiff will second-guess.

What makes this one non-optional is the contract itself. The California Architects Board requires a written contract for architectural services, and most client agreements carry an insurance clause that names professional liability at a stated limit. That number is the floor, not a suggestion. For the form to answer, read whether its definition of “professional services” matches the scope you signed — design-only, specifications, site observation, and construction administration are not always treated the same way by every form.

2. A construction defect, job-site injury, or property damage occurs

A worker is hurt during site observation, a firm employee damages property on the job, or a defect in the finished building causes physical harm. The coverage is general liability for bodily injury and property damage to third parties.

What trips architects is the line next door. Economic loss from a design error — the client’s financial harm without bodily injury or property damage — is a professional-liability matter, not a general-liability claim. General liability does not turn a client’s financial loss into a covered claim. A bad specification that inflates construction cost, or a coordination failure that forces rework, sits on the E&O side. The boundary between the two is read from the policy, not assumed, and a construction-defect claim can pull both lines into the same dispute.

In practice you carry general liability because the project demands it. Owners and general contractors require it before site access, commonly at named per-occurrence limits, and name themselves additional insured. The premises exposure at your own office rides on the same line.

3. A subconsultant’s negligence comes back to you

You engaged a structural engineer, an MEP consultant, or a soils engineer, and their work was deficient. The owner sues you as the architect of record because you coordinated the team and stamped the package. This is vicarious liability — exposure to someone else’s professional act — and it is the exposure that separates a solo practitioner from a firm that leads a design team.

The AIA’s guidance on indemnifying subconsultants states the risk plainly: an architect may face vicarious liability for a subconsultant’s negligence, and the indemnity and defense wording in the subconsultant agreement should be checked with the insurer. California Civil Code §2772 defines indemnity as a contractual promise to shift loss from one party to another, which means the words in your subconsultant agreements decide who pays when the engineer’s error becomes your lawsuit.

Two details earn the attention they rarely get. First, whether your E&O form covers the subconsultant’s work at all — many architect policies cover only the firm’s own professional acts, not the acts of independent consultants, unless endorsed. Second, whether your upstream contract with the owner makes you responsible for subconsultant negligence in language broader than the service you actually performed. A contract that shifts every project loss to the architect can create an obligation no standard policy satisfies.

4. Client or project data is breached

Ransomware, a vendor failure, or a privacy misstep exposes the plans, client records, or payment information you held. Two paths hit you at once, and that is what makes this exposure different from a design claim. Your client can sue or demand proof of coverage under the design agreement — but your state’s attorney general can also act under state privacy law, whether or not any client complained. The contract is one trigger; the statute is another.

The coverage is cyber. The distinction that matters is first-party versus third-party. The cost of your own forensic, notification, and ransomware response is first-party cyber; the lawsuits that follow a breach of project data sit on the third-party side. A standalone E&O form leaves the first-party side bare, which is why many design firms carry cyber separately. The mechanics of what cyber responds to live on the sister library, isthiscovered.org.

5. An employment claim surfaces

Your first real termination, a reduction in force, or a dispute over whether a draftsperson was misclassified. The former worker — or a candidate you never hired — alleges discrimination, harassment, or retaliation. The coverage is EPLI.

This one is unlike the others, and the difference matters: nothing requires it. No statute, no client, no owner demands EPLI. It is a judgment call, and that is exactly why it is underbought. The exposure starts at employee one, because every hiring, pay, discipline, and termination decision is a potential claim that none of your other policies will answer — general liability, E&O, and workers’ comp all exclude employment acts. The EEOC identifies retaliation as the most frequently alleged basis of discrimination, which compounds quietly: whatever you do after an employee complains can become a second claim even when the first fails. The policy’s most-used benefit is paying for a defense that ends in no finding of wrongdoing.

The decisions that are actually yours

Strip away the requirements and a pattern emerges across the five. The same three questions decide almost every line, and buyers conflate them constantly:

Exposure	Legally required?	Someone will require it?	Prudent even if not?
Professional liability (E&O)	No (contract-driven)	Yes — owner / design agreement	Yes, before any stamped work
General liability	No	Yes — owner or GC for site access	Premises and job-site exposure
Subconsultant indemnity	No	Yes — owner upstream contract	Yes, the moment you lead a team
Cyber	Partly — state privacy law	Sometimes — client contract	Yes, if you hold any project data
EPLI	No	Rarely	Yes, at your first hire

Those are different reasons to buy the same policy, and they point at different limits. The genuine decisions — the ones a brochure will not make for you — are narrower still. Size limits against your worst single exposure, not a generic tier. The floor is whatever your largest contract demands; the sanity check is the most plausible loss from one design failure, defense costs included. Read the claims-made trigger before you switch carriers. Architect E&O is written claims-made, and projects span years, so a changed retroactive date or a lapsed policy can open a gap over design work performed long ago. Decide who indemnifies whom when you engage a subconsultant, because a one-sided indemnity clause can push a subconsultant’s error outside your coverage.

A short checklist

1. Signed a design agreement → read the insurance clause; the E&O limit it names is your floor.
2. First site access requested → confirm the general-liability limit and the additional-insured endorsement the owner or GC demands.
3. Engaging a subconsultant → match the indemnity wording to your E&O form before the subconsultant starts.
4. First hire → get an EPLI quote and decide on numbers, not on category.
5. Renewing or switching carriers → check the retroactive date and prior-acts language before you replace a policy.

---

Sources are linked below. This playbook frames the liability exposures; the coverage mechanics — forms, certificates, mandates, claims — are on isthiscovered.org, and each exposure above links to its own question page for the sourcing behind the claim.