Grant-funded programmes don't always stay where they started. The community group funded to run a youth football programme gradually expands into social work. The environmental restoration project becomes a community development initiative. The research programme funded to study health outcomes pivots to advocacy.
This phenomenon — scope creep, programme drift, or mandate expansion — is common in the community sector and raises genuine accountability questions for grantmakers. When a programme has moved significantly from what was funded, has the grantee misused the grant? Or have they appropriately adapted to community need?
The answer is rarely simple, and the way funders respond to programme drift significantly affects grantee trust and the quality of the funder relationship.
Community needs evolve: The community problems that programmes are designed to address shift over time. A programme designed around one community need may discover that the underlying need has changed, or that a different intervention would be more effective.
Grantee learning: Organisations learn through delivery. A programme that was designed based on what the organisation understood about community need may discover, through delivering, that different approaches work better. Adaptation is a sign of a learning organisation.
Opportunity and mission pull: New opportunities — a partnership with another organisation, a community request, an emerging need — pull programmes toward new activities. Grantee staff may see these opportunities as mission-aligned extensions of their funded work.
Strategic drift: Some scope creep reflects organisational strategic drift rather than community-driven adaptation — mission creep toward more fundable activities, organisational expansion beyond genuine competence, or leadership pursuing personal interests at the expense of community focus.
Funder signals: When funders signal interest in certain activities through their conversations and publications, grantees may adapt their programmes toward what they believe funders want. This can produce drift away from what communities need toward what funders find interesting.
Adaptive evolution: When a programme adapts its methods while maintaining its purpose — a youth sport programme that adds social work support because it discovers that participants' primary barriers are family stability — this is programme learning, not drift. The purpose (supporting young people's wellbeing) is maintained; the methods have evolved.
Purpose drift: When a programme loses sight of its original purpose — the youth sport programme gradually transforms into a social enterprise because the grantee finds business development more interesting than youth work — this is genuine drift that raises accountability questions.
The test is purpose, not method. The question isn't "are they doing exactly what they said?" but "are they pursuing the purpose they were funded for in a way that makes sense given what they've learned?"
Progress reports: Regular progress reports should require grantees to describe what they've done and connect it to the programme as funded. Significant divergence from the funded programme should be visible in honest reporting.
Site visits: Seeing a programme in operation reveals things that written reports don't. A site visit that shows a different programme from what's described in reports is a red flag.
Community feedback: Community members served by programmes sometimes have better information than reports reveal. Maintaining informal channels — through community relationships, sector networks, or direct community consultation — provides ground-truth about programme delivery.
Financial analysis: Programme drift often shows in spending patterns. If a grant for direct service delivery is being spent on staff who are doing something different, financial reports will show unusual expenditure patterns.
Conversation: Regular substantive conversations with programme leadership — beyond transactional reporting — reveal what organisations are actually prioritising and thinking about.
Distinguish cause before responding: Is the drift adaptive (good) or dysfunctional (concerning)? Understanding why the programme has evolved before responding prevents punishing good organisational learning.
Have an honest conversation: Raise the concern directly — "we've noticed that what you're describing in your reports is different from what we funded; can you help us understand what's happened?" This conversation often reveals legitimate reasons for evolution that weren't communicated.
Assess against purpose, not plan: If the evolved programme still serves the original purpose effectively, consider whether a formal grant amendment to reflect current reality is more appropriate than insisting on returning to the original design.
Require a grant amendment for significant changes: For significant programme changes, a formal grant amendment — documenting what's changed, why, and with the funder's agreement — maintains the accountability record and ensures both parties are aligned on what's being funded.
Address dysfunctional drift firmly: If scope creep reflects misuse of funds, strategic confusion, or poor governance, this requires a firm response — a formal improvement plan, suspension of further grant payments, or in serious cases recovery of funds.
Consider whether your requirements contributed: Some programme drift is funder-induced — programmes adapt toward what funders seem to want, or in response to grant conditions that don't fit the community context. Honest reflection on whether your requirements contributed to the drift is valuable.
Clear purpose statements: Grant agreements that clearly state the purpose (not just the activities) of the funded programme give grantees a foundation to navigate when opportunities to drift arise.
Adaptive expectations: Grant conditions that explicitly acknowledge that methods may evolve, while requiring prior communication for significant changes, legitimise adaptation while maintaining accountability.
Regular conversation, not just reporting: Funders who maintain ongoing relationship conversations (not just formal reporting exchanges) hear about programme changes as they happen, rather than discovering them retrospectively.
Permission to change course: Grantees who believe they need funder permission for every programme decision may quietly adapt without disclosure to avoid administrative burden. Clear guidance on what requires formal amendment and what doesn't — with genuine flexibility for the latter — encourages transparency.
Tahua's grants management platform supports grant compliance management with progress reporting that connects grantee activity to funded programme purposes, amendment workflows for legitimate programme changes, and the relationship tracking that helps funders maintain the ongoing conversations that prevent silent programme drift.