Grant Management Tool for a Ukrainian Agriculture Programme
International development company
In short
How can an aid programme track the full grant cycle in one system?
When grants, private-sector co-investments and contracts are tracked in different tools, managers cannot see the portfolio, each stage of the grant cycle depends on who holds the file, and money for Ukrainian agriculture moves more slowly than it should. We built one grant management system on Microsoft tools for the client.
Results in numbers
- grant system users
- c. 70
- grant managers
- c. 20
At a glance
- One system for the full grant cycle
- About 70 users, about 20 of them grant managers
- Seven-week window for deployment and training
The client
The client is an international development company that runs aid programmes for donors in many countries. This programme supports Ukrainian agriculture, works with small and large providers, and uses Microsoft 365, SharePoint and Teams.
What it was costing them
- Fragmented tools: grants, co-investments and contracts sit in separate places, so the portfolio is hard to see.
- Slow grant cycle: signing, monitoring and closing depend on manual hand-offs between teams and providers.
- Short window: seven weeks leaves no time for a long build or a slow search for a product.
- Maintenance burden: a heavy custom system is costly for a team that wants lower upkeep.
What we built
We built a grant management system on Dataverse and Power Apps that follows each grant from concept to close, using the client's SharePoint folders and Teams.
- One record per grant: a Dataverse model holds provider, contract, milestones and documents, so the whole portfolio sits in one place.
- Every stage tracked: stages run from concept and review through award, monitoring and close, with a process bar and clear owners.
- Familiar document home: grant folders stay in the existing SharePoint structure and are linked from the record.
- Less chasing: Power Automate sends approvals, reminders and alerts for late reports in Teams and email.
- A portfolio view for leaders: Power BI shows grants by stage, provider and status.
- Right access for the right people: security roles for grant managers, operational staff and portfolio leads, with sensitive data restricted.
- Ready for change: a build-or-buy comparison with Dynamics 365 Project Operations was made before the final scope.
- Realistic timeline: configuration, training and deployment fit the seven-week window the client asked for.
Results
- Result: grant managers find the status of any grant in one place, instead of searching folders and email.
- Result: fewer missed reports, because reminders and alerts are sent automatically at each stage.
- Users: about 70 in total, about 20 grant managers and up to 50 operational users.
The risk most teams miss
A grant system succeeds or fails on the process around it. In month three, providers submit in different ways, stages are skipped and the portfolio view shows gaps. We fixed one stage model and one set of required fields from day one, and we review it with the grant managers after the first live grants.
What we would add today
Improvements we would add on top of what is live.
- Add a Power Pages portal for providers later, so they submit reports and documents under their own sign-in, as the client suggested.
- Use AI Builder document processing or Azure Document Intelligence to read grant applications and financial reports.
- Add a Copilot Studio agent for grant managers to ask about a grant, its milestones and documents.
- Use Dataverse row and field security so financial and provider data is visible only to the roles that need it.
- Deploy with Power Platform pipelines and connection references, so test and production stay separate.
Technology
Power Apps (model-driven), Microsoft Dataverse, Power Automate, Power BI, SharePoint Online, Microsoft Teams, optionally Dynamics 365 Project Operations.
Tell us how many stages your grants go through and where they stall, and we will tell you what one system for them can look like.
Products and capabilities
- Power Apps
- Dataverse
- Power Automate
- Power BI
- SharePoint
- grant management
- grant lifecycle
The service behind this work
Power Platform developmentMore on this industry
Public sector
Related use cases
Management and planningProgramme Collaboration Platform on Microsoft 365
A cooperation programme that runs events, registrations, surveys and shared workspaces across many countries cannot do it well with an ageing mail system and separate tools. We built a platform for the programme that puts all of it on Microsoft 365 and Power Platform.
- 78
- tender requirements met
- 65
- programme staff
Copilot and Power Platform Use Case Mapping
Most Copilot projects stall on one question: where does Copilot help, and where does the business need something else? the client had that question across its corporate teams. We turned business problems and role stories into a map that names the Microsoft tool for each, so spend goes to the right place.
- 34
- problems matched to a tool
- 29
- role-based use cases
Getting More from Teams, Planner and SharePoint
A group that has just moved to Microsoft 365 often uses only a few of its tools, and each company works in its own way. The client wanted its people to use more of the tools they have and work more efficiently. We put in place a productivity programme to make Teams, Planner and SharePoint the normal way to work together.
- c. 100
- users across the group
- 5
- group companies
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.