How to Define Your Scope of Services Before the Project Starts

A scope of services document does one essential thing: it defines the edges of an architect’s engagement before any work starts.

It is not a list of aspirations or a project description. It is a boundary-setting document – one that tells both parties exactly what is included, what is not, and what constitutes a change to the agreement.

Without it, work expands without authorisation. Clients assume services are included. Architects absorb extra rounds of revisions, additional meetings, and unpaid coordination work. The scope of services document is the primary tool that prevents all of this.

Whether you are preparing your first appointment letter or reviewing a practice template, the principles here will help you write scope documents that protect your fee and set clear expectations from day one.

Why Vague Scopes Lead to Unpaid Work

The most common cause of unpaid architectural work is not a difficult client – it is ambiguous scope language that leaves room for conflicting interpretations.

When a scope says the architect will provide design services “as required throughout the project”, that phrase means something different to the architect than it does to the client. The architect reads a defined workload. The client reads unlimited availability.

Four language failures recur most often in poorly written scopes.

The first is undefined revision limits. When the number of permitted revisions is not stated, every round of client changes is implicitly included – regardless of how many rounds occur or what causes them.

The second is absent exclusions. A scope that lists inclusions but does not name exclusions creates a vacuum. Any service not explicitly excluded can be claimed as included.

The third is open-ended coordination responsibilities. Phrases like “coordinating with the wider project team” give no indication of what that coordination involves, how far it extends, or who bears the cost when consultants fail to deliver.

The fourth is ambiguous approval points. Without a defined sign-off process at each stage, there is no mechanism to confirm the client has accepted a design direction – and no basis for charging when they later ask to reverse it.

Each of these failures compounds over a project’s duration. By the time the architect recognises the problem, the unpaid work has already accumulated.

Scope of Services vs Scope of Work vs Professional Services Agreement: What Is the Difference?

These three terms are often used interchangeably in practice, but they describe distinct documents with different functions.

The scope of services defines what the architect will do – the professional tasks, deliverables, and activities covered by the fee.

The scope of work describes the physical project being designed – the building type, size, location, programme, and brief. It sets the context that the fee is based upon, not the architect’s role within it.

The professional services agreement (PSA) is the overarching legal and contractual document. It governs the relationship: liability, intellectual property, termination, payment terms, dispute resolution, and professional indemnity obligations. The scope of services sits within the PSA as a schedule or appendix.

Understanding the relationship between these documents matters because changes in the scope of work – such as an increase in floor area or a change of use – should automatically trigger a review of the scope of services and the fee.

Without this linkage built into the agreement, scope changes can occur without recognition or compensation.

For a fuller understanding of how architectural appointments fit within the broader project process, the guide to RIBA Work Stages is a useful reference point.

The Core Parts of a Properly Written Architecture Scope

A well-structured scope of services contains seven distinct components. Each one performs a specific function, and omitting any one of them creates a gap that can be exploited – unintentionally or otherwise.

Inclusions

Inclusions are the services the architect will explicitly provide within the agreed fee. Every service listed here should be described with enough precision to be verifiable.

“Architectural design services” is not sufficient. “Preparation of planning application drawings including site location plan, block plan, existing and proposed floor plans, sections, and elevations at a scale of 1:100” is sufficient.

The risk of vague inclusion language is that it invites the client to fill in the gaps with their own expectations. The more precisely a service is described, the easier it is to demonstrate when a request falls outside it.

Exclusions

An exclusions list is as important as the inclusions list, and is far more commonly absent. Named exclusions remove the ambiguity that creates unpaid work.

Commonly excluded services include structural engineering, mechanical and electrical design, cost consultancy, party wall advice, planning consultancy, principal designer duties under CDM, contractor performance monitoring, and health and safety plan preparation.

Simply listing these exclusions is not enough. Each should be accompanied by a brief statement explaining that these services are available by separate appointment, or that the client is responsible for procuring them independently.

Assumptions

Project assumptions define the conditions the fee is based on. They are the scope’s early warning system.

If the fee is calculated on the assumption that the planning approach is a householder application, and it later becomes a full application, the fee basis has changed. Without a documented assumption, that change goes unrecognised.

Assumptions should cover: brief stability at the point of appointment, number of design options to be developed, planning pathway, site conditions as understood at appointment, programme, and the number and identity of consultants to be coordinated.

Client Responsibilities and Decision Points

The client has obligations too, and documenting them prevents the most common source of programme delay: late or absent decisions.

Client responsibilities typically include: supplying accurate surveys and existing information, making timely decisions at each stage, attending scheduled reviews, and nominating a single point of contact with authority to approve work.

