Short answer
A well-written architect exclusions section can strengthen your position when a client says a service should have been included. It shows in writing what your firm agreed to provide and what it didn’t. It can’t guarantee you won’t be sued, and how a claim is handled still depends on your policy wording and the facts. Many of the disputes we reviewed began with a client’s assumption about scope rather than a design error.
Why an architect exclusions section matters
Small firms doing residential and light commercial work often write short, friendly contracts. Clients tend to read them quickly and fill in the gaps themselves. If the contract says nothing about civil or structural engineering, a client may assume the architect handles it.
An architect exclusions section removes that guesswork by naming the services your firm won’t provide and who is responsible for them instead. When a dispute comes up, you can point to the signed document rather than relying on anyone’s memory of a conversation.
The scenarios below are anonymized composites based on real claim files. Project types and details have been changed.
Three scenarios where scope language made a difference
Scenario A: The client skipped the civil engineer
A small firm took on a change-of-use retail renovation of about 2,000 SF. The client also acted as his own contractor. The contract excluded civil engineering, and the architect recommended hiring a civil engineer at the start.
The client declined and said an AI chatbot told him he didn’t need one. Later, the city’s zoning review required a site and civil package. The client then demanded free redesign work with a 24-hour turnaround. He threatened to terminate the contract, demand a full refund and file a licensing board complaint.
The firm reported the situation right away and didn’t admit fault or offer money. The exclusion and the original recommendation were both in writing.
Other firms can put every recommendation for an outside consultant in writing, not only in conversation. It also helps to check whether your policy responds to licensing board complaints, since coverage for those varies. Our article on how project emails can become part of a claim explains why written records matter.
Scenario B: Structural was excluded and the client blamed the architect anyway
A two-principal firm took over a residential renovation that another architect had abandoned. The contract excluded structural engineering. The client never hired a structural engineer, the permit was issued and work began. Then work stopped, and the client said structural design “should have been included.”
The explicit exclusions list gave the firm its strongest position. When you inherit someone else’s project, confirm in writing who is responsible for each discipline before you start. Don’t assume the previous scope carries over.
Scenario C: The kitchen designer treated as the general contractor
A small residential design firm handled only kitchen and bath design on a home renovation. The homeowner filed a consumer-protection complaint that treated the firm as the contractor. The principal planned to handle it alone and called the broker two days before the settlement conference.
A line in your contract stating that your firm is not the contractor can help here. Regulatory complaints are often reportable under a policy, so report them early. Waiting until a conference is scheduled leaves little time to get guidance.