← Back to blog

Acceptance Criteria: How to Write Them, With Examples

November 18, 2026
Acceptance Criteria: How to Write Them, With Examples

Acceptance criteria are the specific, testable conditions a deliverable must meet before your client accepts it. You write them before the work starts, in words both you and the client can check, so "done" is a yes or no answer and not an opinion. For a freelance project manager, they are the cheapest protection against rework, unpaid revisions and the dreaded "this isn't what I meant." Below you will find how to write them, the formats that work, examples for software and non-software deliverables, and how they differ from the definition of done.

The Freelance PM Club
Build Stronger Project Management Skills
The Freelance PM Club offers expert-led courses, personalized career coaching, and a supportive community for independent project managers and consultants.
Visit

TL;DR

  • Acceptance criteria are pass/fail conditions for one story or deliverable. The definition of done is a shared quality standard for all work.
  • Write them as outcomes the client can observe, never as instructions for how to build.
  • Use a short rule list for simple items and Given/When/Then for behavior that changes with context.
  • Agree on them in writing before work begins, and keep each criterion small enough to test on its own.
  • Freelancers who define both layers early spend less time on scope arguments and final-week surprises.

Table of Contents

What acceptance criteria are

Think of acceptance criteria as the checklist the client would use at the moment of handover. Each line is something that is either true or not true when they look at the work.

Official guidance says the same thing in more formal words. The Ohio Office of Budget and Management describes acceptance criteria as conditions set in advance that a deliverable must meet for user acceptance. Its phrase for the goal is moving from "works as coded" to "works as intended." The same guidance stresses that the recipient of a deliverable, not only its creator, decides whether it fits its purpose. That point matters most to freelancers, because the person paying you is the person whose definition counts.

NASA's Software Engineering Handbook defines the term as the conditions a system or component must satisfy to be accepted, including performance requirements and essential conditions for project deliverables. It also notes that criteria support acceptance testing: expected results are compared with observed results, and a test passes when they match or fall within an agreed tolerance. That tolerance idea is useful outside engineering. "Report delivered within two business days of month end" is a criterion with a built-in tolerance.

What acceptance criteria are

What they are not

Acceptance criteria are not a full specification, a to-do list for your team or a design brief. They say what must be true, not how you get there. That leaves you free to choose the method, and it leaves the client free from technical detail they never wanted to read.

How acceptance criteria relate to a user story

If you work with software teams, you will meet the user story. It is a one-sentence description of a need, usually in the form "As a [type of user], I want [something] so that [benefit]." It explains why the work matters.

Acceptance criteria explain what has to be true for that need to be met. The Scrum Alliance explains the split this way: the story carries the user's goal, the criteria state the observable conditions, and the team keeps the choice of how to implement. A 2022 systematic literature review published through SciTePress concludes that user stories are informal, user-centered feature descriptions, while acceptance criteria are higher-level conditions that make verification possible. The same paper presents criteria as a bridge from the informal story to verifiable scenarios, and notes they can cover behavior, business rules and quality aspects.

In practice:

  • Story: As a returning customer, I want to reset my password so that I can get back into my account.
  • Criteria: The reset link arrives by email. The link stops working after use. The new password must meet the stated length rule. An unknown email address gets a neutral message.

The story alone would let two people build very different things. The criteria narrow it to one testable result. If you plan work as stories, our guide to user story mapping shows how to arrange them into sprints before you write criteria for each.

Formats for acceptance criteria

There is no single required format. Two are common, and you can mix them in one backlog.

Rule-based lists

A rule-based list is a set of short statements, each independently checkable. It suits simple deliverables, content work and anything without many branches.

The Ohio guidance recommends statements that are clear, simple and unambiguous, with enough detail to be useful and an objective pass or fail result. It also says to use functional, non-functional or performance measures as appropriate. In plain terms: each line should have one verb you can verify and no word like "fast" or "user-friendly" left undefined.

Given/When/Then scenarios

Given/When/Then (sometimes called Gherkin style) describes behavior as a scenario. "Given" sets the starting state, "When" names the action, and "Then" states the expected result. The SciTePress paper describes these as preconditions, expected behavior and expected results, and recommends keeping each scenario simple and splitting large criteria into smaller ones.

Example:

  • Given a client has an approved invoice in the portal, when they click "Download PDF," then a PDF with the invoice number, date and total opens in a new tab.

Which one to pick