Decision points should be written as programme milestones. When the client fails to meet a decision point, the scope should specify what happens to the programme and whether abortive work becomes a chargeable event.

Additional Fee Triggers

Additional fee triggers are the events that entitle the architect to charge beyond the agreed fee. These must be named before work begins, not negotiated after the event.

Typical triggers include: approved brief changes, authority redesign requirements, consultant errors requiring rework, client-supplied information that proves inaccurate, value engineering exercises not anticipated in the brief, and delays that require programme recovery work.

Each trigger should be written as a clear clause that specifies the event, the mechanism for notifying the client, and the basis on which additional fees will be calculated – usually an agreed hourly rate schedule appended to the appointment.

Start with Project Assumptions

Project assumptions are the foundation of a defensible scope. They document the specific conditions under which the fee was calculated, making it possible to identify – and charge for – any deviation from those conditions.

Brief stability is the most critical assumption. If the scope is written on the basis of an agreed brief, and that brief changes materially after appointment, the architect has grounds for a fee review. This assumption should be written explicitly, with a mechanism for brief change review built in.

Site conditions should be documented as understood at the time of appointment – not guaranteed. If the architect is relying on information provided by the client, that reliance should be stated.

If a topographical survey or ground investigation has not yet been completed, the scope should note that the fee is based on the site conditions as currently understood, and that unknown conditions may affect the scope.

Planning pathway assumptions are particularly important. A planning application can range from a minor householder application to a full application requiring environmental impact assessment. The scope should state which pathway is anticipated and exclude others unless separately instructed.

Programme assumptions set the expected timeline. A compressed programme may require additional resource; a prolonged one may require rework as design information becomes stale. Documenting the expected programme at appointment stage creates a reference point for both events.

Define the Service Stages and Deliverables

A scope tied to named project stages is far easier to administer than one that describes services in general terms. Stage-based scopes create natural review points, define what is due at each point, and establish the mechanism for authorising progression.

Each stage entry should specify: the work to be carried out, the deliverables to be produced, the approval mechanism, and the conditions for proceeding to the next stage.

A stage-gate clause might read: “Stage 2 – Concept Design will be considered complete upon written client approval of the concept design report and associated drawings. Progression to Stage 3 is conditional upon receipt of that approval and payment of the Stage 2 instalment.”

This language does three things. It defines completion. It requires explicit approval. It ties progression to payment. All three protect the architect.

Aligning scope stages with the architecture design process also helps clients understand where they are in the project and what decisions are required of them at each point.

Set Clear Limits on Revisions and Design Changes

Revision limits are one of the most important and most frequently absent elements of an architect’s scope. Without them, every client request for change is implicitly included in the fee.

Revision limits should be set per stage, not per project. A single project-wide limit of “two rounds of revisions” does not distinguish between a minor comment on a single drawing and a wholesale redesign of a planning scheme.

A stage-level revision clause might read: “The fee for Stage 3 – Developed Design includes up to two rounds of client-requested revisions to the approved concept. Further revisions will be charged at the hourly rates set out in Schedule B.”

Revisions should also be categorised. Client-driven revisions are changes requested by the client to a design they have already approved. These are the clearest candidates for additional fees.

Revisions caused by authority requirements or consultant coordination issues fall into a different category and should be addressed separately in the scope.

The distinction matters because conflating all types of revision into a single limit is unfair to the architect and confusing to the client. A clear categorisation prevents disputes at the point of invoicing.

State What Is Excluded from the Fee

The exclusions list is arguably the most protective part of the scope document. Services that are not explicitly excluded can be – and often are – claimed as included.

The following services are most commonly excluded from an architect’s basic fee and should be named explicitly in every appointment.

Structural design and calculations. This is the discipline most frequently assumed to be part of architectural services by clients unfamiliar with the distinction. The exclusion should state that the client is responsible for appointing a structural engineer independently.

Mechanical and electrical design. Unless the practice has in-house MEP capability, all services engineering should be excluded and the client directed to appoint separately.

Quantity surveying and cost consultancy. Architects are not cost consultants. Any cost advice provided should be clearly labelled as indicative only, and formal cost consultancy excluded.

Party wall surveying. This is a specialist legal role under the Party Wall etc. Act 1996 and should always be excluded from architectural services.

Planning consultancy. Where a planning consultant or heritage consultant is required, this should be excluded and appointed separately by the client.

Principal Designer duties under CDM 2015. These carry specific statutory obligations and should only be included if the practice has expressly accepted them and priced accordingly.

