DailyWF / Projects
Project Change Request
Evaluate requested changes to scope, budget, schedule, or acceptance criteria.
Project use
Use this when proposed changes affect scope, budget, schedule, acceptance criteria, or risk.
- Describe the requested change and why the current plan no longer fits.
- Identify impact on cost, schedule, scope, risk, support, and dependencies.
- List options: approve, reject, defer, split, or replace another item.
- Record decision authority and any conditions.
- Update the project plan and stakeholders after the decision.
Expected output
A project record that states the decision, owner, boundary, dependency, next checkpoint, and evidence needed to continue.
Common failure mode
Approving scope change informally and discovering consequences later.
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 CharterDefine purpose, scope, owner, constraints, and success criteria.
- Milestone ReviewCheck whether a project should continue, adjust, pause, or close.
- Project IntakeCapture a proposed project before committing time or budget.
- Project Status ReportReport progress without hiding risk or uncertainty.
- Assumption LogTrack project assumptions before they become invisible sources of risk.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.