Section

Temperature Monitoring

Temperature monitoring turns a shipment into a record. This section looks at how data loggers and monitoring workflows are specified, what the resulting data can and cannot show, and which documents belong with the data, such as calibration certificates and configuration records.

Monitoring is one part of an evidence chain, not a product category. The guides separate the decisions that belong to the equipment (sensor, interval, memory, interface) from those that belong to the process (placement, download, review, retention), and they point back to the source documents a team should read for its own product and market.

Illustrative image of a temperature data logger placed inside a shipment
Illustrative image

How the monitoring guides fit together

Reading order

The monitoring guides split into two pairs. The first covers the device and the workflow, the second the evidence around them. Begin with how to specify a cold chain temperature data logger, which defines the attributes you will need to state for any purchase: range, accuracy, logging interval, export method and the documents to request. Next, read real-time tracking versus downloadable loggers to decide how quickly data must reach you and what you can do when it arrives. Then turn to the paperwork. Reading a sensor calibration certificate shows what a certificate should tell you before you accept a logger. Finally, temperature mapping versus shipment monitoring keeps two different questions from being answered with the wrong evidence.

Teams that already own loggers can start with the certificate guide and the mapping comparison, then return to the specification guide when it is time to replace equipment.

What to have on paper first

Each decision is easier with a short written starting point, listed here.

  • Before specifying a logger, write down the product temperature range from the product documentation, the longest expected journey, and who will download or review the data.
  • Before choosing between real-time and offline workflows, list the lanes, the handover points and who would act on an alarm, and how fast.
  • Before reviewing a certificate, have your own accuracy and range requirement ready so you can compare it against what the document states.
  • Before commissioning mapping or monitoring, state which question you are asking: how a space behaves, or what one shipment experienced.

None of the guides states a safe range for any product. That comes from your product documentation and quality team.

Handing over to the neighbouring sections

Monitoring depends on the packaging decisions that come before it. Logger size, probe placement and interval all follow from the box and refrigerant you picked, so if those are open, read selecting insulated shippers first. Going the other way, the logger has to be started, placed and recorded during assembly, which is where the packout station guide picks up. Later, when you write requirements for a purchase, the equipment RFQ checklist is the place to carry the logger and data requirements into a request for quotation.

Mistakes these guides help avoid

  • Specifying a logger by headline accuracy without checking the range, interval and memory against the actual journey.
  • Choosing real-time tracking when the lane has no reliable connectivity, or choosing offline loggers when nobody can act on the data in time.
  • Filing a calibration certificate without checking device identity, dates, reference traceability and stated results.
  • Treating a mapping study of a cold room as proof of what happened in transit, or the reverse.
  • Leaving data responsibility vague, so that nobody owns download, review and retention.

Together the guides treat monitoring as an evidence chain. A logger produces a record, a certificate supports trust in the sensor, and mapping describes the environment. Each answers a different question. The guides do not rank devices or vendors, and they report no test performed by this publication.

All guides

Temperature Monitoring guides