Skip to content

Planning Readiness Summary

Template Library

Planning Readiness Summary Template

Summarize the ES-103 planning package and decide whether ES-104 architecture and technical approach can begin responsibly.

ES-103 Readiness Gate Summary

Template purpose

Use this template to summarize the ES-103 planning package.

This artifact records whether the plan, work breakdown, ownership model, milestones, dependencies, estimates, risks, and review evidence are sufficient for ES-104 — Architecture and Technical Approach 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-103 — Planning and Work Breakdown
Project workspace target docs/project-workspace/planning/planning_readiness_summary.md
Next stage ES-104 — Architecture and Technical Approach

ES-103 package summary

<One or two paragraphs summarizing the planning package.>

Completed artifacts

Artifact Project Workspace Reference Status Notes
Planning Overview docs/project-workspace/planning/planning_overview.md <draft / reviewed / accepted / incomplete> <notes>
Work Breakdown Structure docs/project-workspace/planning/work_breakdown_structure.md <draft / reviewed / accepted / incomplete> <notes>
Roles and Responsibilities docs/project-workspace/planning/roles_and_responsibilities.md <draft / reviewed / accepted / incomplete> <notes>
Milestones docs/project-workspace/planning/milestones.md <draft / reviewed / accepted / incomplete> <notes>
Dependency Map docs/project-workspace/planning/dependency_map.md <draft / reviewed / accepted / incomplete> <notes>
Estimation Record docs/project-workspace/planning/estimation_record.md <draft / reviewed / accepted / incomplete> <notes>
Risk Register docs/project-workspace/planning/risk_register.md <draft / reviewed / accepted / incomplete> <notes>
Planning Review docs/project-workspace/planning/planning_review.md <draft / reviewed / accepted / incomplete> <notes>

Major work areas

Work Area Key Work Packages Architecture Impact
<area> <WP-IDs> <impact>

Major risks

Risk ID Risk Architecture / Planning Impact Mitigation
<R-ID> <risk> <impact> <mitigation>

Architecture-relevant issues

Issue Source Needed in ES-104
<issue> <requirement, constraint, dependency, risk, work package> <architecture decision, model, tradeoff, spike, review>

Ownership and evidence status

Area Status Notes
Work ownership <clear / partial / unclear> <notes>
Evidence ownership <clear / partial / unclear> <notes>
Review ownership <clear / partial / unclear> <notes>
AI verification ownership <clear / partial / unclear / not applicable> <notes>
Risk ownership <clear / partial / unclear> <notes>

Dependency status

Area Status Notes
Critical dependencies <resolved / planned / open / blocked> <notes>
Architecture dependencies <resolved / planned / open / blocked> <notes>
External dependencies <resolved / planned / open / blocked> <notes>

Readiness decision for ES-104

Can architecture and technical approach work 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

  • [ ] Planning traces to accepted requirements and constraints.
  • [ ] Work packages are deliverable-oriented.
  • [ ] Owners are assigned for work, evidence, review, risks, and dependencies.
  • [ ] Milestones include readiness evidence.
  • [ ] Dependencies are visible and assigned.
  • [ ] Estimates include confidence and uncertainty.
  • [ ] Risks are recorded, assigned, and actionable.
  • [ ] AI verification work is planned where relevant.
  • [ ] Architecture-relevant issues are visible.
  • [ ] ES-104 can begin without hiding major uncertainty.

Continue to Architecture Templates

Use the accepted planning package to begin ES-104 architecture and technical approach work.

Open Architecture Templates →