Overnight Record Gap: Why Auditors Flag It (Case Teardown)
8 min read
An auditor found 10 hours of missing temperature records every night. Here is what happened and how the business fixed it in a week.
The BRCGS 2024–25 Annual Report confirms that certification bodies identified an average of 4.86 non-conformities per audit across all Food Safety Standard Issue 9 assessments, with record control under Clause 3.3.1 ranking as the ninth most common finding globally. That statistic sounds manageable until you watch a single documentation gap cascade into three linked NCs during a live assessment, which is exactly what happened at a chilled distribution facility preparing for its BRCGS recertification in late 2025.
This case teardown reconstructs the scenario: a site with strong hygiene scores and well-maintained infrastructure that lost its audit-ready status because the overnight shift relied on manual temperature logs, and one log went missing. The cascade from Clause 3.3.1 (record control) into Clause 2.11 (corrective action) and Clause 3.4 (internal audit) illustrates why the BRCGS record-control NC is not a standalone finding but a stress fracture that exposes weaknesses across the entire management system.
Read this alongside the Cold Chain Compliance pillar, the BRCGS Audit Non-Conformities analysis, and the Food Safety Temperature Monitoring guide so the corrective actions described here map to the same evidence spine your day-to-day compliance documentation already uses.
In this guide
Why this matters to an EHO
EHOs and BRCGS assessors test the same underlying question: can you produce complete, timestamped, verifiable temperature records on demand? A site that passes its hygiene walk with flying colours but cannot produce the overnight temperature log for Tuesday 14 January sends a clear signal: the management system has gaps, and those gaps exist during the hours when nobody is watching. That is exactly the pattern that triggers an improvement notice from an EHO or a major NC from a BRCGS assessor.
The Cold Chain Federation's compliance guidance reinforces this: operators must demonstrate that temperature monitoring covers the full 24-hour cycle, including overnight and weekend periods when staffing is reduced. A missing log is not a minor administrative oversight: it is evidence that the HACCP monitoring procedure failed to detect a potential loss of control at a Critical Control Point, which is the definition of a system failure under both BRCGS Issue 9 and the Food Hygiene (England) Regulations 2013.
Implementation checklist
- Audit overnight temperature records weekly and flag any gap longer than 30 minutes as a CAPA item before an assessor finds it.
- Train night shift staff on the legal weight of temperature records — they are not admin tasks, they are Section 21 due diligence evidence.
- Cache the last 72 hours of continuous readings offline so unannounced visits during overnight hours never encounter a documentation void.
- Cross-reference overnight monitoring evidence with the Cold Chain Federation's 24-hour coverage guidance to demonstrate compliance awareness.
- Present overnight record density (288 automated readings vs 2 manual entries per day) at every BRCGS opening meeting and EHO handoff.
The scenario: a routine BRCGS recertification audit
The facility operated four temperature-controlled zones: a 2–4 °C high-care chiller, a 0–5 °C ambient cold store, a -22 °C blast freezer, and a 5–8 °C dispatch dock. Day shift staff recorded SC2 temperatures at 07:00 and 15:00. Night shift: a two-person crew running 22:00 to 06:00: was supposed to log readings at 23:00 and 03:00 on a paper form clipped to the chiller door. The facility had passed its previous three BRCGS audits with an AA grade.
During the recertification assessment, the auditor sampled temperature records for the previous 28 days. Twenty-seven days had four manual entries each. Day 14: a Tuesday night in mid-January: had only two: the 07:00 and 15:00 day-shift readings. The 23:00 and 03:00 night entries were blank. The paper form was on the clipboard, but the temperature fields were empty. The night shift supervisor had been redeployed to cover a stock-receiving backlog and nobody else completed the log.
Implementation checklist
- Never rely on a single person to complete overnight temperature records — the task must be assigned to a role, not a name.
- Implement automated monitoring that records independently of staff presence so redeployment decisions cannot create documentation gaps.
- Check the previous 28 days of records weekly (matching the BRCGS assessor sampling window) to catch gaps before the audit.
- Keep a contingency recording procedure for nights when staffing changes — if the primary recorder is redeployed, who completes the log?
- Document staffing changes in the SFBB diary so assessors see that management was aware of the redeployment and had a mitigation plan.
The cascade: three non-conformities from one missing log
The first NC was straightforward. Clause 3.3.1 requires sites to 'maintain genuine records to demonstrate the effective control of product safety, legality and quality.' A blank overnight temperature log for a high-care chiller is a textbook record-control failure. The assessor wrote: 'Temperature monitoring records for Zone 1 (high-care chiller, 2–4 °C) were incomplete for the night shift of 14 January. No readings were recorded between 15:00 on 14 January and 07:00 on 15 January: a 16-hour gap in CCP monitoring.'
The second NC followed within minutes. Clause 2.11 requires root cause analysis and corrective action for non-conformities. The assessor asked: 'What corrective action was taken when the gap was identified?' The site QA manager had not identified the gap before the audit. No corrective action existed, no root cause analysis had been performed, and no preventive measure had been implemented to stop it recurring. The assessor noted: 'No evidence of corrective action or root cause analysis for the 16-hour monitoring gap identified under 3.3.1.'
The third NC targeted the internal audit programme. Clause 3.4 requires a scheduled programme of internal audits covering HACCP prerequisite programmes and record completeness. If the site's own internal audits had sampled overnight records in the 28 days before the assessment, they would have found the gap. The assessor asked to see the last three internal audit reports covering temperature monitoring. None of them had specifically sampled overnight records. The assessor wrote: 'Internal audit programme does not include sampling of overnight/out-of-hours temperature monitoring records, which contributed to the 3.3.1 finding remaining undetected.'
Implementation checklist
- Include overnight and weekend record sampling in every internal audit cycle so gaps are found internally before external assessors arrive.
- Treat any monitoring gap longer than 30 minutes as a CAPA item requiring root cause analysis, corrective action, and verification — do not wait for the audit.
- Log the CAPA against the same record ID system your Daily Log uses so the assessor sees a coherent evidence chain.
- Set automated alerts for any 60-minute period without a recorded reading so gaps trigger immediate investigation.
- Brief the internal audit team on the cascade risk: one record-control gap can generate NCs across Clauses 3.3.1, 2.11, and 3.4 simultaneously.
The fix: continuous automated monitoring eliminates the root cause
The root cause was not a lazy night shift worker: it was a system that depended on human memory to generate legally critical evidence. When the supervisor was redeployed, the system failed silently. No alert was generated, no escalation was triggered, and the gap was invisible until an external assessor sampled the records four weeks later.
Automated continuous monitoring eliminates this root cause entirely. A sensor firing every five minutes generates 288 readings per day per zone: including the 16 overnight hours that manual logs consistently miss. Shield tier captures those readings with hash-chained record IDs, UKAS-traceable calibration certificates, and tamper-evident storage. The readings exist independently of whether anyone is standing in front of the chiller. If the January night shift had been monitored by a sensor instead of a clipboard, the assessor would have seen 192 overnight readings instead of zero, and Clause 3.3.1 would never have been raised.
Command tier extends the fix into the corrective action and internal audit layers. AUTO-DETECTED SFBB diary entries flag every excursion and every gap without waiting for a human to notice. Excursion Reports auto-generate the five-step CAPA structure (Trigger → Impact → Corrective Action → Verification → Prevention) that Clause 2.11 requires. And the Management Confidence Statement surfaces open items to leadership daily, which means the internal audit programme under Clause 3.4 is supplemented by continuous governance: not dependent on a quarterly sampling exercise that may or may not include overnight records.
Implementation checklist
- Deploy sensors in every temperature-controlled zone so monitoring is independent of staffing levels, shift patterns, and redeployment decisions.
- Set connectivity alerts so any sensor that goes offline for more than 15 minutes triggers an immediate investigation — not a silent gap.
- Configure AUTO-DETECTED diary entries for every overnight excursion and every monitoring gap so the SFBB pack captures events as they happen.
- Use the Excursion Register's five-step CAPA structure for every gap event: what triggered it, what was the impact on product safety, what corrective action was taken, how was it verified, and what prevents recurrence.
- Present the avoided-NC count (zero record-control findings since deployment) at every BRCGS opening meeting as evidence of continuous improvement.
Tier the lesson: Shield prevents Clause 3.3.1, Command prevents the cascade
Shield (£29/month) eliminates the overnight record gap that generated the first NC. With 288 immutable readings per day, Clause 3.3.1 record completeness is a structural guarantee rather than a staffing gamble. The hash-chained architecture means every reading carries a deterministic record ID, calibration certificate reference, and timestamp that no manual process can match.
Command (£59/month) prevents the cascade into Clauses 2.11 and 3.4. AUTO-DETECTED diary entries surface gaps in real time, Excursion Reports auto-generate CAPA records with root cause analysis, and the Management Confidence Statement ensures leadership reviews overnight evidence before the next shift starts. The assessor who sampled Day 14 would have found 192 sensor readings, an automated diary acknowledgement, and a management sign-off: instead of a blank clipboard. At the 4.86-NC average, eliminating three findings from a single root cause drops the site comfortably below the global benchmark. Print the tier ladder on every pre-audit briefing with deployment dates, avoided NCs, and the record IDs that prove each control is live.
Implementation checklist
- Map Shield to Clause 3.3.1 prevention and Command to Clauses 2.11 and 3.4 prevention on your pre-audit briefing sheet.
- Quantify the three avoided NCs as the ROI case: each NC closure requires staff time, documentary evidence, and 28-day follow-up — eliminating three at source saves weeks of post-audit work.
- Display tier badges (£29/£59) with deployment dates and the record IDs they generate on every audit preparation document.
- Present the 4.86-NC benchmark alongside your own NC trend to show continuous improvement trajectory.
- Share this case teardown with site QA teams, internal auditors, and BRCGS certification bodies so the lesson is embedded before the next assessment cycle.
Common mistakes
- Treating a missing overnight log as a minor administrative oversight rather than a system failure that will cascade into multiple BRCGS non-conformities across Clauses 3.3.1, 2.11, and 3.4.
- Relying on night shift staff to complete manual temperature logs when the entire point of HACCP CCP monitoring is that the system must detect deviations regardless of human availability.
- Excluding overnight and weekend records from internal audit sampling, which guarantees that monitoring gaps remain invisible until an external assessor finds them.
- Performing root cause analysis only after an external audit raises the finding, when the CAPA should have been generated internally the morning after the gap occurred.
- Quoting the 4.86-NC average as a target rather than treating it as a ceiling: continuous monitoring should drive your site's NC count to zero for record-control findings.
FAQ
How does a single missing temperature log generate three BRCGS non-conformities?
The missing log is a direct Clause 3.3.1 (record control) failure. Because no corrective action was taken when the gap occurred, Clause 2.11 (corrective action and root cause analysis) is also breached. And because the internal audit programme failed to detect the gap before the external assessor, Clause 3.4 (internal audit) is cited for inadequate coverage of overnight monitoring records. One gap, three clauses, three NCs.
What is the BRCGS average non-conformity count per audit?
The BRCGS 2024–25 Annual Report confirms an average of 4.86 non-conformities per audit across all Food Safety Standard Issue 9 assessments. 59% of findings fall within Section 4 (site standards), but record control (Clause 3.3.1, ranked #9) and document control (Clause 3.2.1, ranked #7) are the most common documentation failures — and the easiest to eliminate with automated records.
Can automated monitoring really prevent all three of these NCs?
Yes. Shield tier's 288 five-minute readings per day eliminate the Clause 3.3.1 gap because the sensor records independently of staffing. Command tier's AUTO-DETECTED diary entries and Excursion Reports auto-generate the CAPA evidence Clause 2.11 requires. And continuous monitoring makes overnight record gaps visible in real time, which means internal audits under Clause 3.4 are supplemented by automated surveillance that catches gaps the moment they occur.
How quickly must BRCGS corrective actions be closed after a finding?
BRCGS requires evidence of corrective action within 28 calendar days for major non-conformities. Critical NCs may require immediate closure with re-audit. With automated monitoring, the corrective action evidence — the sensor readings that filled the gap going forward, the CAPA record documenting the root cause, and the verification check confirming the fix — can be generated and submitted within days rather than weeks.
Keep exploring
- Cold Chain Compliance in the UK: HACCP, SFBB, and the Complete Regulatory MapPillar hub
- Chicken Cottage Hygiene Rating UK: Our Analysis of 75 Sites Across the Network
- Dixy Chicken Hygiene Ratings UK: What Our Analysis of 122 Sites Shows
- UK University City Food Hygiene Rankings 2026: Which Student City Has the Worst Ratings?
Recommended tools