On this page
Readings cannot be edited, including by us.
The strength of a temperature record is not how it looks. It is whether anyone could have changed it after the fact.
In TempGuard they cannot. Temperature readings are written once and the database itself refuses to update or delete them. This is not a rule enforced by the app, which could be bypassed by a bug or a stray query. The permission to modify a stored reading does not exist for the application at all, so there is no path by which a reading changes after it lands, for any account, including ours.
Around that sits everything an inspector actually asks about:
- Every reading
- Continuous history per device, each reading carrying a server-side timestamp rather than one supplied by the device.
- Every excursion
- When a reading leaves its configured range, all four alert channels go out together: phone call, WhatsApp, email and mobile push. No staged cascade, no waiting.
- Who responded
- Acknowledgement and resolution are attributed to the person who performed them, with the time they did it.
- Who did not
- An alert nobody acknowledges within 60 minutes escalates, and the silence is recorded as an event in its own right.
- Gaps in the data
- A device that stops reporting is flagged after 24 hours. A hole in the record is treated as something that happened, not as nothing.
- Setting changes
- Thresholds, devices and user access changes are logged separately, showing the person, the field, the previous value and the new one.
- Calibration status
- Each device carries a calibration date and expiry, and the register flags anything expiring or overdue before an auditor finds it.
One export, for one date range, in one go.
Most temperature systems can show you a graph. The question at audit time is what you actually hand over, and how long it takes to produce.
TempGuard generates an audit pack for whatever period you are asked about: readings, alerts and the change log as CSV, plus a calibration register and a summary as PDF. It is one action, and the output is the same whether the range is a week or a year.
The worst time to find out what your records look like is during an inspection. If you want to see a sample pack for your own sector before committing to anything, ask us for one.
The rules are not the same for everyone.
What an authority asks of you depends on what you store and who licenses you. Rather than summarise all of it here, each industry page quotes the requirements that apply to it, from the source documents, with links so you can read them yourself.
- Pharmacies, clinics & hospitals
- Ministry of Health storage and distribution guidance for medicines.
- Food & beverage
- Municipal food control: Dubai, Sharjah and Abu Dhabi each publish their own.
- Cold storage
- Whichever applies to what is on the rack, and often both at once.
- Logistics & supply chain
- Food transport rules, or the federal regime for medical products.
- Research & laboratories
- Your accreditation and your own protocols rather than a sector regulator.
- Server rooms & data centres
- Your uptime commitments. No temperature regulator applies.
If you operate across more than one of these, the platform does not change. The thresholds, the recipients and the reports do.
If you need something specific that we do not produce today, tell us and we will scope it.
Continuous monitoring and alerting.
That is the category TempGuard is in, and it is worth being precise about what it means: the always-on layer that watches the points that matter, keeps the record, and tells a named person within seconds when something drifts, whether or not anyone is on site.
It runs every minute of every day rather than at a scheduled visit, and its output is a continuous history plus an alert trail rather than a report on a date. If you need something outside that, tell us what you are trying to prove and we will tell you honestly whether we are the right fit.