An architect’s scope of services is a written document that defines exactly what an architect will and will not do within a given commission, under what conditions, and to what standard of deliverable.
It sets out the responsibilities the architect accepts, the boundaries around those responsibilities, the assumptions the fee is built upon, and the triggers that convert informal requests into additional instructions.
It is not a project description. It is not a marketing statement. It is the contractual foundation of the architect-client relationship, and everything that follows – fees, programme, deliverables – depends on how precisely it is written.
The operating system for new practice owners
Start and run your whole practice from one place.
Pipeline, pricing, cash flow, clients and the weekly routine that holds it together. Six hosted tools, 41 resources and 12 template sets, in one private workspace.
A scope of services should be agreed and signed before any design work begins. In practice, this is one of the most frequently skipped or rushed stages of the architectural process, and it is where a significant proportion of unpaid work originates.
Why the Scope of Services Matters More Than Most Architects Realise
Most architects understand that scope definition is important in principle. Far fewer treat it with the commercial discipline it demands in practice.
The scope of services is not an administrative formality appended to a fee letter. It is the document that determines whether a project is profitable, whether the client relationship remains functional under pressure, and whether the architect retains professional authority when expectations diverge.
When a project runs over programme, when a client requests a fourth round of revisions, or when a planning resubmission is required, the scope is the only document that objectively defines whether that work was included in the original fee. Without a clear scope, the answer defaults to the client’s recollection of the conversation.
Understanding the full range of architectural services is the starting point for building a scope document that reflects the real complexity of what an architect provides. Many practices undersell or under-define their services at the outset, which leads directly to scope creep downstream.
A well-constructed scope also communicates professionalism. Clients who receive a clearly structured, project-specific scope of services before fees are discussed understand immediately that they are working with a practice that manages its commissions with rigour.
The Scope Is Where the Fee Is Really Won or Lost
Architects often focus their commercial attention on the fee number itself. The real financial risk, however, sits in the scope language beneath that number.
Imprecise inclusions, unlimited revision rounds, undefined meeting obligations, and open-ended responsibilities create commitments that were never costed. Each one represents work that the practice will absorb as unpaid time.
Scope and fee must be developed together, not in sequence. The fee is only defensible if the scope it corresponds to is precise enough to hold up when a client asks why additional work is being charged separately.
Practices that approach fee negotiation without a finalised scope are negotiating blindly. They cannot accurately cost what has not been defined, and they cannot protect what has not been written down.
The discipline required here is straightforward: no proposal should be issued until the scope that generates it has been worked through in full. This applies equally to small domestic commissions and large commercial projects.
Service Description vs Obligation Boundary: The Critical Difference
There is a meaningful legal and commercial difference between describing what an architect does and defining what an architect is contractually responsible for delivering.
A service description is a narrative. It explains the architect’s role, their design process, and the value they bring to a project. It is useful for marketing, for proposals, and for helping clients understand the profession. It is not, by itself, a scope of services.
An obligation boundary defines what the architect must deliver, by when, under what conditions, and with what limits. It is specific, enumerable, and defensible. When a dispute arises – over revisions, deliverables, or additional requests – the obligation boundary is the document that matters.
Many architects conflate these two things. They issue proposals containing well-written descriptions of their process and believe this constitutes a scope. It does not. A client reading a service description will draw their own conclusions about what is included, and those conclusions will rarely match the architect’s intent.
Translating a service description into a set of obligation boundaries is the technical skill at the heart of scope writing. It requires precision, project-specific thought, and a willingness to define limits explicitly – even where doing so feels commercially awkward.
What a Strong Architectural Scope of Services Should Define
A robust scope of services document is built from five distinct components. Each one performs a different function in protecting the commission and managing the client relationship.
Inclusions: What Is Covered and Under What Conditions
Inclusions define the specific deliverables and activities the fee covers. The key word is specific – a list of drawing types, a stated number of design iterations, a defined meeting attendance limit per phase.
Phrases like “full architectural service” or “all necessary drawings” are not inclusions. They are invitations to dispute. A well-written inclusion names the deliverable, the format, and the conditions under which it applies.
For example: “Two rounds of design revisions following client feedback at concept stage, with a third round triggered as an additional service instruction.” That is enforceable. “Design revisions as required” is not.
Exclusions: What Falls Outside the Fee
Exclusions are the most commercially valuable component of a scope document and the one most frequently omitted by architects who are uncomfortable drawing hard lines.
The categories most commonly left undefined include architectural visualisations beyond basic diagrams, measured survey coordination, specialist interior design, procurement management, planning resubmissions following refusal, and post-occupancy evaluation.
Each of these should be named explicitly as an exclusion if it falls outside the fee. A client who sees an exclusion list is not alarmed – they are informed. The conversation about what those services would cost, if needed, becomes straightforward rather than confrontational.
Assumptions: The Conditions Under Which the Fee Holds
Assumptions are the stated conditions that must remain true for the fee to remain valid. They protect the architect when external factors change the nature or complexity of the commission.
Typical assumptions include: that existing drawings provided by the client are accurate and up to date; that the local planning authority will process the application within the statutory timeframe; that all required consultant appointments will be made by the client within an agreed period.
If an assumption proves incorrect – if the existing drawings turn out to be inaccurate and a measured survey becomes necessary – the stated assumption creates the basis for a fee adjustment conversation. Without it, the architect absorbs the additional work in silence.
Client Responsibilities: What the Client Owns
Defining client responsibilities is as important as defining architect responsibilities. The scope should explicitly name what the client is obligated to provide, and by when.
This includes: providing accurate site and building information, making design decisions within agreed review periods, appointing structural, MEP, and other specialist consultants independently or through a named process, and providing written approval at each design gateway before the next phase begins.
When client responsibilities are named in the scope, delays caused by the client’s failure to fulfil them become a legitimate basis for programme and fee adjustment. Without this language, the architect typically absorbs the programme impact and the associated cost.
Additional Service Triggers: When the Fee Changes
Additional service triggers are the pre-agreed conditions that convert an informal request or changed circumstance into a new fee instruction. They are, in commercial terms, the most important part of the scope document.
Triggers should cover events that are foreseeable but not guaranteed: a planning refusal requiring resubmission, a client brief change after design sign-off, a contractor query volume exceeding a defined threshold during construction, or a requirement for additional authority submissions such as listed building consent.
When these triggers are written into the scope and agreed by the client at the outset, the fee recovery conversation that follows a triggering event is a straightforward reference to an agreed document. Without pre-agreed triggers, it becomes a negotiation the architect usually loses.
What to Include in a Scope of Work for an Architecture Project
A phase-by-phase breakdown provides the clearest structure for communicating deliverables and helps clients understand exactly what they are commissioning at each stage of the project.
The following breakdown reflects standard UK architectural practice and aligns broadly with the RIBA Work Stages, though the scope should always be adapted to the specific project rather than copied from a template.
Concept Design (RIBA Stage 2): Initial design options, spatial arrangement studies, massing diagrams, planning feasibility assessment, and a concept document or presentation for client sign-off. Number of design options and revision rounds stated explicitly.
Design Development (RIBA Stage 3): Developed design drawings including floor plans, sections, and elevations at an agreed scale. Coordination with structural engineer at outline stage. Schedule of accommodation. Design review meeting, with attendance limit stated.
Planning Application (RIBA Stage 3/4): Preparation and submission of a full or householder planning application. Drawing package specified by type and scale. Design and Access Statement if required. Liaison with planning officer limited to a defined number of exchanges. Resubmission excluded unless triggered as additional service.
Technical Design (RIBA Stage 4): Full technical drawing package including construction details, specification clauses, and coordinated consultant drawings. This is where construction details are developed and issued for contractor use. Number of detail drawings stated or described by building element.
Tender (RIBA Stage 4/5): Preparation of tender documentation, issue to agreed list of contractors, tender query responses up to a defined number, tender appraisal report, and recommendation. Pricing and contract administration are distinct roles and should be scoped separately if included.
Construction Administration (RIBA Stage 5): Site visits at a stated frequency, contractor query responses up to a defined monthly limit, inspection reports, review of contractor submissions, and practical completion sign-off. Post-completion defects review period stated explicitly.
What to Exclude or Clarify Before the Project Starts
There is a predictable set of services that practices absorb as unpaid work on almost every project. The reason is consistent: these services were not named as exclusions in the original scope.
Contractor query responses beyond a stated limit: During construction, contractor queries (RFIs) can run into the dozens. Unless the scope defines a monthly limit – for example, ten responses per month included, additional responses charged at an hourly rate – this becomes an open-ended obligation.
Value engineering exercises: When a tender return exceeds the client’s budget, the request to “value engineer” the scheme can represent weeks of redesign work. If value engineering is not named as an additional service trigger, the architect typically absorbs it under the original fee.
Planning resubmissions: A planning refusal followed by a revised resubmission is a common scenario on residential and commercial projects. Unless the scope explicitly excludes this – or defines it as a triggered additional service with a pre-agreed fee – it tends to be treated as part of the original planning service.
Specialist consultant coordination beyond outline level: Coordinating structural, MEP, acoustic, or heritage consultants to a detailed level is a significant time commitment. If the scope does not define the depth of coordination included, the architect risks becoming an informal project manager for the consultant team without a corresponding fee.
Informal client meetings and calls: On long-running projects, unscheduled calls and informal check-ins accumulate into meaningful time. A well-structured scope defines meeting attendance by phase and treats additional meetings as billable time.
How Vague Scope Language Hands Control to the Client
Undefined scope language does not create neutrality – it creates a vacuum that the client fills with their own assumptions. And those assumptions are almost always more generous than the architect intended.
Phrases such as “full architectural service,” “as required,” “ongoing design support,” or “regular site visits” read as comprehensive commitments to a client who has no professional frame of reference for what they actually mean. The architect who writes them may mean something quite specific. The client reads something quite different.
This expectation gap is one of the most common sources of tension in architectural practice. It does not arise from bad faith on either side. It arises from a scope document that left room for interpretation.
The same dynamic applies to design scope conversations during the early stages of a project. When the range and depth of design exploration is left undefined, the client naturally assumes that the process will continue until they are satisfied. Without a stated limit, the architect has no basis for introducing one mid-project without damaging the relationship.
Vague language also erodes professional authority. When a client questions a fee for additional work, and the architect cannot point to a clear scope boundary, the client’s assumption tends to carry more weight in the conversation than the architect’s recollection of intent. Precision in scope writing is, therefore, an act of professional self-respect as much as a commercial discipline.
How to Link Scope, Fee, Programme, and Deliverables
A scope of services document does not exist in isolation. To be commercially effective, it must be aligned with the fee structure, the project programme, and the deliverable schedule so that each reinforces the others.
The fee should map directly to the phases defined in the scope. If the scope includes six phases, the fee should show how it is allocated across those six phases. A client should be able to read the scope, look at the fee breakdown, and understand exactly what they are paying for at each stage.
The project programme should align with the scope assumptions. If the scope assumes a twelve-week planning determination period, the programme should reflect that. If determination takes longer, the scope assumption creates the basis for a programme extension conversation.
The deliverable schedule – a list of specific drawings, documents, and reports to be issued at each phase – should mirror the inclusions listed in the scope. Any deliverable listed in the scope should appear in the schedule. Any deliverable in the schedule should have a corresponding inclusion. Gaps between these two documents create ambiguity about what is included.
Architects who treat scope, fee, and programme as separate documents prepared in sequence miss the opportunity to build a proposal that is internally coherent and commercially airtight. The architectural design process itself depends on this coherence – a well-structured proposal shapes not just the commercial relationship but the way the project is managed from start to finish.
Case Studies: Scope Definition in Practice
Case Study 1: Residential Extension – Undefined Revisions
A small practice was appointed on a residential rear extension. The scope described “design development and planning application” without specifying the number of design iterations included in the fee.
The client, who had strong opinions and difficulty committing to decisions, requested seven rounds of revisions across concept and developed design. The practice, having no contractual basis to stop or charge, delivered them all. The project ran significantly over the estimated hours, and the client felt the friction when the architect eventually raised the issue informally. The relationship deteriorated before planning was even submitted.
A single clause – “Two rounds of design revisions per phase included; further revisions charged at an hourly rate of X” – would have resolved this before it arose.
Case Study 2: Commercial Fit-Out – Exclusions Not Named
An architect appointed on a commercial office fit-out scoped their services as “interior architecture and design.” The client interpreted this as including furniture specification, lighting design, artwork curation, and procurement coordination.
None of these services had been named as exclusions. By the time the practice raised the issue, the client had already made decisions based on the assumption that this work was included. Recovering the fee became a dispute rather than a conversation, and the practice absorbed most of the additional work to preserve the relationship.
An exclusions clause listing furniture procurement, specialist lighting design, and artwork sourcing as services outside the fee would have resolved the expectation at the outset.
Case Study 3: Planning Resubmission – Assumed to Be Included
A planning application for a new house in a sensitive landscape setting was refused. The scope of services described “preparation and submission of a planning application” without addressing what would happen if consent was refused.
The client assumed that a resubmission was part of the original service. The architect had assumed it was not. Neither assumption was wrong in itself – the problem was the silence in the scope. The resubmission took six weeks of additional work, which the practice partially recovered only after a protracted negotiation that damaged the client relationship.
A scope clause stating “One planning submission included. Resubmission following refusal or significant design changes requested by the authority triggered as an additional service at agreed rates” would have resolved this before it became a dispute.
Case Study 4: New Build – Consultant Coordination Scope Gap
An architect leading a new residential development of four units was appointed alongside a structural engineer and an MEP consultant appointed separately by the client. The scope described the architect’s role as “lead designer,” without defining what consultant coordination was included.
In practice, the architect managed all consultant outputs, coordinated clash detection, chaired fortnightly consultant meetings, and managed the issue of coordinated drawing packages. None of this was included in the fee. The coordination role consumed approximately 20% of the total project hours.
A defined consultant coordination clause – specifying the meetings attended, the coordination outputs produced, and the level of review provided – with a named trigger for project management services beyond that limit, would have created the basis for a proper fee.
Case Study 5: Heritage Project – Statutory Approvals Overlap
An architect working on the conversion of a listed farmhouse prepared and submitted a planning application. The scope did not address listed building consent as a separate approval process, even though it was foreseeable from the outset of the commission.
Listed building consent required a separate drawing package, an additional heritage statement, and sustained correspondence with the conservation officer. This added eight weeks and a substantial volume of work to the project. Because the scope had not named listed building consent as a distinct approval process with its own fee, the architect had no clear basis for raising an additional service instruction.
On any heritage project, statutory approvals should be listed individually in the scope – planning consent, listed building consent, advertisement consent, scheduled monument consent where relevant – each defined as a separate inclusion or exclusion, with its own deliverable set and fee trigger.
Common Scope Definition Mistakes Architects Make
Scope definition errors follow predictable patterns. Understanding them is the first step to avoiding them.
Issuing a fee before the scope is finalised. When the fee is agreed first and the scope written around it, the scope becomes a justification document rather than a commercial one. The fee should follow the scope, not precede it.
Using template language without project-specific adjustment. A scope template is a starting framework, not a finished document. Every project has different complexity, different client behaviours, and different risk factors. A template applied unchanged fails to address any of them.
Omitting exclusions entirely. Many architects write only inclusions and assume that anything not listed is excluded by implication. Clients do not read scopes this way. Explicit exclusions remove ambiguity and make conversations about additional services significantly easier.
Failing to link revisions to fee. Revision limits are among the single most protective clauses an architect can include. Omitting them is one of the most common and costly mistakes in residential and small commercial practice.
Avoiding the scope conversation with existing clients. Many practices apply rigorous scoping to new clients but revert to informal arrangements with repeat clients, assuming the relationship provides sufficient protection. It does not. Scope discipline should apply regardless of the client relationship.
Practical Questions to Ask Before Issuing a Proposal
Before any scope of services is finalised and any proposal issued, the following questions should be worked through carefully. They identify the project-specific risk factors that the scope must address.
On project complexity: How well-defined is the brief? Is the site constrained or sensitive? Are there known heritage, ecological, or planning policy factors that might generate additional approval processes? What is the realistic planning risk?
On client decision-making: How experienced is this client with construction projects? How quickly do they typically make decisions? Is there a clear decision-maker, or does approval involve multiple parties? What is the likely revision appetite?
On consultant involvement: Which consultants are required, and who appoints them? What level of coordination is the architect expected to provide? Is a lead designer or principal designer role anticipated? Are any consultant scopes dependent on the architect’s output?
On approval routes: Which statutory approvals are required? Are any of them uncertain or subject to pre-application negotiation? Does the project involve listed building consent, conservation area consent, or any other specialist process alongside planning?
On change drivers: What are the most likely causes of scope change on this specific project? Brief instability, budget pressure, consultant delays, client decision-making pace? Each identifiable change driver should have a corresponding trigger or assumption in the scope document.
Thorough answers to these questions, developed before the scope is written, produce a document that is specific, defensible, and appropriate to the actual project. Architects who find the feasibility stage of a project informative in this respect are right to do so – early project intelligence directly improves scope quality.
Conclusion: Your Scope Is a Commercial Document, Not an Admin Task
A precisely written scope of services is one of the most powerful tools available to an architect in practice. It protects the fee, manages client expectations, defines professional authority, and creates the conditions for a functional, productive project relationship.
The operating system for new practice owners
Start and run your whole practice from one place.
Pipeline, pricing, cash flow, clients and the weekly routine that holds it together. Six hosted tools, 41 resources and 12 template sets, in one private workspace.
The practices that treat scope definition as an afterthought – issuing template language, omitting exclusions, leaving revision rounds open, failing to name additional service triggers – consistently absorb unpaid work, experience client friction, and struggle to build profitable commissions. The work is done. The fee is not recovered. The relationship suffers anyway.
The practices that invest time in precise scope writing before issuing a single proposal find that the conversations downstream are simpler, the fee recovery conversations less confrontational, and the client relationships more durable.
Scope definition is a professional skill. Like detailing or drawing, it improves with deliberate practice, project-specific thinking, and a willingness to be precise even where precision feels commercially uncomfortable. Treat it as foundational. The fee depends on it.
