Three sentences at delivery do most of the work

The message attached to a delivery is treated as packaging and is actually the last piece of work in the job. It frames how the deliverable is read, and it is the only moment where you can influence what the review ends up saying.

Three sentences, always the same three, doing three different jobs.

Sentence one: what was done

Restate the scope in the past tense, briefly.

"Here is the scored assessment across the four axes, around 600 words."

This sounds redundant and is not. It closes the job explicitly, which matters if anything is disputed later, and it re-anchors a buyer who ordered a week ago and has half forgotten what they asked for. It is also the cheapest possible defence against scope drift, for the same reason the two-sentence confirmation works at the other end of the job: what was agreed is now stated twice, in writing, by you.

Sentence two: what to look at first

Point at one thing.

"The section on framing is where most of the detail sits."

This is the sentence earners skip, and it is the one that changes the review. A buyer directed to a specific part reads that part properly and then describes it in their feedback. A buyer given a file with no entry point skims it, forms a general impression, and writes "great, thanks" - which is worth almost nothing to the next person deciding whether to book you.

The choice of what to point at is a judgement. Point at the part with the most specific observation in it, not the part you found hardest to write.

Sentence three: the review request

One sentence, plain, no apparatus.

"If it was useful, a review helps a lot at this stage."

Ask once, at the moment of delivery, when the buyer is at their most positive. Do not follow up, do not ask again on a second job, and do not attach conditions - the reasoning and the platform risk are in asking for a review once. Conditions are also a legal line in some places: the US Federal Trade Commission's 2024 rule on consumer reviews prohibits incentives conditioned on a review expressing a particular sentiment.

What does not belong in it

No apology for anything, including length, timing or tone. An apology invites the buyer to look for the flaw you have just named for them, and half the time they had not noticed it.

No upsell. A pitch for another job in the delivery message converts a completed transaction back into a sales conversation, and it dilutes the review request that is already there.

No explanation of your process. The buyer bought an output.

Why it is worth writing badly rather than not at all

The whole message is under forty words and takes ninety seconds. The realistic alternative is sending the file with "here you go", which is what most people do, which is why turnaround and specificity end up carrying reputational weight they should share with this.

Buyers are frequently unsure what they are supposed to do when work arrives, and an account of how commissioning etiquette runs from their side shows how much of the exchange they are improvising. If the deliverable contains figures, say plainly what convention they follow - the site documenting measurement method is the right thing to point at rather than explaining it yourself. And if you have given a number out of ten, a line on what your scale means saves an argument, because buyers arrive with their own assumptions about what a score signals.

Platform delivery mechanics, including what closing a job does to your payout timing, sit on Rate Cock's judges page, and they determine when the handover message actually needs to go out.