Acceptance Criteria Before Adjectives: Writing Briefs a Stranger Can Price
Most task briefs fail in a predictable way. They describe the kind of person wanted and the mood of the project, then leave out the thing a worker needs most: a definition of what finished looks like. A stranger reading "we need a friendly, detail-oriented writer for our product pages" cannot tell how many pages, what counts as done, who approves the work, or whether revisions are included. The result is wasted applications, mismatched expectations and disputes that were never really about quality. This article takes a narrower angle than general advice on tone or formatting. It focuses on acceptance criteria, the observable conditions that let a reader decide whether they can do the work and how the work will be judged. Writing these well is less about polish and more about removing guesswork.
Start With the Observable Output
Begin the brief by naming the deliverable in a form someone else could inspect. Instead of "improve our onboarding," write "a revised onboarding email sequence of five messages, each under 150 words, delivered as a single document with subject lines." The second version tells a worker what they will hand over, in what format, and at what size. If you cannot describe the output this concretely, the task may not yet be ready to post, and that is useful information to discover before anyone applies.
Separate the output from the process. Saying that a worker should use a particular spreadsheet method, interview technique or research source is sometimes necessary, but it belongs in a separate line marked as a requirement, not mixed into the description of what you want. Readers often assume that a method is a choice they are free to make, and they only find out it was mandatory after they have committed time.
Write Acceptance Criteria as Checkable Statements
Acceptance criteria are statements that a reviewer can answer yes or no to after receiving the work. Good examples include: every figure cites its source in a footnote; the document contains no claims about competitors; the code runs on the stated version without modification; the summary fits on one page. Weak examples include: the work should be high quality, professional, or engaging. Those words describe hopes, not tests.
Aim for three to six criteria. Fewer than three usually leaves the reviewer improvising; more than six often signals that the task has been bundled and should be split. Each criterion should be something you could verify in a few minutes without asking the worker a question.
Define the Boundaries Explicitly
Boundaries are the limits of the job: what is in scope, what is excluded, how many revision rounds are expected, and what happens if new requirements appear midway. Many disagreements between employers and workers trace back to an unstated boundary. A worker who assumed one revision round and an employer who expected unlimited edits will both feel wronged, and neither was acting in bad faith.
State the boundaries in the brief itself. Include the number of review rounds if you intend to have any, the point at which additional requests would be treated as a new task, and whether source material or tools will be supplied. If you do not know yet, say that you do not know and describe how the question will be resolved, rather than leaving a silent gap.
A Short Pre-Posting Checklist
Before publishing, read the brief as if you were a capable professional who has never met you. Confirm that the deliverable is named in concrete form. Confirm that each acceptance criterion could be checked by someone without further explanation. Confirm that scope, exclusions and revision limits are written down. Confirm that any required method or tool is labelled as a requirement. Confirm that the compensation you state is an indication and that you have not implied it is guaranteed or already funded.
The last point matters especially on open listings. A brief that describes a proposed need is not the same as a confirmed vacancy, and readers deserve to know which they are looking at. Stating the status of the opportunity plainly, along with the criteria and boundaries, is what allows an independent worker to decide quickly and fairly whether to apply.
A brief written this way will not guarantee a hire or a good outcome. What it does is make the decision easier for both sides, because the question shifts from "what did they mean?" to "can I produce this?", which is the question that should have been asked from the start.