Autonomous reliability evaluation checklist
A reusable evaluation record for scope, evidence, safety boundaries and the adoption decision.
Define the evaluation
Use this as a working template. Record an owner, evidence link, status (confirmed, pending, not applicable), and review date for every item. A checked box is not a certification or a substitute for reviewing the supporting evidence. Resolve critical unknowns before relying on the workflow.
- Project/application: ____; owner/reviewer: ____; environment/version: ____; evaluation dates: ____.
- Decision to support: ____; critical workflows: ____; acceptance threshold and stopping conditions: ____.
- Baseline process, known failures and representative data set: ____; evidence source: ____.
Validate the workflow
Use the same representative workload when comparing alternatives. Preserve unsuccessful and inconclusive results alongside successes.
- Context: can the reviewer identify the requirement, dependency and version used to select each check?
- Test quality: do actions and assertions verify the expected behavior, including negative and permission cases?
- Execution: are retries, timeouts, skipped work and environment failures visible?
- Evidence: can a second reviewer reproduce the finding using the recorded configuration and artifacts?
- Remediation: are proposed changes, verification and approval recorded separately from deployment authorization?
Assess operation and cost
Measure the work required to operate the system, including review and maintenance.
- Access/data: document credentials, data flows, storage, retention, model processing and customer-managed dependencies.
- Integration: verify supported interfaces, failure handling and the owner of compatibility changes.
- Cost: record subscription, usage, infrastructure, implementation, review and recurring maintenance assumptions.
- Support: confirm contracted hours, escalation, incident communications and responsibility boundaries.
Record the decision
Summarize observed results and unresolved uncertainty. Approve a bounded next step rather than extrapolating every result to all applications.
- Accepted scope: ____; rejected or unevaluated scope: ____; evidence package: ____.
- Critical gaps and mitigation owners: ____; review deadline: ____.
- Decision: proceed / revise / stop; decision owner and date: ____; expansion criteria: ____.
Related guidance
Use the enterprise guides to develop the workflow behind this template. Confirm product capabilities, commercial commitments and deployment-specific controls with the relevant owner.
