Prep follows the current service
Show the covers and menu assumptions behind the dish proposal so managers can challenge the plan.
For venue owners and hospitality managers in Australia
Compare a fixed 100-cover plan with a late booking change and short delivery. See the dish quantity and supply gap before a manager chooses the response.
Built around your working day
Bookings change, deliveries arrive short and the kitchen still needs a clear plan. We connect covers, menu assumptions, usable stock and manager decisions so prep, purchasing and staffing drafts respond to the same information.
Your current tools matter. your bookings platform, POS, inventory and roster systems are useful starting points for scoping. We check the actual records, access and supported actions in your account before promising a connection.
What changes for you
Show the covers and menu assumptions behind the dish proposal so managers can challenge the plan.
Recalculate the supply gap against usable portions before sharing revised station instructions.
Keep purchasing, prep and roster proposals attached to the same approved service plan.
Example system · Simulated business data
Compare a fixed 100-cover plan with a late booking change and short delivery. See the dish quantity and supply gap before a manager chooses the response.
Fixed assumptions of 100 covers and 70% dish selection produce a 70-dish proposal.
HV-02 / BK-v1 / BK-v2 / v1 · example reviewThe complete architecture
Blue connections show the scenario path. Stage selection changes explanation only. Dashed paths need a new decision.
01 / Source control
Match booking snapshots and POS context to the same venue and service period. Distinguish confirmed records from manually supplied planning assumptions. The example manager reviews the 10-portion supply gap before preparing station and order drafts. The selection rate is a supplied assumption, not a forecast result.
Service source register / simulated
| Source or item | Recorded value | Decision |
|---|---|---|
| BK-v1 / MA-02 | 100 covers × 70% | 70 proposed dishes |
| ST-03 | 60 usable portions | Current count |
| Supply gap | 10 portions | 70 − 60 |
| Team availability | Manager check | No staffing-law decision |
The example manager reviews the 10-portion supply gap before preparing station and order drafts. The selection rate is a supplied assumption, not a forecast result.
Inspecting window · scenario output stays tied to its recorded decision
Fixed example assumption of 100 covers for one service.
Historical window is context only. The 70% selection rate is a fixed supplied input.
60 usable portions in the initial stock input.
70 proposed dishes and 10 portions to source.
Demand rates are fixed example assumptions. Responsible staff decide substitutions, food handling and staffing. Captured records do not establish food safety or compliance.
01 / Source control
Match booking snapshots and POS context to the same venue and service period. Distinguish confirmed records from manually supplied planning assumptions.
What you receive Service source register.
02 / Explicit assumptions
Apply the fixed 70% dish-selection assumption to the example cover count. Show the multiplication rather than presenting the result as a predictive model.
What you receive Dish quantity proposal.
03 / Independent checks
Bring usable stock and supplier notice together, preserving units and timestamps. A short delivery changes the usable quantity and therefore the supply gap.
What you receive Portion and supply comparison.
04 / Human decision
Present supply, menu and capacity options with the changed assumptions. Responsible staff decide substitutions, food handling and any staffing response.
What you receive Manager option sheet.
05 / Version and variance
Prepare station, purchasing and roster drafts from the manager’s plan version. Later service outcomes can be compared with the proposal without rewriting the earlier assumptions.
What you receive Service draft and variance register.
Demand rates are fixed example assumptions. Responsible staff decide substitutions, food handling and staffing. Captured records do not establish food safety or compliance.
The decision stays with your team
Demand rates are fixed example assumptions. Responsible staff decide substitutions, food handling and staffing. Captured records do not establish food safety or compliance.
FSANZ describes evidence of critical food-safety controls for businesses within the tool’s scope. A forecast or captured record does not replace responsible staff or establish compliance. FSANZ evidence tool ↗
Primary source checked . This original example illustrates a design, not a delivered client result.
What it costs
Booking and POS windows, recipe assumptions, stock units, waste records and supplier updates shape the scope. Start with one service period and a clear manager approval step.
We map the current process, agree the review points and put the scope, fixed fee and payback estimate in writing. Software and usage costs are considered separately. Your own baseline determines the business case.
One process, rebuilt to run without you. Monitoring and documentation included.
Several connected processes across two or more systems, where the data needs cleaning first.
Agents that read unstructured information, decide and write back, with human review and a full audit trail.
Priced on how much you run and what your business loses the day one of them stops.
When something breaks
An absent booking update can invalidate prep while every previous run looks successful. We monitor expected changes, empty stock responses and failed draft writes, preserving the service period and plan version during recovery.
We design checks for a run that fails, a run that returns nothing and a run that never starts. The care scope names the person who receives an alert, the information they need and how a held record returns to review.
You own the workflows and accounts. Handover includes the record identifiers, review rules and recovery instructions. No lock-in is required to keep your work.
See ongoing supportBefore you decide
No. It uses fixed inputs of 100 or 130 covers and a supplied 70% selection assumption. We show the arithmetic so you can inspect the effect of a changed input.
That decision stays with responsible venue staff. Availability is only one consideration. The example does not assess allergens, food handling or whether a substitution is appropriate.
No. FSANZ’s evidence tool has a defined scope and record requirements. Capturing a record or showing an alert does not establish that a control was performed correctly or replace trained staff.
We assess the exact records and operations exposed by your current platforms, including time windows, units, permissions and update frequency. Familiar tool categories do not prove connector coverage.
The new booking version changes the affected service assumptions. Prep and supply proposals are recalculated and returned to the manager before downstream drafts change.
Yes. One venue and one service period provide a useful boundary for checking booking changes, stock units and manager decisions before extending the process.
For work with several evidence lanes, version changes and explicit review gates, our n8n operating model explains the orchestration decisions. The platform choice still depends on your access, maintenance capacity and data path.
A useful first conversation
Show us where the records arrive, who makes the decision and what the next person needs. We will map a useful first scope with you.
Book a call