The Liability You Didn't Price: Code Compliance, Zoning, and the AIA B101 Gap

When Nantucket Cottage Hospital opened in early 2019, its $89 million new building couldn't get full Medicare and Medicaid licensure. The reason was a material choice. The exterior walls had been clad in cedar shingles to satisfy the island's Historic District Commission, and those shingles violated fire safety code. In July 2023 the hospital sued its architect, CannonDesign, for $8 million, alleging breach of contract, negligence, and malpractice.

That is the bind in one project. One government authority wanted the shingles. Another called them a hazard. The design satisfied the first and tripped the second, and the liability landed on the design team, not on either authority that set the rules.

Most architects assume two things stand between them and that result. First, the standard of care: you're only liable if you fell below what a reasonable architect would have done. Second, that zoning and entitlement are the owner's problem, not yours. The contract you sign and the case law built on it contradict both. The document turns code compliance into something close to strict liability on one axis, and leaves you silently exposed on the other.

The clause you signed says "comply," not "do your best"

The AIA B101 owner-architect agreement, in its 2017 form, requires the architect to "design the Project to comply with all applicable federal, state and local laws, statutes, ordinances, codes, orders, rules and regulations" (§3.1.5). Read that verb. It isn't review, and it isn't take into account. It's comply.

The distinction is not academic. Elsewhere in the same agreement, §3.2.1 asks the architect to "review laws, codes, and regulations applicable to the Architect's services," a review obligation measured against professional judgment. So B101-2017 carries both verbs: a review duty in schematic design and an absolute comply duty in the general obligations. One sets a standard you're judged against. The other sets a result you're on the hook for.

A Florida appellate court drew that line in the cleanest case on the books. In School Board of Broward County v. Pierce Goodwin Alexander & Linville, an architect renovating a high school proposed an alternative to a code-required emergency exit staircase. A peer reviewer had flagged the requirement.

The school district accepted the alternative, and the parties negotiated for months before bid. After construction began, the building official rejected the design and required the staircase. A costly change order followed.

The architect lost. Not because it fell below the standard of care. The court reached the result through the contract language, which obligated the firm to comply with "any and all applicable codes, laws, ordinances." As Kent Holland's analysis of the ruling put it, the parties had "unambiguously allocated to the architect the risk for costs and expenses attributable to design plans that were not code-compliant." The express provision set a heightened duty, and the firm had to perform to the contract, not to the profession's general standard.

That is the trap in its purest form. You can do what a reasonable architect would do and still lose, because the words on the agreement promised a result, not an effort.

Code claims are easy to bring and expensive to lose

A negligence claim against an architect usually needs an expert. Someone has to testify about what a reasonably prudent architect would have done in the same locale, time frame, and facts. That requirement is a filter. It raises the cost of bringing a claim.

Code-compliance claims often skip the filter. In Lillibridge Health Care Services v. Hunton Brady Architects, a medical office building in Celebration, Florida ran a surgical center and physician offices off a single air handler, a code violation. The owner sued the architect and its engineer.

The federal court denied summary judgment and ruled that expert testimony wasn't required to establish the standard of care, because code noncompliance is a relatively objective question. The code is the standard. Either the design met it or it didn't.

That ruling carries a second sting. The HVAC work was the engineer's, a subconsultant to the architect of record. The architect was on the hook anyway. The exposure runs through the contract, and a subconsultant's code failure becomes the prime's problem.

The Berkley Design Professional Claims Benchmark Report, published March 2026, puts numbers behind that mechanism. Architects show above-average claim frequency, much of it tied to vicarious liability for subconsultants. Only one-third of architectural claims involve subconsultants, yet those claims account for 45 percent of total claim dollars.

The report also names the worst contractual posture: client-drafted contracts and verbal agreements produce the greatest risk, while firm-drafted standard contracts produce the best outcomes.

What does a single code miss cost? Berkley's published claim scenarios put the figure in seven digits. Take a setback error at a multifamily project. A surveyor used outdated plans, deep foundations and first-floor structure went in at the wrong location, and the completed work had to come out. That drew a $1 million insurer payment plus more than $100,000 in defense costs. An egress-window failure on an apartment building, where 200 windows didn't meet code after the building type changed mid-project, ran $900,000.

Those are not catastrophic outliers. They are routine code misses at ordinary multifamily projects, and they cost more than most firms net in a year.

A duty your policy may not fully cover

Here is the part that should change how you read the next agreement on your desk. The "comply with all" clause may obligate you to something your professional liability policy doesn't fully reach.

Errors and omissions (E&O) coverage is built around the standard of care. It defends and indemnifies negligence, the failure to meet professional judgment. When a contract raises the duty above the standard of care into an absolute promise to comply, it can push part of that obligation outside what the policy was written to cover. JCJ Insurance's analysis is direct: a "comply with all"-type clause "elevates an architect's professional standard of care beyond what is typically insurable," and the language should be replaced with words like "take into account" or "review."

Read that against Broward. The contract created a duty the architect had to honor, and the duty was the kind insurers warn does not sit cleanly inside a standard policy. Government and institutional owners routinely insist on this language, because it shifts risk to the design team. Many architects sign it without registering that they may be promising a result on their own balance sheet, not their carrier's.

