How the screening works
How the planned service is designed to decide whether a dish fits the choices you set. It is a description of the method as designed; the service is not operating yet.
Designed, not yet operating. Independent verification has not yet been completed.
The problem it is designed to solve
A menu name or a photograph says little about what is in a dish, and a dish can change when a supplier, a recipe or a portion changes. The service is designed to work from the restaurant’s own dated recipe record instead.
The recipe record
Each dish’s record is planned to hold its ingredients, their amounts, what is inside sauces and bought-in items, the portion and preparation notes, with each sauce, option and substitution recorded as its own part. The restaurant signs the record, and each change is planned to be recorded as a new dated version.
Fixed, written rules
The check uses fixed, written rules. Fixed rules give the same answer for the same record. That makes a result repeatable; it does not prove that a rule is right. So each release of the rules is planned to carry its source, the date it takes effect and the sign-off of qualified clinical reviewers, to be engaged before launch.
Each published rule is designed to show what it checks, the figure it uses, its source, the date it takes effect and its version.
Because every recipe record and every release of the rules carries a version, a past result is designed to be repeatable: the same dish version and the same rules version give the same answer. A sample case shows what happens when a recipe changes.
How a dish is checked
For each dish, the rules compare the recorded figures and ingredients with the limits and the foods to avoid that you set. A dish passes only when every figure the check needs is recorded and is at or below the limit you set, and none of your foods to avoid is in its recorded ingredients.
When a figure is missing, the dish is held back from the views that need that figure and is never shown as a match. A recipe record that is not confirmed again on time leaves the checked views until the restaurant confirms it. Ranking then only orders the dishes that passed; it cannot add back a dish the rules left out.
How records are to be checked
Under the plan, every location is to be checked remotely each quarter against a fixed list of evidence, with an on-site audit within 90 days of going live and at least once a year after that. Until our own staff take this on, the results are to be signed by an independent lead auditor, to be contracted before the first pilot order.
Privacy by design
The service is designed so that a restaurant sees only what it must cook to, such as a food an order must leave out, and never the reason behind it.
What exists today
| Part | Stage |
|---|---|
| Sample menu demo | On this website today, with fictional dishes only. |
| Checking real restaurant dishes | Designed; not operating. |
| Independent checks of each location | Planned to start with the first pilot order. |
| First pilot location | Targeted for April 2027, after platform acceptance and full labelling of its menu. |
What the method cannot do
The method compares recorded information with the choices you set. It does not predict how a meal will affect you, it does not assess cross-contact, and it does not replace advice from your healthcare professional.
Words we use
Recipe record: the restaurant’s signed, dated description of a dish, with every ingredient and amount.
Rules version: a dated release of the written rules, with its source.
Held back: left out of a view because a figure the view needs is missing or out of date; never shown as a match.
Ranking: putting the dishes that passed in an order; it never adds a dish back.