When a freelance project goes badly, the story usually sounds like a character problem: unreliable, not strategic, did not get it. Look closer and the same structural gaps appear. Nobody defined finished. Context arrived after the draft. Feedback came from four people with four opinions. The rewrite was built into the setup.

Define finished before you start

Most briefs describe the work and forget the finish line. Say what the deliverable is, in what format, at what length, and what must be true for it to be accepted. A finished article might mean eight hundred words, three internal links, two sources, a meta description, and a draft in the shared document by Friday at noon.

When acceptance criteria are explicit, feedback becomes a comparison against a list rather than a matter of taste.

Share context, not just tasks

Freelancers work at a distance from the business, so they need more context than employees do. Give them access to the product, the last three pieces of content, the customer questions your support team answers most, and a note on what this piece is meant to achieve commercially.

Thirty minutes of context at the start prevents an hour of explanation later. A short call is usually better than a long document, provided it ends with written notes.

One contact point

Assign one person to give feedback. When three people comment, the freelancer receives conflicting instructions and either guesses or asks for a meeting. Both cost time.

The contact point can gather internal opinions, but should deliver one consolidated response. If a stakeholder must speak directly, make it clear whose view decides.

Two sets of feedback is not twice the quality. It is one more round of revisions.

Give feedback on the draft, not on the person

Comment on the text. Say what is missing, what is unclear, and what should be cut. Avoid adjectives like weak or flat without a reason; they give the writer nothing to act on. Quote the sentence and say what it should do instead.

If the whole structure is wrong, say so in one message before line edits. Detailed comments on a draft that needs restructuring waste both sides.

Send feedback within two working days if you can. A draft that sits for a week loses the thread, and the freelancer has usually moved to another project by the time comments arrive. If you cannot review yet, say when you can.

Limit the rounds

Two rounds of revisions is a reasonable default. Round one addresses structure and content; round two addresses accuracy and polish. A third round is fine when scope changed, but it should be agreed and paid for.

Unlimited revisions create a strange incentive: the freelancer cannot plan capacity, and the client never has to decide. The work drifts instead of finishing.

Brief the deadline backwards. If the piece must be live on the fifteenth, the final file is needed on the twelfth, the second draft on the eighth, and the first draft on the first. Freelancers plan in working days, not calendar days, and a deadline that ignores weekends is a deadline that will be missed. Share the backwards plan in the brief so both sides are working from the same arithmetic.

Pay on time, and keep a paper trail

Pay deposits promptly and pay invoices on the agreed date. Freelancers talk to each other, and a client who pays in two days gets priority when a schedule is tight. If your process takes thirty days, say so in the brief so nobody plans around money that arrives later.

Do not ask for speculative work, free samples, or a discount in exchange for exposure. It filters out the people you actually want.

Store briefs, drafts, and final files in a shared folder rather than in chat threads. Confirm scope changes in writing, even one line in an email. When a project is questioned six months later, the record answers the question.

Agree in advance who owns the source files and the final work, and whether the freelancer may show the piece in a portfolio.

"The usual rate" is not a number. What UK freelance copywriters actually charge is the reference to check before agreeing a figure, and it is the same page a freelancer will check before accepting it.

Habits checklist

  • Written acceptance criteria for every deliverable.
  • Access to product, past content, and customer questions.
  • One person delivering consolidated feedback.
  • Structural feedback before line edits.
  • Two revision rounds in the agreement.
  • Payment terms stated in the brief and met.
  • Files and drafts stored in one shared folder.

None of this is about trust. It is about removing the ambiguity that turns a good working relationship into a rewrite, and a rewrite into a delay nobody planned for.