Acceptance Criteria Generator
A step-by-step framework for generating acceptance criteria from any user story. Covers happy path, edge cases, error handling, and performance criteria in the Given-When-Then format. Use the framework manually or let Vantage generate criteria automatically from your connected product data.
Why acceptance criteria matter
Acceptance criteria are the bridge between what the product manager wants and what the developer builds. Without clear criteria, developers make assumptions, QA engineers test the wrong things, and the PM discovers gaps during review — after the code is already written.
The most common mistake is writing criteria that are too vague ("the feature should work well") or too detailed ("the button should be 44px with a 6px border-radius"). Good criteria describe observable behavior that anyone can verify: "When I click the filter, the list updates within 2 seconds." This framework helps you systematically generate criteria that hit the right level of specificity.
The acceptance criteria generation framework
Five steps that produce thorough, testable acceptance criteria for any user story.
Start with the User Story
Write or paste the user story you want to generate acceptance criteria for. The story should follow the standard format: "As a [persona], I want to [action], so that [outcome]." The persona and action determine who the acceptance criteria serve, and the outcome determines what the criteria should verify.
Example input: "As a hiring manager, I want to filter candidates by years of experience, so that I can quickly find applicants who meet the minimum qualifications for the role."
Tips
- Ensure the story has a specific persona — "hiring manager" not "user"
- The action should be a single verb phrase — if it uses "and," split the story first
- The outcome should describe measurable value, not just the action restated
- A well-written story makes criteria generation straightforward; a vague story does not
Generate Happy Path Criteria
The happy path is the scenario where everything works as expected. Start by generating criteria for the primary use case described in the story. Each criterion follows the Given-When-Then format: a precondition, an action, and an expected result. Write 2-3 happy path criteria that cover the core behavior.
Example happy path criteria: (1) Given I am on the candidate list page with 50+ applicants, when I select "5+ years" from the experience filter, then the list updates to show only candidates with 5 or more years of experience and the result count updates. (2) Given I have applied an experience filter, when I change it to "10+ years," then the list updates to show only candidates with 10 or more years.
Tips
- Cover the most common scenario first — this is what the developer builds first
- Include the expected system response, not just the user action
- Be specific about quantities, timing, and visual changes
- Each criterion should be independently verifiable
Generate Edge Case Criteria
Edge cases are scenarios that fall outside the typical usage but must still work correctly. Common edge cases include empty states (no results), boundary values (minimum and maximum inputs), and concurrent actions. Generate 2-3 criteria for the most important edge cases.
Example edge case criteria: (1) Given I apply a filter that matches zero candidates, when the list finishes loading, then I see an empty state message with a suggestion to broaden my criteria. (2) Given I am on the list with filters applied, when I click "Clear all filters," then all filters are removed and the full candidate list is displayed. (3) Given I apply a filter while another filter request is in progress, when both complete, then the list shows results for the most recent filter selection only.
Tips
- Always include an empty state criterion — what happens when there are no results?
- Test boundary values: what is the minimum and maximum input?
- Consider concurrent actions: what if the user clicks twice quickly?
- Consider data variations: what if the field is blank or contains unexpected values?
Generate Error Handling Criteria
Error criteria define what happens when something goes wrong: network failures, invalid inputs, permission errors, and timeouts. These criteria are often overlooked but are critical for user experience. Generate 1-2 criteria for the most likely error scenarios.
Example error criteria: (1) Given the API call to fetch filtered results fails due to a network error, when the request times out after 10 seconds, then I see an error message with a "Retry" button that re-sends the request. (2) Given I am a user without permission to view candidate details, when I apply a filter, then I see filtered results but candidate contact information is hidden with a "Request Access" link.
Tips
- Include at least one network failure criterion for any feature that makes API calls
- Specify the timeout duration and the error message content
- Define the behavior for permission errors, not just authentication errors
- Error states should always provide a path forward (retry, contact admin, go back)
Generate Performance Criteria
Performance criteria set expectations for speed, responsiveness, and scalability. These are non-functional but directly affect user experience. Include at least one performance criterion for any feature that involves data loading, searching, or processing.
Example performance criteria: (1) Given a workspace with 10,000 candidates, when I apply an experience filter, then results load within 2 seconds. (2) Given I am on a mobile device with a 3G connection, when I apply a filter, then I see a loading indicator within 200 milliseconds and results within 5 seconds.
Tips
- Specify the data volume for performance testing (e.g., 10,000 records)
- Include both desktop and mobile performance targets
- Define what the user sees during loading (spinner, skeleton, progress bar)
- Set p95 or p99 latency targets, not just average response times
Related templates
Acceptance Criteria Template
The Given-When-Then format with a complete template structure.
View template →Acceptance Criteria Examples
Real examples across SaaS, e-commerce, and mobile products.
View template →User Story Template
Write well-formed user stories with the standard format and INVEST checklist.
View template →Frequently asked questions
Generate acceptance criteria with AI
Connect your product data and Vantage generates criteria grounded in analytics, designs, and conversations. Free to start.
Free to start. No credit card required.