Building Evidence

The fix costs less than the report telling you to fix it.

Continuous compliance for the buildings you’re already responsible for. Sensors that watch the standards. Evidence that proves the case.

The Evidence

Same pattern. Every building type.

Over the years we’ve used IoT to monitor offices, heritage estates, warehouses, hospitals, cold storage, care homes, social housing, hospitality venues, casinos, and schools. The pattern doesn’t care what the building is for: heating systems run when rooms are empty, cooling stacks chill space nobody uses, ventilation runs against schedules that haven’t been right in years. The walls and the calendar disagree. The sensors caught it every time.

What we found is that monitoring isn’t enough. Better data, no extra hands to act on it. We were loading customers with more problems than they could fix.

Planetic is the result of that experience.

Sensor

Configured by the room it's in

A bedroom isn't a kitchen isn't a plant room. Each sensor knows where it lives — and what 'good' means there.

Standard

Picked by the building type

School → BB101. Care home → HTM. Social housing → Awaab's Law. The right rulebook is applied automatically.

Engine

Orchestrates end-to-end

Smart rules, AI judgement, n8n flows. Not another dashboard — the task is given, sent, chased, closed.

In most cases this isn’t a cost. It’s using the resource you needed anyway. No overheating. No drive-by maintenance. First-time fix stops being marketing bullshit bingo.

10Building types
24/7Continuous data
1Pattern, every time
Where the Money Goes

Three things change when you measure.

Measurement is the cheap bit. The savings come from what the building does with the readings.

Each radiator listens to its room

Smart valves (eTRVs) zone the building at the room level. Heat the desk. Skip the empty cupboard. No new boiler, no rewiring — the radiators do the thinking.

eTRVs · per-room zoning

The boiler fires to occupancy

Not to a 1970s timeclock. Weekend mornings stay off. Half-term stops costing £400 a day. Smart scheduling drops the curve to match when people actually arrive.

Boiler control · BMS integration

Stuck radiators get caught in hours

Drifting set-points, jammed valves, dead sensors — flagged the day they happen, not at month-end billing. The waste stops before the invoice notices.

Anomaly alerts · continuous QA
The Three Regulations

One platform. Three regulations. One audit trail.

Most platforms cover one of these. We cover all three because most of our buyers carry all three on their statutory register.

Legionella

Continuous outlet-by-outlet temperature evidence. Replace clipboard log sheets with a live audit trail. ACOP L8-aligned.

L8 · HSG274

Damp & Mould

Continuous humidity, temperature and dew-point evidence per dwelling. Catch the conditions before the complaint arrives.

Awaab's Law · HHSRS

Excess Cold & Heat

Continuous internal temperature evidence per occupied space. Schools, social housing, healthcare estates — under one bar.

HHSRS Phase 2 · BB101 · CIBSE TM52
How It Works

Sensor to evidence, in six stages.

Same sensor data. The room decides what ‘good’ looks like. The system decides what to do about it. The people see exactly what they need.

01

Sense

Sensors in every room — temperature, CO₂, humidity, occupancy, damp, energy.

Field layer
02

Carry

LoRaWAN gateways and LNS — kilometres of range, a decade of battery.

Transport
03

Ingest

Cloud webhook plus payload decoders. Raw bytes become structured readings.

Pipeline
04

Context

Standards plus zone type plus customer dial → RAG. The reading carries the rulebook.

The differentiator
05

Orchestration

Tasks created, sent, chased. Rules today, AI judgement next. Every action traceable to a line of config.

Decision engine
06

Action

Tasks to your workforce — email, M365, your CAFM, your helpdesk. Dashboards for the people who want them. Evidence packs for the auditor.

Action layer
Standards · zone types · RAG
Rules · cron · n8n · agents next
Tasks · alerts · dashboards · evidence

The room decides what ‘good’ looks like. The system decides what to do. The people see exactly what they need.

Beyond The Redline

Not another dashboard.

A reading is the beginning, not the end. When a room crosses the red line, we create the task, we send it where your team already works, and we don’t stop chasing until the fix is signed off. The audit trail builds itself.

Context

The room knows the rule.

Every sensor is tagged to its room type and the standards that apply to it. A classroom is judged against BB101. A ward against HTM. A dwelling against Awaab's Law. No-one configures a threshold by hand.

Task

The task writes itself.

A reading is the beginning, not the end. When the room crosses a red line, we don't just colour a chart amber — we create the task, with the standard, the location, the suggested fix, and the role responsible. Typed in, not faxed over.

Loop

The loop closes.

Industry calls it SLA-driven escalation. We call it nagging. If the assignee doesn't action the task in the window, it climbs. To the supervisor. To the manager. To the duty board. Until someone closes the loop — and the close is logged with evidence.

Where it lands

Your stack stays. We push out. There are hundreds of facilities management and ticketing tools — most platforms make you pick one. We don’t care which one is yours.

Email / SMSthe always-on default
Microsoft 365Outlook tasks · Teams
Your CAFMPinnacle · Concept · MRI · Verisae · whatever you run
Your helpdeskServiceNow · FixFlo · Jira · ticketing of choice
Your team chatSlack · Teams · Webhook
Your own APIif it's documented, we connect

Sensors. Standards. Tasks. The full chain — and the human at the end of it can’t pretend the email got lost.

Next Step

Spend the next pound on the fix.

Funding shouldn’t go to another consultant. Start with sensors. End with evidence.