How to stop scope creep in grant-funded projects
Scope creep drains budgets and time. Learn how NGO teams can define scope, say no kindly, and use a simple change request process with their donor.
Short answer
Stop scope creep by writing down what is in and out of scope, agreeing it with your donor and partners, and sending every new request through a simple change process: describe the change, assess its impact on time, budget and quality, decide, record the decision and update the plan. Never add work without checking the trade-off.
Key points
- Write clearly what is in scope and what is out of scope.
- Scope creep is extra work added without checking time, budget and approval.
- Every request goes through one short change process.
- Say yes only with a trade-off: more time, more money or less of something else.
- Record every decision, including the no.
What is scope creep in an NGO project?
Scope creep is the slow growth of a project's work beyond what was agreed. A community leader asks for an extra training. A partner wants one more village. A donor representative suggests a new report. Each request seems small and reasonable. Together they use staff time and budget that the grant did not cover, and the planned results suffer.
In plain terms, scope creep is adding work without examining the effect on schedule, budget or resources, and without approval. The UK government's change control guide says unmanaged change can cause scope creep, where requirements are added in an uncontrolled way, leading to time and cost limits being breached.
In a grant-funded project the risk is higher, because the logframe and budget are agreed with the donor and some changes need written approval.
How do you define scope clearly?
Scope management starts with a clear statement of what the project will and will not do. Project DPro, the method used by many development NGOs, explains that a well-defined scope shows what must be done, creates a shared understanding of the work, and puts boundaries around deliverables to avoid scope creep. It names the work breakdown structure and the logframe as useful tools.
Write a one-page scope statement that includes:
- Objectives and results from the logframe
- Main deliverables with quantities and places
- Exclusions, written as plainly as inclusions, for example "does not include rebuilding of private homes"
- Assumptions and limits, such as budget lines and dates
Review it with partners and your donor focal point at the start. Our guide to project charters can hold this statement in one place.
How do you handle a new request?
Use the same short process for every request, whoever makes it. The UK guide says every change request should be assessed through an impact assessment, and only necessary and beneficial changes that further the objectives should be approved.
- Capture the request. Write who asked, what they asked and why.
- Check it against the scope statement. Is it in scope, a variation or a new need?
- Assess the impact. Ask how long it will take, what it will cost, who will do it, and what other tasks depend on it. Also ask: if this causes delay or overspend, what else must be given up, or can more time and money be made available?
- Decide. Approve, reject, delay or swap. Include the donor if budget lines, results or dates must change.
- Record the decision. Log it with the date and reason.
- Update the plan. If approved, change the work plan, budget and tracker.
Our article on managing changes to scope, budget and timeline goes deeper into this process.
How do you say no without damaging trust?
Trust matters in community work, so a flat refusal can cause harm. A better approach is to say what you can do:
| Request | Weak answer | Better answer |
|---|---|---|
| Add two villages | "No, not in the plan." | "We can check budget and access. We will give you an answer by Friday." |
| Extra training day | "We have no time." | "We can add it if we drop the follow-up visit. Which is more useful?" |
| New report format | "That is extra work." | "We can adopt it from the next period. Can we agree the template now?" |
Notice that each better answer links the request to a trade-off. That is the heart of change control.
When is a change a good idea?
Not every change is scope creep. Contexts shift, and in Myanmar access, prices and needs can change quickly. A change is healthy when it better serves the project objective and is approved properly. If the context has changed enough that the plan no longer works, ask the donor for an amendment instead of quietly adjusting. Our guide to adaptive management covers this.
How do you spot scope creep early?
Watch for these signs:
- Staff say "we also did" in updates, but the extras are not in the plan
- Activities appear in monthly reports that have no budget line
- The team is busy but results are behind
- Partners deliver different things from what was agreed
Add "new requests this month" as a standing item in your team meeting. If the list is long, the scope is under pressure.
What mistakes should you avoid?
- Vague scope. Unclear wording lets everyone read it their own way.
- Only the project manager knows the rules. Share them with the whole team and partners.
- Verbal agreements. Staff change and memories differ. Write it down.
- Treating the donor request as automatic. Even donor suggestions need an impact check. Raise the effect on budget and time.
Donor rules differ. Check your grant agreement for what changes need written approval.
How EMPO can help
EMPO is a reliable, trusted training and consultancy provider and one of Myanmar's leading names in practical NGO training, with 1,200+ people trained and 15 partner organisations. We are based in Yangon and deliver in English and Burmese, online and in person across Myanmar. Our project management training covers scope, work plans and change control with practical exercises. See our training services or contact us.
Sources
- Chapter 22: Change control — UK Government Project Delivery, 2024
- The Project Model — PM4NGOs, Project DPro Starter
Questions people ask
What is the difference between scope creep and a legitimate change?
A legitimate change is assessed, approved and recorded, and the plan and budget are updated. Scope creep is added without that check.
How do we say no to a donor or community request?
Do not refuse on the spot. Say you will check the impact on budget, time and agreed results, then respond with options: do it later, swap it with another activity, or ask for a formal amendment.
Do small extras really matter?
Yes. Several small extras add up to real cost and delay. Log each one so you can see the total.