Records¶
Everything that has been filled in, one day at a time. This is the book.
Where: menu → Food Safety → Records.
Finding one¶
A day at a time, with arrows either side and the date in the middle — Today, 18 September or Thu 11 September 2026. Today jumps back to now.
Search by form or verifier… and the category chips narrow what is shown.
Checks still being filled in¶
A check somebody has started sits on its day alongside the filed records, marked In progress and reading "Tom is filling this in · 20 min ago". Tap it and you carry on from where Tom got to, on whichever till you are standing at. A cooling log takes hours and several people, so this is what half-done work looks like rather than a gap in the day.
It is not a record until it is filed. Nothing in progress counts towards the day's totals, the reports or an export, and one left untouched for twelve hours goes back to reading as Draft.
What a record holds¶
Tap one for the whole thing: every field as it was filled in, who filled it, when, and what it was recorded for. A check that did not pass says so at the top.
⋮ gives you Edit record and Copy to new record — the second for when today is much the same as the record you are looking at.
With Inventory switched on too, a receiving check that names a supplier shows Book into stock: it starts a delivery from that supplier with the invoice number from the check, and the two stay linked. Once booked it shows In stock (or Delivery started), and tapping it opens the delivery. See A delivery.
When a check did not pass¶
The record carries a banner until something is done about it:
A check did not pass — A corrective action is expected for this.
File corrective action beside it opens the Corrective Action Log with the failed record already attached. Once it is filed, the banner changes to Corrective action filed and lists the linked record, which you can tap through to.
They are joined to each other, not matched up by date. A corrective action filed three days later still points at the right check, and a verifier following the trail lands on the entry rather than on a date to go hunting from.
Putting a wrong record right¶
A record is never written over. You change the values, and the old ones stay beside the new ones.
Changing anything asks Why the correction? — "2 fields changed. The record keeps what it said before, with your name, the time and this reason beside it." A reason is required; Save correction stays greyed out without one. The hint suggests the shape: "e.g. dry goods, temperature not applicable".
The record then carries an Amendments section: when, who, what moved, and why.
A corrected exception stays on the exceptions list, marked amended. It does not quietly disappear. Somebody reading the book later sees both the mistake and the fact that it was looked at and put right — which is a better thing for a verifier to find than a clean book that was tidied.
This is also how you deal with an old exception that was never really an exception: a dry goods delivery logged against a chilled temperature rule reads as a failure until it is amended, and then reads as corrected.
Good to know¶
- The record keeps the words the form had at the time. Renaming a field on the form later does not reach back and rename it here.
- Deleting a record is possible and is not the answer to a wrong one. Amend it. A deleted record is a gap in the book; an amended one is a story.
- Whoever was signed in is whose name is on it. If your shop asks for a PIN, that is the name a verifier reads.
- Records filed with no signal arrive when you are back on. The dot in the top bar says which you are.