SituationBetter formatWhy
Document, report or content deliverableRule listEach condition is a single check
Feature with different outcomes by user stateGiven/When/ThenContext changes the result
Performance or quality limitsRule list with numbersA figure and a tolerance are easy to verify
Workflow with several stepsGiven/When/Then, one scenario per pathKeeps each path testable alone

How to write acceptance criteria that hold up

The following steps work whether you are managing a software build or a consulting engagement.

  1. Start from the outcome the client wants. Ask what the client will do with the deliverable. A dashboard exists so a director can see weekly pipeline numbers on Monday morning. That is the real test.
  2. Write with the client in the room. The client is the person who decides fit for purpose, so their words belong in the criteria. A 30-minute call is usually enough for a single deliverable. If you need a structure for that conversation, the 60 minute kickoff agenda leaves a slot for it.
  3. Describe the outcome, not the method. "Users can filter by date" is a criterion. "Use a dropdown built with library X" is a design choice that belongs elsewhere.
  4. Make each line pass or fail. Replace adjectives with observations or numbers. "The page loads quickly" becomes "The page loads in under three seconds on the agreed test device."
  5. Keep one idea per criterion. If a line contains "and," it is probably two criteria. Splitting them also makes it clear which half failed.
  6. Cover the unhappy path. What happens when there are no results, the file is too large or the user is signed out? Missing edge cases are where most disputes start.
  7. Add non-functional conditions that matter. Security, accessibility, performance, file formats and response times are all legitimate criteria when the client cares about them.
  8. Get written agreement. An email reply that says "approved" is enough for many engagements. Save it with the project documents.
  9. Revisit only through a change request. Once agreed, new criteria are new scope. Our scope creep control process covers how to price and approve those changes without souring the relationship.

Common mistakes

  • Writing criteria after the work is built, so they describe what exists instead of what was wanted.
  • Using vague words such as "easy," "modern" or "intuitive."
  • Stuffing implementation details into the criteria and limiting the team's options.
  • Writing thirty criteria for a story that should be split into three.
  • Forgetting that someone on the client side must be named as the person who accepts.

Stronger criteria also help with client expectations in general. The client expectation management playbook pairs well with this step, since criteria are expectations made concrete.

Acceptance criteria examples

Example 1: product search (software)

Story: As a shopper, I want to search the catalog so I can find a product quickly.

  • Searching for an exact product name returns that product first.
  • Searching for part of a name returns every product containing that text.
  • Results are shown 20 per page, with controls to move between pages.
  • When nothing matches, the page shows a "No results found" message and a link back to the full catalog.
  • A search returns results in under two seconds for the agreed catalog size.

The last line shows how a performance condition can sit alongside functional ones.

Example 2: monthly report (consulting deliverable)

Deliverable: a monthly project status report for a client's leadership team.

  • The report is delivered by email by 5 p.m. on the third business day after month end.
  • It fits on two pages and uses the client's slide template.
  • It lists every milestone due in the period, each marked on track, at risk or late.
  • Each at-risk or late item has an owner and a recovery date.
  • The client's project sponsor confirms in writing that the format meets their needs, once, in the first month.

That final line is a trick worth borrowing. Where taste is involved, convert it into a single named approval at a specific time.

Example 3: website landing page (given/when/then)

  • Given a visitor on a phone, when the page loads, then the sign-up form is visible without horizontal scrolling.
  • Given a visitor submits a valid email, when they press "Join," then they see a confirmation message and receive a welcome email.
  • Given a visitor submits an invalid email, when they press "Join," then the field shows an error and the form keeps what they typed.

Example 4: process document

Deliverable: a standard operating procedure for onboarding a new vendor.

  • Each step names a role responsible, not a person.
  • The procedure lists the forms required and where each is stored.
  • Two staff members who did not write it complete a dry run using only the document.
  • Any step that took more than five minutes to understand is rewritten and rechecked.

Definition of done: the second layer

Acceptance criteria answer "does this item do what the client wanted?" The definition of done answers "has the work been finished to our quality standard?" Both must be true before an item counts as complete.

The Scrum Guide (2017 edition) defines the Definition of Done as a shared understanding of what it means for work to be complete, applied when a Product Backlog item or Increment is described as Done. The guide says that when an organization already has a convention or standard for Done, the Scrum Team must follow it at minimum. Otherwise, the team writes one that fits the product. It also expects teams to expand their definition of done as they mature, adding more stringent quality criteria.

If you manage projects inside Scrum and Agile frameworks, you will be asked about the definition of done early, often at your first sprint planning session.

