Why projects fail to end
Design work does not finish by itself. Without structure, each round of feedback can raise new questions, and each new version can invite fresh opinions. The project drifts, the schedule slips, and the designer’s time stretches far past the original plan. The cause is rarely bad intent. More often, nobody defined what “done” meant or how decisions would be made.
A structured revision process answers three questions in advance: when feedback happens, who gives it, and how a stage gets approved.
Define the rounds up front
Many designers include a set number of revision rounds in the agreement, often a small number, though the right count depends on the type of project. A round means one cycle of consolidated feedback followed by one set of updates from the designer. It does not mean every individual comment, and it does not mean unlimited tweaks until the client is content.
Stating this clearly at the beginning does two things. It tells the client that their feedback is expected and welcome, and it encourages them to make each round count. It also gives you a fair basis for discussing extra rounds if the project needs them, which relates closely to project scope and how changes are handled.
Work in stages that lock
A common reason for endless revision is that early decisions are reopened late. If the client approves the overall direction and then changes it when seeing the final polish, the work done in between is lost.
Breaking a project into stages helps. A typical sequence might be:
- Direction. The client chooses a concept or approach.
- Development. The chosen direction is built out.
- Refinement. Details such as spacing, color and wording are adjusted.
- Final. Files are prepared and delivered.
At the end of each stage, ask for explicit approval before moving on. Explain that earlier stages are considered settled once approved, and that returning to them may affect the cost and schedule. This is not meant to be rigid. It is meant to help the client understand that choices build on one another.
Ask for feedback that can be used
Vague feedback such as “make it pop” or “it does not feel right” is hard to act on, and guessing leads to extra rounds. You can guide the client toward more useful comments in several ways.
- Ask them to relate feedback to the goals in the brief rather than personal taste.
- Ask specific questions: “Does this tone suit your audience?” or “Is the headline prominent enough?”
- Request that comments be tied to particular elements, ideally on the design itself or in a numbered list.
- Ask what problem a requested change would solve, since the problem is sometimes better addressed another way.
The broader idea of design feedback is covered elsewhere, but in a revision process the key practice is to translate opinions into actionable items.
Consolidate the comments
When several people review the work, individual comments often conflict. One person wants a larger logo while another wants it smaller. A designer who receives these piecemeal can spend hours reconciling them.
Ask the client to gather all comments into a single set before sending it. Better still, have a single decision maker, as mentioned in scope discussions, who resolves disagreements internally. If conflicting notes still arrive, point out the conflict politely and ask which should take priority instead of choosing for them.
Set time limits on responses
Delayed feedback can cost a freelancer as much as excessive feedback, since a designer might hold time open for a project that then goes quiet. Agreements often say how many days the client has to respond, and what happens if they do not: for example, the schedule moves, or the project is paused until the next available slot. Stating this gently at the start is easier than raising it after a long silence.
Record each approval
An approval is only useful if it is clear. Ask for a short written confirmation, such as an email reply saying “approved”, at the end of each stage. Keep it with your project records. If there is ever a question about what the client accepted and when, you have an answer that does not depend on memory.
Make sure the person approving is the person with authority to do so. An informal “looks good” from a colleague may not reflect the decision maker’s view.
Handling extra rounds gracefully
Sometimes a project legitimately needs more feedback than planned. A new stakeholder joins, or the first rounds show that the brief missed something. In those cases:
- Say plainly that the included rounds have been used.
- Offer to continue under a stated arrangement, such as an additional fee or a short scoped add-on.
- Let the client choose, rather than making the decision for them.
Treat it as a practical conversation rather than a penalty. Many clients appreciate the transparency.
Keep the tone constructive
Revision requests are not criticism of you as a person, even if they sometimes feel that way. At the same time, your process is not an obstacle to the client. Explaining why you work in stages, and how it protects their budget and timeline, usually earns cooperation. When feedback is especially frustrating, techniques for working with difficult feedback can help you respond calmly. A process that is clear, kind and consistent is the best protection against a project that never ends.