UnflakeOps
PPROGRAMME EXPORT
Service activity
Period · service · outcome · status
POWER PLATFORM AUTOMATION FOR UK CHARITIES
Turn one recurring charity report into a repeatable workflow.
Start with one funder, impact or trustee report. We map its sources, checks, hand-offs and delays, then build a controlled Power Platform workflow your team can run again.
Show us your last reportA redacted example or walkthrough is enough — no beneficiary data needed.
Funder reports · Impact reports · Trustee reports
Illustrative workflow showing programme, finance and approval information assembled into a quarterly funder report ready for a charity team to review.
Follow the reporting journey One report · One workflow · One useful result
Skip animation ↓
Good information.
Progress.
the numbers.
COLLECT · CHECK · APPROVE
READY FOR YOUR REVIEWTrustee
01 / FROM SCATTERED TO CONNECTED
Good information.
In too many places.
The records exist. Bringing them together is still someone’s job.
Service recordsCRM
People. Programmes.Progress.
Grant spendFINANCE
FundActualCommunityReconcileOutreachReconcile
Impact evidencePROGRAMMES
The story behindthe numbers.
ApprovalsINBOX
Re: latest version?
Can you check these figures before we send the report?
COLLECT · CHECK · APPROVEREADY FOR YOUR REVIEWYOUR NEXT
Trustee
report.
✓ Source information connected
✓ Checks and approvals visible
✓ Ready to run again
Your systems.
One repeatable workflow.↗
One repeatable workflow.↗
02 / FIND THE FRICTION
Sound
familiar?
The small workarounds that become everyone’s working day.
- 01
The same information is entered twice.
People move data between tools because the tools do not move it themselves.
- 02
The process depends on one person.
The real instructions live in memory, inboxes and last year’s spreadsheet.
- 03
Checking takes longer than collecting.
Teams repeatedly reconcile versions, totals, gaps and approvals—then rebuild the same process next time.
03 / WHAT THIS COULD LOOK LIKE
Three reports.
Less manual work.
Start with the report your team already produces. These illustrative scenarios show where a focused pilot could help.
FUNDER REPORTINGThe quarterly
The quarterly
deadline.
Activity+Spend↓One funder return
Illustrative scenario / 01For programme & finance teams
Delivery figures live in one spreadsheet. Grant spend lives in another. Someone matches them by hand every quarter.
Explore the proposed workflow
A focused starting point
Agree the fields for one grant return. Bring approved activity and spend exports into a shared staging area, flag missing project codes and route the draft to its owner.
What we would measure
Preparation hours, missing entries and how many corrections are needed before sign-off.
Possible tools
Power Automate for collection and approval; SharePoint or Dataverse for agreed records. The choice depends on your data and licences.
TRUSTEE REPORTINGThe board pack.
The board pack.
Without the chase.
Updates+Review↓One trustee pack
Illustrative scenario / 02For operations & leadership teams
Updates arrive by email, in different formats. The pack owner chases contributors and checks which version is final.
Explore the proposed workflow
A focused starting point
Use one agreed update format, track submissions and send reminders. Make the review status visible before assembling a draft pack.
What we would measure
Time spent chasing, late submissions and the number of versions circulated for review.
Possible tools
Power Apps or a SharePoint list for updates, with Power Automate for reminders and approvals. Trustees still receive the format you agree.
SERVICE IMPACTBring the outcomes
Bring the outcomes
into focus.
Services+Outcomes↓One impact view
Illustrative scenario / 03For service & impact leads
Different teams count activity differently. Reporting week becomes a round of checking totals and explaining gaps.
Explore the proposed workflow
A focused starting point
Agree one service’s reporting definitions. Combine approved exports, flag duplicates and missing fields, and prepare a consistent view for review.
What we would measure
Reconciliation time, unresolved data gaps and whether the team can repeat the process unaided.
Possible tools
Power Query for preparation and Power BI for the agreed report, with access and refresh requirements checked during scoping.
Proposed approaches, not completed UnflakeOps client projects. Scope, feasibility and success measures are agreed with your team.
YOUR REPORT / YOUR WORKFLOWHave a recurring report that feels like one of these?
Show us your last report04 / PUBLISHED UK CHARITY CASE STUDIES
What’s possible.
In practice.
Microsoft’s UK charity customer stories show what connected systems can achieve. These are other organisations’ projects, not UnflakeOps clients or results.
MICROSOFT CUSTOMER STORY · UK CHARITY
The Salvation Army UK
Days → moments
Monthly reporting, as reported by Microsoft
Siloed data and manual reporting made property decisions difficult. Microsoft Fabric and Power BI created a single source of truth, while Power BI also connects to an internal Power Platform app.
Why it matters: connected data can turn a recurring manual report into a faster, more trusted process.
Read Microsoft’s case study Published 26 June 2025MICROSOFT CUSTOMER STORY · UK CHARITY
National Zakat Foundation
80% less waiting
For aid disbursement, as reported by Microsoft
NZF combined Power Platform, Copilot Studio and Dynamics 365 to improve application handling. A unified data model also supported impact reporting and collaboration.
Why it matters: less manual coordination can improve the work behind both service delivery and reporting.
Read Microsoft’s case study Published 27 March 2025These broader programmes included technology beyond a small reporting pilot. Their reported results are context, not a forecast for your organisation.
05 / A FOCUSED PILOT
ONE
report
ONEworkflow
ONEuseful result
We start with a real recurring report, map the work as it happens today, and automate the useful parts around the systems you already use.
We are testing this focused pilot with UK charities. The first conversation is diagnostic: no build is assumed, and scope and success measures are agreed before work starts.
- Fixed scope
- Microsoft Power Platform
- Tested with your team
- Documented handover
HOW WE WOULD PROVE IT
A useful pilot has
a before and an after.
Time the last report.
Record preparation time, manual steps and corrections with the people doing the work.
Build one working flow.
An agreed report, its input checks and review process, plus instructions your team can use.
Run it against the baseline.
Compare the same report scope. Check the output as well as the time spent producing it.
Let your team run it.
Confirm who owns it, how to handle exceptions and what ongoing support would involve.
Success criteria, licences, access, price and scope are agreed before a build starts.
06 / BUILT WITH YOUR TEAM
Good systems.
Human judgement.
We follow the actual work, make the decisions visible and leave your team able to operate what we build.
Service records
Grant spend
Outcome notes
Project codes
2 figures to confirm
Reporting period
Programme lead
Finance lead
Final owner
SHOW
Walk through the last report.
The files, systems, people, checks and delays.
TRACE
Find the manual work.
Repeated entry, reconciliation, chasing and hand-offs.
BUILD
Automate the useful parts.
A controlled solution without replacing everything.
HAND OVER
Put the team in control.
Tested, explained and ready for the next reporting cycle.
07 / BEFORE WE START
The practical
questions.
Do we have to replace our current systems?
The starting point is one report using information your systems can already provide. We assess available exports and connections first. If a reliable connection is not possible, we explain the constraint before agreeing a build.
Is this included in our Microsoft 365 subscription?
Not necessarily. Requirements depend on the connectors, data storage, users and reporting tools involved. We check your existing licences and identify any additional subscription costs during scoping.
What should we bring to the first conversation?
A redacted example of the last report, a list of its source systems and the person who puts it together. A walkthrough is enough to start; you do not need to send identifiable beneficiary records.
What if our data is messy?
We identify gaps, conflicting definitions and duplicated records before automating them. Any necessary clean-up has to be scoped explicitly. Automation alone will not make unreliable source data accurate.
08 / START A CONVERSATION