Food safety records for a small bakery: what inspectors actually look at

An inspection is not a test of your food. It is a test of your paperwork about your food, because the inspector sees one hour of one day and the records are the only evidence of the other 2,000 hours a year.

This is an operational description of what those records look like in practice. It is not legal advice, and it does not tell you what you are required to keep.

The record types that come up almost everywhere

Regimes differ, but the same six families turn up in nearly every scheme.

Temperature logs. Fridges and freezers, usually checked at least at the start and end of each trading day. Plus process temperatures where your product has them: a cooking or bake core temperature, and cooling, which is the one small bakeries most often have no record of at all. A large batch of custard or a filled cake cooling on the bench overnight is a process with no evidence behind it unless somebody wrote a time and a temperature.

Cleaning schedules. Two parts, and they get confused. The schedule says what is cleaned, how, with what and how often. The verification record says it happened and who did it. A schedule with no verification record proves you planned to clean.

Supplier and delivery records. Who you buy from, and what condition the goods arrived in. Chilled delivery temperature checked on arrival, packaging intact, date codes in range, and the rejection recorded when you sent something back. This is also the thread you pull if a product has to be traced backwards.

Allergen information. What is in each product, kept current against your actual recipes, plus how you handle cross-contact. This is the record most likely to be out of date, because recipes change and the allergen sheet does not change with them.

Pest checks. A walked inspection of entry points, bait stations and evidence, dated and signed, plus any contractor visit reports.

Staff records. Training completed and dated, and the fitness-to-work side: who reported symptoms, when, and what you did about it.

What "records that hold up" means

Three properties. Getting these right matters more than adding a seventh category of record.

Contemporaneous. Filled in when the check happened, at the fridge, not reconstructed at the kitchen table the night before a visit. Reconstructed records are recognisable and they cost you more credibility than the gap they were covering. The tell is that they are too regular: eleven weeks of readings in the same pen, all within half a degree, taken at exactly 08:00 including on the day the delivery ran late.

Complete. Gaps read worse than bad readings. A run with four missing days raises a question nobody can answer months later, whereas a warm reading with a note beside it answers its own question. If a check genuinely did not happen, because you were closed, record that it did not happen and why. A line saying "closed, no stock held" is a record. A blank is not.

Showing action. This is the one that separates a good file from a tidy one. The reading that a fridge ran warm is not the interesting part. What you did next is: what you checked, what you moved, what you discarded, whether the unit was repaired, and whether it read correctly at the next check. A file of uninterrupted good numbers demonstrates that nothing has ever been noticed. A file with a handful of exceptions, each one closed out, demonstrates that the system works.

The corrective-action habit

Write the fix next to the failure, at the time, in the same place. Not in a separate incident book, not in your head, not in a text message to your supplier.

Four fields cover almost every corrective action:

• What was found (the reading, the sighting, the failure).
• What was done with the affected food.
• What was done to the cause.
• Who did it, and when it was confirmed back in range.

That last one is the field people skip, and it is the one that closes the loop. A corrective action with no verification is an intention.

Paper or digital is an evidence question

Both work. Neither is inherently more credible. Judge either one against three questions.

Is it contemporaneous? Paper wins when the form is on the fridge door and the phone is in the office. Digital wins when it timestamps the entry itself, so the record carries when it was made rather than when somebody says it was made.

Is it retrievable? Can you produce eight weeks of fridge temperatures, and the corrective actions attached to them, while somebody stands in your kitchen waiting? A folder in date order does this well. A folder with loose sheets in it does not, and neither does a phone gallery of photographed forms.

Is it tamper-evident? Can an entry be silently changed after the fact? Paper answers this with ink and strike-throughs. Digital answers it with an append-only log where corrections are recorded as corrections rather than overwrites.

The failure modes differ. Paper fails by loss, water and illegible handwriting. Digital fails by nobody entering anything for a week because the tablet was flat. Pick the one that fits how your kitchen moves, then guard against that medium's failure.

A cadence that survives a busy month

Record	Cadence	The line it produces
Fridge and freezer temperatures	Open and close, every trading day	Unit, reading, time, initials
Process temperatures	Every batch of the products that have a limit	Batch, stage, reading, time
Time out of refrigeration	Every time food sits out, started and closed	Batch, start, outcome
Delivery checks	Every chilled or frozen delivery	Supplier, temperature, accept or reject
Cleaning verification	Weekly for the schedule, daily for high-risk surfaces	Area, done by, date
Pest walk	Weekly, plus contractor visits as scheduled	Areas checked, findings, action
Allergen sheet review	Whenever a recipe changes, and at a fixed interval	Product, change, reviewed by
Training and fitness to work	On hire, on refresh, and per report	Person, topic, date

Daily temperatures, weekly cleaning verification and per-delivery supplier checks are the backbone. If you keep only three things, keep those three, and keep them without gaps.

Your local rules are the source of truth

Requirements vary widely. Which records are mandatory, how long you keep them, whether a documented food safety plan is required at your scale, and how you are assessed all differ by country and often by local authority. Some places operate published hygiene rating or scoring schemes where the result is displayed publicly or online; others inspect without a published grade. Nothing above is a statement of what applies to you. Your local authority or regulator publishes guidance for your kind of business, and that guidance is the source of truth. Read it before you design your forms, because the shape of a record is easier to get right at the start than to retrofit across a year of history.

What to do this week

ibakepro keeps this side of it in one place: control points with the limits you declared, readings logged against a snapshot of the limit they were judged by, a corrective action opened automatically when a reading falls outside, and a period pack you can print when somebody asks. The detail is in food safety and compliance records that hold up. Readings are entered by a person, so someone still walks to the fridge, and a control point is judged once you have confirmed it. Software timestamps the record and stops it being quietly rewritten. Making the check happen is still yours.