Decide what needs approval before work begins
Client approval is most useful when it marks a decision that affects the next stage of a project. For a design project, those decisions might include the brief, a chosen direction, a developed design, and the final files. A smaller project may need fewer checkpoints. Too many can slow progress; too few can leave important assumptions untested until the work is nearly finished.
At the start, agree on what each milestone covers, who can approve it, and what happens afterward. An approved direction, for example, might mean the freelancer can develop the selected concept rather than continue exploring alternatives. Name the approver if several people will provide feedback. Others can contribute, but one person should gather their comments and communicate the decision. This keeps conflicting opinions from becoming competing instructions.
Send a review request that is easy to answer
A vague message such as “What do you think?” invites a wide-ranging conversation when you may need a specific decision. Instead, identify the milestone, describe what the client is reviewing, and state exactly what you need them to approve. Link or attach the relevant version, using a consistent file name so it cannot be confused with an earlier draft.
Give the client enough context to judge the work. Briefly explain how it responds to the agreed brief and point out any choices that still need their input. If the review is limited to layout and direction, say so; otherwise, a client may assume every detail is final. Ask for feedback by a reasonable agreed date, and explain how a delayed decision could affect the next step. Avoid treating a missed deadline as approval unless that arrangement was clearly agreed in advance.
A simple request could read: “Please review homepage concept v2 for layout, visual direction, and content hierarchy. Are you happy for me to use this direction for the remaining pages? If changes are needed, please send one consolidated list by Thursday. Final copy and mobile details will be reviewed separately.”
Separate feedback from a decision
Feedback tells you what someone notices or wants changed; approval authorizes you to proceed. A message containing both praise and revision requests is not necessarily a sign-off. If the decision is unclear, reply with a short summary: what you understand to be approved, what remains open, and whether the requested edits need another review.
Conditional approval can be useful when the remaining changes are narrow. For example, a client might approve a layout provided one image is replaced. Record the condition, make the change, and confirm whether the client wants to check it before the next milestone. If feedback introduces a substantially different direction, pause to discuss its effect on the work rather than quietly treating it as a minor revision. A clear decision at this point is easier to act on than several scattered comments across messages.
Keep a record that someone else can understand
Document approvals in the project’s usual communication channel, even if the decision was made on a call. A useful record includes the milestone, the exact version reviewed, the date, the name of the approver, the decision, and any conditions or outstanding items. Keep the approved file with that record or provide a stable reference to it. “Approved the design” is much less useful later than “Approved homepage concept v2 for desktop layout and visual direction; mobile layout remains open.”
After a meeting, send a concise recap and invite corrections: “My understanding is that concept B is approved for development, with the navigation labels to be revised. Please let me know if I missed anything.” This is not a substitute for an explicit approval request when one is needed, but it gives both sides a chance to correct the record. Store decisions somewhere the project team can find them, rather than relying on memory or searching through multiple chat threads.
Use approval to guide the next step, not end the conversation
Once a milestone is approved, restate what happens next and which decisions are still ahead. This helps the client understand that approving a concept does not mean they have seen every final detail. It also gives the freelancer a clear basis for continuing work.
If a client later wants to revisit an approved choice, approach it as a new request to discuss, not as a failure of the approval process. Clarify what would change, what work may need to be repeated, and whether the plan or timeline needs updating before proceeding. Good documentation does not prevent every change. It makes changes easier to discuss fairly, with a shared understanding of what was decided and when.
