Overview#
When a local authority transparency officer is asked to publish this quarter's service performance figures, the answer should be a published dataset within the hour, not a three-week data-warehouse project. Service Reporting and Open Data Analytics turns the operational data a council already holds into statutory open data and executive insight, with no secondary extract-transform-load pipeline to build or maintain.
The capability generates, schedules, and exports service performance reports for municipal and public-sector organisations directly from live request records. The same underlying figures power a private executive dashboard for managers and an unauthenticated open-data endpoint for citizen-facing portals, so the numbers a director sees in the morning are the numbers residents can read on the public site that afternoon. Reports cover service level compliance, citizen satisfaction, service demand, category breakdown, geographic heatmaps, budget allocation, and trend analysis, with multilingual budget labels for communities served in more than one language.
Key Features#
-
Multiple report types: Produce service level compliance, citizen satisfaction, service demand, category breakdown, geographic heatmap, budget allocation, trend analysis, and fully custom reports from a single reporting domain, each parameterised by date range, department, and service category.
-
Executive dashboard: A real-time management view aggregates open request counts, requests resolved this month, service level breaches, average satisfaction score, service level compliance rate, top service categories, channel breakdown, and historical trend data, all drawn from pre-aggregated daily summaries for fast response.
-
Unauthenticated open-data publishing: A public endpoint serves selected reports and a per-fiscal-year budget overview, including total budgeted, total spent, and per-department utilisation rates, to citizen portals with no login, no API key, and no exposure of internal records.
-
Selective publication controls: An explicit public flag on each report and budget item governs exactly what reaches the open-data endpoint, so transparency teams publish statutory figures while keeping operational detail private by default.
-
Daily service summaries: Operational request records are rolled up by department, service category, and channel into daily summaries capturing total received, resolved, open, and breached counts, plus average and 90th-percentile resolution times and average satisfaction scores.
-
On-demand and scheduled runs: Any report can run immediately or on a recurring schedule of daily, weekly, monthly, quarterly, or annual cadence, removing the manual effort behind routine performance and compliance reporting.
-
Point-in-time snapshots: Every report run stores a historical snapshot, preserving an auditable record of what each figure was on the day it was published, which supports comparison over time and defensible transparency disclosures.
-
Multilingual budget labels: Budget items carry locale-specific labels, allowing the same fiscal data to be presented in each community language on public portals without duplicating the underlying figures.
Use Cases#
Local Authority Transparency Reporting#
A council transparency office publishes its annual budget overview and quarterly service performance to a public portal. The budget overview endpoint returns total budgeted, total spent, and department utilisation rates per fiscal year, satisfying statutory open-data and local authority performance reporting obligations straight from operational data.
Municipal CRM Operations Management#
Service managers open the executive dashboard each morning to see open request volumes, requests resolved this month, service level breaches, and average satisfaction, then drill into top categories and channel breakdown to direct resources where demand and breach risk are highest.
Scheduled Compliance and Satisfaction Reporting#
Performance teams configure recurring service level compliance and citizen satisfaction reports on a weekly or monthly cadence. Each run is generated automatically, exported, and snapshotted, replacing the manual cycle of pulling figures and assembling spreadsheets.
Citizen-Facing Open Data Portals#
Developers building a resident portal read published reports and the budget overview from the public endpoint without handling credentials, presenting service statistics and spending transparency to citizens with multilingual budget labels rendered in the reader's language.
Geographic and Demand Analysis#
Planning teams use geographic heatmap and service demand reports to understand where requests cluster and how demand shifts seasonally, informing depot placement, staffing, and capital planning decisions.
Integration#
The capability is exposed as a typed GraphQL API for authenticated operations, giving developers one reporting interface to drive executive dashboards, list and create reports, schedule recurring runs, manage budget items, and read daily summaries and historical snapshots. Authentication uses the platform's OAuth2 and JWT model with per-organisation isolation, so every authenticated read and write is scoped to the caller's tenant.
The public open-data path is served without authentication for citizen portals, returning only records marked for publication and the aggregated budget overview. Reports export as JSON for downstream applications or CSV for spreadsheets and open-data catalogues, with exported files referenced by a stable download path. Because reports are built from the same operational request and budget records that power day-to-day operations, customers plug in their existing municipal CRM data and obtain transparency outputs immediately, with no separate reporting database or extract-transform-load project to fund and maintain.
Open Standards#
-
GraphQL (June 2018 specification): The reporting domain publishes its read and write operations as a typed GraphQL API, letting a console or portal fetch dashboard metrics, report lists, budgets, and snapshots in a single typed request rather than across many bespoke endpoints.
-
JSON (RFC 8259): Report results, dashboard payloads, and the open-data export format are encoded as standard JSON, so any client or open-data catalogue can consume them with no custom parser.
-
CSV (RFC 4180): Reports export to RFC 4180 comma-separated values for direct use in spreadsheets and open-data tooling, with field values sanitised to keep exported files safe to open.
-
ISO 8601: Report date ranges, daily summary dates, and snapshot dates use ISO 8601 calendar date formatting, giving unambiguous, locale-independent dates across reports and public datasets.
-
ISO 4217: Budget items and the budget overview express monetary amounts as decimal currency values aligned to ISO 4217 currency representation, suitable for fiscal transparency publishing.
-
ISO 639-1: Locale labels on budget items key multilingual public-portal text by ISO 639-1 language codes, so the same fiscal figure renders in each community language without duplicate records.
-
W3C DCAT: The public open-data endpoint exposes published reports and budget overviews as discrete datasets, mapping cleanly onto the W3C Data Catalog Vocabulary used by government open-data portals to describe and list datasets.
-
W3C CSV on the Web (CSVW): CSV exports follow the tabular structure W3C CSVW describes for publishing tabular data on the web, easing annotation and ingestion by open-data catalogues.
-
OAuth2 and JSON Web Token (RFC 6749 / RFC 7519): Authenticated reporting and budget management operations are authorised with OAuth2 bearer tokens carried as JSON Web Tokens, scoping every privileged read and write to the caller's organisation.
Security and Compliance#
Authenticated reporting operations enforce per-organisation isolation and ontology-level access control, so report, dashboard, summary, and budget data are confined to the owning tenant. Open-data publishing is deliberately opt-in: only records explicitly flagged as public and the aggregated budget overview are reachable without authentication, and the aggregated overview exposes departmental totals and utilisation rates rather than individual operational records. CSV exports are value-sanitised to prevent formula injection when opened in spreadsheet applications. Point-in-time snapshots provide an auditable history of every published figure, supporting transparency obligations including open-data publication and local authority performance reporting duties under applicable data protection law.
Last Reviewed: 2026-05-26 Last Updated: 2026-05-26