Use a completion checklist
GOV.UK's service guidance describes acceptance criteria as checks that a user need has been met, with supporting evidence. A pilot brief can use the same approach to make acceptance explicit.
GOV.UK: acceptance criteriaOutcome as a Service
A defined result your team can check.
An early-access delivery model in development for a specific piece of work. Agree the output, completion checks and reviewer before work begins, then assess the result against that brief.
Discuss a pilot
Early-access services. Scope, integrations and pricing agreed before work starts.
- Best for
- A deliverable with clear acceptance criteria.
- You receive
- The agreed deliverable, check results and unresolved exceptions.
- Measure
- Acceptance rate, corrections and total preparation plus review time.
Define acceptance before delivery
Example pilot: reconcile an agreed batch of records. Set the checks before work starts so your team can make a clear acceptance decision.
- Input
- Two agreed record exports, a matching rule and the eligible batch.
- Deliverable
- A reconciliation report listing matched records and unresolved differences.
- Completion checks
- Every eligible record is accounted for. Each match or exception links to its source.
- Acceptance
- The named process owner checks completeness and records a decision.
- Boundaries
- Source records stay unchanged. Any correction requires separate permission.
- Measure
- Compare preparation, review and correction time with the current process.
Define done before delivery
Specify the input set, required output and checks that determine acceptance. A pilot could produce a source-linked document review, a reconciliation report or a software change with agreed verification.
A named reviewer accepts the work. Missing evidence, unresolved exceptions or failed checks are recorded and handled through the agreed correction process.
Measure the result and the effort
A completed report is a deliverable. Reducing the effort needed to prepare and review it is a separate business result. Record the current process before comparing the pilot.
Include review time, corrections and operating costs in that comparison. Pricing may be fixed for the pilot or tied to accepted units; the proposal defines the unit, exclusions and rework terms.
Practical details and sources
These references inform pilot planning. The delivery tools and responsibilities are agreed for your task.
Compare more than output volume
GOV.UK recommends combining performance measures with user research and other data. Task completion and time taken can be compared over repeated assessments; output count alone does not establish value.
GOV.UK: measuring service successDocumentation checked 15 October 2026.
Set the boundaries before connecting data.
Each pilot needs a clear agreement on access, data handling, approval and exceptions.
- Access
- Agree the data sources, permitted operations and person who can revoke access. Begin with retrieval and drafts where suitable.
- Data handling
- Confirm hosting, model providers, destinations and retention before connecting sensitive information.
- Approval
- Name the reviewer for messages, record changes and other consequential actions. Check the target and approval before execution.
- Exceptions
- Test failures and misleading inputs. Agree the activity record, escalation owner and recovery steps for each enabled action.
Related guidance: OWASP AI agent security and NIST generative AI risk management. Controls and responsibilities are agreed for each engagement.
Common questions
Does outcome mean guaranteed savings or growth?
The service model starts with a deliverable your team can accept. Savings, revenue and other business effects need separate measures and evidence. They are not guaranteed by completing a deliverable.
What happens if the work fails its checks?
Record the failed checks and apply the correction or escalation process in the pilot agreement. Review windows, rework and excluded cases are agreed before delivery.
Who accepts the result?
Your team names the accountable reviewer. Automated checks and evidence support that person's decision; an agent's own assessment does not establish acceptance.
Start with one useful task.
Bring one deliverable, an example of acceptable work and the person responsible for signing it off. We will assess the access, integration and review requirements before proposing a pilot.