prepd360

The readiness engine

The difference between recorded and ready

A site can have every form signed and still not be safe to open: the only trained fryer operator called in sick, the walk-in has been out of service for three days, four corrective actions are open. Readiness is the question nobody else is answering.

Recorded

Did the team complete their checks yesterday?

Answerable by every system on the market. Tells you about the past.

Ready

Can this site run safely for the next twelve hours?

Needs the roster, the training records, the equipment state and the open issues read together. Tells you about now.

What it reads

Built from data you already have

No new forms, no extra reporting burden, no asking busy people to tell the system something it could work out. Readiness is computed from records the operation already produces.

Roster against sign-ins: a no-show shown as checks that have lost their owner.
  • Roster against sign-ins

    Who should be here, who actually is, and what that leaves uncovered.

  • Competency

    Who is trained and in date for each task. A check with no qualified person on shift is a coverage gap, not a to-do item.

  • Schedules and due times

    What is owed, when it was owed by, and what has slipped past it.

  • Equipment state

    What is out of service, overdue a service, or has been failing its readings.

  • Open corrective actions

    What has been raised and not closed, how long it has been open, and who owns it.

  • Credential expiry

    Training and certificates lapsing, with enough notice to do something about it.

How it decides

Rules you can read, not a score you have to trust

An assurance system that cannot explain itself is worse than no system, because it gives false confidence. Everything that touches a safety decision is deterministic and inspectable.

  • Explicit rules, server-side

    The conditions that make a site ready, or a corrective action closeable, are configuration rather than hidden logic. You can read them, change them, and show your working.

  • Every number opens up

    A readiness figure is never a dead end. Click it and you get the specific gaps behind it, each one linked to the record it came from.

  • Answerable after the fact

    You can show why the system said what it said on a given morning, which is exactly what an investigation or a client audit asks for.

On AI

It summarises and suggests. It never decides.

There is a version of this product that uses a model to judge whether a kitchen is safe. We are not building it. A model that occasionally invents a reading, or quietly smooths over a failure, is a liability dressed as a feature.

What it does

  • Summarises a week of exceptions into something a regional manager can read in two minutes
  • Spots patterns across sites, such as one fridge model failing everywhere
  • Drafts a corrective action for a manager to review and approve
  • Answers questions about what happened, with links to the underlying records

What it never does

  • Decides whether a reading passed or failed
  • Closes a corrective action
  • Creates, edits or infers a record that nobody entered
  • Changes a readiness result

See how Prepd360 could work in your kitchen

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.