Behind Every Meal
Everything your kitchen needs for today.
Queux turns attendance, menus, recipes, shopping, dietary requirements and daily food-safety tasks into one clear kitchen day.
Built to support your site’s approved processes and records — never to replace professional, regulatory or Food Safety Plan decisions.
- Attendance
- Menu
- Quantities
- Shopping
- Service
- Records
The daily kitchen problem
Important work should not be scattered across five systems and a bench full of paper.
Counts change. Dietary needs matter. Recipes need scaling. Records still need completing. Queux puts the operational picture in one calm place.
The day keeps moving
Records need context
Today’s Kitchen
Open the day and know where to begin.
Today’s Kitchen assembles the current service plan into a practical sequence for preparation, service, records, cleaning and handover.
- Room and meal-service counts shown in the kitchen’s language
- Dietary and texture totals presented as operational aggregates by default
- Due tasks linked to the approved procedure or site-configured record
- Completion, issues and tomorrow’s preparation carried into handover
From attendance to quantities
Counts become a plan the kitchen can actually use.
Queux keeps source snapshots and manual adjustments visible, then applies them to meal services, rooms and approved recipes.
01
Bring in counts
Manual entry, CSV or an authorised provider connection.
02
Review changes
See what changed, when and from which source.
03
Confirm service
Set the room, meal and dietary totals for the day.
04
Scale recipes
Calculate practical quantities using reviewed recipe data.
05
Prepare clearly
Carry the plan through shopping, prep, service and handover.
Recipes that scale
Change the serves. Keep the preparation visible.
Scale reviewed recipes to arbitrary service counts while preserving units, preparation notes, discrete-item rounding and alternative versions.
Original stays intact
A scaled kitchen view does not silently rewrite the approved recipe.
Uncertainty stays visible
Incompatible units and suspicious source data are flagged for review.
Menus and shopping
Plan the menu, then turn it into an organised shop.
Build menu cycles from approved recipes, account for service counts and alternatives, and consolidate the ingredients the site needs.
Menu planning
Plan cycles, track approved substitutions and communicate changes without losing the original assignment.
Shopping and budget
Aggregate ingredients, deduct on-hand quantities and use the site’s own price records. Queux does not invent live supermarket pricing.
Dietary and room counts
Operational detail without collecting more personal information than the kitchen needs.
Queux is designed around aggregate service-group, meal, dietary and texture counts by default.
Room-level clarity
Minimum necessary data
Visible changes
Human confirmation
Food-safety records
Map digital records to the site’s own plan.
Configure fields, ranges, review steps and corrective-action triggers around the service’s approved Food Safety Plan or Program.
- Finalised submissions retain their original values
- Corrections create a reasoned amendment trail
- Manager and Food Safety Supervisor review can be configured
Practical serving guidance
Carry useful preparation knowledge into meal service.
Keep reviewed serving options, texture guidance, equipment variations and site notes close to the daily recipe — without silently altering the master.
Serve with context
Allow for the site
Keep notes reviewable
Feedback and waste
Turn observations into a practical improvement loop.
Record acceptance, waste, texture and serving feedback by service group. Bring useful site history forward when a recipe returns.
“Toddler room accepted this better when the sauce was served separately.”
Integration-ready
Works beside your childcare software — with honest fallbacks.
Queux is the specialist kitchen layer. Where a provider offers suitable access and an agreement is in place, a connector can bring authorised operational counts into the workflow.
Handbook and training
Keep approved site knowledge connected to the work.
Build a versioned kitchen handbook, link policies and SOPs, assign acknowledgements, and keep internal learning distinct from recognised external training.
- Draft, review, approval, publication and archive states
- Organisation clauses with site-specific variations
- Training and certificate review dates with accountable records
Security & privacy
Organisation and site boundaries are part of the design.
Tenant-scoped retrieval, policy checks, private storage and auditable history support responsible operations.
Private by default
Private uploads remain outside the public web directory and require authorised access.
Explicit tenant scope
Organisation and site context is verified at protected boundaries.
Accountable history
Critical records retain actor, time and amendment context.
Less personal data
Kitchen calculations use aggregate operational counts by default.
Simple pricing
One complete site plan.
Start with the full kitchen workflow rather than choosing between essential operational modules.
Complete Site
A$99+ GST / site / month
Or A$990 + GST per site per year — annual billing includes two months at no additional charge.
Subscription commencement and billing follow the account setup and acceptance flow.
Included
- One physical childcare service
- Unlimited reasonable staff users
- Site setup
- Today’s Kitchen
- Recipes and scaling
- Menus and shopping
- Daily records
- Handbook
- Staff and FSS records
- Feedback and reports
- Platform updates
Optional assisted setup: A$399 + GST once per site. For multi-site pricing, contact Queux.
Questions, answered
Useful things to know before you begin.
Does Queux replace our childcare-management software?
No. Queux is a specialist kitchen layer designed to work alongside your existing system. Manual and CSV workflows are available; provider connections depend on suitable access, documentation and agreements.
Does Queux guarantee food-safety compliance?
No. Queux supports operational processes and records. Your approved Food Safety Plan or Program, applicable obligations and qualified human decisions remain authoritative.
Do we need to provide children’s names?
Kitchen calculations are designed to use aggregate room, meal, dietary and texture counts by default. Where identifiable data is genuinely required and authorised, it should be minimised.
Can a recipe be changed automatically from feedback?
No. Feedback can inform a proposed improvement, but unreviewed feedback does not silently change the master recipe.
Can Queux support more than childcare?
The first sector pack is childcare. The core uses organisation, site, service-group and meal-service concepts so future sector packs can support other meal-service organisations.
A clearer kitchen day starts here