Change Request

A change request captures a proposed change to a project’s agreed baseline and routes it through a decision. It typically describes what is being asked for, why, and its impact on scope, time, cost, and risk, so that whoever owns the decision — often a sponsor or change board — can weigh the trade-off and approve, reject, or defer it. The key idea is that changes to what was agreed are handled consciously and on the record, not slipped in informally.

This process is the main defence against scope creep. Requirements do legitimately evolve, and a good change process does not resist that; it simply insists that each change is made visibly, with its cost understood and the plan adjusted accordingly. Without it, additions accumulate unnoticed and the project quietly falls behind. With it, every stakeholder can see what changed, why, and what it cost — which keeps expectations honest and the plan credible. In agile delivery the same discipline is achieved differently, by pulling changes onto a prioritised backlog and trading them off openly.

In HR and GCC programmes, change requests bring order to initiatives that attract constant additions. When a hiring programme is asked to take on more roles, an HR-system rollout to add another integration, or a centre set-up to absorb an unplanned function, treating each as a change request — assessed for its impact on timeline, budget, and resources — forces an honest conversation about the trade-off. That converts “can you just also do this?” into a decision with visible consequences, which protects both the plan and the team delivering it.