Define client acceptance tests for an AI deployment

When to use this guide

A client accepts an agency's chatbot based on a video demo, but its own production embed has different notice settings.

This is a fictional implementation scenario. The procedure below is Article 50 Hub's suggested working method, not a prescribed legal form, a customer result or a claim that every step is an additional statutory requirement.

Review procedure

1. List the delivered surfaces, configuration and version under test.

2. Define notice, attribution, failure-path and evidence checks relevant to the agreed scope.

3. Assign who runs the tests and how defects are recorded.

4. Verify the actual client deployment and document any accepted scope limitation.

What the example review finds

• The demo configuration differs from production.

• The acceptance record has no test of the embedded route.

Keep these example observations separate from your own results. An unknown or untested state should stay open until the relevant evidence has been inspected.

Fields for your working record

• Delivered version

• Acceptance case

• Expected result

• Client evidence

• Open defect

Use the downloadable blank worksheet linked on this page to connect the observed behavior with the deployed system. Add a reviewer, date, evidence reference, unresolved questions and a next action. The worksheet is editable locally and does not upload your records to Article 50 Hub.

Completion and handoff

Close the task only for the scope actually reviewed. Preserve the result that another authorized reviewer can reproduce, identify the owner of remaining work, and record a retest when the implementation changes. A completed worksheet is not a substitute for the underlying evidence.

Decision boundary

Client acceptance is a delivery decision and does not establish regulatory compliance or waive statutory duties.

The official references below provide legal or technical context. Resolve applicability and exception questions with the responsible qualified reviewer; use the product's tools to organize implementation work within that assessment.