Define the service first
Which kitchen, meal and guest count are you planning for? We use this daily framework to define the demo and starting scope.
- Service areas and meals
- Expected guest counts
- Team responsible for starting
How it works
From the first service plan to the next.
The Atlas workflow starts with a menu. Ingredient needs, stock, purchasing and waste records gain meaning in the same service context. Team review stays part of every step.
Follow a service, step by step.
Choose a step to see the inputs, the review and the handoff to the next stage.
STEP 01
Plan the menu around the service.
Bring dishes, recipes, service dates and expected guest counts together.
- Input
- Menu · Recipes · Guest count
- Review
- Portions, variety, cost and missing price information.
- Handoff
- A preparation plan reviewed by the team.
WITHIN THE OPERATION
Setup follows your kitchen’s workflow.
Align recipes and ingredients
Review dish names, ingredients, units and portions. Keep missing prices or uncertain units visible within the calculation.
See recipes through production- Recipe and portion review
- Ingredient names and units
- Price source and date
Try one service together
Compare planned quantities with available stock. Clarify who reviews purchasing, preparation and records.
See team responsibilities- Plan and stock comparison
- Review and approval steps
- First-service review
Bring observations into the next plan
Review post-service records knowing the dish and preparation quantity. Your team’s observations inform the discussion of the next plan.
Follow records through review- Dish and service context
- Record-quality review
- Preparation quantity review
START TOGETHER
Enough for a first conversation.
Start with the information you have today. We can clarify missing inputs and the scope of a first service together.
- A daily or weekly sample menu
- One recipe and its portions
- Service area and guest count
- Stock and supplier prices, if available
YOUR QUESTIONS
Before you begin.
Can we start without a camera and scale?
Menu, recipe, cost and ingredient-demand workflows can be reviewed independently of camera and scale setup. Waste capture needs a separately agreed station and connection scope.
Must every field be complete on day one?
We can identify missing information together. Review the calculation’s scope rather than treating missing prices, stock or portions as complete.
How long does setup take?
It depends on recipe and ingredient data, service areas, connections and hardware needs. Once we understand the scope, we can agree an appropriate starting plan.
SEE ATLAS IN YOUR OWN SERVICE
Let’s plan your first service together.
Start with a menu, a recipe and the priorities of your team.
Request a demo