Bullets beat paragraphs for anything you will need to point at later

Write a scope box as two short bulleted lists - included and not included - with a number in every line that can take one. A scope has to tell a buyer what they get before they pay and settle the argument if they later think otherwise, and prose does the first badly and the second not at all.

A paragraph is read once, at speed, by someone deciding whether to book you. A list is read once at that speed and again, line by line, on the day it matters.

Why the format decides the outcome

When a job goes sideways, you or the buyer or a platform moderator will end up quoting the scope back at each other. What gets quoted is a line. Nobody quotes a subordinate clause from the middle of a 90-word paragraph, and if they do, the other side reads it as lawyering rather than as the plain terms they agreed to.

There is also an attention argument, and it is not a small one. Jakob Nielsen's analysis of 45,237 logged page views estimated that users read about 20% of the text on the average page (Nielsen Norman Group, 2008), and later eyetracking by the same group found the first few words of each line draw more fixations than the rest. That is not a reason to write badly. It is a reason to put the load-bearing words at the front of short lines.

The two lists

Every workable scope box is two lists with a heading each. Included, then not included. The second list is the one that does the work, and it is the one most earners leave out because it feels negative.

It is not negative. It is the difference between a buyer who is disappointed and a buyer who was never expecting the thing in the first place.

A written assessment scope looks roughly like this.

Included

• One written assessment, 600 to 900 words
• Scores on four named axes, each with a written reason
• Delivered as a PDF, within 48 hours of the brief
• One round of clarifying questions after delivery

Not included

• Rewrites or a second assessment of new material
• Comparison against another submission
• Anything outside the four axes listed above
• Live discussion, calls or scheduled sessions

Four to six lines a side is the working range. Below four you have not said enough to prevent anything. Above eight the list stops being scanned and becomes a paragraph with bullets in front of it.

Wording that prevents the common misunderstandings

Three misunderstandings account for most of the friction in this trade, and each has a phrasing that heads it off.

Quantity, not adequacy. Write "one round of clarifying questions", not "reasonable follow-up". Reasonable is whatever the person reading it thinks is reasonable, and the person reading it has an interest. Every line that could be settled with a number should have a number in it.

A new instance is a new job. The single most common drift is a buyer sending a second submission and treating it as part of the first. "Assessment of one submission; additional submissions are booked separately" ends that conversation before it starts, and it is far easier to write in advance than to say to someone mid-job.

Delivery is a clock, not a mood. "Within 48 hours of the brief" is enforceable. "Fast turnaround" is a feeling you have promised. State what starts the clock too, because a job where the brief arrived incomplete has not started, and you want that written down rather than argued.

Two more that are worth a line each if they apply to you: what file or format arrives, and what happens if the material cannot support the assessment asked for.

Where the box goes, and how many of them you need

It goes in the listing, and then again in the confirmation message when a job is booked. The listing version persuades; the confirmation version protects. The two-sentence confirmation that carries the same content into the message thread is what a moderator will actually look at, because it is timestamped and specific to the job.

One box per format. If you sell a written assessment and a recorded one, they have different lengths, different turnarounds and different exclusions, and a merged box that tries to cover both is the one that will fail. This is also why listing several services without confusing anyone is mostly a structural problem rather than a copywriting one.

What it is not for

A scope box is not a terms-and-conditions document, and lengthening it does not make it stronger. The strength comes from being short enough that a buyer has genuinely read it, which is the only condition under which "you agreed to this" means anything.

Nor is it a substitute for saying yes to the small extra thing occasionally. Scope exists so that the extra thing is a decision you make rather than an erosion you notice three requests too late; the mechanics of handling one when it arrives are a separate skill from writing the box.

Buyers, for their part, mostly do not arrive intending to squeeze anyone - the commissioning side's own account of how a request is normally framed describes a fairly polite process, and most scope creep is genuine confusion rather than pressure. Be precise about anything that sounds like a measurement, because a buyer who has read the conventions for how measurements are stated will expect your numbers to mean what those numbers usually mean. And be explicit that you are excluding what an automated tool already gives away free, since what an automated score covers is the baseline your buyer has almost certainly already seen.

If the platform you work through has its own scope fields rather than a free-text listing, use them as written rather than duplicating them - Rate Cock's judge listings put the inclusions in structured fields, and a scope box that contradicts the structured version is worse than no box at all.