How to Write a Freelance Revision Policy Clients Can Understand

A clear freelance revision policy defines the deliverable, what one feedback round means, what is included, and how additional work is agreed. A number such as “two revisions” is not enough if one person means two small edits and the other means two completely new concepts.

The goal is a usable collaboration process. This guide walks through an original fixed-scope flyer project, including an error to correct, an included refinement, and a new asset to quote separately. The sample wording is planning guidance rather than legal advice; have contractual terms reviewed for your work and jurisdiction.

Two adult creative professionals reviewing abstract printed layouts together across a studio desk

Key Takeaways

  • Define a round as a specific feedback-and-return cycle tied to a version.
  • Separate your corrections from client-requested refinements and changes in scope.
  • Agree any added fee and schedule before doing additional work.
  • Record the final version and approval explicitly; silence is not a substitute.

What should a freelance revision policy define?

Begin with the work itself. A two-page PDF flyer is not the same deliverable as a website page, a social carousel, or the editable source files. List what will be delivered, for whom, and in which formats before deciding how changes will be handled.

The Freelancers Union Contract Creator provides fields for revision quantity, additional charges, and response periods. Those are useful prompts for a conversation, not a universal set of numbers you should borrow without considering the project.

Your policy should connect five decisions: the included rounds, the meaning of a round, the feedback window, the treatment of work outside the brief, and the approval process. Also explain how you will correct work that fails to meet the agreed specification.

If you have not yet confirmed audience, content, and decision-maker, use our freelance onboarding checklist first. A revision policy cannot make an incomplete brief precise after the first draft arrives.

How do you choose the number of rounds without guessing?

Estimate the review work inside the project, not just production time. Consider how subjective the decisions are, how many people will review, and how expensive changes become after a milestone. A short copy edit and a multi-stage visual concept need different review arrangements.

Choose a number you can describe and deliver within the price and schedule. The example below uses two rounds for one defined flyer; it is not a recommendation that every freelancer offer two rounds.

Tie review to meaningful milestones

For complex work, an early direction review can prevent unnecessary production. Confirm the concept before polishing many variations. If the client later changes the approved direction, assess that request against the agreed scope rather than treating an unused round as permission for any new work.

Leave room for the client to understand your process before accepting it. Ask whether one person can consolidate the feedback and whether the proposed window fits their internal approvals. A realistic window is more useful than a strict deadline everybody expects to miss.

What counts as a correction, a revision, or new work?

Use concrete examples from the project. If you mistype the supplied workshop date, correcting it should not consume the client’s discretionary refinement allowance in the sample policy below. If the client wants a shorter headline within the same brief, that can be an included revision.

A new audience, format, or concept may require a change to the agreed work. The Freelancers Union guide to avoiding unpaid revisions emphasizes defining revision rounds and scope, rather than relying on an informal expectation of endless small changes.

Request in the flyer exampleClassificationProposed handling
Correct a date mistyped by the freelancer.Correction against the brief.Fix it without using a refinement round.
Shorten the introduction for the same audience.Included refinement.Collect it in the next agreed round.
Add a new Instagram carousel.Additional deliverable.Agree scope, price, and timing first.
Replace the supplied event date after drafting.Changed input.Assess impact before promising a fee or deadline.

The last row matters. Not every change fits a rigid label instantly. Ask what changed and what it affects. You can agree to accommodate a small request, but make that decision visible rather than creating an expectation that every future change is included.

What does an original sample policy look like?

Here is sample planning wording for a fictional two-page workshop flyer. It is deliberately specific so you can see the decisions; replace them through discussion for your own project rather than presenting this as a complete contract.

“The agreed deliverable is one two-page PDF flyer for the approved workshop and adult audience. The project includes two refinement rounds. Each round is one consolidated set of comments on the submitted version, followed by one revised version from me.”

“Please return each feedback set within three business days. I will confirm the return date after reviewing the comments. If the window is missed, we will agree a revised schedule; I will not assume that silence means approval.”

“I will correct my errors against the agreed brief without using a refinement round. A new format, additional asset, or changed concept will be assessed separately. I will explain any additional price and timing and obtain written agreement before starting that work.”

“Please nominate one person to combine stakeholder comments and approve the final version. Approval should identify the filename or version number. Delivery of source files, if required, must be listed separately.”

Notice what this wording does not attempt: it does not settle ownership, payment disputes, cancellation, confidentiality, or local legal requirements. Those need their own suitable agreement. A revision process is one part of the project arrangement.

How do you handle a mixed feedback email?

Imagine the fictional client returns three comments on Flyer_v1: fix the incorrect date, shorten the introduction, and turn the flyer into an Instagram carousel. Do not answer the entire email with either an automatic yes or an extra invoice.

Classify, then propose the next step

Confirm that the date error is yours and will be corrected. Accept the shorter introduction as part of refinement round one. Explain that a carousel is a separate deliverable and ask whether the client wants a quotation for it.

An original reply could read: “I’ll correct my date error and shorten the introduction in Flyer_v2. That completes the first included refinement round. The carousel needs a separate layout and export plan; I can quote it once we agree the number and size of slides.”

For this invented case, the client requests a five-slide carousel. You propose an additional $80 and two extra business days, with its own defined review arrangement. These are illustrative terms, not a market rate. The client agrees in writing before you begin.

The outcome is clear: the flyer’s correction and included revision proceed; the carousel becomes separately agreed work. If the client declines the addition, you can finish the original PDF without arguing about whether every item in the email was one revision.

How do you close a round and record approval?

Return the revised file with a short change summary and a stable version name. Explain which agreed comments were addressed and flag any decision still needed. Avoid scattering final files across several messages named Final, Final2, and ActuallyFinal.

  • Keep the submitted version and its consolidated feedback together.
  • Record which round was completed and how many remain under the agreement.
  • Identify any unresolved question before treating the round as finished.
  • Ask the authorized reviewer to approve the named version explicitly.

If two stakeholders give contradictory instructions, request one resolved direction before revising that element. You can continue unaffected work where practical, but explain what is waiting and whether the schedule changes.

Our guide to writing a small-business SOP can help turn this into a repeatable internal process. Keep it short: request, classification, agreement, revised version, and approval. The record should help both parties understand what happens next.

Conclusion

Before sending your next quote, write one sentence defining the deliverable and one defining a feedback round. Add a correction rule, a change-approval step, and a named final approval. Test the policy against a mixed request before a real project depends on it.

Frequently Asked Questions

Should I offer unlimited revisions to reassure a new client?

Only offer an arrangement you can define and sustain. An unlimited label leaves important questions about scope, timing, and approval unanswered. You can reassure clients more concretely by explaining your process, showing relevant examples, and discussing what happens if the first direction misses the brief.

What if a client asks for another change after approving the file?

Check the request against your agreement and the approved version before deciding. A remaining error against the brief needs different handling from a new preference or asset. Explain the classification and any proposed price or schedule, and obtain agreement before additional work rather than assuming approval authorizes a surprise charge.

Leave a comment

E-mail
Password
Confirm Password