Contractor performance monitoring and defects management. Site observation during construction does not include responsibility for contractor performance, quality control, or defects liability management unless specifically included and priced.

An example exclusion clause: “The following services are not included within the agreed fee and are excluded from this appointment: structural engineering design, mechanical and electrical engineering, quantity surveying, party wall surveying, planning consultancy, Principal Designer duties under CDM 2015, and contractor performance monitoring.

These services are available by separate appointment and the client is responsible for procuring them independently.”

Define Client Responsibilities and Decision Points

Client obligations are too often treated as implied rather than documented. When they are not written into the scope, the architect has no formal basis for raising a delay or a fee claim when the client fails to deliver.

Information supply is the first obligation to document. The client should be required to provide accurate surveys, existing drawings, title information, and any other information on which the architect’s design is based – by a specified date, or prior to the commencement of the relevant stage.

The scope should include a reliance clause: “The architect will rely on information supplied by or on behalf of the client in preparing design and application documents. The architect accepts no liability for errors arising from inaccurate or incomplete client-supplied information.”

Timely approvals are the second obligation. Each stage should have a defined approval period. If the client does not respond within that period, the scope should specify whether the stage is considered approved by default, or whether the programme is extended accordingly.

Decision-making authority should be established at appointment stage. The client should nominate a single named individual with authority to make decisions and approve work. This prevents the common scenario where approved work is later reversed because a decision-maker who was not involved objects to a direction already confirmed.

Programme adherence should also be documented. If the client’s delays cause the architect to rework information or extend the period of service, a delay clause gives the architect the basis to charge for the additional resource.

Identify What Will Trigger Additional Fees

Additional fee triggers protect the architect’s margin. Without them, the gap between agreed fee and actual cost grows with every unrecognised event.

The following triggers should be addressed in every scope of services.

Brief changes after stage approval. Any material change to the agreed brief following stage sign-off constitutes additional work. The clause should specify that a brief change notification will be issued and that additional fees will be agreed before rework commences.

Authority-required redesign. Where a planning authority or building control body requires design changes beyond the submitted scheme, this constitutes additional work. The scope should separate submission from response – the fee covers submission; response to material comments is a separate instruction.

Consultant failures requiring rework. If a client-appointed consultant provides incorrect or late information that requires the architect to revise work already completed, the additional work is chargeable. The reliance clause supports this position.

Client-supplied information errors. Where a survey, title document, or other client-supplied information proves inaccurate, any rework required is a chargeable additional service.

Value engineering exercises. If the project proceeds to a cost plan and the architect is asked to redesign to reduce cost, this is a new instruction – not a continuation of the original scope – unless expressly included.

Delayed decisions. Where client-caused delays require the architect to re-issue, update, or revise information that had already been completed and submitted, the additional resource is chargeable.

Additional site visits or inspections. Site visits beyond the agreed frequency or outside the agreed stage are chargeable at the stated rate. Contractor-requested visits should be routed through the client and treated as additional instructions.

Understanding how fee negotiation works in practice is useful context when structuring these trigger clauses, particularly for smaller practices where fee recovery is critical to viability.

Clarify Meetings, Communication, and Approval Processes

Unlimited meetings are one of the most common and least-recognised sources of unpaid architectural work. The scope should define meetings as clearly as any other deliverable.

Meeting scope should cover: the format of each meeting type (site visit, design review, client briefing, consultant coordination), the frequency, the expected attendees, and the basis for recording decisions.

A simple meeting clause: “The fee for Stage 2 includes up to three client design review meetings, held remotely or at the client’s premises. Additional meetings will be charged at the hourly rate in Schedule B. All meetings will be followed by a written record of decisions and actions issued within five working days.”

The written record is as important as the meeting itself. It creates a contemporaneous document confirming what was discussed, decided, and approved – and it makes the approval process auditable.

Stage sign-off should be a formal, written process. An email confirmation from the client, acknowledging the stage deliverables and authorising progression, is sufficient. The key is that it must be explicit, not implied.

Cover Consultants, Third Parties, and Authority Approvals

The architect’s relationship with the wider consultant team must be clearly defined in the scope, particularly on multi-disciplinary projects where coordination is extensive.

The architect’s coordination role should be described in terms of what it includes – attending coordination meetings, checking for clash between architectural and structural drawings, issuing drawing registers – and what it excludes.

The architect is not responsible for the quality, accuracy, or programme of other consultants’ work unless the appointment expressly states otherwise.

Third-party information reliance should be addressed directly. Where the architect designs on the basis of a structural engineer’s scheme, a specialist’s performance specification, or a client-supplied survey, that reliance should be documented.

