Reporting & Dashboards

Most businesses do not lack data; they lack reporting. The numbers exist — in the accounting system, in job files, in someone's spreadsheet — but assembling them into a picture costs hours, the picture is stale by the time it arrives, and nobody fully trusts it. Our reporting practice builds the opposite: a small set of measures that matter, collected reliably, presented clearly, and delivered on a rhythm you can set your calendar by.

Our reporting philosophy

Three beliefs shape every reporting engagement we run. First, fewer measures, better chosen — a page of twelve numbers that drive decisions beats forty charts that decorate one. Second, reporting must reconcile — operational numbers that disagree with the financials get ignored within a month, so we build the reconciliation in from day one. Third, reporting is a product with users — we design it around who reads it and what decision they make with it: you, your bank, your board, or a funding body.

What a reporting engagement looks like

1. Decision inventory. We list the recurring decisions you make — pricing, hiring, purchasing, capacity — and identify the measures that genuinely inform each one.
2. Data audit. We trace each measure to its source, fix the definitions, and eliminate the double-counting and version conflicts that make current numbers unreliable.
3. Build. We construct the collection pipeline and the dashboard or pack — automated wherever a system can feed it, with a simple manual routine where it cannot.
4. Calibrate. We run the reporting alongside your old process for a cycle, reconcile the numbers, adjust, and then switch over. Trust is earned by comparison, not assertion.

Dashboards for operations, packs for governance

We build two distinct artefacts. Operational dashboards are live views of the measures your team steers by — jobs in progress, response times, stock cover, utilisation — designed for frequent, glanceable use. Governance packs are the monthly or quarterly documents for banks, boards and funding bodies: consistent, reconciled, with commentary that explains variances honestly. Most clients need both; the discipline is keeping the two connected, so the pack never contradicts the dashboard.

Data quality: the unglamorous half

Reliable reporting stands on unglamorous work: agreed definitions (what counts as a "job" or a "lead"), validation at the point of entry, a named owner for each measure, and a short monthly checklist that catches drift before it compounds. We build all of it, document it, and hand it over with a maintenance routine your team can run. Reports that survive are reports whose plumbing is understood.

Security and confidentiality

Reporting systems concentrate your most sensitive commercial information, so we treat their security as part of the build: access limited by role, credentials held in a documented register, backups tested rather than assumed, and — for community and health sector clients — handling practices aligned with your funding and privacy obligations. Your data stays in your tenancy and your control.

Common reporting problems we are asked to fix

The same handful of problems account for most of the reporting engagements we take on, and it is worth naming them because readers usually recognise their own. The shadow ledger: a parallel spreadsheet that "corrects" the system's figures, so two versions of the truth compete monthly. The December problem: reporting that works in quiet months and collapses when the business is busiest — precisely when the numbers matter. The mystery variance: a number that changes every month for reasons nobody can explain, so the report carries a permanent footnote of doubt. The funder special: a report assembled from scratch for one audience that never reconciles with anything else. Each has a known fix — agreed definitions, automated feeds, a reconciliation routine, a single core data set — and none requires heroic effort once the foundation is built.

What reporting costs, and what it returns

Because this page is read by people with budgets, some candour about economics. A scoped reporting build for a typical SME — one core data set, a dashboard for the team, a monthly pack for governance — is a modest, fixed-price engagement, and most of the effort goes into the unglamorous plumbing: definitions, data quality, the reconciliation routine. The return shows up in three ways: hours returned to the team each month (often the largest line, and the easiest to measure); decisions made earlier and on better evidence, which rarely get measured but are usually worth the most; and the quiet retirement of the anxiety that accompanies every "can you send me something by Friday?" from a bank or funder. We measure the first at the start of every engagement, and we would rather under-promise the other two than inflate them.

Frequently asked questions