All writing

Compliance· · 4 min read

Chain of custody for sensor data

Compliance data only counts if you can prove nobody changed it. What chain of custody means for sensor readings, where logbooks fail, and what to ask a vendor.

By Alessio Grespi, Founder & CEO

A compliance record is only worth something if you can prove nobody changed it. Chain of custody is the term for that proof: an unbroken account of where a piece of evidence came from, who handled it and whether it was altered.

It is a familiar idea for physical evidence and lab samples. This post applies it to sensor readings, and sets out what to look for when a monitoring system is going to produce the records you rely on.

Why it matters

Most of the time nobody looks at monitoring records. Then something goes wrong, and they become the most important documents you hold.

  • Audits and inspections. The record is how you show the control was working on the day in question, not only today.
  • Disputes. When a client, landlord or insurer questions what happened, the party with the more credible record usually wins the argument.
  • Enforcement. After an incident, investigators ask what you knew and when. A record that could have been edited afterwards answers neither.
  • Time. Records have to stay credible for years. For Legionella control, the Health and Safety Executive expects monitoring records to be kept for at least five years.

In each case the question is the same. It is not "do you have the data?" but "why should we believe it?"

Where paper and spreadsheets fail

Logbooks and spreadsheets record what someone wrote down. They cannot show that it happened.

  • Backfilling. A month of readings can be written in one sitting, and the page looks the same.
  • No proof of time. The date on an entry is whatever the writer put.
  • No proof of place. Nothing ties a reading to the outlet it claims to come from.
  • Silent edits. A spreadsheet cell can be changed without a trace.
  • Missing visits look like nothing. A gap in a logbook is easy to overlook, and easy to fill in later.

None of this assumes bad faith. Most gaps come from busy people and missed rounds. The weakness is that an honest record and a tidied-up one are indistinguishable.

The chain, link by link

Sensors remove the person from the act of recording. That helps only if every step between the probe and the report can be accounted for.

  1. Device identity. Each device has its own credential, so a reading can be tied to one physical unit at one known location.
  2. Time. The reading is stamped when it is taken, and again when it is received. A large gap between the two is visible.
  3. Transport. Readings travel over an encrypted, authenticated link, so they cannot be altered or injected on the way.
  4. Storage. Readings are written once and never overwritten. A correction is a new entry that points at the old one.
  5. Access. Every view, export and configuration change is logged against a named user.
  6. Gaps. Missing data is recorded as missing. A sensor that went offline for a day shows a day-long hole, not a smooth line.
  7. Reports. A report can be traced back to the raw readings it was built from.

Break any link and the chain is only as good as the weakest remaining one. A perfectly secure database fed by devices anyone could impersonate proves little.

It is also worth being clear about what the chain does not prove. It shows the reading is what the sensor measured. It does not show the sensor was in the right place or working correctly. Installation records and periodic checks cover that.

What to ask a vendor

  1. Can a stored reading be edited or deleted? By whom, and is that logged?
  2. How is each device identified, and what stops someone copying that identity?
  3. What happens to readings taken while a device is offline?
  4. How do gaps and device faults appear in a report?
  5. Can I export the raw readings as well as the summary?
  6. How long is data kept, and what happens to it if I leave?
  7. Who at your company can access my data, and is their access logged?

A vendor who has thought about this will answer quickly. Vague answers to the first two questions are the ones to worry about.

Frequently asked questions

What is chain of custody for sensor data? A record of where each reading came from, when it was taken, how it travelled and who has accessed it, kept in a way that shows whether anything was changed.

What does tamper-evident mean? That any change leaves a visible trace. It does not mean change is impossible, only that it cannot happen unnoticed.

Is sensor data accepted as a compliance record? Records can be kept electronically. What matters is that they are complete, available and credible. Check the specifics with your own auditor or regulator.

Does this need blockchain? No. Write-once storage and a proper access log do the job with ordinary, well-understood technology.

Records you can stand behind

Paqett designs its monitoring around these principles, so the data your business relies on holds up when someone asks why they should believe it. Talk to us about what you need to prove.

Sources

Keep reading

Water hygiene· · 5 min read

Manual vs automated Legionella monitoring

Monthly thermometer rounds or sensors? How manual and automated Legionella temperature monitoring compare on cost, coverage, records and risk, and when each makes sense.

Engineering· · 9 min read

Why per-device IoT pricing punishes fleets

Per-device and per-message IoT pricing scales with your success, not with what your fleet costs to host. A worked example at 1,000 and 50,000 devices, and the alternative.

Water hygiene· · 2 min read

Your rounds, plus the 29 days in between

A monthly temperature round is one reading per outlet. This is what the rest of the month looks like when a probe stays behind.

Engineering· · 5 min read

What chip for what kind of device

ESP32, Nordic nRF or RAK3172: which chip suits which kind of device, and what each one costs you.

Get new posts by email

One email when we publish. Nothing else.

Or talk to us about a deployment: water hygiene, white-label or built to spec.