Read from your systems
Roster, people and asset data can come from the system that already owns it.
What it covers
Replaces the clipboard, the equipment folder, the training wall chart and the incident book. One record, one place, one version of what happened.
What is in it
Each one has a page of its own. They are listed rather than tiled because the point is the run, not eight separate claims.
Fridges, freezers, hot holding, cooking and cooling probes. Ranges live on the asset rather than being typed into a form, so they cannot be widened to make a problem go away.
See how it worksDaily, weekly and deep-clean tasks by area, with the product and contact time attached. Signed off by whoever actually did it, not by whoever had the clipboard at close.
See how it worksEvery asset with make, serial, warranty, service interval, contractor and full history. Knows the next service is due before the engineer does.
See how it worksTraining, certificates and right to work, with expiry warnings weeks ahead. Competency drives who is allowed to own which task.
See how it worksPublish the week, staff sign in on the tablet. Attendance is the spine: it is what makes every other record accountable to a named person.
See how it worksProducts, storage location, stock level and the safety data sheet attached to the product itself, not filed in a binder in the office.
See how it worksInjuries, allergen near-misses, pest sightings and complaints, recorded on the spot with photographs and routed to a manager. Actions close on evidence, not on assertion.
See how it worksAttendance, checks, issues and equipment history, exported for any date range. When a client or an inspector asks what happened in March, you send it the same afternoon.
See how it worksAt the point of entry
A temperature is checked against the range held on that asset, not against a number typed into a form. Out of range and the tablet will not take it until the person records what they did.
What happens next
Every problem runs one workflow: open, in progress, awaiting verification, closed. The closure conditions are evaluated by the server, so the close button stays disabled with the unmet reason on screen.
Over time
Readings, cleans, faults, services and corrective actions all attach to the same asset. Five low readings logged by five different people over a fortnight become a pattern somebody can see.
Fits what you run
Enterprise operators already have systems for people and assets, and the last thing they need is a tenth place to type a staff name. prepd360 is designed to sit across what exists: pull the roster, read the asset register, publish templates from the centre and report back up.
Roster, people and asset data can come from the system that already owns it.
Group standards go out as versioned templates, with controlled local variation.
Group, region and client-level reporting from the same records the kitchen produced.
Focused on purpose
A platform that tries to be everything becomes a worse version of the tools you already pay for. We would rather integrate with those and be genuinely good at one thing.
Whether you are running one kitchen or managing several locations, we would be happy to show you how it works and talk through what you actually need.