What a temperature mapping report should contain

The report closes the loop opened by the protocol. Its reader may be an auditor years later, so it has to stand alone.

Structure

• Study information: space, dates, protocol reference, personnel, loading condition.
• Dataset: loggers used, calibration evidence, sampling interval, total records, unit of temperature.
• Data preparation and quality: gaps, duplicates, sensor faults, exclusions and the reason for each.
• Configuration: acceptance limits, excursion definition, analysis criteria.
• Per-sensor statistics: minimum, maximum, mean and spread, with the study-wide summary.
• Hot and cold spots, with the sensors, locations and values that identify them.
• Excursions: sensor, start, end, duration, peak, and assessment.
• Limitations: what the study could not show (season, loading, events).
• Findings and recommendations, including monitoring locations.
• Review and approval with names, roles and dates; version history.

A draft report should be visibly marked as not approved until the review is complete. ValiTrac's mapping engine produces exactly this structure and keeps the draft flag until a reviewer signs off.

The section-by-section test

The report's reader may be an auditor several years later with no access to the people involved. Each section therefore has to answer a question that reader will have, and a section that does not answer one is padding.

Conclusions that are actually usable

The weakest part of most mapping reports is the conclusion, which says the study met its acceptance criteria and stops. That is a verdict, not a result. What the site needs is a statement it can act on: which positions are approved for product storage, which are excluded and how the exclusion is enforced, where the monitoring sensor must be placed or moved to, what the re-mapping interval is and why, and what limitations the reader should carry forward.

Every action needs an owner and a date. A report that recommends relocating the monitoring probe and is filed without anyone relocating it has documented a known, unresolved risk — which is materially worse than never having looked.

Draft until signed

• Mark the draft visibly as not approved, on every page, until the technical review is complete. A draft circulating without that mark will be quoted as final by someone.
• The reviewer is a competent person who did not perform the analysis, and the review record says what was checked, not just that it happened.
• Attach the evidence: raw data export, logger calibration certificates, photographs of sensor positions, the approved protocol.
• Version amendments properly. An amended report references the version it replaces, and the original is retained.

A useful final check: hand the report to a colleague who was not involved and ask them to state where the hot spot is and why the monitoring sensor sits where it does. If they cannot, the report is not yet standing alone.