If the third-party information changes, a review of the architectural work and associated fees is justified.

Planning and building control authority comments require particular attention. The scope should make clear that the fee covers one submission and one response to minor, non-material comments from the authority.

Material redesign required by the authority – changes of layout, scale, massing, or approach – constitutes additional work and should be priced separately.

Pre-application meetings with the local authority, heritage body, or highways department should also be treated as separate instructions unless explicitly included. Each meeting carries resource implications and should be scoped accordingly.

Address Construction-Stage and Site Services Carefully

Construction-phase appointments carry the greatest scope risk of any project stage. The duration is long, the variables are many, and client and contractor expectations of the architect’s role frequently exceed what has been agreed.

Site visit frequency should be specified numerically. A clause such as “the fee for construction observation includes up to one site visit per fortnight during the construction period, estimated at 26 weeks” is defensible. “Regular site visits as required” is not.

The nature of site attendance must be clarified. The architect’s role during construction is observation – checking that work is broadly in accordance with the design intent – not supervision, inspection to a contractor’s standard, or quality control. The scope should state this explicitly.

Contractor-requested visits are a particular risk. Contractors will often contact the architect directly to resolve site queries. Unless the scope addresses this, those visits and the time spent on site queries become an unmanaged cost.

The scope should route all contractor requests through the client, or establish a protocol for recording and charging additional queries.

Defects liability management, snagging inspection, and final certificate administration should only be included if they are explicitly priced. Each has specific resource implications and legal significance.

For practices managing construction-stage appointments, the guide to understanding architectural services provides a clear overview of how different service levels relate to project stages and fee structure.

Example Scope Language Architects Can Adapt

The following clause examples are written as usable starting points, not legal templates. Each should be reviewed against the specific project, adapted to the practice’s appointment form, and checked against relevant professional indemnity requirements.

Revision limit clause: “The fee for each design stage includes up to two rounds of client-requested revisions to the approved design. Revisions are defined as changes to a design that has already received client approval at the relevant stage gateway.

Further rounds of revision will be instructed in writing and charged at the hourly rates set out in Schedule B.”

Stage approval clause: “Stage completion is confirmed by written client approval of all deliverables listed in the relevant stage schedule. The architect will not proceed to the subsequent stage without written approval. If the client does not respond within 14 days of issue of stage deliverables, the architect will notify the client in writing and pause progress until approval is received.”

Client information reliance clause: “The architect will rely upon information supplied by or on behalf of the client, including surveys, title documents, and consultant reports.

The architect accepts no liability for errors, omissions, or design changes arising from inaccurate or incomplete information supplied by the client or their representatives.”

Authority redesign clause: “The fee for planning application preparation covers the preparation and submission of one application and one response to minor, non-material clarifications from the local planning authority.

Where the authority requires material changes to the design, massing, or layout as a condition of approval, this will constitute an additional service and will be instructed and charged accordingly.”

Site visit clause: “Construction-stage observation services include up to one site visit per fortnight during the construction period. The architect’s role during site visits is to observe the general progress and quality of work as it relates to the design intent.

This role does not constitute supervision, inspection to contractor’s standard, or responsibility for contractor methods, safety, or programme.”

Consultant exclusion clause: “Structural engineering, mechanical and electrical engineering, quantity surveying, party wall surveying, planning consultancy, and Principal Designer duties under CDM 2015 are excluded from this appointment.

The client is responsible for procuring these services independently. The architect will coordinate with client-appointed consultants as described in the Stage Schedules, but accepts no responsibility for the accuracy, quality, or programme of their work.”

Case Studies: How Scope Definition Shaped Real Project Outcomes

Case Study 1: Residential Extension – Revision Limits and Brief Change

A small practice appointed on a rear extension project had included a two-revision limit per stage in their scope, linked to a written stage-approval process.

Following planning approval, the client requested changes to the internal layout – changes that contradicted decisions confirmed in writing at Stage 2.

Because the stage-approval record existed and the revision clause was clear, the practice issued a brief change notification before commencing rework and agreed additional fees in advance.

Without the stage-approval record, the client could reasonably have argued the changes were within the original brief. The written approval created an unambiguous reference point that made the additional fee discussion straightforward.

Case Study 2: Commercial Fit-Out – Excluding MEP and Cost Consultancy

A practice working on a commercial interior had named both MEP design and cost consultancy as explicit exclusions in their appointment letter, with a note directing the client to appoint these disciplines separately.

Midway through design development, the client asked the architect to produce a cost report and coordinate MEP routing. Because both were excluded by name, the practice was able to respond clearly: these services could be provided as additional appointments, priced separately.

