Requirements Readiness Summary
Template Library
Requirements Readiness Summary Template
Summarize the ES-102 requirements package and decide whether ES-103 planning and work breakdown can begin responsibly.
ES-102
Readiness
Gate Summary
Template purpose
Use this template to summarize the ES-102 requirements package.
This artifact records whether requirements, constraints, use cases, traceability, and review evidence are sufficient for ES-103 — Planning and Work Breakdown to begin.
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-102 — Requirements and Constraints |
| Project workspace target |
docs/project-workspace/requirements/requirements_readiness_summary.md |
| Next stage |
ES-103 — Planning and Work Breakdown |
ES-102 package summary
<One or two paragraphs summarizing the requirements package.>
Completed artifacts
| Artifact |
Project Workspace Reference |
Status |
Notes |
| Requirements Overview |
docs/project-workspace/requirements/requirements_overview.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Functional Requirements |
docs/project-workspace/requirements/functional_requirements.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Non-Functional Requirements |
docs/project-workspace/requirements/non_functional_requirements.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Constraints |
docs/project-workspace/requirements/constraints.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Use Cases |
docs/project-workspace/requirements/use_cases.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Traceability Matrix |
docs/project-workspace/requirements/traceability_matrix.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
| Requirements Review |
docs/project-workspace/requirements/requirements_review.md |
<draft / reviewed / accepted / incomplete> |
<notes> |
Major requirements themes
| Theme |
Related Requirement IDs |
Planning Impact |
<theme> |
<FR/NFR/C IDs> |
<impact> |
Major constraints
| Constraint ID |
Constraint |
Planning / Architecture Impact |
<C-ID> |
<constraint> |
<impact> |
Traceability status
| Area |
Status |
Notes |
| Requirements trace to ES-101 evidence |
<complete / partial / incomplete> |
<notes> |
| Requirements trace to stakeholders or use cases |
<complete / partial / incomplete> |
<notes> |
| Requirements have verification approaches |
<complete / partial / incomplete> |
<notes> |
| AI, data, and governance concerns are traceable |
<complete / partial / incomplete / not applicable> |
<notes> |
Open issues
| ID |
Issue |
Owner |
Must Resolve Before |
| RI-001 |
<issue> |
<owner> |
<planning / architecture / implementation / release> |
Planning risks
| Risk |
Impact on ES-103 |
Mitigation |
<risk> |
<impact> |
<mitigation> |
Readiness decision for ES-103
Can planning and work breakdown begin?
<Yes / No / Conditional, with rationale.>
Conditions for proceeding
If readiness is conditional, list required actions.
| Condition |
Owner |
Due |
<condition> |
<owner> |
<date or stage> |
Reviewer notes
<Optional reviewer comments.>
Readiness checklist
- [ ] Requirements are aligned to ES-101 vision evidence.
- [ ] Functional requirements are sufficiently clear.
- [ ] Non-functional and trustworthiness requirements are explicit.
- [ ] Constraints and prohibitions are documented.
- [ ] Use cases cover major stakeholder goals.
- [ ] Requirements are traceable.
- [ ] Verification approaches are identified.
- [ ] Requirements review was completed.
- [ ] Open issues are visible and owned.
- [ ] Planning can begin without hiding major uncertainty.
Continue to Planning Templates
Use the accepted requirements package to begin ES-103 planning and work breakdown.
Open Planning Templates →