01 — Setup
Define the kitchen once. Every log knows where to land.
Most of the diary work is structural — defining the fridges, freezers, prep areas and templates that match the kitchen. Set them up once, and every reading, every delivery, every cooking core temp lands against the right piece of equipment, in the right zone, with the right pass/fail limit. No more "where do I log this?" from a new starter on Monday.
- Every fridge, freezer, prep area and probe captured in one structured list.
- Pass/fail temperature limits per item so the diary auto-validates entries.
- Equipment grouped by area for instant cross-section reporting.
- Opening, closing and weekly checklist templates ready to clone.
The kitchen does the work in each log every shift. Setup defines what gets logged where; the export pulls the entire diary together when an EHO walks in.
Define once. Every log lands against the right item.
Fridge, freezer, probe with auto pass/fail.
Supplier, temp, packaging, accept/reject.
Multiple products per record where relevant.
Opening, closing, weekly — template driven.
Task, area, completed-by, timestamp.
Reference temp, drift, pass/fail.
Open → investigating → resolved.
Certification, awarding body, expiry.
Every log type, user attribution, pass/fail preserved.
- Daily logs — the high-frequency core: temperatures, deliveries, cooking.
- Checklist-driven — opening, closing, weekly tasks run from one template library.
- Periodic / annual — probe calibration and staff training stay alongside the diary.
02 — Temperature logs
Pass/fail built into every reading.
Temperature checks are the most frequent task in a kitchen diary — and the easiest to get wrong on paper. Ordello asks for the equipment, the reading and the user, then validates the result against the limits set for that piece of equipment. Failed readings cannot close until a corrective action is recorded. The diary never lies about anything.
- Every reading auto-validates pass or fail against the equipment limits.
- Failed readings require a corrective action before they save.
- Probe attribution links each reading to the most recent calibration.
- Filter by equipment, date or status to spot fridges that drift.
03 — Goods-in deliveries
Check at the door, not after the fact.
Out-of-spec deliveries do not belong in the walk-in. Ordello's delivery log captures the supplier, temperatures, packaging condition and dates as goods come in — and flags out-of-range readings the instant they are entered. Acceptance, partial acceptance or rejection is on the record before service starts, with the reason attached.
- Every delivery linked to the supplier so trends become visible over time.
- Temperature on receipt with out-of-range flagged immediately.
- Acceptance status recorded with a reason for partial or full rejection.
- Quick notes capture packaging issues, missing items or short-dated stock.
04 — Cooking core temps
Core temperature, hold time, defensible record.
Cooking logs cover the high-risk dishes — anything where the centre needs to reach the target temperature for the target time. The log captures multiple products in one cook-off, so an eight-portion chicken bake is one entry, not eight. Every reading cross-references the probe calibration, so any audit question about accuracy has an immediate answer.
- One log entry for a whole cook-off — multiple products per batch.
- Target, achieved and hold time captured against the user who probed.
- Probe calibration cross-referenced so readings are defensible.
- Corrective actions tracked when targets are not met first time.
05 — Daily and weekly checklists
Opening, closing and weekly checks from one template library.
Checklists are template-driven, so a manager builds the opening check once — and every shift runs the same template, completed by a named staff member with every item ticked or flagged. Missed items roll forward visually, so the next shift sees what was left undone. Daily and weekly cadences live side by side.
- Build once, run forever — every shift inherits the same structure.
- Each run captures the staff member and per-item completion.
- Missed items roll forward to the next shift visually.
- Filter run history by template, date or staff member instantly.
06 — Cleaning and probe calibration
Two specialised logs, same audit standard.
Cleaning and probe calibration sit alongside the main diary because both carry their own audit demands. A cleaning task — mop floors, deep-clean fryer, sanitise probes — ties to an area and the staff member who did it. A calibration check captures probe drift and pass/fail, and becomes the cross-reference that defends every cooking log behind it.
- Cleaning tasks defined per kitchen, logged per shift.
- Probe calibrations capture drift, reference and pass/fail.
- Every cooking log can trace back to the calibration check it relied on.
- Both logs flow into the same export an inspector asks for.
07 — Incidents
Every incident closed with what was done about it.
Pests, illness reports, complaints, contamination and equipment failures all flow into the incidents log. An incident is not just logged — it has to be closed. Open incidents stay visible on the dashboard until a corrective action is recorded. The diary tells the story of how problems were resolved, not just that they happened.
- Every incident type captured — pest, illness, complaint, contamination, equipment.
- Status flows from open to resolved, with corrective actions required to close.
- Reporter and resolver are both stamped on the record.
- Open incidents surface on the dashboard until they are closed.
08 — Staff training
Certifications on the same record as the diary.
The first question an EHO asks after the diary is "who is trained and when do their certificates expire?". Ordello holds every staff certification — Level 2 Food Safety, Allergens, HACCP — with the awarding body and the expiry date. Certificates due to expire surface on the dashboard well before the date, so re-training is planned, never panicked.
- Every certification recorded with awarding body and expiry.
- Expiry warnings surface well before the date arrives.
- One click answers "who is allergen-trained right now?".
- Optional document upload for the full audit trail.
09 — Audit and export
One CSV, ready when the EHO walks in.
The point of every log is the moment an inspector or auditor asks for the last 30 days. Ordello's export gives you that — one CSV bundling temperature, delivery, cooking, checks, cleaning, incidents, training and calibration records for the period you choose. Hand it over as-is, or filter it first. Run it monthly as an internal audit even when no EHO visit is on the calendar.
- Single CSV bundle covering every log type for the chosen period.
- User attribution preserved so "who did this?" has an immediate answer.
- Pass/fail status preserved alongside the corrective actions.
- Run a monthly internal audit using the same export.
SUMMARY
The shape of it.
A working SFBB diary is the document an inspector trusts and an owner can defend. Ordello structures it around the work kitchens already do every shift — temperatures, deliveries, cooking, cleaning, calibration, incidents — so the diary is never out of date by Wednesday.