The client initially pushed back, believing both services were “part of architecture”. The named exclusion clause resolved the dispute without negotiation – the language was unambiguous.

Case Study 3: Planning Application – Authority Redesign and Additional Fees

A practice had separated planning submission from authority response in their scope, explicitly stating that material redesign required by the local planning authority would constitute additional work.

The authority came back with a requirement to significantly reduce the massing and reposition the principal elevation. The practice issued a brief change notification, proposed a fixed fee for the redesign exercise, and received client approval before commencing.

Because the scope had anticipated this scenario, the additional fee was treated as a natural consequence of the planning process rather than a dispute. The client understood and accepted it.

Case Study 4: New Build Housing – Construction-Stage Site Services

A sole practitioner working on a two-unit new build had specified a fortnightly site visit in their construction-stage appointment, with additional visits chargeable at an agreed day rate.

The contractor began requesting weekly visits and frequent site queries. The practitioner directed all requests through the client, invoiced for visits beyond the fortnightly schedule, and logged all site queries as time against the hourly rate schedule.

The quantified visit schedule and the routing protocol meant that additional costs were recorded in real time and invoiced monthly. By the time practical completion was reached, the construction-stage fee had been accurately tracked and recovered.

Case Study 5: Multi-Consultant Project – Client Information and Third-Party Reliance

A practice working on a mixed-use project had included a client information reliance clause in their appointment. When the client-supplied topographical survey proved inaccurate – with levels several hundred millimetres different from those shown – the structural and architectural schemes both required significant rework.

Because the reliance clause was in place, the practice was able to demonstrate that the fee had been calculated on the basis of the survey as supplied. The rework was agreed as an additional fee, supported by time records showing the extent of the revision required.

Without the reliance clause, recovering those costs would have required negotiation from a weaker position. The clause created a contractual basis for the claim before the problem arose.

Common Scope Loopholes to Close Before Appointment

Even well-intentioned scope documents contain loopholes that become problems later. The following are the most frequently encountered gaps, with specific rewording suggestions for each.

Undefined approval points. A scope that describes stage deliverables without specifying how approval is given and recorded creates ambiguity.

Replace “the architect will present the concept design to the client” with “the architect will present the concept design and issue a written stage sign-off document for the client’s written approval before proceeding.”

Unlimited meetings. Replace “meetings as required during the design process” with “up to three client design review meetings per stage, as set out in the Stage Schedules. Additional meetings will be charged at the rate in Schedule B.”

Vague coordination duties. Replace “coordinating with the project team” with “the architect will attend up to one consultant coordination meeting per stage, review consultant drawings for general coordination, and issue architectural drawing registers.

The architect is not responsible for the quality or accuracy of consultant outputs.”

Absent programme assumptions. Add a project assumption: “The fee is based on the programme set out in the Project Information Schedule. A programme change of more than four weeks, caused by client delay or a change in brief, will be treated as a scope change and may result in a fee adjustment.”

Open-ended “as required” language. Wherever “as required” appears in a scope, replace it with a specific limit or remove it. “Providing technical advice as required during construction” should become “responding to up to three contractor technical queries per month during the construction stage. Additional queries will be charged at the rate in Schedule B.”

Reviewing and tightening scope language before appointment is the most effective way to prevent fee erosion over a project’s duration. It is also the clearest signal to a client that the practice is organised, professional, and serious about managing the engagement well.

Practices building their first appointment templates may also find it useful to review how architecture firms structure their services and operations, particularly in relation to how fee recovery and scope management affect practice viability.

For those developing architectural concept documents that feed into early-stage scoping, understanding what an architectural concept is and how it evolves through design stages can help frame the deliverables listed in each stage of the scope more precisely.

Architects who are earlier in their careers and still building an understanding of professional practice structures may find the guide to architect positions and levels a useful companion to this article, particularly in understanding at which career stage scope-writing becomes a routine responsibility.

Conclusion

A scope of services is not a formality. It is the document that determines whether a practice recovers its full fee or absorbs unpaid work throughout a project.

The principles covered here – named inclusions and exclusions, documented assumptions, defined deliverables, explicit revision limits, stage approvals, client obligations, and additional fee triggers – are not complex.

But they must be written, agreed, and signed before work begins. After that point, they are far harder to introduce without creating conflict.

The best scope documents are written with the problems already anticipated. They describe not just what the architect will do, but what will happen when things change – because on most projects, things change.

A scope that accounts for that reality is the most valuable professional tool an architect can bring to an appointment.