Design Review
Template Library
Design Review Template
Review detailed design for traceability, implementability, testability, access control, AI interaction, failure behavior, technical decisions, and readiness for implementation.
ES-105
Review
Design Gate
Template purpose
Use this template to review the ES-105 design package before declaring readiness for implementation readiness.
The review should determine whether the design is specific enough to implement, test, review, operate, and govern without hiding major uncertainty.
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-105 — Detailed Design |
| Project workspace target |
docs/project-workspace/design/design_review.md |
| Field |
Value |
| Review Date |
<date> |
| Reviewers |
<names or roles> |
| Design Version |
<version or commit> |
| Review Type |
<self / team / peer / instructor / stakeholder / governance> |
| Scope of Review |
<all design artifacts / selected artifacts / changes only> |
Artifacts reviewed
| Artifact |
Reviewed? |
Notes |
design_overview.md |
<yes / no> |
<notes> |
interface_design.md |
<yes / no> |
<notes> |
data_design.md |
<yes / no> |
<notes> |
workflow_design.md |
<yes / no> |
<notes> |
access_control_design.md |
<yes / no> |
<notes> |
ai_interaction_design.md |
<yes / no / not applicable> |
<notes> |
error_and_exception_design.md |
<yes / no> |
<notes> |
technical_decision_records.md |
<yes / no> |
<notes> |
Review checklist
- [ ] Design traces to architecture.
- [ ] Interfaces are clear.
- [ ] Data structures support evidence needs.
- [ ] Workflows include normal, alternate, and exception flows.
- [ ] Access-control behavior is explicit.
- [ ] AI interaction is explicit or marked not applicable.
- [ ] Failure behavior is defined.
- [ ] Technical decisions are recorded.
- [ ] Design is testable.
- [ ] Evidence production is designed.
- [ ] Security and privacy implications are addressed.
- [ ] Operational and monitoring implications are visible.
- [ ] ES-106 readiness is clear.
Findings
| ID |
Finding |
Severity |
Affected Artifact |
Action |
Owner |
Status |
| DRF-001 |
<finding> |
<low / medium / high> |
<artifact> |
<action> |
<owner> |
<open / closed> |
Traceability review
| Area |
Concern |
Action |
<architecture, requirement, ADR, risk> |
<concern> |
<action> |
Implementability review
| Concern |
Impact |
Action |
<unclear contract, missing data rule, ambiguous workflow, missing state, unclear owner> |
<impact> |
<action> |
Testability review
| Concern |
Affected Artifact |
Action |
<untestable behavior, missing acceptance criteria, unclear error behavior> |
<artifact> |
<action> |
Access, AI, and failure review
| Concern |
Impact |
Action |
<access control, AI interaction, human review, exception handling, escalation, audit evidence> |
<impact> |
<action> |
Review decision
<Accepted / Accepted with revisions / Not ready>
Required revisions before readiness
| Revision |
Owner |
Due |
<revision> |
<owner> |
<date or stage> |
Reviewer notes
<Optional reviewer comments.>
Continue to Design Readiness Summary
Summarize the ES-105 design package and decide whether ES-106 implementation readiness may begin.
Open Design Readiness Summary →