Definition of done checklist

A typical definition of done applies to every item in the work, whatever the feature:

  • Code or content has been reviewed by a second person.
  • Tests that were agreed for the item have been run and passed.
  • Documentation or user notes are updated.
  • The work is merged into the main version or saved in the shared project folder.
  • No known defects are left open against the item.
  • The product owner or client contact has seen it working.

For non-software engagements, translate the same idea. A consulting deliverable might be done when it has been proofread, checked against the data source, formatted to the client template, stored in the shared folder and logged in the project tracker.

Acceptance criteria vs definition of done

Acceptance criteriaDefinition of done
ScopeOne story, deliverable or featureEvery item the team completes
Question answeredDoes it do what this client needs?Has it met our quality standard?
Who writes itClient or product owner, with the teamThe whole team, often with the organization's standards
Changes how oftenFor each itemRarely, as the team matures
Example"Shows 20 results per page""Peer reviewed and tests passed"

A short test: if a line would be the same for every story, it belongs in the definition of done. If it is specific to one story, it is an acceptance criterion.

A search feature can satisfy every acceptance criterion and still not be done, because nobody reviewed the code. A reviewed, tested feature can be done by the team's standard and still be rejected, because it does not match what the client asked for. You need both.

Using both as a freelancer

Independent project managers do not have a company's process to fall back on, so these two layers become your process. A few habits make them pay off:

  • Put your definition of done in your proposal or statement of work. It tells the client how you work and sets a standard they can rely on.
  • Attach acceptance criteria to each deliverable or milestone. Payment triggers become clear: a milestone is invoiced when its criteria are met.
  • Name the accepter and a review window. For example, the client has five business days to confirm or list unmet criteria. Silence after that window counts as acceptance, if your agreement says so.
  • Reuse your templates. After two or three engagements you will have a standard definition of done and a bank of criteria you adapt, not write from scratch.
  • Close with a clean handover. When criteria are met, the project handover templates help you package files, access and documentation so nothing is lost.

If you are also onboarding new clients, the client onboarding checklist is a natural place to introduce how acceptance works on day one.

Perspective

Most of the freelance PMs we talk with do not lose money because their work was poor. They lose it because "good" was never defined. A client expects one thing, the deliverable shows up as another, and the next week is spent on revisions that nobody budgeted.

Writing acceptance criteria is the habit that fixes this, and it is one of the first skills we encourage in people moving from a corporate role into independent work. Inside a company, a process quietly defined done for you. On your own, you have to bring that structure yourself.

That is why our platform combines courses, templates, a community of other independent project managers and career coaching in one place. The aim is a structured pathway: learn the practice, borrow a tested template, and talk it through with peers who have faced the same client conversation.

Start small. Pick your next deliverable, write five pass/fail lines, and send them to the client before you begin. You will feel the difference by the first review.

Ashanti

Build the skill with The Freelance PM Club

Writing criteria well is a skill that improves with practice and feedback. The Freelance PM Club gives independent project managers and consultants a membership with curated job listings, expert-led courses, a library of templates and tools, a networking community, virtual events and career coaching. Plans are published on the subscriptions page: Job Board Access is $5 per month, Freelancer Pro is $10 per month and Freelancer Elite is $20 per month. If you want one-to-one guidance on moving into freelance project management, coaching is available.

The Freelance PM Club

FAQ

What is the difference between acceptance criteria and requirements?

Requirements describe what a product or project must provide overall. Acceptance criteria are the specific, testable conditions attached to one item that show a requirement has been met. A requirement can have several criteria, and each one gives a clear pass or fail.

Who writes acceptance criteria?

The product owner or client usually leads, because they decide whether the result fits their purpose. The delivery team or project manager helps make the wording specific and testable. As a freelancer, you often draft them and ask the client to confirm.

How many acceptance criteria should a story have?

There is no fixed number, but a handful is typical. If a story needs many criteria, it is probably too big and should be split. Research on writing criteria also recommends splitting large ones into smaller scenarios.

Can I use acceptance criteria outside software?

Yes. Any deliverable can have conditions the client can check: a report, a training session, a process document or a campaign plan. Government guidance on deliverable acceptance is written for general project work, not only for code. Write each condition so that someone other than you could check it.

Should the definition of done include acceptance criteria?

No. Keep them separate. The definition of done is a standard that applies to every item, while acceptance criteria are specific to one item. An item is finished only when it satisfies both.

Sources