Defining Scope of Services in Architecture:
What to Include, Exclude, and Protect
The scope of services is the document that determines whether the fee holds. Not the contract. Not the billing system. The scope. A scope written in categories invites expansion. A scope written in deliverables protects the fee, makes scope creep visible, and creates the foundation for billing additional services when the project changes. Here's how to write one that actually works.
The Scope of Services Is the Most Important Document in the Proposal
Most A/E firms spend more time on the fee number than on the scope that surrounds it.
That is exactly backwards.
The fee is a floor — the minimum the firm can charge and remain profitable. But whether the firm actually collects that fee, and whether it absorbs hours of uncompensated work along the way, is determined almost entirely by the scope of services.
A fee of $185,000 protected by a specific, deliverable-level scope of services will perform better than a fee of $210,000 surrounded by vague category language. The higher fee looks better on paper. The lower fee is more likely to hold in practice — because the scope makes the boundaries visible.
The difference between a scope that holds and one that doesn't is almost always the same thing: specificity.
A scope written in activities describes what the firm will do. A scope written in deliverables defines what the firm will produce — how much of it, under what assumptions, with what limits on revision. The activity-based scope invites interpretation. The deliverable-based scope makes interpretation unnecessary.
Most scope disputes in A/E firms are not disputes about money. They are disputes about what was meant. The client remembers the broad language. The firm remembers the intent behind it. Neither party is lying. The scope simply never resolved the ambiguity.
A well-written scope resolves it before the project starts.
Scope disputes are almost never about money. They are about what was meant.
Both parties are usually acting in good faith. The problem is that the scope language left room for two different interpretations — and they found each other six months into the project. Specificity at the proposal stage eliminates most of this before it starts.
The Anatomy of a Scope That Protects the Fee
A scope of services that holds under real project conditions has five characteristics:
1. It is organized by phase
Scope organized by phase matches how A/E projects are actually delivered — and how fees are structured. When scope is presented as a flat list of services, clients cannot see which work belongs to which phase, which makes it harder to track what has been delivered and easier for out-of-phase requests to be treated as included.
Phase-organized scope creates natural checkpoints. At the end of each phase, the firm and client can review what was delivered against what was scoped. That review protects both parties — the client can confirm the deliverables were met, and the firm can identify scope additions before they become embedded in the next phase.
2. It defines deliverables, not activities
This is the single most important characteristic of a scope that holds.
An activity is what the firm will do: "Prepare construction documents."
A deliverable is what the firm will produce, under what assumptions: "Prepare a construction document set including architectural floor plans, elevations, sections, details, and specifications sufficient for permit submission and contractor bidding. Assumes one set of owner review comments per phase. Additional review cycles are an additional service."
The difference is not word count. It is precision. The deliverable-based scope answers the questions the client will ask — and the ones they won't ask but will act on — before they become disputes.
Every phase of the scope should define:
- What documents or work products will be produced
- What level of detail is assumed (schematic, permit-ready, construction-ready)
- How many owner review and revision cycles are included
- What consultant-produced content is coordinated but not produced by the firm
3. It states what is excluded
Explicit exclusions are as important as inclusions.
Many scope disputes arise not from work the client requested in the contract, but from work the client assumed was included because it wasn't listed as excluded. Interior design. Furniture layouts. LEED documentation. As-built drawings. Specialty consultant coordination beyond structural and MEP. Landscape architecture.
Each of these may or may not be in scope for a given project. When the proposal is silent, the client fills the silence with their own assumption.
A scope that explicitly excludes services the client might reasonably expect closes that gap. The client sees the exclusion, asks about it if they need it, and either accepts the additional fee or adjusts their expectations — before the project is underway.
4. It defines assumptions that could affect the fee
Some scope items are priced against assumptions that may change — and when they do, the fee needs to change with them.
Common assumptions that belong in the scope:
- The construction budget range the fee was calculated against
- The number of buildings, units, or floors assumed
- The delivery method (design-bid-build, design-build, CM at risk)
- The number of bid packages
- The anticipated permit jurisdiction and complexity
- The number of design alternatives the client will review before a direction is confirmed
When these assumptions are stated in the scope, changes to them create visible fee triggers. When they are unstated, the same changes happen silently — and the firm absorbs the cost.
5. It defines the additional services process
Every scope of services should include a clear statement of what constitutes an additional service and how it will be handled.
This is not a legal disclaimer buried at the end of the document. It is an operational agreement that both parties review together before the project begins.
An effective additional services clause:
- Lists the categories of work that are explicitly additional (redesign after approved documents, extended CA beyond the assumed construction period, value engineering iterations beyond one round)
- States that additional services require written authorization before the work begins
- States the billing method for additional services (hourly at the listed rates, or fixed fee for defined tasks)
Clients who were told at proposal time how additional services work are clients who approve additional services invoices. Clients who encounter the concept for the first time at billing time are clients who dispute them.
Explicit exclusions protect the fee as much as inclusions do.
Work the client assumed was included — because it was not listed as excluded — is almost always treated as included. A scope that lists exclusions specifically closes the gap between what the firm intended to include and what the client expected to receive.
What Gets Scoped Too Loosely — and What It Costs
These are the scope items that generate the most billing disputes in A/E practice. Each one represents a category where vague language produces predictable, recurring problems.
Revision cycles
The most commonly under-scoped item in architecture proposals.
When the number of revision cycles is not stated, the client's assumption is unlimited revisions until they are satisfied. The firm's assumption is however many rounds the fee can absorb. Those assumptions collide somewhere around the third or fourth revision cycle on a design that was originally scoped for two.
Fix: State the number of review cycles for every phase. "Assumes two rounds of owner review comments per phase. Additional review cycles billed at hourly rates." One sentence eliminates most revision cycle disputes.
Construction administration duration
CA fees are typically set based on an assumed construction period. When construction runs long — due to contractor performance, owner-directed changes, or permit delays — the CA scope expands without a fee adjustment unless the proposal established the assumption.
Fix: State the assumed construction period and the basis for CA billing if the period extends. "CA fee assumes a construction period not exceeding 14 months. CA services required beyond this period billed hourly."
Consultant coordination
Proposals frequently list "coordination with structural, MEP, and civil engineers" without defining what coordination means — how many coordination meetings, what level of review, whose drawings the firm is responsible for checking.
When the structural engineer misses something that creates a field condition, the question of whether resolving it is included in the original fee or an additional service depends entirely on whether the scope defined what structural coordination included.
Fix: Define consultant coordination specifically. Name the consultants assumed to be in the scope. State that coordination with consultants not listed is an additional service.
Value engineering
Value engineering — reviewing the design for cost reduction opportunities after the construction budget exceeds the owner's target — is one of the most time-consuming services in A/E practice and one of the most consistently under-scoped.
Fix: Include one round of value engineering in the scope for projects where the construction budget is at risk of overrun. State that additional VE iterations are an additional service. Make the assumption explicit.
Permit resubmittals
A single permit review cycle is typically scoped. Multiple resubmittals — driven by jurisdiction comments, plan check corrections, or scope changes that affect permitted documents — are frequently absorbed as though they were included.
Fix: State that the fee includes one permit submittal and one resubmittal in response to jurisdiction comments. Additional submittals required due to scope changes or jurisdiction-requested revisions are an additional service.
Program changes after design approval
When the client approves a schematic design and then changes the program — more square footage, relocated functions, revised unit mix — the construction documents are no longer a continuation of the approved design. They are a new design delivered under the time pressure of the CD phase.
Fix: State clearly that changes to the approved program after design approval constitute additional services requiring a revised fee. Many firms state this verbally. Very few state it in the proposal, where it creates a binding shared understanding.
Revision cycles are the most under-scoped item in architecture proposals — and the most expensive.
One sentence — "assumes two rounds of owner review comments per phase; additional review cycles are an additional service" — eliminates most revision cycle disputes. It takes thirty seconds to write and returns that time many times over on every project.
How Scope Definition Connects to Profitability
The connection between scope definition and firm profitability is direct and well-documented.
Firms with specific, deliverable-level scopes have lower write-off rates. They have fewer billing disputes. They identify additional services earlier — while the work is still being performed and the conversation is straightforward — rather than at billing time when it is already done and the client is resistant.
They also run better projects. A project manager who has a specific scope to reference makes better decisions about how to spend time. When a client request falls outside the scope, the PM can identify it immediately rather than absorbing it and discovering the overrun later.
Scope definition and additional services are the same practice
A well-written scope does not just protect the original fee. It creates the conditions under which additional services can be identified and billed.
Additional services happen on nearly every project of meaningful size. The question is not whether they will occur. The question is whether the firm will recognize them, have a conversation about them while the work is still ahead, and bill them as the separate revenue stream they represent.
That recognition depends entirely on the scope. If the original scope is specific enough that a client request clearly falls outside it, the additional services conversation is easy — both parties can see it. If the scope is broad enough to arguably include almost anything, every additional services conversation becomes a dispute about what was meant.
Firms that write specific scopes do not just protect existing fees. They systematically increase revenue by capturing work that would otherwise be absorbed.
→ Read: Scope Creep in Architecture Projects
→ Read: What Are Additional Services in Architecture?
The Scope as a Working Document
A scope of services is not a document that gets filed after the proposal is signed.
It is a reference that should be active throughout the project — consulted at phase kickoffs, reviewed when client requests arrive, and referenced when billing decisions are made.
Firms that use the scope actively — that reference it in project meetings, that send scope reminders when out-of-scope requests arrive, and that have the additional services conversation at the moment the work is identified rather than at billing time — operate with a financial clarity that transforms how projects run.
The scope is only as valuable as the discipline applied to using it.
That discipline starts at the proposal — with language specific enough to be worth referencing. It continues through the project as a tool that makes every financial decision easier, every billing conversation shorter, and every additional services discussion more straightforward than it would otherwise be.
→ Read: How to Write an Architecture Fee Proposal
→ Read: Fee Proposals for A/E Firms: The Complete Guide
Cut Your Billing Time by 60% Within 90 Days — Or We Refund Every Penny
We're so confident BaseBuilders will transform your billing process that we're putting our money where our mouth is.
BaseBuilders’ easy-to-use software is specifically designed to help small to mid-sized firms track time, manage projects, stay on top of expenses, and more. We’ll handle the invoicing for you so you can focus on growing your firm and designing wonderful spaces.