HACCP Principle 7 is the recordkeeping principle: it requires you to keep records and documentation that prove your HACCP system is doing what the plan says it does. That means the written plan and its support, plus the day-to-day records of monitoring, corrective actions, and verification at every critical control point.
It is the last of the seven principles and the one auditors spend the most time on, because records are the only evidence that Principles 1 through 6 actually happen on the floor. A plan can be flawless on paper and worthless in practice; the records are what tell the difference. This guide covers what a HACCP record set contains, what a single entry has to show, how long you hold records, and why a digital record captured at the station holds up better than a binder filled in after the fact.
What is HACCP Principle 7?
HACCP Principle 7 is "establish recordkeeping and documentation procedures." It requires a documented system of records that demonstrates the HACCP plan is being followed, monitoring results, deviations and the corrective actions taken, and the verification activities that confirm the plan still works. Records are the proof the system runs.
The principle sits at the end of the sequence for a reason. Principles 1 and 2 build the plan (hazard analysis and critical control points), Principles 3 through 5 run it (critical limits, monitoring, corrective actions), and Principle 6 verifies it. Principle 7 is what makes all of that auditable: without records, there is no way for an inspector, a customer, or your own team to know whether a CCP was actually monitored on the night shift six weeks ago. The full framework is covered in HACCP certification; this post is the deep dive on the records that hold it together.
What records does a HACCP system keep?
A HACCP record set has four parts: the plan and its support documents, CCP monitoring records, corrective-action records, and verification and validation records. The first is written once and reassessed; the other three are generated every shift the line runs.
The support documents are worth calling out because teams forget them: the composition of the HACCP team the product description and intended use, the flow diagram, and the validation evidence behind each critical limit. Those establish that the plan was built by qualified people on real data. The monitoring, corrective-action, and verification records then prove it stayed real day to day. Your sanitation SSOPs and other prerequisite programs keep their own records alongside the HACCP file.
What must every record entry contain?
Every monitoring entry must show the actual observed value, not a checkmark, recorded at the time the observation happens, with the date, the time, and the initials or signature of the person who made it. Regulations are specific: the FDA seafood rule and the FSIS meat and poultry rule both require the entry to be made at the moment the event occurs.
The reason the "actual value" rule exists is that a checkmark can be filled in for a whole shift in ten seconds at the end of it. A recorded temperature of 76.4°C against a 74°C limit shows a real observation with real margin. When a value lands out of range, the record has to link straight to the corrective-action record that says what happened to the affected product.
How long do you keep HACCP records?
Retention depends on the product's shelf life. Under the FDA seafood HACCP rule, you keep records for at least one year for refrigerated products and at least two years for frozen, preserved, or shelf-stable products. The USDA FSIS meat and poultry rule uses the same one-year and two-year split.
| Product type | Minimum retention | Rule |
|---|---|---|
| Refrigerated seafood | 1 year | 21 CFR 123.9 |
| Frozen, preserved, or shelf-stable seafood | 2 years | 21 CFR 123.9 |
| Refrigerated / slaughter meat & poultry | 1 year | 9 CFR 417.5 |
| Frozen, preserved, or shelf-stable meat & poultry | 2 years | 9 CFR 417.5 |
Two practical notes. First, retention runs from the date the record was created, so the clock on a frozen product made today runs to 2028. Second, records have to stay retrievable that whole time, a box in a trailer that floods, or a spreadsheet on a laptop that leaves with an employee, does not meet the requirement. On-site record availability for federal inspection is part of the rule, not an option.
Do digital records satisfy auditors?
Yes. Auditors and regulators accept electronic records as readily as paper, provided the electronic record has the same integrity paper is supposed to have: it is attributable to a specific person, made at the time of the event, accurate, and protected from undetected change. Those are the qualities 21 CFR Part 11 spells out for electronic records and signatures.
In practice, a well-built digital record is easier to defend than paper, because the system enforces the discipline the regulation asks for. A station-level entry is time-stamped by the system, not by the operator's memory. It is tied to a named user login rather than an unreadable initial. It cannot be quietly back-dated, because the audit trail records when it was actually entered. And an out-of-limit value can trigger the corrective-action workflow the instant it is keyed, instead of being noticed during a record review two weeks later. The failure modes of paper, missing entries found at audit, values written in after the fact, illegible handwriting, a binder no one can find, are exactly the ones a good digital system removes.
How do you organize records so an audit is a search, not a scramble?
The goal is that any record an auditor asks for is in your hands in under a minute, with its context attached. That is a system design question, not a filing question:
- Index every record to product, CCP, date, and shift. If you cannot pull "all cook-CCP records for product X in March" in one query, the records are stored for storage's sake, not for use.
- Capture at the point and time of the observation. The record should be created where the check happens, when it happens, not transcribed later from a clipboard, which is where entries go missing and values drift.
- Link deviations to their corrective actions automatically. An out-of-limit monitoring record and its corrective-action record are one story; store them as one, so no deviation can sit without a documented disposition.
- Build record review into the schedule, not the audit. A qualified reviewer signs off on monitoring and corrective-action records within a defined window (often a week for CCP records) so gaps surface the same week, not the same year.
- Keep the plan and its support current. When the process changes, reassess and re-date the plan; an audit that finds the flow diagram no longer matches the line undermines every record beneath it.
Do these five and the audit becomes a demonstration instead of an excavation. The HACCP plan template gives you the structure for the plan and support documents; Principle 7 is about keeping the living records under it honest and findable.
What do the primary sources require?
The recordkeeping obligations come straight from federal rule and the Codex framework:
- Principle 7 is defined in the FDA HACCP Principles & Application Guidelines which lists the four record categories a plan maintains.
- Seafood recordkeeping and retention, one year refrigerated, two years frozen or shelf-stable, entries made at the time of the event, are set in 21 CFR Part 123 (§ 123.9).
- Meat and poultry recordkeeping, including the same one- and two-year retention, is in 9 CFR 417.5.
- Electronic records and signatures are governed by 21 CFR Part 11 which is the reference for making digital HACCP records defensible.
How do you keep Principle 7 from becoming a paper mountain?
Every CCP you monitor generates records forever, and every record has to be made on time, reviewed, and held for one to two years. Run that on paper across three shifts and the failure is predictable: entries get missed, values get written in later, and audit prep turns into a week of hunting through binders to find the one gap that becomes a finding.
The fix is to make the record a by-product of doing the check, not a separate chore. When CCP monitoring, corrective actions, and verification are captured at the station and time-stamped as they happen, a missed check is visible the same shift, a deviation opens its corrective-action record immediately, and retrieving "every record for this product and CCP" is a search instead of a binder hunt. Harmony builds that layer for food and beverage plants, turning paper CCP checks and quality logs into live, searchable, time-stamped data on the systems you already run, no rip-and-replace. One manufacturer replaced paper production logging entirely and automated its daily reporting on exactly this pattern. Build the records off the plan template keep the team reassessing on schedule, and Principle 7 stops being the part of the audit you dread.