Acceptance and evaluation criteria are BABOK technique 10.1: acceptance criteria are the conditions one solution must meet to be accepted (pass or fail), and evaluation criteria are the weighted measures used to compare and rank several options. On the Certified Business Analysis Professional (CBAP) exam, the technique mostly appears inside Requirements Analysis and Design Definition (30% of the exam) and Solution Evaluation (14%).
Last verified: October 2026 (exam facts from iiba.org).
What acceptance and evaluation criteria are
Acceptance and evaluation criteria are two uses of the same idea: define, before you judge a solution, what good looks like and how you will measure it. The BABOK Guide v3 treats them as one technique because both rest on the same elements:
| Element | What it means | Example |
|---|---|---|
| Value attributes | the characteristics stakeholders care about | response time, cost, usability, regulatory fit |
| Assessment | how each attribute will be checked or measured | a test, a demo, a score from 0 to 5 |
The difference is in the decision they support:
| Acceptance criteria | Evaluation criteria | |
|---|---|---|
| Question answered | Is this solution good enough? | Which option is best? |
| Number of options | one | two or more |
| Result | pass or fail | a ranking or score |
| Typical form | testable conditions, Given-When-Then scenarios | weighted scoring matrix |
| Typical moment | approval, acceptance testing, release | design options, vendor selection, value analysis |
A useful test: if you could have only one candidate and still need the criteria, they are acceptance criteria. If the criteria only make sense when you compare candidates, they are evaluation criteria.
Why it matters on the CBAP exam
The technique matters because it supports tasks in several knowledge areas, not just one. In the BABOK Guide v3 it is listed for tasks including Approve Requirements (5.5), Define Future State (6.2), Specify and Model Requirements (7.1), Validate Requirements (7.3), Analyze Potential Value and Recommend Solution (7.6), and the solution evaluation tasks that measure and analyse performance (8.1, 8.2). Our map of all 50 BABOK techniques by knowledge area shows where it sits among the others.
According to the International Institute of Business Analysis (IIBA), the CBAP exam has 120 scenario and case-study questions in 210 minutes. Scenario questions rarely ask for a definition; they ask what the analyst should define or use next. That makes the acceptance-versus-evaluation choice a classic distractor.
How the technique works, step by step
The technique works in five steps, whether you are accepting one solution or ranking several.
- Identify the value attributes. Ask stakeholders what makes a solution valuable to them. Use the business objectives and the requirements as input.
- Decide on the decision type. One candidate and a go/no-go decision means acceptance criteria. Several candidates and a choice means evaluation criteria.
- Make each criterion assessable. Replace vague words with a measure: not "fast" but "search results in under 2 seconds for 95% of requests". If nobody can say how to check it, it is not a criterion yet.
- For evaluation criteria, add weights and a scale. Agree on the relative importance of each attribute and the scoring scale before anyone looks at the options.
- Agree and record. Stakeholders sign off the criteria, and they are traced to the requirements they test.
Our article on quality criteria for requirements covers what makes a single requirement testable; this technique takes the next step and turns that testability into a decision rule.
Example: choosing and accepting a claims platform
An insurer needs a new claims platform. The same project uses both kinds of criteria, at different moments.
Evaluation criteria (Analyze Potential Value and Recommend Solution, 7.6). Three vendors respond. The team agrees the attributes, weights and a 0–5 scale before the demos:
| Attribute | Weight | Vendor A | Vendor B | Vendor C |
|---|---|---|---|---|
| Fit to core claims process | 40% | 4 | 3 | 5 |
| Total cost over five years | 25% | 3 | 5 | 2 |
| Integration with policy system | 20% | 4 | 3 | 3 |
| Usability for adjusters | 15% | 3 | 4 | 4 |
| Weighted score | 100% | 3.6 | 3.65 | 3.7 |
Vendor C ranks first, but only by a small margin. The scores are close enough that the team checks its weights with the sponsor before recommending, which is what a good analyst does when a ranking depends on judgment.
The approach mirrors public procurement guidance: the Australian Digital Health Agency recommends a 0–5 scale, weights that total 100%, and criteria and weights validated with stakeholders before any response is scored.
Acceptance criteria (Approve Requirements, 5.5, and acceptance testing). After selection, each requirement gets acceptance criteria. For example: given a claim under the auto-approval limit with no fraud flags, when the adjuster submits it, then the system approves it and notifies the customer within 5 minutes. This criterion is pass or fail; the platform either does it or it does not.
What practitioners say
Practitioners agree on three points: write criteria early, make them testable, and keep the business view in them.
- Swati Pitre, a CBAP-certified senior BA and trainer, writes on Modern Analyst: "Acceptance criteria define the minimum requirements the solution must meet." She warns that analysts often hand validation to QA, which loses the business perspective, and that teams forget to plan the test data the criteria need.
- A Cyber Sierra article updated in July 2026 quotes a product manager: "Acceptance Criteria should be written on the story before it is started." It adds that criteria should describe outcomes, not implementation.
- Techcanvass describes evaluation criteria as factors with weightings and a scoring system, used mainly when options are being selected, and acceptance criteria as the check before delivery.
- An OpenExamPrep CCBA study guide, updated in August 2026, lists two common traps: confusing acceptance criteria with the Definition of Done, and using acceptance criteria where a vendor ranking needs evaluation criteria.
- An IISCM technique note on the Fhyzics blog names value attributes and assessment as the core of the technique, with testability for acceptance and ranking for evaluation.
Common misconceptions
Most mistakes come from treating the two halves as the same thing.
- Acceptance criteria are only for agile user stories. They apply to any solution component, including a vendor package or a process change. Given-When-Then is one format, not the definition. See our article on Behavior-Driven Development for that format.
- Acceptance criteria are the Definition of Done. The Definition of Done applies to every backlog item; acceptance criteria are specific to one item. Our comparison of Definition of Done and Definition of Ready explains the team-level checklist.
- Evaluation criteria can be set after the demos. Setting weights after seeing the options invites bias toward a favourite.
- A higher score means the option is acceptable. The best-ranked option can still fail a mandatory acceptance criterion. Many teams screen with pass/fail criteria first, then score the options that pass.
- Verification and validation are the same use. Checking that criteria are testable is part of verifying requirements; checking that the solution delivers value is validation. Our article on verify vs validate requirements covers the line between them.
Practice Questions
These are original questions written for this article.
Question 1
A business analyst must help a steering committee choose one of four CRM packages. Stakeholders disagree on what matters most. What should the analyst define first?
A. Acceptance criteria for each package B. Evaluation criteria with agreed weights C. A Definition of Done for the project D. Test cases for the package demos
Answer: B. Comparing several options calls for evaluation criteria, and disagreement about importance is resolved by agreeing weights before scoring. Acceptance criteria give pass or fail for a single solution and do not rank options.
Question 2
A requirement states that the reporting module must be easy to use. During a review, the tester says she cannot write a test for it. Which element of the technique is missing?
A. Value attribute B. Assessment C. Weighting D. Traceability
Answer: B. Usability is the value attribute, but there is no way to assess it. The analyst should add a measurable assessment, such as a task completion time or rate observed in a usability test.
Question 3
Vendor X has the highest weighted score but cannot meet a regulatory data residency requirement that the sponsor marked as mandatory. What should the analyst recommend?
A. Select Vendor X, because it scored highest B. Lower the weight of data residency and rescore C. Exclude Vendor X, because it fails a mandatory acceptance criterion D. Ask the vendors to rescore themselves
Answer: C. A mandatory condition works as an acceptance criterion: failing it rules the option out, whatever the weighted score. Changing weights after scoring to protect a preferred option undermines the evaluation.
Related techniques
Acceptance and evaluation criteria rarely work alone. Decision Analysis (10.16) uses evaluation criteria to compare options, and our article on decision modelling and decision analysis covers the matrices. Business Cases (10.7) and Financial Analysis (10.20) supply cost and benefit attributes; see business cases and value modelling. Metrics and KPIs (10.28) turn acceptance criteria into measures you can track after release, and Reviews (10.37) are where criteria get agreed.
If you are preparing for a Scrum exam as well, acceptance criteria also come up in Product Owner questions; you can practise those on our PSPO I practice exam.
FAQ
What is the difference between acceptance criteria and evaluation criteria?
Acceptance criteria decide whether one solution or requirement is acceptable, so the result is pass or fail. Evaluation criteria compare several options with weighted measures, so the result is a ranking. The BABOK Guide v3 covers both in technique 10.1.
What are the elements of the Acceptance and Evaluation Criteria technique?
The two core elements are value attributes, the characteristics stakeholders value, and assessment, the way each attribute is tested or measured. Evaluation criteria add weights and a scoring scale so options can be ranked.
Are acceptance criteria the same as the Definition of Done?
No. The Definition of Done is a quality checklist that applies to every backlog item. Acceptance criteria are written for one specific item and describe the behaviour it must show to be accepted.
When should evaluation criteria be defined?
Before anyone reviews the options. Setting attributes, weights and the scale first, and getting stakeholders to agree, keeps the comparison fair and makes the recommendation easier to defend.
Which CBAP knowledge areas use this technique?
It appears in several, most visibly in Requirements Analysis and Design Definition, Requirements Life Cycle Management (approval) and Solution Evaluation. Expect scenario questions that ask which kind of criteria fits the situation.
Sources
- IIBA: Certified Business Analysis Professional (CBAP)
- Modern Analyst: Writing Foolproof Acceptance Criteria as a Business Analyst
- Techcanvass: Understanding Acceptance Criteria
- Cyber Sierra: How to Write Acceptance Criteria That Engineers Actually Follow
- OpenExamPrep: Acceptance and Evaluation Criteria Definition
- Fhyzics: BA Techniques, Acceptance and Evaluation Criteria
- Australian Digital Health Agency: Establishing a scaled scoring approach