BRC Global Standard compliance is one of the most demanding certification frameworks in food manufacturing — and maintenance documentation sits at its core. For Quality Assurance Directors navigating BRCGS audits, a gap in maintenance records is not a minor administrative oversight. It is a potential major non-conformance that can cost your facility its certification. Understanding exactly what BRC food safety standard auditors look for — and how to structure your maintenance documentation program to meet it — is the operational foundation every audit-ready QA team needs. Start your free trial and build a BRC-compliant maintenance documentation system today.
Automate BRC Maintenance Documentation
Generate audit-ready maintenance records, calibration logs, and corrective action reports automatically — built for BRCGS compliance.
What BRC Global Standard Requires for Maintenance Documentation
The BRCGS Food Safety Standard (Issue 9) dedicates Clause 4.7 specifically to maintenance and hygiene — and it goes far beyond simply having equipment repaired when it breaks. BRC compliance maintenance requires a documented, proactive program that covers infrastructure maintenance, equipment condition, calibration of monitoring devices, and corrective action records for every maintenance-related non-conformance identified.
Auditors reviewing BRC maintenance requirements are not checking whether you have a maintenance department — they are verifying that your maintenance program is systematically documented, consistently executed, and directly linked to food safety outcomes. Facilities that manage maintenance through informal verbal systems or disconnected spreadsheets consistently generate audit findings in Clause 4.7, even when the physical maintenance work itself is performed competently. Sign up free to see how a structured CMMS eliminates Clause 4.7 documentation gaps before your next audit.
Sites shall implement a documented planned maintenance and repair program for all equipment and buildings, with records demonstrating that the schedule is being met and that deviations are subject to corrective action.
The Four Documentation Pillars of BRC Maintenance Compliance
Every BRC audit documentation review for maintenance will examine four distinct record categories. QA Directors must ensure all four are current, complete, and readily accessible at the time of audit.
Infrastructure Maintenance Program
A documented schedule covering buildings, fabric, equipment, and utilities with defined frequencies, assigned ownership, and completion records showing planned vs. actual maintenance execution.
Calibration Records
Documented calibration of all measurement and monitoring equipment used at food safety critical control points, with calibration standards traceable to national or international references.
Corrective Action Records
Records of every maintenance deviation, equipment defect, or non-conformance — including root cause, immediate action taken, product safety assessment, and preventive action implemented.
Hygiene After Maintenance Records
Sign-off documentation confirming that sanitation and food safety checks were completed after any maintenance activity on food contact equipment before production restart was authorized.
BRC Infrastructure Maintenance Program: What Auditors Actually Check
When a BRCGS auditor reviews your infrastructure maintenance program, they are looking for evidence of a systematic approach — not a collection of reactive work orders. The BRC food safety standard requires that your maintenance program address building fabric (walls, floors, ceilings, drains), equipment (food contact and non-food contact), utilities (compressed air, water, refrigeration), and pest control infrastructure as a coordinated whole.
In practice, this means your BRC audit documentation must show a master maintenance schedule with defined frequencies for every asset category, records of completed maintenance tasks matched against the schedule, a documented process for identifying and escalating defects found during inspections, and evidence that high-risk areas — particularly high-care and high-risk zones — receive maintenance treatment appropriate to their hygiene status. Temporary repairs are permissible under BRCGS, but they require documentation of the temporary nature of the fix, a timeline for permanent correction, and a risk assessment confirming the temporary measure does not compromise food safety. Book a demo to see how automated work order workflows handle temporary repair documentation end-to-end.
| Infrastructure Category | BRC Documentation Required | Typical Audit Frequency Check | Common Non-Conformance |
|---|---|---|---|
| Building Fabric (walls, floors, drains) | Inspection schedule, defect log, repair records | Quarterly minimum | Undocumented cracks or damage with no corrective action |
| Food Contact Equipment | PM schedule, task completion records, hygiene sign-off | As per HACCP plan frequency | Missing post-maintenance sanitation verification records |
| Refrigeration & Cold Chain | Temperature monitoring logs, PM records, calibration certs | Monthly PM + continuous monitoring | Calibration gaps on temperature monitoring devices |
| Compressed Air Systems | Filter change records, pressure logs, contamination testing | Semi-annual | No records of filter changes or air quality testing |
| Pest Control Infrastructure | Device map, inspection records, contractor reports | Monthly | Devices not listed on current site map or inspection gaps |
| High-Care / High-Risk Zone Equipment | Enhanced PM schedule, zone-specific maintenance procedures | Increased frequency vs. ambient zones | Same PM intervals applied regardless of zone status |
BRC Calibration Records: Meeting the Traceability Standard
Calibration is one of the most frequently cited sources of BRC audit non-conformances globally. The BRCGS standard requires that all equipment used to monitor food safety critical parameters — temperatures, weights, metal detection sensitivity, pH meters, pressure gauges — be calibrated at defined frequencies against references traceable to national or international measurement standards.
What this means in documentation terms is substantial. For every monitoring instrument covered by your calibration program, your BRC compliance maintenance records must show the calibration method and acceptance criteria, the date and result of each calibration, the reference standard used and its traceable certification, the action taken when calibration is found out of tolerance, and a product safety assessment for any production that occurred since the last confirmed in-tolerance calibration. Sign up free and build a calibration register that tracks expiry dates and traceability automatically.
Calibration Documentation Requirements by Equipment Type
Calibration certificates traceable to UKAS or equivalent. Frequency typically annual minimum with documented interim checks. Out-of-tolerance records must include product impact assessment.
Per-shift sensitivity test records using certified test pieces. Monthly calibration with documented sensitivity settings. Reject mechanism function verification at every check.
Calibrated test weights with traceable certificates. Calibration frequency matched to production intensity. Records showing zero and span verification at shift start.
Buffer solution calibration records with lot numbers and expiry dates. Single-use buffer policy documentation where required. Two-point calibration records for critical applications.
Annual calibration against a traceable master gauge. CCP-linked gauges require more frequent verification. Master gauge calibration certificate maintained on file.
Sensor calibration records, alarm set point verification logs, and data logger accuracy validation. Software version control records where applicable to BRC Issue 9 requirements.
BRC Corrective Actions for Maintenance: Closing the Loop on Non-Conformances
Every maintenance non-conformance — a defect found during inspection, a calibration instrument found out of tolerance, a planned PM task completed late — requires a documented corrective action record under the BRC Global Standard. This is one of the areas where food facilities most commonly accumulate audit findings: physical maintenance work is performed, but the corrective action documentation is incomplete, missing a root cause analysis, or fails to address the systemic issue that caused the non-conformance.
BRCGS corrective action records for maintenance must capture the nature and date of the non-conformance, the immediate corrective action taken, the root cause of the failure, the preventive action implemented to prevent recurrence, and verification that the corrective action was effective. For non-conformances that affect food safety monitoring equipment or food contact surfaces, the record must also include a documented assessment of the product safety impact during the period the issue existed. Book a demo to see how structured corrective action workflows enforce root cause documentation before any record can be closed.
Non-Conformance Identification & Logging
Document the defect, deviation, or maintenance failure immediately upon discovery. Record the date, location, equipment ID, and the nature of the non-conformance. Assign severity classification to determine escalation and response timeline.
Immediate Corrective Action
Record what was done immediately to address the non-conformance — repair, isolation, product hold, or process adjustment. Include the date completed, the technician responsible, and any materials or parts used. For food contact equipment, document the sanitation actions performed before production restart.
Root Cause Analysis
Identify why the non-conformance occurred — not just what happened, but the underlying systemic cause. Common root causes include incorrect PM intervals, inadequate technician training, missing inspection criteria, or spare parts stockout delays. Root cause depth is specifically evaluated by BRCGS auditors.
Preventive Action & Effectiveness Verification
Document the systemic change implemented to prevent recurrence — PM interval adjustment, training delivery, procedure update, or spare parts stocking change. Record a verification date and the evidence used to confirm the preventive action was effective. Close the corrective action record only once effectiveness is confirmed.
How CMMS Platforms Generate BRC-Ready Audit Documentation
Manual maintenance documentation systems — spreadsheets, paper checklists, shared drives — are structurally incompatible with BRC compliance at scale. They depend on individual discipline rather than systematic workflow triggers, produce records that are difficult to retrieve during audit, and provide no real-time visibility into compliance gaps before the auditor arrives. For Quality Assurance Directors responsible for BRC certification, a CMMS configured for BRCGS compliance transforms documentation from a reactive burden into an automatic output of normal maintenance operations. Sign up free and replace your spreadsheets with an audit-ready CMMS built for food manufacturing.
A food industry CMMS generates the BRC audit documentation your facility needs as a natural byproduct of how work is executed: PM schedules produce completion records automatically; calibration workflows generate calibration logs with no additional data entry; corrective action workflows enforce root cause documentation before records can be closed; and hygiene sign-off workflows create post-maintenance sanitation records linked to specific work orders. When the auditor arrives, every record exists, is searchable, and is tied to the specific asset, date, and technician — without a week of pre-audit record-hunting.
| BRC Documentation Requirement | Manual System Output | CMMS-Generated Output | Audit Impact |
|---|---|---|---|
| PM Schedule Completion Records | Spreadsheet, often incomplete or not current | Auto-generated work order history with timestamps | Instant retrieval; no gaps from manual oversight |
| Calibration Logs | Paper certificates filed by date; difficult to cross-reference | Digital records linked to each asset with expiry alerts | Complete traceability per instrument per audit period |
| Corrective Action Records | Email chains, Word docs; root cause often missing | Structured workflow enforcing root cause before closure | Consistent, complete records that satisfy BRCGS clause |
| Post-Maintenance Sanitation Sign-Off | Paper form, frequently lost or misfiled | Digital sign-off linked to work order; cannot be bypassed | Eliminates the most common Clause 4.7 finding |
| Planned vs. Actual Maintenance Reporting | Manual calculation, prepared for audit reactively | Live compliance dashboard, always current | QA can identify and close gaps before the auditor does |
| Temporary Repair Risk Assessments | Undocumented or informally noted | Structured temporary repair workflow with timeline and sign-off | Turns a common non-conformance source into a compliant record |
Audit-Ready BRC Documentation, Automatically
Stop preparing for audits. Start operating in a state of perpetual audit readiness with CMMS-generated BRC maintenance documentation.
BRC Audit Preparation: A Documentation Readiness Checklist for QA Directors
BRC audit preparation for maintenance documentation is most effective when it is treated as a continuous operational discipline rather than a pre-audit sprint. The following checklist reflects what BRCGS auditors systematically review under Clause 4.7 and related infrastructure clauses — and what QA Directors should verify is current and complete on a monthly basis, not in the week before an announced audit.
Common BRC Maintenance Non-Conformances and How to Prevent Them
Understanding the patterns of BRCGS maintenance non-conformances is one of the most actionable inputs a QA Director can use to prioritize documentation improvements. The following non-conformances recur most frequently across BRC audits globally — and in the majority of cases, they are documentation failures rather than physical maintenance failures.
Undocumented Planned Maintenance
PM tasks performed but not formally recorded against the schedule. Physical work done; no evidence exists for the auditor. Prevention: CMMS work order closure is required before tasks are marked complete.
Calibration Certificate Gaps
Monitoring instruments with expired calibration dates or missing traceability documentation. Prevention: Automated calibration expiry alerts with mandatory renewal workflow before expiry.
Missing Post-Maintenance Hygiene Sign-Off
Production restarted after maintenance on food contact equipment without documented sanitation verification. Prevention: Digital sign-off workflow that blocks production restart authorization until sanitation is confirmed.
Shallow Corrective Action Root Cause
Corrective action records that describe the symptom ("bearing failed") rather than the root cause ("PM interval insufficient for operational intensity"). Prevention: Structured corrective action workflow that requires root cause field completion before record closure.
Undocumented Temporary Repairs
Temporary fixes in place with no documentation of the temporary nature, risk assessment, or permanent repair timeline. Prevention: Mandatory temporary repair classification in the work order system with automatic escalation after defined duration.
Contractor Maintenance Records Missing
External contractor maintenance activities not captured in the site's maintenance records or sanitation verification system. Prevention: Contractor work order integration requiring site sign-off before contractor departure.
Frequently Asked Questions: BRC Maintenance Documentation
What maintenance documentation does BRC require?
The BRC Global Standard requires a documented planned maintenance program covering all equipment and infrastructure, with completion records showing planned versus actual maintenance. Additionally, calibration records for monitoring equipment with traceable certification, corrective action records for maintenance non-conformances, and post-maintenance hygiene sign-off records for food contact equipment are all required under Clause 4.7 and related infrastructure clauses.
How long must BRC maintenance records be retained?
BRCGS Issue 9 requires that maintenance records be retained for a minimum period consistent with the shelf life of the products produced, or a minimum of one year — whichever is longer. For products with extended shelf lives, the retention period extends accordingly. Calibration records for CCP monitoring equipment are typically expected to be available for the full shelf life of the longest-shelf-life product produced during the calibrated period.
Can a CMMS system satisfy BRC documentation requirements?
Yes — a CMMS configured for BRCGS compliance can fully satisfy BRC maintenance documentation requirements, provided the system generates work order completion records with timestamps and technician identification, maintains a calibration register with expiry tracking, enforces corrective action workflows with root cause documentation, and produces audit reports showing planned versus actual maintenance compliance. Auditors accept digital records provided they have appropriate access controls and audit trail integrity.
What is required for post-maintenance hygiene documentation under BRC?
BRCGS requires documented evidence that any equipment used in the production of food is inspected and cleaned (if appropriate) following maintenance activities, prior to recommencement of production. The record must confirm the inspection and cleaning were performed and that the equipment is in a satisfactory condition for food production. This sign-off must be dated and identify the person authorizing production restart.
How does BRC treat temporary repairs in maintenance documentation?
The BRC Global Standard permits temporary repairs but requires that they are documented as temporary, accompanied by a risk assessment confirming the repair does not compromise food safety or product quality, and subject to a defined timeline for permanent correction. Temporary repairs left in place beyond their documented timeline without reassessment are a source of audit non-conformances. Permanent repair completion must also be documented.
