Recipes demand analysis

Stage 2 · Analysis

The operator jobs behind Recipes searches

Interpret observed language, identify required evidence, and preserve record authority before proposing Tools.

  1. 1

    Maintain one production specification

    Record Ingredients, quantities, units, ordered method, equipment, timing and expected output.

    Recipe is a versioned production specification. Dish and Drink reference it; training views and cards are projections.

    Evidence: restaurant recipe management software · standard recipe management restaurant

  2. 2

    Scale safely for required output

    Recalculate Ingredient quantities for a target batch, portion count or yield while preserving ratios and units.

    A scaled Recipe is a run-specific calculation. It does not overwrite the approved base Recipe unless an operator deliberately revises it.

    Evidence: recipe scaling calculator restaurant · batch recipe calculator kitchen

  3. 3

    Measure usable output and portion conversion

    Record expected and observed batch yield, preparation loss, portion size and resulting portion count.

    Observed yield is evidence. A default or AI estimate must remain labelled and cannot silently drive authoritative cost or Inventory.

    Evidence: recipe yield management restaurant · portion and yield control kitchen

  4. 4

    Calculate batch and portion cost

    Roll effective Ingredient prices, usable yields, quantities and sub-Recipes into batch and per-portion cost.

    Cost is derived with traceable sources, units and effective time. Missing prices, conversions or yields remain unknown.

    Evidence: restaurant recipe cost calculator · cost per portion recipe

Record map

Evidence the capability owns, references, or derives

kitchen.recipes.recipe

Recipe

ownedpartial

Owner: Recipes

Recipe identity works today; the complete versioned components, method and yield specification remains incomplete.

  • Recipe identity and lifecycle
  • Ingredient and sub-Recipe quantities
  • ordered method and controls
  • expected yield and portions
  • version and approval

kitchen.recipes.ingredient-evidence

Recipe Ingredient evidence

referencepartial

Owner: Ingredients

Recipe calculations depend on compatible Ingredient identity, units, yields and effective acquisition evidence.

  • Ingredient identity
  • unit and conversion evidence
  • yield evidence
  • effective acquisition evidence

Required record questions

What must Recipes make knowable?

  • Which Kitchen owns the Recipe and which version is draft, approved or retired?
  • Which Ingredients or sub-Recipes are used, in what quantities and units?
  • What ordered method, equipment, timing and control points define production?
  • What expected batch yield, yield unit, portion size and portion count are approved?
  • What observed yield was measured, when, by whom and under which Recipe version?
  • Which conversions are explicit and which require density, preparation-loss or edible-yield evidence?
  • Which effective Ingredient prices support the batch and portion cost?
  • Which Dishes, Drinks or other Recipes depend on this Recipe?
  • Which scaled output is needed for a Mise or production run without changing the base Recipe?
  • Which missing evidence or proposed revision needs operator review?
Analysis conclusion
Recipes owns the Kitchen production specification: components, quantities, method and yield. Scaling and costing are traceable projections over an approved version; observed yield remains separate evidence, and missing conversions or prices stay unknown.
Review proposed Tools