04 · Government & public sector
Public estates. Public scrutiny. Audit-ready.
Government and public-sector estates carry obligations most private operators do not - public reporting, freedom-of-information disclosure, procurement-framework rules, and political accountability. They also tend to span every asset class under one owner: schools, hospitals, council offices, courts, depots, defence - all of which have to report consistently against the same net-zero trajectory.
Wia is built for public-sector deployment. GDPR-by-default, EU-resident data, and audit lineage that survives external scrutiny. The retrofit-first model fits the maintenance-deferred reality of most public stock - installs happen around teaching, opening hours and political timing, not the other way around. And the same data layer publishes the open-data feeds the public expects.
GDPR-by-default
EU-resident data
Audit-ready
Full data lineage
Heritage-safe
Non-invasive retrofit
How public-sector rollout works
Three steps. Procurement-clean.
01
Onboard against your procurement reality
Whether your buyer goes via a national framework, a direct-award route, or a one-off statement of work, the call-off paperwork is shaped around what your team already files. Information-security and data-protection reviews are completed up front so they do not get re-litigated per deployment.
02
Install around operations
Schools during holidays, hospitals during planned maintenance windows, courts and council offices out of hours. Heritage and listed buildings handled with non-invasive retrofit. No teaching cancelled, no patients diverted.
03
Publish, report, defend
Net-zero pathway reports, grant-funding evidence packs, freedom-of-information responses and internal board updates all come from the same dataset. Lineage from every published number back to the meter that produced it, audit-defensible by default.
Inside Government & public sector
Everything Government & public sector brings, in one place.
Net Zero baselines per asset
Every asset gets a baseline year and a trajectory against the owner's Net Zero pathway. The dashboard shows the gap-to-target per asset and per sub-portfolio (academy trust, NHS trust, council directorate) so the team works on the assets that move the line.
Grant-funding evidence packs
Whether the application is to a net-zero public funding scheme, a local-authority climate fund, or an internal capital-allocation review, Wia produces the baseline reporting, kWh and tCO₂e abatement evidence, and project-level attribution the application needs. The evidence pack drops out of the same dataset that runs the operations.
Heritage-safe install
Many public assets are listed or heritage-protected. The retrofit hardware is non-invasive - clamps and pulse readers on the meter, no drilling into fabric, no visible install. Where a listed-building consent is required, the conversation is unusually short.
Operational-window aware
Schools install during half-term, hospitals during planned maintenance windows, courts out of session. Wia plans rollout against the calendar of the building, not the calendar of the project manager. Tenants, patients, staff - uninterrupted.
Critical-load awareness
In hospitals and defence sites, some loads cannot share infrastructure with general monitoring. Wia keeps critical-load circuits visible without touching them - read-only, isolated, with a separation that survives an information-security review.
Open-data publishing
Where the obligation exists (or the political case calls for it), Wia publishes anonymised, building-level consumption to a public open-data feed. The same data that runs the operations becomes the evidence the public sees.
Public-sector operators use Wia where audit-defensible data, procurement compliance and openness to public scrutiny are non-negotiable from day one.
Lineage
Every published number traces back to a meter.
Public reporting demands a chain of custody that private reporting often skips. Wia keeps that chain on by default: the meter reading, the conversion factor, the period, the tariff, the rollup logic - every step recorded and queryable. When a parliamentary question or FOI request arrives, the answer is one click, not a fortnight of spreadsheet archaeology.
Audit by design. Public scrutiny becomes routine, not an event.
FAQ
Common questions
How do you handle classified estates?
For defence and other classified estates, Wia deploys with critical loads kept entirely read-only and isolated from the rest of the platform. Data residency, security posture and physical install handling are agreed up front in the contract, not re-litigated per site.
What about heritage or listed buildings?
The retrofit is non-invasive by design - clamps and pulse readers on the meter, no drilling, no visible install. Where listed-building consent is required, our install spec is usually enough on its own. We've never had a heritage estate refuse install on the basis of physical impact.
Can we expose the data publicly?
Yes - anonymised, building-level consumption can be published to a public open-data feed via our API. Most public-sector owners use this to get ahead of FOI volume rather than wait for individual requests. The published data is the same data running the operations, so it survives scrutiny.