Two sentences before you start, every time

Almost every dispute in this trade is an argument about what was agreed, and almost none of them would exist if what was agreed had been written down. The fix is two sentences, sent in the platform's own messaging before you begin, on every job including the obviously fine ones.

It is not a contract and it is not a negotiation. It is a timestamped record that names the deliverable and the date, produced by you, in the place a moderator will look.

What the two sentences have to contain

Four facts, and no more than four, because a long confirmation reads as suspicion and gets skimmed.

The deliverable, named as an object. Not "a review" but "a written assessment of around 500 words, across the four axes on my listing, as a PDF". A buyer cannot later say they expected video if the message says PDF.

The date. An actual date, not "within 48 hours", because 48 hours from what is the second most common thing people disagree about.

What is included beyond the deliverable. Usually the revision allowance: one round of corrections, or none, or clarifying questions answered for a week. Say the number.

What the buyer still owes you. If you are waiting on material, say that the clock starts when it arrives. Half of all late deliveries are late because the buyer sent something on day three of a three-day turnaround.

Here is the whole thing in practice: "Confirming: one written assessment, around 500 words across the four axes listed, delivered as a PDF by Thursday 21st, including one round of corrections. Starting now unless you want anything changed."

The second half of that last sentence is doing real work. It converts your record into their agreement, because a buyer who reads it and does not object has accepted it, and moderators treat an unchallenged confirmation as agreed terms.

Where you send it decides whether it exists

On the platform. Not by email, not in a chat app, not in a direct message on a social account you also use for something else.

A dispute is decided by someone reading the message history the platform holds. Anything outside that history is a screenshot, and a screenshot of a conversation held somewhere else persuades nobody, because it is trivially editable and the platform cannot verify it. Card disputes run on the same logic: Stripe's dispute documentation says a "not as described" claim is answered by showing the service "was accurately represented prior to purchase", with communication with the customer as supporting evidence.

This is also the practical reason not to move a job off-platform for a buyer's convenience. The commission is buying an evidence trail, among other things, and what a platform commission actually buys is worth pricing honestly before you agree to skip it.

Why you send it to the pleasant buyers too

The selection is the problem. If you only confirm scope when a buyer seems difficult, you are relying on your ability to spot a difficult buyer from three messages, which nobody can do.

The jobs that go wrong are almost never the ones that looked like they would. They are the friendly ones where everything was easy until an offhand "could you also" on day two, and then a second one, and then an expectation you never agreed to and cannot now point at.

Universal application also removes the tone problem. A confirmation you send every time reads as process. A confirmation you send only sometimes reads as an accusation, and buyers notice.

What it saves you when nothing goes wrong

Most of the value is not the dispute you win. It is the twenty small negotiations that never happen because the answer is already in writing above the request.

Scope creep is not usually an attack. It is a buyer who genuinely does not know where the edge is, asking a reasonable-sounding question. When the edge is written down, they mostly stop at it without being told, and when they do not, you can quote yourself instead of drawing a new line under pressure - which is a much easier conversation, and the wording that keeps a revision policy from collapsing sits directly on top of it.

There is a pricing effect too. Buyers who receive a precise confirmation ask for fewer extras and leave more specific reviews, because the confirmation told them what to notice.

The version for larger jobs

Above a certain size the two sentences stop being enough, and the threshold is roughly the point where the fee would hurt to lose.

For those, name the payment schedule and the cancellation terms as well: what happens if the buyer withdraws halfway, and whether any part of the fee is non-refundable. This is not lawyering, it is arithmetic - you are deciding in advance who carries the cost of an abandoned job, and if you do not decide, it is you.

The same discipline is what makes disputes survivable when one does arrive, and the evidence that actually carries weight with a moderator is mostly the confirmation plus the delivery record, in that order.

Buyers, for their part, are not surprised by any of this. The commissioning side treats a confirmation as ordinary professional behaviour, and the buyer-side account of how a job normally opens describes it as the point at which they relax rather than the point at which they get nervous. Where confirmations do get awkward is when the deliverable is a number and the buyer expected something the number cannot carry, which is a definitional problem rather than a scope one - what a score is and is not claiming is the reference for that, and naming the axes in your confirmation heads off most of it. If precision itself is what you are selling, the conventions worth naming explicitly are documented on the measurement side rather than invented per job.

Platforms differ in how much of this they hold for you and for how long. Rate Cock's judges page sets out what its own order flow records automatically, which is the part you do not need to duplicate.