Project Change Request
Evaluate requested changes to scope, budget, schedule, or acceptance criteria.
Purpose
Change work should separate intent, risk, approval, communication, execution, validation, and rollback. The purpose is not to slow change; it is to prevent avoidable surprise.
Project use
Use this page before project momentum makes assumptions hard to correct. It should make the work easier to approve, pause, adjust, or close.
| Decision supported | What does this document help decide? |
|---|---|
| Owner | Who is accountable for updating it? |
| Boundary | What is included, excluded, deferred, or assumed? |
| Evidence | What confirms completion, acceptance, or handoff? |
When to use
- When the work repeats often enough that memory is no longer reliable.
- When more than one person may request, perform, review, or inherit the work.
- When risk, approval, evidence, or handoff needs to be visible later.
Common failure modes
- Rollback is assumed but not practical.
- Affected users are notified too late.
- Validation checks do not prove the intended result.
- Scope grows without a decision record.
Review guidance
Review this page after a material incident, after a role or system change, and on a normal cadence appropriate to its risk. During review, check whether the owner is still correct, whether inputs are still complete, whether the output is still useful, and whether related pages need updates.
External guidance
These resources are references for terminology, control thinking, or review design. DailyWF adapts the ideas into lightweight operating pages rather than reproducing full standards.
- NIST Cybersecurity Framework 2.0General cybersecurity risk management structure: govern, identify, protect, detect, respond, recover.
- CIS Critical Security Controls v8Prioritized safeguards for common enterprise security risks.
- ISO quality management principlesProcess approach, evidence-based decisions, improvement, and relationship management.