Food safety and compliance

Compliance is a tab inside the Business section of ibakepro. It holds the control points you have declared, the readings and events logged against them, the corrective actions those raise and the pack you print when somebody outside your business asks to see your records.

Why it exists

A folder of paper temperature sheets has two problems. The first is that a bad reading gets noticed, dealt with verbally and never written down, so the record shows an unbroken run of good numbers and the one moment that mattered is missing. The second is that nobody can tell, months later, which limit a reading was judged against, because the limit on the sheet is today's.

Your numbers, not ours

The limits that judge your readings are the ones you declare. ibakepro carries suggested figures, and they are shown as starting points when a control point is being set up, but a suggestion never judges a reading.

A control point is created as a draft and judges nothing while it stays there. It becomes active only when a person confirms it, and the confirmation records who confirmed it and when. Change its limit, its limit type or the unit it was written in, and it drops back to draft, because the confirmation attested one specific number in one specific unit.

Limits come in four shapes: a range (between two values), a minimum hold (this value for this long), a tolerance (within so much of a reference), and an observation (a thing you looked at and recorded, like a twelve-monthly test and tag).

Logging, and what happens to a bad number

The Log button covers a reading, an incident, a pest sighting, a checklist run and a test and tag entry. A reading logged from a control point's own card already knows which check it answers and prints the limit beside the field.

When a reading falls outside its limit, three things happen. It is stored as a breach against a snapshot of the limit it was judged against, so a later revision cannot rewrite history. A corrective action is opened and left open for a person to close. And a control point breach alert fires, graded by how far past the limit the reading went.

A bad reading is always recorded. There is no way for it to leave no evidence.

The two hour and four hour timers

For food sitting out of storage there are danger zone timers. The clock counts total time in the zone across every session in the last 24 hours for the same batch, so refrigerating something and bringing it back out does not hand it a fresh start. At two hours the timer moves into its use now phase; at four it moves into discard. The temperature band itself comes from the country your compliance settings are set to.

You close a timer with an outcome: refrigerated, used or discarded. A timer that runs past four hours with no outcome recorded is marked expired, so an abandoned timer reads as an abandoned timer rather than disappearing.

Alerts go to your team, and nothing gates them

Compliance alerts go to your own team, not to customers, so marketing consent does not apply to them. Breach alerts, incident alerts, pest alerts, checklist escalations and the danger zone timers all reach your team regardless of any customer opt-out.

What they do wait on is you switching them on: open Automation, find the compliance alerts card, choose the recipients and enable the groups you want. Nothing is emailed to anyone until you do.

The pack you hand over

Choose a period and ibakepro builds a pack of your program and its records for those dates.

Records are append-only. There is no hard delete, and removing something needs a reason and leaves an audit entry.

Design decisions

Your program is yours. Where you have flagged something as needing monitoring but never supplied a number, ibakepro raises it as a candidate control point with the limit left empty for you to fill, and a person accepts each one. Transcribing a program document you already have works the same way.
Ask choux answers from your confirmed control points and open corrective actions, says so when the program does not cover a question, and leaves your uploaded documents yours alone.
Readings are entered by a person, or posted through the API.
A breach opens a corrective action. Doing the work and recording it is a person's job, by design.
It is not advice about your obligations. What you monitor, at what limit and how often is between you and whoever regulates you where you trade.

Food safety and compliance records that hold up