Data and Evidence Flow
Template Library
Data and Evidence Flow Template
Map how data and engineering evidence are created, transformed, reviewed, stored, retained, protected, and used downstream.
ES-104
Flows
Data + Evidence
Template purpose
Use this template to document how data and evidence move through the system.
ETIS treats evidence as an architectural concern. Important engineering and operational actions must leave reviewable traces. This includes requirements evidence, AI-use evidence, decision records, review records, test results, operational events, incidents, monitoring signals, release decisions, and stewardship evidence.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-104 — Architecture and Technical Approach |
| Project workspace target |
docs/project-workspace/architecture/data_and_evidence_flow.md |
Data flow summary
<Describe major data flows.>
Evidence flow summary
<Describe where engineering or operational evidence is created, reviewed, stored, retained, and used.>
Flow register
| Flow ID |
Source |
Destination |
Data / Evidence |
Review Required? |
Storage / Retention |
Related Requirement |
| F-001 |
<source> |
<destination> |
<data/evidence> |
<yes / no / conditional> |
<location/rule> |
<requirement> |
Data classification
| Data / Evidence Type |
Sensitivity |
Access Control |
Retention / Disposal |
<type> |
<public / internal / confidential / restricted / sensitive> |
<control> |
<rule> |
Evidence creation points
| Point |
Evidence Created |
Trigger |
Owner |
<point> |
<evidence> |
<event> |
<owner> |
Evidence review points
| Point |
Evidence Reviewed |
Reviewer |
Decision Supported |
<point> |
<evidence> |
<reviewer> |
<decision> |
Evidence storage points
| Evidence |
Storage Location |
Retention |
Access |
<evidence> |
<location> |
<retention> |
<access> |
AI evidence flows
Use this section if AI is used in the system or engineering workflow.
| Flow ID |
AI Input |
AI Output |
Human Review |
Evidence Preserved |
| AIF-001 |
<input> |
<output> |
<review> |
<prompt/output, decision, review, evaluation, log> |
Audit and observability flows
| Flow ID |
Event / Signal |
Producer |
Consumer |
Use |
| OBS-001 |
<event or signal> |
<component> |
<reviewer, operator, monitor, dashboard> |
<audit, operations, incident response, stewardship> |
Open evidence flow questions
| ID |
Question |
Owner |
Needed By |
| EFQ-001 |
<question> |
<owner> |
<date or stage> |
Review checklist
- [ ] Major data flows are documented.
- [ ] Evidence creation points are identified.
- [ ] Evidence review points are identified.
- [ ] Evidence storage and retention are defined.
- [ ] Sensitive data and evidence are classified.
- [ ] AI evidence flows are included where relevant.
- [ ] Audit and observability flows are considered.
- [ ] Open evidence flow questions are recorded.
Continue to Quality Attribute Strategy
Define architectural strategies for quality, trust, security, reliability, observability, maintainability, and operation.
Open Quality Attribute Strategy →