Change request form template
A free change request form template in Word and Markdown — description, reason, type, impact on scope, schedule, cost, quality and risk, options, decision and implementation, ready for a change control board.
What's inside
- Request detailsChange request number, title, date raised, and who is asking.
- Description of the changeWhat would change, exactly: the deliverable, requirement, date or budget line affected.
- Reason and benefitWhy it is needed, and what happens if it is not made.
- TypeCorrective action, preventive action, defect repair, or an update to the plan or a requirement.
- Impact assessmentThe effect on scope, schedule, cost, quality, risk and resources (table below). Say "none" rather than leaving a blank.
- Options consideredThe alternatives, including doing nothing, and why this one is recommended.
- DecisionApproved, rejected or deferred; who decided (sponsor, change control board) and when, with any conditions.
- ImplementationWho updates which baselines and documents, and how the people affected are told.
Includes a ready-made table with 4 columns: Area · Impact · Amount (days or money) · Notes.
What a change request is
A change request is a formal proposal to change something that has been agreed: a deliverable, a requirement, a baseline date or budget, or a plan. Writing it down lets the right person decide with the full picture, and leaves a record of why the project changed.
When to use it
Whenever someone wants to change an approved baseline or a controlled document. Corrective actions, preventive actions and defect repairs go through it too in most organisations, though they can often be approved at a lower level.
How to fill it in
- Describe the change exactly: what changes, and which deliverable, requirement, date or budget line it touches.
- Say why: the reason, the benefit, and what happens if the change isn't made.
- Assess the impact on every area in the table: scope, schedule, cost, quality, risk and resources. Write "none" rather than leaving a gap, so readers know it was checked.
- Show the options, including doing nothing.
- Record the decision: who decided, when, and on what conditions. If it was approved, list the baselines and documents to update and who will tell the people affected.
Common mistakes
- Doing the work first and raising the change afterwards. That is a change nobody decided.
- Only the cost impact. A cheap change can still move the critical path or add a risk.
- Approved by the wrong person. Check the approval limits in your governance plan; the decision log records who decided.
See it used on a real project: B3 · Manage and control changes