How Change Requests Are Raised and Approved
A change request (CR) is a formal mechanism for requesting something that falls outside the agreed scope of your current Statement of Work. Changes are a normal part of project delivery — what matters is managing them transparently.
What Triggers a Change Request?
- Adding new features or functionality not in the original SoW
- Changing the technical approach or architecture
- Expanding the scope of existing features significantly
- Changing agreed timelines (particularly accelerating them)
- Requiring additional environments, third-party integrations, or licences
- Requests that invalidate assumptions listed in the SoW
How to Raise a Change Request
- Discuss the proposed change with your Project Manager — they will assess whether it is in or out of scope
- If out of scope, your PM will produce a Change Request Form documenting the change, the reason, the estimated additional cost, and the timeline impact
- You review and either approve or reject the CR in writing (via the portal or email)
- Work on the change begins only after written approval — oral approval is not sufficient
Impact on Timeline and Budget
Every approved change request adds to both cost and time. We will always be transparent about the impact before you approve. We never begin change work speculatively.
Small Changes & "Minor Amendments"
Not every small tweak requires a formal CR. Your Project Manager has discretion to absorb genuinely minor amendments (e.g. copy corrections, colour adjustments within existing design) without a formal CR. If in doubt, ask — it is always better to clarify than to assume.