Monitoring is the fourth of HACCP's seven principles, and it's the one a kitchen or plant does every day. The committee that wrote the principles defines it as "a planned sequence of observations or measurements to assess whether a CCP is under control and to produce an accurate record for future use in verification." In practice a monitoring procedure answers four questions for each critical control point: what is measured, how, how often, and who does it. And it produces a record with a real reading on it. Below are the four questions with examples, what the rules say a record needs, one day of a made-up cafe's log, and the file.
The short version
- For every CCP, write down what is measured, how, how often and who.
- Measure the thing the critical limit is about: a temperature, a time, a pH, a test piece rejected.
- Continuous monitoring is preferred where it's possible. Otherwise pick a frequency you can defend.
- Write the actual value, the date and time, and initials. A tick isn't a reading.
- The person monitoring is trained, and reports a miss at once.
- Someone else reviews the records.
- TaroStack puts your checks on each batch record. More below.
The four questions
| The question | Examples | |
|---|---|---|
| What | The measurement the limit is written in | Internal temperature; time; pH; sanitizer strength; test pieces rejected |
| How | The instrument and the method | Probe thermometer in the thickest part, two places; pH meter on a blended sample |
| How often | Continuous, or a set frequency | Every batch; every 2 hours; at 2 and 6 hours of cooling |
| Who | A named job, trained for it | The cook on the kettle; the packer at the detector |
What. Monitor what the critical limit says. If the limit is 165°F in the center of the food, the oven's dial isn't the measurement. Choosing the limit itself is in critical limits for CCPs.
How. Name the instrument and where it goes. The guidelines add that monitoring equipment must be carefully calibrated: a thermometer that reads four degrees high makes every record wrong.
How often. The guidelines prefer continuous monitoring where it's feasible, such as a chart recorder on a cooker. Where it isn't, the frequency has to be reliable enough to show the CCP is under control. A useful test: if this check fails, everything since the last good check is in doubt. How much product is that?
Who. The guidelines say the people who monitor are often in production, and that they must be trained in the technique, understand why it matters, report honestly, and report a miss immediately.
What a record needs
| Rule | For | What it asks |
|---|---|---|
| HACCP guidelines, Principle 4 | Everyone | Records dated and signed or initialed by the person doing the monitoring |
| 9 CFR 417.2(c) | Meat and poultry plants | Procedures and frequency listed in the plan; records with the actual values and observations |
| 21 CFR 117.145 | FDA food facilities | Written procedures with their frequency; monitoring documented in records |
| 21 CFR 117.145(c)(2) | FDA food facilities | Refrigeration records may be exception records, showing only loss of control |
So a monitoring record has five things: what was measured, the reading, the date and time, who took it, and what was done if it was out. "OK" and a tick tell a reviewer nothing. 38°F does.
One day's log
This cafe cooks chicken soup, cools it and holds it cold. Its limits are the FDA Food Code's: 165°F for poultry, cooling from 135°F to 70°F within two hours and to 41°F within six in all, and cold holding at 41°F or less.
| Time | CCP | Reading | Limit | OK? |
|---|---|---|---|---|
| 9:10 | Cooking, kettle 1 | 181°F | 165°F or more | Yes |
| 11:15 | Cooling at 2 hours, pan 3 | 76°F | 70°F or less | NO: act |
| 3:10 | Cooling at 6 hours, pans 3a and 3b | 39°F | 41°F or less | Yes |
| 4:00 | Cold holding, walk-in | 38°F | 41°F or less | Yes |
At 11:15 pan 3 had missed the two-hour mark by six degrees. The pan was four inches deep. The cook did what the plan's corrective action says: split it into two shallow pans, and when it read 68°F at 11:35, after the two hours, reheated it to 165°F and cooled it again. All of that is on the record, with a time. A month of ticks would have hidden it, and hidden that four-inch pans don't cool in time.
Monitoring, verification and corrective action
The three get mixed up, and they're different jobs.
- Monitoring is the reading, taken by the person at the step.
- Corrective action is what's done when a reading is out: to the food, and to the cause. See corrective action form.
- Verification is someone else checking that monitoring works: reviewing the records, calibrating the thermometer, watching a check being done. See validation vs verification.
This is general information, not legal advice. Where monitoring sits in the whole plan is in HACCP plan summary, and writing one from the start in how to write a HACCP plan.
Get the log
Download the CCP monitoring log. Two sheets and a read-me: a monitoring log that takes a reading and a limit and says whether it's inside, with columns for the action taken, who monitored and who reviewed, and a monitoring procedures sheet with what, how, how often and who for each CCP. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers.
Where this stops working
The log says pan 3 was reheated and cooled again. It doesn't say which batch of soup pan 3 was, which chicken went into it, or which day's lunches it was served at. The monitoring record and the production record are two pieces of paper, and the only thing joining them is that someone remembers.
How TaroStack does it
TaroStack puts the checks on the batch they belong to.
Your checks are fields on the batch record. Cook temperature, the two cooling readings, who took them: the form is yours to set up, and each batch carries its own answers.
The batch notes the lots it used, automatically, so a reading is tied to the chicken that went in.
Every batch is a lot with a date, and what ships or is used is recorded by lot.
One report for a lot: what it was made from, where it went, and what's left.
| The question | Paper log | In TaroStack |
|---|---|---|
| Which batch was pan 3 | Unknown | The batch the reading is on |
| What went into it | Another sheet | The lots on the batch |
| Where it went | Memory | The lot's history |
| Last month's readings | A binder | On each batch record |
TaroStack isn't a thermometer or a chart recorder, and it doesn't write your HACCP plan. Recipes, batches and lots are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
