On this page
Why a sprint needs a revision budget
An offshore design sprint can consume its revision allowance before the first client review if nobody defines what the allowance covers. The team may treat every comment as included, while the client expects a fixed number of rounds. A written budget check turns that ambiguity into a shared expectation before the work starts. The check is not a pricing negotiation. It is an operating record that states the number of rounds, the type of changes included, the turnaround for each round, and the person who approves an exception. That record protects the designer from unlimited rework and the client from surprise limits.
Define the revision unit
A revision round is not a single comment. It is a bounded review cycle in which the client reviews a version and returns a consolidated set of changes. The budget should state how many rounds are included and what counts as a new round rather than a correction of the previous one. Write the definition in plain language and put it in the project brief. If a client sends changes in three separate messages, the coordinator should consolidate them into one round with a dated summary. That summary becomes the record for the next review.
Separate included changes from new scope
Content corrections, spacing adjustments, and image swaps may be included in the revision allowance. A new page, a new component, a new language, or a change to the approved information architecture is usually new scope. The budget check should list examples of each so the team can classify a request consistently. When a request is ambiguous, the coordinator records the question and routes it to the account owner. The designer should not absorb a scope change silently to keep the client happy. That decision belongs to the person who owns the commercial relationship.
Check the budget before the sprint starts
Before the sprint begins, confirm the approved brief, the number of included rounds, the review owner, and the feedback window. Check that the client has the materials needed for the first review, including content, brand assets, and approval authority. A sprint that starts without those inputs often spends its first round collecting them. Record the check date and the people who confirmed it. If the client cannot provide an input, mark the dependency and decide whether the sprint can proceed. Do not start the clock on the revision budget until the required inputs are available.
Track usage during the sprint
The coordinator should update the revision log after each round. Record the round number, the date received, the changes requested, the classification, and the remaining allowance. The log should be visible to the designer and the account owner, not kept in a private note. When the allowance is nearly exhausted, raise the question before the next round begins. The client can consolidate the remaining requests, approve additional scope, or defer some changes. That conversation is easier before the work than after the designer has already implemented another round.
Close with a revision summary
At the end of the sprint, summarize the rounds used, the changes included, the exceptions approved, and any open requests. Attach the summary to the final handoff so the next phase starts with a clear baseline. If the client requests more changes after the summary, treat them as a new scope decision. A quarterly review can compare the budget check with actual usage. If most projects exceed the allowance, the template or the brief is probably unclear. Fix the input, not the reminder.
Keep the check short enough to use
The budget check works when it fits on one page and names the few facts the team needs before starting. It should not become a second contract or a transcript of every comment. Keep the revision unit, the included examples, the review owner, and the exception path visible. The test is whether a new coordinator can open the brief and explain the allowance to the client without asking the designer. If that is possible, the check is doing its job.
Turn the guidance into a reviewable handoff
Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.
Plan a website production handoff