Project Plan Template

# Project Plan

Project name:
Plan owner:
Last updated:
Target launch or finish date:

## Goal
- Primary outcome:
- Success looks like:
- Main audience or user:

## Scope
In scope:
- [deliverable, workflow, audience, or channel]
- [deliverable, workflow, audience, or channel]

Out of scope:
- [request or feature not included now]
- [quality level, platform, or audience not included now]

## Requirements
- Must have:
- Should have:
- Nice to have:
- Known constraint:

## Milestones
| Milestone | Owner | Target date | Done enough means | Status |
| --- | --- | --- | --- | --- |
| [discovery] | [name] | [date] | [decision or artifact] | [status] |
| [build] | [name] | [date] | [working draft or release candidate] | [status] |
| [review] | [name] | [date] | [approval or changes logged] | [status] |

## Risks
- Risk:
  Impact:
  Signal to watch:
  Mitigation:

## Dependencies
- Person, team, vendor, or system:
  Needed by:
  Backup plan:

## Review and Launch Checks
- Stakeholders reviewed:
- Test or proof needed:
- Rollback or correction plan:
- Communication owner:

## Next Actions
1. [owner] will [action] by [date].
2. [owner] will [action] by [date].
3. [owner] will [action] by [date].

## Boundary Reminder
- Do not hide uncertain dates; mark them as estimates.
- Keep future ideas in a backlog instead of expanding scope silently.
- Update owners when work changes hands.