How to Stop Change Requests From Blowing Up Your ERP Project

Short answer: Change requests are normal; uncontrolled change is what kills ERP projects. The cure is simple and needs discipline on both sides: a signed scope for each phase, a one-page change request for anything new, a clear decision on each request (now, later or never), and a formal sign-off at the end of each phase. Most "small" requests belong in a phase-two backlog, not in the go-live plan.
In almost every delayed project I have reviewed, the original scope was achievable. What made it late was a steady stream of additions, each reasonable on its own, with nobody tracking their combined effect.
Why does scope creep?
- Users see the system for the first time during testing and ask for what they now realise they want.
- Departments that skipped the analysis workshops add their needs late.
- Management changes priorities mid-project.
- The partner says yes to keep the client happy, without stating the cost.
The five parts of good change control
1. A signed scope per phase
The solution design document lists what is in, and also what is explicitly out. Both sides sign it. This is the baseline every request is measured against.
2. A one-page change request
| Item | Content |
|---|---|
| Requested by | Name and department |
| Description | What is needed, in business terms |
| Reason | The problem it solves, and what happens without it |
| Impact | Effort, cost and effect on the timeline, estimated by the partner |
| Decision | Approve now / defer to phase two / reject, with the approver's name |
3. One person decides
The client's project owner approves or rejects requests, with the sponsor involved when cost or timeline changes significantly. Requests do not go directly from users to developers.
4. A visible backlog
Deferred requests go into a phase-two list. People accept "not now" much more easily when they can see their request is recorded and will be reviewed.
5. Phase sign-off
At the end of each phase, the client signs that the delivered scope is accepted. Issues after sign-off are handled as support or as new requests, not as reopening the phase.
What is a change, and what is a defect?
- Defect: something in the signed scope that does not work as agreed. The partner fixes it.
- Change: something new or different from the signed scope. It goes through the change process.
Agreeing this distinction at the start avoids most arguments later.
Frequently asked questions
Doesn't this make the partner rigid?
No. It makes changes visible. Good partners still accept changes, but everyone knows their cost and effect on the date.
What if a legal or tax change requires a new feature?
It still goes through the same process, usually with high priority. The process is about visibility, not about blocking necessary work.
How many changes are normal?
Some changes are always expected. The warning sign is when approved changes keep moving the go-live date.
Run your ERP project with clear scope
ExtraMile delivers Odoo projects with signed phases and a transparent change process. Talk to us before your next phase starts.
Talk to our project team or message us on WhatsApp: Egypt · Gulf
This article was drafted with AI assistance and reviewed and edited by Mohamed El-Baddaly, Chairman of ExtraMile Business Solutions.
