VanillaPM
Sign in Get started free Dashboard
Free template

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.

Download Word (.docx) Download Markdown (.md) Free · no sign-up · opens in Word, Excel, Google Docs/Sheets and LibreOffice

What's inside

  1. Request detailsChange request number, title, date raised, and who is asking.
  2. Description of the changeWhat would change, exactly: the deliverable, requirement, date or budget line affected.
  3. Reason and benefitWhy it is needed, and what happens if it is not made.
  4. TypeCorrective action, preventive action, defect repair, or an update to the plan or a requirement.
  5. Impact assessmentThe effect on scope, schedule, cost, quality, risk and resources (table below). Say "none" rather than leaving a blank.
  6. Options consideredThe alternatives, including doing nothing, and why this one is recommended.
  7. DecisionApproved, rejected or deferred; who decided (sponsor, change control board) and when, with any conditions.
  8. 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

  1. Describe the change exactly: what changes, and which deliverable, requirement, date or budget line it touches.
  2. Say why: the reason, the benefit, and what happens if the change isn't made.
  3. 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.
  4. Show the options, including doing nothing.
  5. 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