Projects
Change Request Form Template: How to Fill It In, With an Impact Example
A change request (CR) is the document you use when someone wants to change something a project has already agreed: its scope, schedule, budget or quality bar. It records what would change, why, what it would cost in time and money, and who decided. Without it, "can you just add this?" requests pile up, the deadline slips and nobody can say when or why the plan changed.
This page gives you a ready-to-use change request form template in Word, explains every field, walks through a filled example with an impact assessment, and lists the steps of a simple change control process and the mistakes teams make most often.
What is a change request form?
A change request form is a formal proposal to change the project baseline. The requester describes the change and the business reason; the project manager analyses the impact on scope, schedule, cost, quality and risk; and a decision-maker or change control board approves, rejects or defers it. Once approved, the plan, budget and requirements are updated so that everyone works from the same baseline.
A change request is not the same as an issue. An issue is a problem that has already happened and needs resolving; a change request proposes changing what was agreed. If resolving an issue means changing the baseline, raise a change request for it. Where a supplier contract is involved, an approved change request usually also needs a contract variation signed by both parties.
When do you need a change request?
- A client or business team asks for a feature or deliverable that was not in the agreed scope
- New regulation, a policy change or a change in another system forces a requirement change
- The schedule or budget needs to move away from the approved baseline
- You plan to change the configuration or infrastructure of a live IT system
- Work you have contracted to a supplier needs to change
Change request form template: field by field
The download has three parts: the request, the impact assessment and the decision. The requester fills in the first part, the project manager the second and the decision-maker the third.
Request
| Field | What to write | Example |
|---|---|---|
| CR number | A unique ID with the project code so the request can be tracked in the change log. | CR-CRM26-021 |
| Requested by / date | Name, team and the date the request was logged. | Maya Collins, Customer Success, 16 Nov 2026 |
| Description of change | What exactly should change, in one or two specific sentences. | Add automatic renewal reminders to the customer portal |
| Reason / business case | Why it is needed and what happens if it is not done. | 12% of renewals are missed because customers forget the date |
| Priority | Critical, high, medium or low, with a short reason. | High: needed before the January renewal cycle |
Impact assessment
| Field | What to write | Example |
|---|---|---|
| Area | Scope, schedule, cost, quality or risk. | Schedule |
| Current baseline | The value in the approved plan. | Go-live 15 Dec 2026 |
| After change | The value if the change is made. | Go-live 12 Jan 2027 |
| Impact | The difference and what it means, in one line. | +4 weeks; overlaps the year-end freeze |
Decision and implementation
| Field | What to write | Example |
|---|---|---|
| Options considered | Full change, partial change or defer to a later phase, with pros and cons. | Option B: email reminders only in phase 1 |
| Decision | Approved, rejected or deferred, with who decided, when and any conditions. | Approved with conditions (option B), sponsor, 20 Nov 2026 |
| Implementation and rollback plan | When and by whom it is deployed, and how to undo it if it fails. | Deploy to staging 8 Dec; restore previous release if tests fail |
| Communication | Who must be told about the decision, and how. | Customer Success, Finance, vendor project manager |
Change request example
A CRM project where the customer success team asks for automatic renewal reminders. The impact assessment puts the baseline and the new value side by side so the difference is obvious.
| CR number | CR-CRM26-021 |
|---|---|
| Project | Customer portal and CRM rollout |
| Requested by | Maya Collins, Customer Success |
| Decision | Approved with conditions (option B: email reminders only in phase 1) |
Impact assessment
| Area | Current baseline | After change | Impact |
|---|---|---|---|
| Scope | 14 portal features | 15 features (renewal reminders) | +1 feature |
| Schedule | Go-live 15 Dec 2026 | Go-live 12 Jan 2027 | +4 weeks |
| Cost | $120,000 | $134,500 | +$14,500 (+12.1%) |
| Quality | 160 integration tests | 178 integration tests | +18 tests, regression run needed |
| Risk | Medium | High | Go-live overlaps year-end change freeze |
Tip: when the full change is too expensive, offer a smaller option such as option B. Decision-makers approve faster when they can choose between clear alternatives.
Free download
Free, no sign-up. Opens in Excel, Google Sheets, Numbers, Word, Google Docs and LibreOffice.
Open the downloaded file in Nobami, our web office, to edit it right away.
How to run a simple change control process
- Log every request in writing. Even requests made in a meeting or chat get a CR number and an entry in the change log.
- Assess the impact. The project manager compares scope, schedule, cost, quality and risk with the baseline and asks the people doing the work for estimates.
- Prepare options. Describe two or three options (full, partial, defer) and the impact of each.
- Get a decision. The agreed decision-maker or change control board approves, rejects or defers, and the decision, date and conditions are recorded.
- Update the baseline and communicate. Update the plan, budget and requirements, tell everyone affected and, if a supplier is involved, agree a written contract variation.
- Implement and close. Record the result, including whether a rollback was needed, and close the change request.
Good practice: contracts and governance
No general law requires a change request form for private projects. Contracts, however, usually say how they can be varied. Many require written changes signed by both parties, so an internal approval is not enough on its own when a supplier's price, deadline or deliverables change. Check the variation clause before instructing a supplier.
Public-sector projects follow their own governance. In the UK, for example, the government's project delivery functional standard expects projects to control changes to their agreed baselines. If you work on a public contract, follow the client's change procedure.
Change requests can contain names and contact details of client staff. Store them in a system with access control, and share them only with the people who need them.
Sources
- GOV.UK: Project delivery functional standard (checked November 16, 2026)
- European Commission: data protection explained (checked November 16, 2026)
General information, not legal advice. Contract variations depend on your contract and local law; ask a qualified adviser for specific cases.
Common change request mistakes
- Agreeing changes verbally in meetings or chat with no written record
- Calling a change "small" and building it without any impact assessment
- Approving the change but never updating the schedule and budget baseline
- Accepting many small changes one by one until the scope has quietly doubled
- Changing a live system without a tested rollback plan
- Instructing a supplier to do extra work without a signed contract variation
Change request FAQ
What is the difference between a change request and an issue?
An issue is a problem that has already happened. A change request proposes changing the agreed scope, schedule, cost or quality. If fixing an issue requires changing the baseline, raise a change request.
Who approves a change request?
The decision-maker named in your project governance, often recorded in a RACI matrix. Typically the project manager approves small changes and the sponsor or a change control board approves changes above agreed thresholds.
Do small changes need a change request?
Purely cosmetic fixes with no effect on the baseline can simply be logged. Repeated small changes should still be grouped and assessed together, otherwise scope creep goes unnoticed.
What if a supplier contract is involved?
The change request is your internal decision. Price, deadline or deliverable changes with a supplier usually need a written contract variation agreed under the contract's variation clause.
Can I use the template in Google Docs?
Yes. The Word (.docx) file opens and edits in Google Docs, LibreOffice and Pages.