Site structure
- Organisation and centre details
- Rooms and capacities
- Meal services and times
Resources
Prepare the decisions that make a kitchen setup useful.
These practical guides help teams understand the Queux workflow before they configure a site. They are operational prompts, not legal or compliance advice.
Site setup checklist
Start with information your service has already reviewed.
You can save and return during setup. Gather what applies to the site; do not create a document merely to fill a screen.
Food and menu
- Current menu cycle
- Approved recipes and alternatives
- Dietary and texture count process
Food-safety records
- Current approved plan or program
- Forms and site limits
- Review and corrective-action roles
Daily procedures
- Opening and closing process
- Cleaning schedules
- Equipment-specific instructions
Policies and handbook
- Current approved documents
- Site variations
- Review dates and approvers
People and learning
- Staff roles
- FSS records
- Internal and external training evidence
Integration readiness
Questions to answer before requesting a provider connection.
A useful integration begins with permission, scope and a reliable fallback.
- 1
Which system is authoritative for attendance or meal counts?
- 2
Has the organisation confirmed it may provide those fields to Queux?
- 3
Does the provider offer supported documentation and credentials?
- 4
Which sites, rooms, dates and meal services must be mapped?
- 5
What minimum dietary summary does the kitchen genuinely need?
- 6
Who reviews sync failures and enters a manual replacement when needed?
Plan mapping prompts
Digitise the site’s decision, not a generic assumption.
For every operational form, identify the approved source and the person accountable for review.
- Plan or program title and current version
- Relevant section or procedure
- Fields, units and locally approved limits
- When a corrective action is required
- Manager or FSS review step
- Retention and export expectations
Short explainers
Understand the boundary before choosing a workflow.
Manual, CSV or provider?
Choose based on reliable authorised access — not the appearance of automation.
Draft, approved or published?
Keep working content separate from the version staff are expected to follow.
Internal or recognised training?
Record both clearly without presenting internal learning as a nationally recognised qualification.
Need help mapping your site?