Change Request
How to manage project change through explicit impact, decisions, and new baselines.
Change is normal
Manage it explicitly.
Scope drift ≠ Change Request
Unnamed change creates risk.
Framework: Change → Reason → Impact → Decision → New Baseline
Use five layers.
Separate need from preference
Reason matters.
Assess systemic impact
Scope, time, cost, risk, dependencies.
Clarify decision authority
Someone must own the trade-off.
Create a New Baseline
Approved change updates the agreement.
Rejected change needs rationale
Make trade-offs visible.
Applying this on Forwork
Use a Change Request Block linked to Scope, Milestones, Decision Log, Work Tracking.
Conclusion
Change → Reason → Impact → Decision → New Baseline.