Changing requirements after approval: why a scope clause is necessary
It's not that the client is difficult. It's not that the designer is inflexible. This is a contract structure issue.
Requesting changes after the design idea has been approved is the most common cause of design projects exceeding costs and timelines. The solution is to establish a clear scope clause from the beginning. Each change outside the signed scope needs a transparent handling process and corresponding costs.
Requesting changes after the design idea has been approved is the most common pain point in the branding design industry. Not because clients intentionally create difficulties, but because no one has established a structure to handle it from the start. The result: the studio wastes time, the client loses money, and the relationship becomes strained just when the project needs trust the most.
Why changes during the project are not anyone's fault
A branding project lasts from six to twelve weeks. During that time, the market changes, leadership holds additional meetings, and internal personnel may change. Or simply, you look back at the approved design idea and realize it does not align with something important. That is normal. Branding is a strategic decision, not a print order. Additional thinking during the process is a sign of seriousness, not a lack of preparation.
The issue is not whether changes occur or not. The issue is that no one communicates in advance how changes will be handled. When that happens, both sides are confused: the studio does not know whether to charge extra, and the client does not know if their request is reasonable. That ambiguity is what breaks the relationship, not the changes themselves.
Understanding the project scope correctly
The project scope is the set of what has been agreed to be executed, within the signed timeline and budget. Anything outside of that set is a scope change, no matter how small it may seem.
In brand design, this boundary is particularly easy to blur. A request to "add a secondary color to the system" sounds simple. But in reality, it entails re-evaluating the entire existing color application, adjusting the guidelines, recreating templates, and seeking approval again. A request to "try changing the font" can disrupt the carefully constructed visual hierarchy. No one is lying when they call these things "minor fixes." They truly do not see the workload behind them.
The designer's job is not just to create something that looks good. The job is to manage decisions, defend the reasons behind each choice, and know when to say no.
Blair Enns, The Win Without Pitching Manifesto
Mechanism of the scope clause: four core components
The scope clause is the structure for both parties to know where they stand, not a tool for the studio to refuse revisions. An effective clause needs to have four components.
First: clearly define what a "revision round" is. Specifically: how many feedback instances count as one round, through which channel feedback is sent, and within how many working days. Without defining this, "three rounds of revisions" in the contract can turn into thirty individual adjustments over two months.
Second: clearly categorize which changes are within scope and which are not. Within scope typically includes: adjusting colors based on feedback from the presentation, refining proportions and spacing, changing text content in the approved layout. Outside of scope typically includes: changing strategic direction after the design idea has been approved, adding new application categories, or starting over after a presentation.
Third: the process for handling changes outside the scope must be documented. Specifically: the studio will assess the additional workload, send a supplementary quote, and only continue after receiving written confirmation. This is not a cumbersome procedure; it is a way to ensure no one is caught off guard.
Wednesday: specify the consequences of changing the scope on the timeline. When the scope changes, the delivery time also changes accordingly. The clause should clearly state: each time a change outside the scope is approved, both parties will initial the new adjustment schedule.
Presenting the clause to the client: non-confrontational language
How the scope clause is presented is just as important as its content. If you hear the studio say "additional revisions will incur a fee" without context, the natural reaction is defensive. But if you hear "this is how we protect your timeline and budget," the reaction will be completely different.
Sinh Vũ presents the scope clause during the kick-off meeting, not in a contract email sent before signing. The reason: when sitting together and understanding the project goals, explaining "why the scope needs to be protected" has specific context. It becomes a discussion about how to work together, not a cold legal clause.
The statement to make clear to clients: "When you request changes outside the signed scope, we will not refuse immediately. We will assess and inform you how it affects the timeline and budget. You decide. We will proceed according to that decision." There is nothing contradictory in that statement.
When changing requirements is a sign that the brief is insufficient
Not every change after the design idea is approved comes from whim. A significant portion arises from the initial brief (project requirements document) being insufficiently deep. Suppose the brief only describes the product and preferred colors. There is no positioning, no specific target customers, no competitors to differentiate from. In that case, the first approved design idea is merely a gamble. In hindsight, you realize it was not right because it truly lacked enough information to be correct.
This is why Sinh Vũ dedicates an independent discovery phase before starting any design work. A good brief is a document that questions competitive positioning, buyer behavior, and what the brand needs to achieve in the next three years, rather than a list of preferences. When discovery is deep enough, the number of strategic changes during the project significantly decreases because everyone has agreed on the foundation before starting to build.
Boundaries that protect relationships, not break them
A well-constructed scope clause does not make clients feel controlled. It makes them feel respected because the studio is professional enough to speak frankly. Conversely, a studio without clear clauses often accumulates frustration with each additional unpaid revision. That frustration leaks out through the quality of work, response speed, and overall team spirit.
The best client relationship is a structured one that can handle tension when it arises, not one without tension. No one needs to feel ashamed or defensive. The scope clause is that structure.
References
Project Management Institute (PMI), Pulse of the Profession 2021. Marty Neumeier, The Brand Gap. Mike Monteiro, You're My Favorite Client. Blair Enns, The Win Without Pitching Manifesto.
Frequently asked questions
Do the terms of the scope make you hesitant?
On the contrary. A clearly defined scope clause before signing is often appreciated more by clients than silence followed by disputes during the project. It shows that the studio has a professional process and respects both parties.
If the client wants to completely change direction after approving the design concept, what should be done?
This situation is referred to as a 'scope reset,' different from minor fixes. The studio needs to pause, assess the volume of changes, draft a new contract addendum with adjusted budget and timeline, and then continue. Skipping this step is a primary cause of project losses.
Do small studios or freelancers need scope clauses, or is it only for larger studios?
More necessary, not less. Large studios have legal departments and ready-made contract templates. Smaller studios and freelancers often suffer the most when there are no clear clauses because they lack sufficient leverage to renegotiate mid-project.