How many sensors are needed for temperature mapping?

The honest answer is that the number of sensors is an output of the study design, not an input to it. Guidance documents give rules of thumb and worked examples, but they consistently ask the study to justify its sensor plan from the space itself.

What drives the count

• Volume and geometry — a small refrigerator and a high-bay warehouse are different problems.
• Known risk points — doors, loading bays, evaporators and air-handling outlets, windows and external walls, ceiling and floor levels, the geometric centre.
• Storage pattern — racking, pallet positions and the height at which product is actually kept.
• Acceptance limits — a tight 2–8 °C range leaves less room for gradients than a 15–25 °C room.
• Whether the study is empty, loaded, or both.

A defensible approach

Start from a three-dimensional grid that covers the storage volume at more than one height, then add sensors at each identified risk point. Document why each location was chosen. Use a sampling interval short enough to capture door-opening events and defrost cycles. Position sensors so they measure air where product sits rather than surfaces or airflow directly from a diffuser.

A common trap is to size the study to the number of loggers available. If the plan calls for more sensors than you own, run the study in phases or hire loggers — but keep a set of common reference positions across phases so the datasets can be compared.

What the analysis needs from the plan

Whatever the count, the analysis depends on clean metadata: a unique sensor identifier, a described location, and the sensor's calibration record. ValiTrac's pre-flight step checks that these are present before any statistics are computed, and it refuses to guess the temperature unit from the values.

These are starting points to argue from, not answers. A 12 m² cold room with two doors and two evaporators needs more than the row above; a simple one with good circulation may justify fewer. What makes any count defensible is the rationale recorded against each position, not the total.

What a larger count buys, and what it does not

More sensors reduce the chance that a real extreme sits between two of them, and they give the study margin — one logger failing mid-study costs a position rather than the conclusion. What they do not do is substitute for placement. Thirty sensors on a regular grid that misses the evaporator discharge and the loading door will produce a beautiful, even distribution and miss both extremes in the building.

The corollary is that the risk-point sensors are worth more than the grid sensors, one for one. If the budget is fixed, take sensors off the grid before taking them off the doors.

Phasing, when the plan exceeds the inventory

• Phasing is legitimate: map one zone, then the next. It is not the same as reducing the plan.
• Instrument a set of common reference positions in every phase. Without a shared anchor the phases cannot be compared or combined.
• Keep ambient conditions comparable across phases, or record the difference. Two phases a month apart in changing weather characterise two different buildings.
• State the phasing in the report. It is a limitation to be declared, not a flaw to be hidden.
• Hiring loggers is usually cheaper than a rejected study. Price both before deciding.

The trap to avoid is writing the plan around the number of loggers in the cupboard. The tell is a protocol whose sensor count exactly matches the equipment inventory, and assessors know to look for it.