Don’t blame the client – scope creep starts with you.

Scope creep is one of the most common frustrations in architectural practice. It is also one of the most misunderstood.

The usual story is simple: the client keeps asking for more. More options, more meetings, more changes, more coordination, more advice, more time. The architect tries to be helpful, the project keeps moving, and somewhere along the way the practice realises it has done a great deal of work it has not been paid to do.

There is truth in that story. Some clients do push boundaries. Some are vague, indecisive or commercially self-interested. Some do not understand how architectural services are structured. Some treat “just one more thing” as if it carries no time, cost or risk.

But in many practices, scope creep begins before the client becomes difficult.

It begins in the way the practice defines the work, manages the relationship and trains its own people to recognise change.

In that sense, scope creep is not just a client problem. It is a practice management problem.

The problem rarely begins where it becomes visible

Scope creep often starts with an unclear agreement.

The fee proposal may describe the project stages but not the practical boundaries of service. It may not say enough about exclusions, assumptions, approval points, client responsibilities, authority delays, consultant changes, builder-driven revisions or what happens when decisions are revisited.

The document may be polite, attractive and professional. It may even be enough to win the work. But if it is not clear enough to guide the project later, it is incomplete as a management tool.

Architects sometimes treat the fee proposal as something that sits at the beginning of the relationship. Once the commission is secured, the real work starts and the proposal fades into the background.

That is risky.

The scope should remain alive throughout the project. It should help the client understand what has been agreed. It should help the team identify when something has changed. It should help the project leader know when to pause, confirm or seek approval for additional services.

If the scope is vague, the practice is left relying on goodwill, memory and interpretation. That may be comfortable at the beginning of a project, but it is a poor basis for managing pressure later.

The generosity problem

Architects are especially vulnerable to scope creep because they care about the work.

That care is one of the profession’s great strengths. It is also one of its commercial weaknesses.

A designer prepares another option because the design will be better for it. A project architect attends an additional meeting because the client seems anxious. A principal absorbs extra coordination because the relationship matters. A team member produces more information than was required because it feels like the right thing to do.

In isolation, these decisions can appear reasonable. Many are made with good professional intent.

The problem is that unpriced generosity accumulates.

Very few practices lose money on a project because of one obvious act of over-servicing. More often, they lose it through a hundred small decisions that no one stops to assess. Each one feels manageable. Together, they become a serious commercial issue.

This is why scope discipline must be cultural, not merely contractual.

A variation clause is useful, but it will not protect the practice if no one uses it. A clear fee proposal helps, but it will not prevent over-servicing if the team is rewarded for absorbing every request. A principal may say they want better scope control, but if they consistently avoid fee conversations, the practice will learn from the behaviour, not the instruction.

The moment to pause

The most important skill in managing scope creep is recognising the moment to pause.

That moment usually arrives before the issue feels serious. It may be a client asking for another design option, a request to revisit an approved direction, a consultant change that increases coordination, an authority requirement that falls outside normal assumptions, or a builder query that opens up additional documentation work.

The practice does not need to respond defensively. It simply needs to stop long enough to clarify what has changed.

A useful response might be:

“We can certainly look at that. Before we proceed, we should confirm whether this sits within the agreed scope or whether it requires an adjustment to time or fee.”

That kind of language is not aggressive. It is professional.

The mistake many practices make is to keep moving. They assume the issue can be sorted out later. They do the work first, hoping the client will accept the additional fee once the value has been demonstrated.

That is rarely the strongest position.

Late fee conversations often feel like claims. Early scope conversations feel like management.

Why late conversations usually fail

Architects often delay scope conversations because they do not want to damage the relationship. This is understandable, especially when the client relationship feels important or the project is under pressure.

However, the delay usually makes the conversation harder, not easier.

By the time the practice raises the issue, the client may already believe the work was included. They may have no memory of the many small requests that created the extra work. They may see the fee claim as unexpected or opportunistic. The architect, meanwhile, may feel frustrated that the client has not recognised how much additional effort has been provided.

Both sides can feel wronged.

This is why good records matter. Written confirmation of decisions, approvals, assumptions and changes is not bureaucracy for its own sake. It is the memory of the project. It protects both the practice and the client from later disagreement about what was requested, agreed and delivered.

It also changes behaviour. When decisions are confirmed clearly, clients are more likely to understand their consequences. When changes are recorded as they occur, additional service conversations feel less surprising. When approvals are treated as real decision points, revisiting them becomes a recognised change rather than a casual preference.

Keeping scope alive through the project

An architecture practice that wants to manage scope properly needs to do more than tighten its contract wording, although that may be a good place to start.

It needs to build scope awareness into the way projects are run.

Project leaders should review the agreed scope at key stages, not only when a problem arises. Teams should understand the difference between normal project development and a genuine change in service. Common scope triggers should be discussed in advance, using examples from past projects. Client approvals should be confirmed in writing. Assumptions should be recorded. Requests outside the agreed scope should be addressed before the work is done.

Principals also need to support their teams when scope issues are raised. If a team member identifies a possible change but the principal dismisses it to preserve goodwill, the practice sends a clear message: the boundary does not really matter.

Over time, this becomes expensive.

The aim is not to turn architects into defensive contract administrators. Nor is it to say no to reasonable client needs. Architecture is a service profession and good service matters.

But good service does not require the practice to absorb every change without question.

A stronger position is to say, “Yes, we can help, and here is what that means.”

That statement protects the client because it gives them clarity. It protects the team because it recognises the value of their time. It protects the practice because it keeps the commercial arrangement connected to the actual work being performed.

Scope creep is often treated as an unavoidable irritation of practice life. It should not be.

A mature practice understands that scope is not just a paragraph in a fee proposal. It is a boundary around the relationship, the service, the team’s effort and the commercial health of the business.

When that boundary is unclear, everyone is left to improvise. The client assumes. The team accommodates. The principal delays the difficult conversation. The project absorbs the cost.

When the boundary is clear and consistently managed, the relationship usually improves. Clients know where they stand. Teams know when to escalate. Additional work is identified earlier. The practice becomes more confident and less resentful.

Scope creep may appear to come from the client, but the practice has more control than it often admits.

That control begins with clarity. It continues through communication. And it depends, ultimately, on leadership discipline.

Because the real question is not whether clients will ask for more. They will.

The question is whether the practice is prepared to manage that professionally.

---

Ross Clark has worked across the architecture industry in almost every capacity — the guidance that he brings from decades working in this industry has been tried, tested and refined working closely with practices just like yours.

If you’re thinking about the next stage of your practice, or want an experienced perspective on how things are currently set up, please reach out.

Get in touch