A change request is a formal proposal to adjust project scope, timeline, or budget after the original agreement has already been approved.
What is a change request?
A change request, often shortened to CR, is used when a client or delivery team wants to add, remove, or modify work that was not covered by the approved Scope of Work.
The key point is that the change must be assessed and approved before implementation starts.
Example
During development of a mobile commerce app, the client asks to add Apple Pay and Google Pay alongside the original card checkout.
Instead of confirming the request verbally, the team estimates the additional work, prepares a formal CR with cost and timeline impact, and starts implementation only after written approval.
Why change requests matter
- They keep scope changes transparent.
- They protect margins from untracked extra work.
- They stop small verbal requests from silently expanding the project.
- They keep the relationship with the client clear and professional.
Standard change request lifecycle
- Document the requested change and its purpose.
- Assess the impact on effort, dependencies, budget, and timeline.
- Send a clear commercial proposal or addendum.
- Start implementation only after written approval.
Scope creep vs. change request
| Aspect | Scope creep | Change request |
|---|---|---|
| Authorization | Informal or unapproved. | Explicitly reviewed and approved. |
| Workflow | Ad hoc and weakly tracked. | Structured, costed, and documented. |
| Financial impact | Often hidden and damaging to margin. | Transparent and priced. |
| Project control | Low visibility and higher stress. | Higher predictability and accountability. |
Common mistakes
- Treating extra work as a “small favor” instead of a formal change.
- Starting development before commercial approval.
- Describing the request vaguely, without a clear scope delta.
- Forgetting to document timeline impact together with budget impact.
How Apropo supports change request workflows
Apropo does not expose a dedicated change request object in the confirmed frontend, but it does support the surrounding workflow for revising scope, pricing, and proposal structure.
- New estimate versions help teams capture changed scope without overwriting the previous agreement state.
- Version workflows can carry comments forward, which helps preserve the review context around a revision.
- Shareable proposal links make it easier to circulate the updated version for review.
- Threaded comments help teams discuss what changed and why inside the proposal workflow.
How Apropo helps operationalize a scope revision
Scope changes are easier to handle when revision history, reviewer discussion, and downstream handoff stay connected.
- Version-specific sharing helps teams point stakeholders to the revised offer instead of a mixed history of drafts.
- Jira export helps move an updated structure into delivery planning after the revised scope is accepted.
- PDF and print outputs help package a revised proposal cleanly.
- Budget tracking can later show how the revised plan performed against actual work.