A formal request to add or alter something outside the agreed scope, priced and approved before it is built.
A change request is the formal mechanism for adding to or altering what was agreed in the scope of work: a new report, an extra integration, a workflow the business did not mention at the start, or a regulatory change such as an e-invoicing field. It describes the change, its effect on timeline and price, and requires approval before work begins.
It matters because without it, scope grows silently and either the implementer absorbs the cost and cuts corners or the client receives an unexpected invoice. For a UAE business on a fixed-price contract, the change request is what keeps the fixed price honest: the base scope stays fixed and additions are visible and chosen.
In an ERP project, expect change requests and treat them as normal; a project with none usually means things were pushed to after go-live. Keep a log, price each one separately, and batch small ones into a phase rather than disrupting the build. Be wary of an implementer who waves everything through without paperwork, and of one who raises a change request for every clarification.
A 30-minute look at how your business runs today, with a senior consultant. Free, and the findings are yours.
Book a 30-minute discovery call