How to manage client revisions without working for free: tips from Uspacy

Gradually, the scope of work expands, deadlines shift, while the cost remains unchanged. The team spends additional time that was never accounted for during the planning stage.

The problem isn’t the revisions themselves—changes are a normal part of working with clients. What matters is learning how to manage them in a way that meets the client’s needs while protecting the business’s resources.

In project management, there is a concept called scope creep — the uncontrolled expansion of the scope of work without a corresponding adjustment to the budget, timeline, or resources. This is how one “small revision” can gradually turn into an additional project within the scope of the original order.

A client may ask to change an approved concept, add a new element, or provide an additional service. Each request may seem insignificant, so the manager agrees to it without conducting an additional assessment.

As a result, the cost of fulfilling the order increases, profitability declines, and the workload on employees grows. Additional work takes time that was allocated to other projects. Without tracking actual time spent, it becomes more difficult for managers to assess the profitability of client orders and forecast the team’s workload.

To avoid these situations, the first step is to distinguish between routine revisions and new work that falls outside the scope of the original agreement.

Not every change request requires an additional payment. The decision depends on what was agreed upon with the client at the beginning of the engagement.

It's important to distinguish between three types of changes:

• Correcting an error made by the provider. If the team did not complete the work according to the specifications, it must correct the issue as part of its existing obligations.
• A revision within the agreed scope. For example, the contract includes two rounds of design revisions. If the client uses one of them, no additional payment is required.
• A new client request. The client asks to add a feature, change an approved concept, or provide an additional service. Such work requires a separate estimate of the cost and timeline.

The key reference point is the documented agreement—not a manager’s subjective feeling that a revision will “only take a little time.”

When a new request falls outside the scope of the original order, the next step is to estimate the resources required to complete it.

Even a request that seems simple at first requires an estimate. A manager should not promise completion until the team determines how much time is needed and how the change will affect the current plan.

Start by documenting the new request. Then estimate the required effort, assign the responsible team members, and determine whether the budget and deadlines will change. Only then should you prepare a proposal for the client.

Discussing additional fees is easier when they are supported by specific calculations. Instead of saying categorically, “That’s not included in the order,” offer several options: complete the work for an additional fee, move it to the next phase, or replace part of the original scope.

For recurring minor revisions, consider offering a support package. When each adjustment takes 20–30 minutes, agreeing on the cost separately each time can be inconvenient. However, these requests can quickly add up to hours of additional work. A solution is a package with a prepaid number of hours, such as 5 or 10 hours. The client can use this time gradually for new requests, while the team tracks the actual effort spent. If necessary, you can set an expiration date for the package, such as three months.

This approach gives the client flexibility while allowing the business to maintain control over its resources. Once the new terms have been approved, it is important to communicate them clearly to the team.

Getting a revision approved by the client is only half the job. Everyone involved in the project needs to understand what has changed and how it affects their work.

Keep the original agreements on record, document new requests, and separate approved changes from those awaiting a decision. Once a change is approved, update the tasks and deadlines and notify the people responsible.

The team should not begin additional work until its scope, priority, and execution terms are clear. Otherwise, employees may spend time on requests that the client has not yet approved.

Pay particular attention to tracking actual time spent. Comparing planned hours with actual hours helps you estimate future projects more accurately and determine the true cost of additional work.

This approach helps you maintain control over the project, even when the client regularly changes their requirements.

When a client changes their requirements, it’s important not only to agree on the new terms but also to organize the work properly. In Uspacy, you can combine CRM, tasks, team discussions, and time tracking to manage the process. This allows the manager to keep track of agreements while giving the team a clear understanding of what needs to be done and how many resources are required.

CRM helps you store the original order terms and document new client requests. In the deal record, you can review the history of the client relationship, the agreed budget, and any changes to the original agreement. This approach to managing deals in CRM makes it easier to distinguish additional work from tasks that are already included in the order.

Tasks and subtasks help organize revision work. Once changes are approved, the manager assigns responsibilities, sets deadlines, and distributes the work among team members. Proper task assignment helps avoid unnecessary back-and-forth, while comments allow employees to discuss details and document results.

Time tracking helps monitor actual effort. In tasks, you can specify the estimated time and record actual time using a timer or manually. This time tracking allows managers to see how many hours the team has spent on additional work and estimate the cost of future orders more accurately.

For example, for support packages, Uspacy allows you to create separate tasks with a clearly defined number of hours. Suppose a client purchases a 10-hour package for minor advertising campaign adjustments. The manager creates a task, specifies the estimated time, and sets a deadline corresponding to the package’s expiration date. When an employee starts another revision, they start the timer and stop it when the work is complete. With time tracking in tasks, the hours worked are included in the actual effort calculation, while the manager can compare them with the planned allocation and monitor the remaining prepaid hours.