The contract is the source of the exposure. That is the unwelcome news and the manageable news at once. A duty created by words on a page is a duty you can read, price, and negotiate before you sign, if you know to look.

The zoning frontier: outside Basic Services by design

Code compliance is the litigated half of the trap. Zoning and entitlement are the half nobody has fully tested yet, and the gap there is wider.

The B101 doesn't make full zoning investigation or entitlement feasibility a Basic Service. The owner furnishes the survey, the geotechnical report, and the legal description. The 2017 revisions widened the separation. The changes moved site evaluation and planning into Supplemental Services (§4.1.1.5), removed the architect's earlier obligation to consult governmental authorities "at appropriate times," and added §4.2.1.3, which makes governmental-required changes after compliant documents are submitted into Additional Services. Full site evaluation and project feasibility live in a separate agreement entirely, the AIA's Site Evaluation and Planning document, not in B101 Basic Services.

So zoning is contractually the owner's problem. In practice, the blame lands on the architect anyway.

The closest the industry has come to testing this is 200 Amsterdam Avenue, a 52-story Manhattan tower. In February 2020 a New York Supreme Court justice found the building's permit had been issued in error and ordered roughly 20 floors removed from an almost-finished building. The flaw was in the zoning lot itself: a "gerrymandered" 39-sided parcel assembled from partial tax lots of a neighboring superblock to generate floor area that wasn't otherwise available.

The design team was never sued. The Appellate Division reversed the ruling on March 2, 2021, and the building stands. But the malpractice question surfaced in public commentary the moment the demolition order came down. The exposure exists. The zoning entitlement, not the building code, determines whether the floor area you designed is even legal. The contract pushes that piece off your scope while leaving you holding the design that depends on it.

A clean architect-liability ruling on a pure zoning failure hasn't landed yet. That is not reassurance. It's the part of the map marked unexplored. The dimensional decisions that drive a project, height, setback, lot coverage, the floor area that pencils the deal, all sit downstream of an entitlement read the contract says isn't your job. For the layered version of that stack, see our piece on the five-rulebook stack on every property, where base zoning, overlays, PUD terms, plat notes, and deed restrictions each impose their own dimensional limits.

The schematic-design trap

The exposure rarely arrives through a signed engagement to study zoning. It arrives quietly, during schematic design, when you just check.

A site comes in. You want to know what fits, so you pull the zoning map, eyeball the setbacks, sketch a massing against a height limit. Reasonable. It's how design starts. The moment you put a dimension on paper that depends on a setback or height limit you read informally, you've taken on the risk of that reading being wrong. For free, outside any scoped service, with no documented diligence behind it.

Walk it through. A mid-rise on an infill lot, schematic phase. The setback looks like 25 feet from the rear line, so you design to it. What the quick map check missed: a recorded plat note imposing a 50-foot setback from the southern property line, which supersedes the code minimum.

The building you sketched, refined, and carried into design development sits 25 feet inside a line that governs. Nobody scoped the entitlement read. You did it informally, at no charge, and now the deep foundations are placed against a line that doesn't hold, the same fact pattern as Berkley's $1 million setback claim.

Code constraints compound the same way once disciplines interact, fire, structural, mechanical, accessibility, the technical mirror of this liability problem and the subject of how Austin's regulations collide across disciplines. The pattern is identical: a constraint you didn't fully map at the start surfaces after the design has hardened, when changing it is most expensive.

The recent cases all share that timing. Air Albany, a $38 million luxury apartment project in Albany, stalled mid-construction in 2023 after a fire-safety review found the exterior walls lacked fire-retardant framing. By May 2025, with the permit expired and $14 million in city tax exemptions at risk, the developer sued the architect for at least $2.5 million. Nantucket, Broward, Lillibridge, Air Albany: the constraint was knowable up front and surfaced too late.

What you control

The exposure is contractual, which means two things the architect controls decide it: the words on the agreement and the diligence behind the drawings.

Read the compliance clause in your next owner-architect agreement before you sign. Know whether it says comply or review, because Broward shows the two words carry different legal weight and JCJ shows one of them may reach past your coverage. If zoning or entitlement work matters to the project, and on any site where dimensions are tight it does, scope it explicitly in its own site-evaluation engagement rather than absorbing it for free during schematic design. Get the owner's zoning representations in writing, and document what you relied on, so that a reading that turns out wrong is the owner's, not your uncompensated guess.

None of that requires perfection in design. It requires knowing the constraints before the design depends on them.

That is the real line between the architects who get burned and the ones who don't. Not talent, and not luck. The ones who don't get burned walk into a project already holding a complete, documented read of the site at the outset: its zoning, its entitlement, its code constraints, mapped while there is still time to design against it and before any exposure has attached.

Their drawings stand on diligence they can point to. The ones who get sued reconstructed that read informally, in pieces, after the design had already committed to it. The cedar shingles were already on the walls, the floors already framed, the staircase already missing. By the time the constraint announced itself, the only options left were the expensive ones.

The constraint is always knowable at the start. The question is whether you know it then, or find out the way Nantucket did.