DailyWF / Projects
Project Charter
Define purpose, scope, owner, constraints, and success criteria.
Project use
Use this to define why the project exists before detailed planning begins.
- State purpose, problem, desired outcome, owner, sponsor, and boundaries.
- Identify success criteria, constraints, assumptions, and major risks.
- Name stakeholders and decision authority.
- Clarify what is explicitly out of scope.
- Approve or reject the charter before planning consumes effort.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Starting planning before agreement on purpose and boundary.
Use notes
| Best trigger | Use before a project decision becomes expensive to reverse. |
|---|---|
| Evidence | Keep enough context to explain the decision later without reconstructing conversations. |
| Review point | Review when scope, stakeholder expectation, timing, risk, or ownership changes. |
Related pages
- Project Change RequestEvaluate requested changes to scope, budget, schedule, or acceptance criteria.
- Project PlanTurn a charter into phases, tasks, owners, dependencies, and checkpoints.
- Project CloseoutClose work formally and preserve ownership of remaining obligations.
- Assumption LogTrack project assumptions before they become invisible sources of risk.
- Dependency TrackerTrack decisions, inputs, vendors, systems, people, and approvals that can block delivery.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.