Bakery baker - the new-product test-bake SOP: from recipe card to production release, three consistent batches before it hits the shelf

You are the product-development consultant for a bakery. Write me an
SOP for new-product test bakes, running from the recipe card to
production release, that a baker can follow to move a new item onto
the shelf without wobble. Scope, stated in the SOP header: new
products, changed formulas, changed ingredient suppliers, and
relaunching after an equipment change all run these five steps.

Step 1: standardize the recipe card
- Every ingredient in baker's percentage: flour is 100, everything
  else a percentage of flour - scaling a batch up or down becomes
  multiplication, not a card-wide recalculation
- Each ingredient line reads "name + state and prep": "butter,
  softened," "raisins, soaked and drained" - never a bare name
- Water temperature logged as measured, never "room temp" or "warm
  water"; one line per bake day for room temperature and humidity
- Every line leaves a blank "actual" column - what really went into
  the bowl gets written in the moment it goes in

Step 2: first test bake
- Follow the card exactly. Log every departure from it: the dusting
  flour the hands added, the two extra minutes of mixing, dough
  running drier or wetter than the card describes - an unlogged
  departure makes the bake worthless
- Out of the oven: weigh every piece, number them, photograph them,
  numbers and photos filed together

Step 3: departure review
- Walk the departure list item by item: where it deviated, why.
  Causes fall into three buckets - environment (room conditions,
  ingredient lot), habit (old hands fighting the new card), or the
  card itself (written wrong, unworkable as written)
- Each bucket has a destination: fix the card; fix the habit - and
  a habit that won't change gets written into the card instead;
  environmental causes get their countermeasure noted on the card
- Output a revised card and move to step four

Step 4: three-batch consistency check
- Three consecutive batches on the finalized card; no parameter
  changes in between
- Each batch logs three things: finished weight, appearance
  (height / color / shape), and a crumb photo from a cut loaf
- All three batches inside the shop's own consistency band, or it
  is not stable: one batch out of band fails the check and sends
  you back to step two
- The band lives in the SOP header, one line per indicator, set by
  the shop

Step 5: production release
- Three deliverables: the finalized recipe card, locked production
  parameters (oven position / oven temperature / batch size / pan
  layout on the deck), and a one-page handover note for the early
  shift and substitutes
- Release is signed: whoever signs owns this version of the card
- Locked means locked - changing a production parameter restarts
  step four

Constraints:
- No sales forecasts, pricing, or market positioning - that is the
  manager's file; this document owns "can we make it, and make it
  the same twice"
- "To taste," "a pinch," "as needed," "about" never appear -
  everything is measurable; a habit that can't be written as a
  number yet gets measured once, then written
- Failing the consistency check does not lead to "put it on the
  shelf and see how it sells" - the first customers' word of mouth
  is all the word of mouth this product will ever get

Why it is written this way

The card goes to baker's percentage in step one because most small-shop cards live in "grams plus feel": scaling a batch means recalculating the whole card, and one arithmetic slip wrecks a batch. With flour at 100 and everything else relative, scaling becomes multiplication and batches of different sizes become directly comparable. States and prep on every ingredient line, water temperature as measured rather than "room temp" - the same principle: write down once what would otherwise be re-judged by memory on every bake.

Step two runs the other way: the card stays rigid, the baker writes everything down. The dusting flour and the two extra minutes are precisely the map of the gap between card and reality; without that list, the revision gets edited from memory. "A habit that won't change gets written into the card" is the pragmatic choice - an SOP is not a reform school for hands, and the card's job is stability: write the card to match what the hands will reliably do, because the card adapting to the hands is cheaper than the hands adapting to the card.

The three-batch check stands in front of release, with no parameter changes between batches, because one good batch can be luck and two can be one habit repeated; three inside the band is the first evidence the card stands on its own. Changing a parameter between batches turns three verifications into three unrelated attempts - three batches of flour burned with nothing proven. The band is left to the shop and written into the header because "how much wobble counts as stable" is a question only this shop's shelf can answer; the SOP does not answer it for them.

The ban on "put it on the shelf and see how it sells" comes from the classic failure: the sample batch had the baker watching it the whole way through, the shelf batch is made by the early shift following the card - the gap between them is exactly the process that got skipped. In a bake-and-sell-same-day shop, reputation starts with the first customer, and an unstable first run sells reviews, not bread. The three batches the check burns are the cheapest insurance this product will ever buy.

Variables