Chef
Reviews recipes and the draft menu, then confirms preparation quantities and the plan.
FROM RECIPE TO SERVICE
How many portions of each dish should you prepare? Connect recipe quantities and portion costs to the service plan; review missing prices before approval.
A CLOSER LOOK AT THE PRODUCT
Service dates, dishes, cost per person and applied rules share one menu plan. Your chef reviews the plan and missing information before confirming preparation.

Review dish and portion costs alongside price coverage. Identify missing information before deciding.
Bring menus, expected covers and recipe quantities into the same preparation plan.
Review Atlas’s draft, adjust dishes and apply the plan with your team’s approval.
THE WORKFLOW, STEP BY STEP
Connect recipe information to daily preparation. Keep your team’s review and decisions visible at every stage.
Organize ingredients, quantities and portion bases. Let production and cost calculations use the same recipe information.
Choose meals, dates, expected guests and menu rules. Include fixed dishes and your operational preferences.
Consider dish compatibility, variety and price coverage. Identify missing prices and adjust dishes using your team’s knowledge.
Review ingredient needs against the planned service and recipes. Give production and purchasing teams the same menu context.
EXPLORE AN EXAMPLE
Calculate an ingredient’s recipe quantity per person against the size of the service. This example shows how total ingredient demand is formed.
EXAMPLE CALCULATION · TOMATO
400 guests × 100 g ÷ 1,000. This calculation covers one ingredient; your team determines final preparation.
GETTING STARTED AT YOUR HOTEL
You can begin with one service and a few current recipes. We can review the planning workflow before preparing your entire archive.
Teams sharing the workflow
Reviews recipes and the draft menu, then confirms preparation quantities and the plan.
Reviews menu demand against stock and supplier conditions.
Follow service scope and cost through the same plan.
BEFORE YOU BEGIN
Let’s define the scope around your hotel’s workflow.
Yes. We first review the ingredients, quantities and portion bases in your recipes. Import and preparation scope depends on the structure of your files.
A missing price affects the scope of the cost calculation. Your team reviews the missing information and its source before deciding; incomplete data is not treated as a complete cost.
Yes. Menus are reviewed as drafts. Your chef can review dishes, rules and service conditions and make adjustments. The final decision remains with your team.
Guest count is a basis for calculating recipe demand. Your chef determines final preparation using buffet format, consumption patterns, service conditions and kitchen experience.
Stock & Purchasing
Compare recipe demand with stock and clarify the purchasing requirement with your team.
SEE ATLAS IN YOUR OWN SERVICE
Start with a sample menu, expected guest count and your team’s priorities.
Request a demo