# Autonomy integration and demonstration brief

Project / prepared by / checked date:
User and task:
Platform, payload and software deliverable:
Operating environment and exclusions:
Functions performed by the system:
Human approvals, supervision and agreed fallback:
Sensors, compute, control and customer interfaces:
Integration owner at each boundary:
Data access, licensing and update responsibilities:
Training, maintenance and support period:
Quote period, recurring costs and excluded engineering:

## Demonstration plan

Site and responsible customer/site contact:
Permitted conditions and permissions to resolve:
Vehicle / payload / sensors / compute / software version:
Acceptance criteria and who agrees them:
Supervision, stopping and recovery procedure owner:
Required evidence and access to logs:

| Attempt | Conditions / configuration | Task result against criteria | Human interventions / recovery | Evidence link | Unresolved finding / owner |
| --- | --- | --- | --- | --- | --- |
| | | | | | |

## Evidence and decisions

| Question | Supplier response | Evidence and checked date | Demonstrated / supplier-stated / untested | Owner / next action |
| --- | --- | --- | --- | --- |
| | | | | |

Configuration changes requiring review or retesting:
Largest remaining assumption:
Next decision and evidence needed:

This is an editable project brief, not a certification standard. Agree acceptance criteria with the people responsible for the intended trial.

Related guide: https://www.defensetechbase.com/sectors/autonomous-systems/#autonomy-guide