How to Accept a Freelancer's Work: Checks and Revisions

How to Accept a Freelancer's Work: Checks and Revisions

Accepting a freelancer's work means checking the result against the brief you wrote, collecting every note into one list, allowing the agreed number of revision rounds, and paying. Everything else is improvisation — and improvisation is where disputes come from. The real secret: acceptance is won on the day you write the brief, not on the day of delivery.

The classic story: the designer sends a mockup, the client looks at it and writes "hmm, not quite it, redo it". A week of messages later both sides are angry, the mockup is worse than the first version, and the budget and timeline have doubled. Here is how to avoid that.

Acceptance criteria are written before the start, not after

Acceptance criteria are a few lines in the brief that answer one question: by which checkable signs will we know the work is done? Not "beautiful", not "converting" — specifics you can verify in five minutes.

  • Format and scope: "home page plus 3 inner pages, Figma file, desktop 1440 and mobile 375".
  • Technical requirements: "mobile PageSpeed 80 or higher", "4,500–5,000 characters", "logo in SVG, PNG and a one-colour version".
  • Checkable quality: "plagiarism check above 90% original", "no horizontal scroll on an iPhone SE".
  • What revisions cover: "2 rounds of revisions within 5 business days after delivery".
  • What gets handed over: source files, fonts, rights.

If writing that from scratch feels hard, build the brief in the free brief generator — it walks you through the questions and gives you a document you can point at during acceptance. A deeper walkthrough lives in how to write a proper brief for a freelancer.

Any requirement that cannot be checked without your mood is not a requirement — it is a wish. Wishes are not accepted and not paid for. They are discussed.

Review against the brief, not against your gut

Open the brief and walk it top to bottom, line by line. Mark each one: done / not done / done differently. Only then look at the work as a whole and ask whether it solves the problem you hired for.

Three rules that save your nerves:

  • Check it in real conditions. Copy inside the layout, not in a document. The site on your own phone, not only on a 27-inch monitor. The logo shrunk to avatar size.
  • Sleep on it. The first reaction to an unfamiliar solution is almost always "not it". Look again a few hours later — half your notes will disappear on their own.
  • Do not crowdsource the verdict. "My wife doesn't like blue" is not an acceptance criterion. If other people sign off, name them in the brief — not on day eight.

One list of revisions, not twenty messages

The worst thing you can do to a contractor is drip notes one by one across five days. They cannot plan, every new detail breaks something already finished, and the project gets more expensive for you.

Do it this way: gather every note in one pass, group by section, number them, send once. A good revision note has three parts: where — what is wrong — which brief item it breaks.

Bad: "The header feels dull, play with the fonts."

Good, copy freely:

  • "1. Home, first screen: headline wraps to two lines; brief item 3 says one line, max 60 characters."
  • "2. Catalogue, product card: price disappears while scrolling on mobile (iPhone 13, Safari). Item 7 says the price stays visible."
  • "3. Global: the Buy button appears in three shades of green. It should be the one from the style guide."

If a note is subjective, say so honestly: "This is my feeling, not a brief requirement. Propose something if you agree." That tone costs less than any pressure. More on tone and message threads in how to handle client communication and revisions.

How many revision rounds are fair

The working market norm: 2 rounds covering up to 10–15% of the work, within 5–10 business days after delivery. Big projects get 3, small tasks often need one. What matters is that the number was named before the start and means the same thing to both sides.

Why are "unlimited revisions" bad for you first? A contractor selling unlimited either prices the risk in — you pay 40% more — or saves effort on the first attempt because they know it will be redone anyway. Limited rounds force both of you to think before, not after.

Revision or new task: where the line is

A revision brings the work in line with the brief. A new task changes the brief itself. One question settles it: was this written down before?

  • "Fix the spacing, it drifted" — revision.
  • "Let's try a different colour scheme" after the concept was approved — new task.
  • "Add two more pages" — new task, always.
  • "There's a typo here" — revision.
  • "We changed our positioning, rewrite the copy" — new task, and that's fine: businesses change.

Growing the scope is normal — just pay for it separately. The fair pattern: the freelancer quotes price and time for the addition, you confirm, work continues. Smuggling new work in disguised as a revision is the fastest way to lose a good contractor and earn a bad review.

When the work is genuinely bad

It happens. First separate "I don't like it" from "it does not match the brief" — only the second one wins a dispute. Then, step by step:

  • Write out exactly which brief items are unmet, with screenshots and links.
  • Give a reasonable deadline to fix it — usually 2–5 business days.
  • If a full revision round brings no movement, offer to close the deal on what exists: partial payment for the accepted part, nothing for the rest.
  • Working through escrow? Open a dispute and attach the brief and the thread. That is exactly why every agreement belongs in writing on the platform. More in the guide to safe deals and fraud protection.

Demanding a full refund for work you are already using is dishonest and loses disputes. If it truly does not fit — do not take the files.

What to check before the final payment

Payment is your last point of leverage. Run the list:

  • Source files: the Figma or PSD with layers actually named, not "Layer 47 copy 3"; the edit project; the repository with history.
  • Formats: everything you asked for — SVG, PNG with transparency, print-ready PDF, fonts or links to them.
  • Rights: written confirmation of the transfer of rights and licences for any stock, fonts and plugins used. Critical for logos and commercial video.
  • Access: hosting, domain, admin panel, analytics — on your accounts, not the freelancer's.
  • Instructions: two paragraphs on how to update this if they vanish tomorrow.

Close the deal properly

Accepted? Pay now, not "Monday, with the batch". A week of silence after "looks great" costs you more reputation on the platform than that week is worth in cash.

And leave a review: 3–4 concrete sentences about deadlines, communication and quality beat five stars with no text. Freelancers pick clients with a good history first and quietly move them up the queue.

The whole thing in one line: a clear brief, a line-by-line check, one list of notes, agreed rounds, and an honest line between a revision and a new task. That is not bureaucracy — it is how you get the result on attempt one or two.

Ready for the next project? Post your task with real acceptance criteria, browse the freelancer catalogue, and check price levels across open projects. Unsure who to hire — start with how to find a reliable freelancer without losing money.

Article author: Dmitry