This 3-sentence summary provides the high-level information about the acceptance criteria document: The document outlines a template for defining measurable acceptance criteria for a project's final product that must be met for the customer and affected staff to accept the product, including topics like functions, appearance, performance levels, costs, and timelines. Each criteria includes the current level, required acceptance level, and any further target levels and dates. The purpose is to have agreement between the customer and supplier on what constitutes an acceptable final product.

1. ACCEPTANCE CRITERIA
Project name insert project name
Release Draft/Final
Date:
PRINCE2
Author:
Owner:
Client:
Document Number:

2. acceptancecriteria-150722065954-lva1-app6892.doc insert project name
Date:
Document History
Document
Loca
tion
This document is only valid on the day it was printed.
The source of the document will be found in the Quality File (filepath).
Revision
Histo
ry
Date of next revision:
Revision
date
Previous
revision date
Summary of Changes Changes
marked
Approvals This document requires the following approvals.
Signed approval forms are filed in the project files.
Name Signature Title Date of
Issue
Version
Distribution This document has been distributed to:
Name Title Date of
Issue
Version
Page 2

3. acceptancecriteria-150722065954-lva1-app6892.doc insert project name
Date:
Purpose
A definition in measurable terms of what must be done for the final product to
be acceptable to the customer and staff who will be affected.
Contents Acceptance Criteria could cover, for example, the following topics. There
may be other unique criteria for a specific product
Topic See Page
Reference to meeting quality expectations
Target dates
Major functions
Appearance
Personnel level required to use/operate the product
Performance levels
Capacity
Accuracy
Availability
Reliability
Development cost
Running costs
Security
Ease of use
Timings
For each topic there may be one or more criteria. Each criterion should
consider the following entries. ‘Current level’ shows what the situation is
before the project. ‘Acceptance level’ is what is acceptable at hand-over time.
If the customer and supplier agree that it is reasonable that the product might
undergo some tuning once in use in order to achieve the final desired level of
acceptability, the other entries may be used.
Topic:
Acceptance criterion
Measurement to be applied
Current level
Acceptance level
Further level Target date
Final level Target date
Page 3

4. acceptancecriteria-150722065954-lva1-app6892.doc insert project name
Date:
Availability
Reliability
Development
cost
Running costs
Security
Ease of use
Timings
Page 4