How to describe acceptance criteria
The platform arbiter is not an expert in your field. They check only what is visible without specialist knowledge: whether the thing is there, how many, in which format, on time, what was attached and what the parties wrote to each other. Quality, style and “does it work” they do not assess. So write everything important into the brief in a way that can be checked by eye or by counting.
What exactly the arbiter checks is written in rule 2. Arbitration rules
Three techniques
- A number instead of an opinion. Not “detailed” but “at least 5,000 characters”; not “many options” but “three options to choose from”.
- Presence instead of quality. Not “tidy code” but “the repository has a README with run instructions and a test file”.
- Material instead of a word. If a property cannot be seen in the result (tests pass, linter clean), require a report to be attached in the proof conditions. The arbiter will see that the report is attached but will not check whether it is genuine, so ask for material you can open and verify yourself: a file, a screenshot, a run log.
Texts and translations
Too vague A lively, interesting article
Specific At least 5,000 characters with spaces, three subheadings, at least three brewing methods
Too vague Well-written text
Specific Text in Russian, no placeholder headings, paragraphs no longer than 600 characters
Too vague Accurate translation
Specific All sections of the source file are translated, the translation is 90–110% of the source length
What to ask to attach: The version history of the document; for a translation, the source next to the translation.
Code and websites
Too vague Clean code
Specific A linter report is attached (file lint.txt), the repository has a README with run instructions
Too vague Everything works without errors
Specific Screenshots or a screen recording of three scenarios are attached: sign-in, order, payment
Too vague The site is fast
Specific A Lighthouse report with a score of at least 90 for the home page is attached
What to ask to attach: The commit history; linter and test reports; a screen recording of the launch and instructions (better make it a mandatory criterion: “a launch recording and instructions are attached”).
Images and design
Too vague A beautiful logo
Specific Three logo options to choose from, PNG and SVG files, at least 2000×2000 pixels
Too vague In the brand style
Specific Colours and font from the attached brand book are used (colour names are given in the mockup)
Too vague A modern layout
Specific Mockups of the home and order pages in Figma, mobile and desktop versions
What to ask to attach: Sketches, the layered source file, a link to the mockup.
Video
Too vague A dynamic clip
Specific Duration 30–45 seconds, 9:16 format, resolution at least 1080×1920, MP4
Too vague Good sound
Specific There is a voice-over and background music from the attached list, closing credits with the title
What to ask to attach: The editing project file; the list of materials used.
Audio
Too vague A clean recording
Specific WAV, 48 kHz, three takes of each line, duration 60–75 seconds
Too vague Expressive voice-over
Specific All lines of the attached text are recorded, each in a separate file
What to ask to attach: Draft takes.
3D models
Too vague A detailed model
Specific No more than 50 thousand polygons, 2048×2048 textures, GLB and the Blender source
Too vague Realistic
Specific Four renders from different sides are attached, the model has the same set of parts as the attached references
What to ask to attach: Intermediate versions of the scene.
What the arbiter will not decide