Power BI for Charity Reporting (Without a Data Team)

Most UK charities already have Power BI in their Microsoft 365 tenant. Most are not using it. Reporting still happens in colour-coded spreadsheets, gets pasted into PowerPoint the night before the board meeting, and is out of date within a week. This is unnecessary, and the fix is more achievable than it looks.

Power BI is not a magic tool. It is a perfectly good reporting platform that, with about ten days of focused work, can replace a year of spreadsheet chaos with a single, trustworthy dashboard. Here is how to get there without hiring a data team.

What Power BI is actually good at

• Pulling data from multiple sources (CRM, finance, Excel, Google Analytics) into one model.
• Creating dashboards that auto-refresh on a schedule.
• Letting non-analysts filter and explore data without breaking the model.
• Embedding views in Teams, SharePoint and Outlook so reports come to people, not the other way around.
• Producing board-quality visuals that look like they came from a consultancy deck.

What it is not for

• Real-time operational dashboards (use the CRM's native dashboards for that).
• Heavy data engineering (it can do it, but you would not enjoy it).
• Replacing your CRM or finance system as the source of truth.

The minimum viable Power BI setup

Step 1: Decide what the dashboard answers

Before opening Power BI, write down the questions the dashboard must answer. For most charities, three sections cover it:

• Fundraising: income by source, by month, against budget, with year-on-year comparison.
• Supporter base: active supporters, new supporters, attrition rate, top segment counts.
• Operations and impact: programme delivery metrics, key impact numbers, reserves position.

Three sections, six to nine charts in total. Anything more becomes a wallpaper that nobody reads.

Step 2: Set up the data sources

Power BI connects to most of what a charity uses: Dynamics, Salesforce, HubSpot, Donorfy via API, ThankQ, eTapestry, SharePoint, Excel, GA4 and most major finance systems. The order of operations matters: connect to the source of truth (the CRM and the finance ledger), not to a downstream export.

Where direct connection is not possible, schedule a clean export to a SharePoint or OneDrive folder that Power BI reads on a refresh schedule. Avoid manual file uploads. The whole point is to remove the human re-keying step.

Step 3: Build a simple data model

In Power BI's model view, link the tables on the identifiers that join them (supporter ID, fund code, date). Keep the model deliberately simple at first: one fact table per topic (donations, supporters, programme outputs) joined to a small number of dimension tables (dates, funds, regions). Resist the temptation to model everything. The art is in what you leave out.

Step 4: Build the report pages

One page per section. Use Power BI's default visuals (bar, line, table, KPI card) rather than custom visuals from the marketplace. They render reliably across Teams and exports. Reserve colour for emphasis, not decoration: most charts should be neutral with one accent colour for the key series.

Step 5: Publish to a workspace and set the refresh schedule

Publish to a Power BI workspace, configure scheduled refresh (daily for fundraising, weekly for impact, monthly for finance), and grant viewer access to the people who need to see it. Embed the key pages in the relevant Teams channels so reports surface where conversations already happen.

Common charity-specific patterns

Funds and budgets

Always model restricted and unrestricted income separately. A combined view obscures the most important financial conversation a charity board has. Add a budget line to every income chart so variance is visible without arithmetic.

Year-on-year comparison

Add a 12-month rolling average to volatile income series. Single-month comparisons in fundraising are misleading; the rolling view smooths seasonal noise and exposes genuine trends.

Supporter cohort retention

Build a cohort retention chart showing what percentage of supporters acquired in a given month are still giving in months 3, 6, 12 and 24. This is the most underused chart in charity reporting and exposes attrition problems years before they show up in income.

Impact alongside income

Pair income figures with at least one programme output metric on the same dashboard. It keeps trustees focused on mission delivery alongside fundraising, and resists the drift toward income-only governance.

Governance and access

Workspace structure

One workspace for the main charity dashboard, with viewer access for the senior team and trustees, edit access for one or two named owners. Keep test reports in a separate workspace so trustees never see broken visuals.

Data sensitivity

Apply Microsoft Information Protection labels to sensitive datasets. Donor-level data should not be on a dashboard that anyone in the organisation can see; aggregate it or apply row-level security so users only see what their role allows.

Backup and version control

Export the PBIX file to source-controlled SharePoint or Git on a monthly cadence. Power BI does not version dashboards natively in the workspace, and a single accidental publish can overwrite hours of work.

A trustworthy monthly dashboard is worth more than a dozen heroic spreadsheets. The goal is not impressive analytics; it is the absence of arguments about what the numbers mean.

Resourcing realistically

Internal owner

One named person owns the dashboard end to end: data quality, refresh, layout changes, viewer access. Without that owner, dashboards rot fast.

External help where it earns its keep

Pay for help with the initial data model and the first three reports. Maintain in-house after that. The first build is the part that breaks if you try to learn on the job.

Time investment

Expect about ten focused days for the initial build with external help, then half a day a month for ongoing maintenance. That is genuinely the order of magnitude required.

The 30-day starter plan

1. Week 1: agree the three sections and six to nine charts the dashboard will contain. Document the source systems and identify the named internal owner.
1. Week 2: connect the CRM and finance system. Build the fundraising and finance pages.
1. Week 3: add supporter and impact pages. Configure refresh and viewer access.
1. Week 4: run the first monthly cycle with the dashboard live. Replace the equivalent spreadsheet reports formally.

Thirty days from kickoff to a board-ready dashboard. Most charities will recover the build cost within the first quarter just from the time fundraising and finance teams stop spending on bespoke monthly reports.

Further reading

Data Subject Access Requests: A Survival Guide for Charities | Choosing a Charity CRM in 2026 | Google Analytics 4 Setup for Charities (Without the Pain)