Preparing a review
Document an AI agent’s mission for review
Before changing an agent used by a client, the team needs to explain its purpose, the version under review, the proposed actions and the decisions already made. A mission record brings these elements together for a technical, business or legal review.
Its value comes down to one question: can someone who did not build the workflow understand what they are reviewing and identify what still needs checking?
In brief
The question and the useful result.
- Question
- What information and supporting material should a team gather to review a version or a change to an AI agent’s mission scope?
- Useful result
- A review record checklist, applied to the move from drafting a reply to sending it, showing missing material and decisions that need clarification.
Preparing a review
Start with the decision the review must support
Define the subject of the review: a new version, a wider mission scope or the conditions for an additional action. State the version and period covered. A record prepared for drafting replies is not enough to assess sending them.
Name the person gathering the material and those reviewing the business, technical or legal questions. These working responsibilities do not, by themselves, establish each organisation’s legal role.
Preparing a review
A checklist for the review record
| Part of the record | What reviewers need to find |
|---|---|
| Purpose | The work assigned to the agent, the intended users and the expected outcome. |
| Scope | The sources, data, tools and actions included, as well as excluded operations. |
| Configuration | Versions of the workflow, instructions and rules, together with the model references actually known. |
| Responsibilities | Who operates the mission, changes its authorisations, makes outstanding decisions and maintains the record. |
| Authorisations and approvals | The permitted actions, their conditions and human decisions tied to a specific version of the content or action. |
| Available material | The checks carried out, their scope, the observations and references to the retained material. |
| State and limitations | Confirmed outcomes, open questions, contradictions and missing material, with an owner for each check. |
Record the source, date and scope of each item. Distinguish material drafted with a model’s assistance from material reviewed or approved by a person. A note written afterwards does not replace a record of the event it describes.
This checklist supports an operational review. It is not a complete list of regulatory requirements.
Preparing a review
Example: moving from drafting a reply to sending it
In this illustrative scenario, the first version drafts replies to customer enquiries. A proposed change would send the message after human approval. No available DUBSAR messaging integration is assumed.
The record contains checks of the drafting process and an example of approved wording. The review must make clear that these items concern the first version. They do not yet establish the authorisation conditions or behaviour of the new sending action.
The checklist exposes three questions: the permitted scope of sending, the approval required for the message and its recipient, and the evidence needed to establish the outcome. The record separates the request, authorisation, attempt, any acknowledgement and the confirmed effect. Approved wording is not evidence of a completed send.
At the end of the review, record the conclusion, its scope and the remaining checks. Keep it linked to the material actually examined.
Preparing a review
How this record relates to the EU AI Act
The EU AI Act provides for technical documentation of high-risk AI systems, notably in Article 11 and Annex IV. The mission record described here does not replace it. The relevant obligations and application dates need to be assessed for the system and the role performed, using the current text on EUR-Lex and European Commission information.
Documenting a mission helps that assessment. It does not automatically classify the system or establish compliance. Legal sources consulted on 17 October 2026.
Preparing a review
Frequently asked questions
Does every item need copying into a new document?
Reuse existing documents and logs. The record needs to identify the right version and provide access to relevant material. An inaccessible reference must remain visible as a limitation.
What if a version or a piece of information is missing?
Record the unknown, who will check it and which decision it prevents the team from making. Do not substitute an assumption for a missing reference.
Does approval of the record authorise the agent’s future actions?
Reviewing a record and authorising an action have different scopes. State what was approved; actions remain subject to their own authorisation conditions.
Preparing a review
DUBSAR’s intended contribution
DUBSAR is developing a foundation to connect durable mission state, authorisations, human decisions and evidence alongside existing tools. The aim is to help teams retrieve a mission’s records and understand what still needs checking.
Selected workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.
Preparing a review