Free template
Acceptance criteria template
Criteria a tester can answer yes or no to, in two formats: Given / When / Then scenarios for flows, and a rule checklist for limits and permissions. Use the sections to cover the happy path, edge cases, states, permissions, limits and non-functional needs.
Markdown pastes into Jira, Linear, Notion and GitHub issues. No sign-up.
The template
Seven parts, each with what to write.
Pick the format per criterion. Given / When / Then fits anything with a before and an after, such as a flow or a state change. A rule checklist fits a fact that is always true, such as a limit or a permission. Mix them in one story.
- 01
Which format to use
Choose scenarios for behaviour over time and rules for facts that always hold.
- Does the criterion have a starting state and a result? Use Given / When / Then.
- Is it a limit, a permission or a format? Use a rule.
- Would a tester need steps to check it? Then use a scenario.
TipDo not force a rule into a scenario. “Given an admin, when they send a 21st invite…” is clearer as “At most 20 invites per admin per hour.”
- 02
Happy path
The main flow working as intended, one scenario per path.
- Given: which state does the user start in?
- When: which single action do they take?
- Then: what do they see, and what is saved?
TipOne When per scenario. If you write “when … and then …”, you have two scenarios.
- 03
Edge cases and errors
The inputs and situations that are not the happy path, each with the exact result.
- Expired, used, revoked or duplicate input
- The wrong account or the wrong workspace
- Which message or error code does the user or API client see?
TipName the error: “shows ‘This invite has expired’ and offers to ask for a new one” can be tested; “shows an error” cannot.
- 04
States: empty, loading, error
What each screen shows before, during and after the data arrives, and when it fails.
- What does the empty state say, and what can the user do from it?
- What shows while loading?
- What happens when the request fails, and can the user retry?
TipThese are the states that get left out of the design and found in review. Write them as criteria before building.
- 05
Permissions
Who may do the action and what everyone else sees.
- Which roles may do it?
- What do the others see: a hidden control, a disabled one or an error?
- Does the API enforce the same rule as the interface?
TipCheck both layers. A hidden button is not a permission rule.
- 06
Limits
The numbers: rate limits, expiry, sizes and counts, each with what happens at the limit.
- What is the limit, and per what: user, workspace, hour?
- What happens at the limit, and when does it reset?
- Where does the number live: in config or in code?
TipState the first request over the limit, not just the limit: “the 21st request returns 429”.
- 07
Non-functional
Performance, accessibility, security, logging and compatibility that the story must meet.
- The smallest screen and the assistive tools it must work with
- The time a step may take, and how it is measured
- What is logged, and what must never be stored or shown
TipMeasure it or leave it out. “Fast” fails review; “completes in under three minutes in CI” passes.
Example
Acceptance criteria for team invitations, filled in.
Two real-sized examples from the Team invitations plan: the accept-invite page in four states, and the invite rate limit.
1 · Which format
The accept page is a flow with a starting state per case, so it uses scenarios. The send limit, roles and expiry are facts that always hold, so they use a rule checklist.
2 · Happy path
- Signed in as the inviteeGiven a pending invite for maria@example.com and the invitee signed in as that addressWhen they open the link from the emailThen the invite is accepted once, and they land in the invited workspace with the invited role
- Signed outGiven a pending invite and no one signed inWhen the invitee opens the linkThen the page offers sign-in or sign-up for the invited address, and the link survives login
3 · Edge cases and errors
- Wrong accountGiven a pending invite for maria@example.com and the visitor signed in as another addressWhen they open the linkThen the page says the invite was sent to another address and offers “Switch account”; the link stays alive through login
- Expired or used linkGiven an invite older than 7 days, already used, or revokedWhen the invitee opens the linkThen the page says which of the three it is and tells them to ask an admin for a new invite; the API returns invite_expired or invite_used
4 · States: pending invites list
| State | What the admin sees | Action |
|---|---|---|
| Empty | “No pending invites. People you invite show up here until they accept.” | Invite button |
| Loading | Skeleton rows, same height as the real rows | None |
| Error | The request failed, with a Retry button | Retry |
All three states are reachable by keyboard.
5 to 7 · Permissions, limits and non-functional rules
| Kind | Rule | Checked by |
|---|---|---|
| Permission | Owners may invite any role; admins may invite admins and members; members cannot invite. | API and modal |
| Limit | An admin can send at most 20 invites an hour. The 21st request returns 429 with the time they can try again. | API |
| Limit | The limit is per admin and per workspace, and lives in config, not in code. | Config review |
| Expiry | A token works once and expires after 7 days. It is rejected after revoke. | API tests |
| Non-functional | The page works at 375 px width and with a screen reader. | Manual check |
| Non-functional | Every rate-limit hit is logged with workspace and admin ID. | Log check |
Result
Every row can be answered yes or no by a tester, with an exact number, message or error code.
How to use it
How to fill it in, step by step.
Write the criteria with the people who will build and test the story, before work starts. Disagreements found here cost minutes; found in review they cost days.
- 01Start with the happy path. One scenario for the main flow, in the order the user sees it.
- 02Walk each state of the screen. Signed out, signed in, wrong account, expired link. Each is a scenario or an open question.
- 03Turn rules into a checklist. Permissions, limits and expiry are facts, not flows. List them with the exact number and what happens at the limit.
- 04Add the non-functional checks that you can measure: width, screen reader, time in CI, what is logged.
- 05Read each criterion as a tester. Could you answer yes or no without asking anyone? If not, add the missing number, message or state.
- 06Cut it down. More than seven criteria on one story is a sign the story should be split.
Skip the blank page
Let SprintProof draft it with you.
Describe the feature and the planner asks the questions a reviewer would, then drafts the brief, done-when, not-now and parts with ranges. The check library adds the edge cases teams usually find mid-sprint.
FAQ
Acceptance criteria questions
What are acceptance criteria?
What is the Given / When / Then format?
When should I use a checklist instead of Given / When / Then?
What is the difference between acceptance criteria and a definition of done?
How many acceptance criteria are enough?
Related templates
Templates that go with it.
- Markdown
User story template
Who, what and why, with the acceptance criteria and the questions to settle first.
- Markdown
Feature spec and feature description template
A feature broken into parts by layer, each with behaviour, states and a range, and a one-page feature description.
- Markdown
PRD template
The problem, who it is for, what done means, what is out, and the open questions, on one page.
- Markdown, CSV
Software estimate template
Best, likely and worst case per part, rolled up into a range you can defend.
- CSV
Sprint planning template
Sprint goal, capacity, a backlog with ranges, risks and a definition of done.
Turn this into a reviewed plan with SprintProof.
Describe the feature and SprintProof turns it into a plan: checked against a library of questions reviewers ask, estimated as a range with 50, 80 and 90% dates, and signed off before anyone starts.