{"canonical_url":"https://engineer.company/glossary/acceptance-criteria/","content_markdown":"# Acceptance criteria\n\n## What it is\n\nAcceptance criteria are the conditions a specific change must meet before it can be accepted. They\ndescribe what someone can observe under stated circumstances. “Send a booking confirmation” names\na feature. “After an available appointment is booked, the confirmation shows the same appointment\nreference and start time as the booking record” gives a way to verify part of the feature. It\nleaves the team free to choose how the confirmation is generated.\n\nThe UK Government Service Manual describes acceptance criteria for a user story as an outcome\nchecklist for confirming that the service has done its job. The story captures the user and the\nneed. The criteria make the agreement concrete enough to discuss, implement and verify. A\ncriterion can address an error path, an accessibility requirement or an operational constraint if\nit materially affects whether this change is acceptable. Different criteria may need different\nkinds of evidence.\n\nConsider the relationship to three other artifacts. A specification can contain requirements that\napply to many changes. A test case is a particular execution or example that produces evidence for\none or more criteria. The Definition of Done in Scrum describes the quality measures that all work\nin an Increment must meet. Individual criteria address the behavior or limits of this change. For\ninstance, a team might check keyboard reachability for every interactive change and also require\nthat a particular appointment can be confirmed and revisited with the keyboard.\n\n## Why it matters\n\nGood criteria make disagreements visible while a change is still cheap to adjust. A project\nsponsor may say that booking is successful when an appointment exists. A customer may expect the\nconfirmation message to arrive, and support may need a reference when that message gets lost.\nThose are different outcomes. Deciding when to show success, what to do after an email provider\nfails and which reference is authoritative avoids discovering the conflict after release.\n\nThey also give verification a destination. A reviewer can inspect the booking page and a test\noperator can interrupt message delivery. Each knows what observation would count. Accessibility\nmay need a keyboard walkthrough in addition to an automated assertion. Timing might need a\nmeasurement under a named load and a known test environment. A condition that only says the system\nmust be “fast” leaves several incompatible choices unresolved.\n\nStandards and regulations still apply without a line in the story. List a change-specific\ninterpretation when the team would otherwise need to guess. If keyboard support is already a\nshared rule, describe how it applies to the unfamiliar date picker and use the existing standard\nas evidence. That keeps the story brief while protecting the behavior readers and operators need.\n\n## What it looks like in practice\n\nImagine a service that lets people reserve an appointment and receive a confirmation message. A\nfirst draft might say “the appointment can be booked and an email is sent”. Bring a service owner,\nengineer and tester together and walk through three concrete attempts. The following examples are\nillustrative. Their exact wording would come from the team operating that service.\n\n- With an available appointment at 14:00 in the stated time zone, one confirmed booking is created\n  and its reference, date and time appear on the confirmation page. Compare the values with the\n  booking record.\n- When the appointment is already taken by the time the request reaches the service, the user sees\n  that the slot is unavailable and can return to available times. The competing request creates no\n  additional booking for the occupied slot.\n- Once the service has confirmed the booking, a simulated message delivery failure leaves that\n  booking intact. The confirmation page still supplies the reference, and the failure is visible\n  to the operator responsible for follow-up.\n\nThe examples state a starting situation, an action and a verifiable result. Gherkin expresses that\nstructure with Given, When and Then. That format can improve readability and connect scenarios to\nautomation. A short checklist works just as well for a simple change. In either form, specify\nwhich reference to compare and decide whose view supplies the evidence. A green status in a send\nqueue cannot demonstrate that an email was received.\n\nRun the first attempt through the actual screen. Test the competing update with the request\nordering controlled. Simulate the message failure after the booking transaction has finished.\nDocument the three observations in the work item so someone can reproduce the evidence. For a\nrelated example of specificity, see [our accessibility statement](/accessibility/), which\ndescribes keyboard checks and what was observed or still requires review. That is the level of\nevidence to ask for when a criterion depends on what a reader can actually do.\n\n## Where it goes wrong\n\nVague language moves the decision to the end. “The error is handled gracefully” is one example.\nName the state, the information shown, the action still available and any effect that must be\nprevented. In the booking example those details tell a tester to verify both the visible recovery\npath and the booking record. A screenshot of the error message by itself leaves the second part\nunanswered.\n\nCriteria can also prescribe implementation before it is justified. “Use the new queue” may be a\nlegitimate architecture constraint, but it will not tell a user what happens when a confirmation\nis delayed. Keep the architecture decision where it can be explained and frame the criterion\naround observable behavior and evidence. If a specific protocol or storage location is compulsory\nfor an external integration, cite that requirement and explain the boundary.\n\nThe opposite problem is a list so large it describes an entire release. Split the work by outcome\nand keep the important failure path with its corresponding behavior. Agree which constraints are\nshared and who verifies this particular change. When a prototype or test reveals a missed\nrequirement, update the criterion with its reason and rerun the affected verification. Recording\nthat change preserves the agreement that was used, so the next person can see both what passed and\nwhat remains open.\n\n## Further reading\n\n- [UK Government Service Manual on user stories and acceptance\n  criteria](https://www.gov.uk/service-manual/agile-delivery/writing-user-stories)\n- [Cucumber's Gherkin reference for scenarios and\n  examples](https://cucumber.io/docs/gherkin/reference/)\n- [The Scrum Guide's Definition of\n  Done](https://scrumguides.org/scrum-guide.html#definition-of-done)\n- [W3C guidance on testing keyboard\n  functionality](https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html)\n\n\u003chttps://engineer.company/glossary/acceptance-criteria/\u003e\n","date_modified":"2026-11-19T06:00:51Z","description":"Learn to write observable acceptance criteria for a specific change, with booking examples, test evidence and a clear distinction from the Definition of Done.","formats":{"gemtext":"https://engineer.company/glossary/acceptance-criteria/index.gmi","gopher":"https://engineer.company/glossary/acceptance-criteria/gophermap","html":"https://engineer.company/glossary/acceptance-criteria/","json":"https://engineer.company/glossary/acceptance-criteria/index.json","markdown":"https://engineer.company/glossary/acceptance-criteria/index.md","pdf":"https://engineer.company/glossary/acceptance-criteria/index.pdf"},"kind":"page","language":"en","title":"What are acceptance criteria?","url":"https://engineer.company/glossary/acceptance-criteria/","version":1}