We've built dashboards for businesses. Community programmes need the same visibility at a bigger scale: one view of a town's placements, businesses, and outcomes — with privacy built in from the start.
A business dashboard answers one owner's question: how is my business doing? Community programmes ask a harder version: how is our town doing? When a sponsor funds a hundred placements across forty local businesses, with training, stipends, and development support flowing alongside, the honest answer lives in a dozen scattered spreadsheets — if it lives anywhere at all. The same dashboard thinking that transformed SME visibility applies here, one scale up. Here's what it takes. ## One Programme, Many Lenses The defining feature of a community-scale dashboard is that different participants need different views of the same truth. The **sponsor** needs programme health: enrolment, attendance, stipend reconciliation, milestones — the evidence file, live. The **programme team** needs operations: which placements are wobbling, which hosts need visits, what's due this week. **Hosts** need their own slice: their placements, their records, their reporting done. And the **community's leadership** — municipal, traditional, or civic — reasonably asks for the town view: how many young people in programmes, how many local businesses participating, what's changing. One data spine, several windows onto it. That's the architecture, and getting it right is the difference between a reporting tool and a community asset. > A spreadsheet tells the programme manager what happened. A shared dashboard tells a whole town what's working — and that changes how a town behaves. ## What Changes When a Town Can See Itself Visibility does quiet work. Hosts who can see their own records stay current, because nobody wants to be the gap on the chart. Sponsors extend programmes they can see working — the difference between renewing on anecdotes and renewing on evidence is real money. Local businesses join programmes their neighbours are visibly benefiting from. And the community's story — youth placed, businesses grown, stipends circulating locally — becomes tellable, to funders, to government, to the town itself. Measurement, done publicly and honestly, is a development intervention in its own right. Honesty matters here: dashboards must show the misses too. A community view that only celebrates is marketing, and everyone can smell it. Drop-offs, stalled placements, and gaps belong on the screen — that's what makes the successes credible. ## The Privacy Line A town-scale dashboard involves personal information at scale — young people's participation, attendance, sometimes circumstances. The design rule is aggregation by audience: individual-level data visible only to those with a genuine operational need (the programme team, the specific host); everyone else — sponsors included, community views especially — sees aggregates that can't be walked back to a person. "How many placements are on track" is a community statistic. "Whether Thabo attended Tuesday" is not. POPIA requires this; decency required it first. Build it into the architecture, not the apology. ## Where the Data Actually Comes From A dashboard is only the visible end of a capture chain, and community-scale projects live or die on that chain's weakest links. The realistic sources: programme administration systems (enrolment, stipends, contracts), simple digital capture at the point of activity — attendance logged on a phone at the host site beats registers photographed at month-end — host self-service for their own records, and periodic verification visits that keep the self-reported honest. What doesn't work is the fantasy version: expecting thirty small businesses to dutifully type into spreadsheets, or parachuting in an enterprise system that assumes connectivity and habits a town doesn't have. Design for the real environment: capture that works offline and syncs later, interfaces that assume a phone rather than a desktop, and as much automation of the boring fields as possible — dates, locations, and identities pre-filled so a host confirms rather than types. Every minute of capture friction you remove shows up later as data you can actually trust. ## Starting Smaller Than You Think The trap in community measurement is trying to dashboard everything from day one. The versions that work start with the few numbers the programme already captures reliably — enrolment, attendance, stipends paid, placements active — displayed cleanly, updated on a real rhythm, and grown as capture matures. A modest dashboard that's always current beats an ambitious one that's always apologising. ## Where Bighearts Online Fits Bighearts Online builds dashboard and tracking systems for programmes across our network — the same infrastructure thinking that powers the Village Dashboard, applied from single businesses up to community-scale projects. If you're designing a programme that a sponsor, a town, and forty hosts will all need to see clearly — and differently — that's an architecture conversation worth having early, and we're glad to have it.