Project management practice
Project change request template with options and impact analysis
Make a change reviewable: explain the baseline, requested change, alternatives, delivery impact, approval authority and implementation conditions.
Make the proposed change explicit
A change request asks the authorised decision-maker to alter an agreed baseline. It should make the difference between today’s commitment and the proposed commitment inspectable. Do not hide a new requirement inside an updated task list.
Describe the business need without assuming the requested solution is the only option. Compare accepting, deferring and declining the change, including the consequence of doing nothing. State where impact estimates are uncertain.
Worked example: a second entrance
The fictional access rollout covers one entrance. A stakeholder asks for a second entrance after the configuration baseline is agreed. The request may be valuable, but it adds hardware, installation, testing and acceptance work.
| Option | Effect | Decision consequence |
|---|---|---|
| Add now | Estimated +3 working days and +2,400 cost units; capacity unconfirmed | Reforecast opening and obtain budget authority. |
| Add after opening | Keep initial scope; separate follow-up visit and mobilisation cost | Accept temporary manual access at the second entrance. |
| Decline | No baseline change | Document the operational limitation and owner of the workaround. |
Follow the change through the artifacts
If approved, update the versioned scope, schedule, cost forecast and responsibility rows. Tell the people who will act on the decision. Keep the original baseline and approval record so later reviewers can reconstruct what changed and why.
Approval may be conditional: a supplier quote, security acceptance or a capped cost. An approval with unmet conditions is not permission to assume every dependency is resolved. Record who checks those conditions before implementation.
Copyable request
Change ID / requester / date: Current approved baseline and version: Problem or opportunity: Requested change and acceptance criteria: Options, including defer / do nothing: Impact on scope, time, cost, quality, risk and people: Estimate basis / confidence / unresolved facts: Recommendation and trade-off: Decision authority / latest useful date: Decision / conditions / approval evidence: Artifacts and stakeholders to update / owner:
Avoid a retrospective approval ritual
Bring the request forward before the team commits effort that requires approval. If urgent action has already been taken under an existing emergency authority, record that basis accurately; do not backdate permission.
This worksheet teaches change reasoning. Apply your organisation’s actual thresholds, contractual obligations and approval process when using it at work.
Method background
These sources provide general background. The worked examples and worksheets are original Response Shift teaching material; the organisations do not endorse this product.
