Fifty Puto, One Recipe Version: A Seller’s Two-Card Consistency System

A recipe version records what the cook intends to make; a batch record shows what actually happened on a particular production run. For fifty promised puto, keep those two records separate. The proposed master card below holds the approved ingredients, weighed fill and steamer setup. The batch card records actual quantities, checks, usable yield and deviations, so a deliberate recipe change can be distinguished from a production error.

Keep a recipe master and a separate batch record

Choose one existing household puto recipe already tested successfully; this article intentionally does not invent a universal batter formula. Write ingredient amounts in a consistent measured system, using grams where practical and recording the exact small-measure convention, record the type and capacity of each mould, and state whether fifty means fifty pieces of exactly one size. The second card should have fields for start time, water level, steamer load, measured batter used, actual sellable pieces, defects and corrective action. Keep food-safety checks separate from presentation preferences. The puto steaming guide helps establish the reference method before it becomes a production card.

Record the version actually cooked

1. Create Master Card V1 from a successfully tested recipe: exact ingredient names and labels, quantities, mould dimensions, tested fill weight, steamer load and the actual allergens. Keep the approval date and a reference photograph. Do not call every conceivable allergen present; distinguish ingredients from cross-contact information.
2. Use a tested fill weight and allow for bowl residue and non-saleable test pieces before promising fifty. For illustration only, 55 moulds at 20 g need 1,100 g usable batter; if 50 g remains on tools, total batter needed is 1,150 g. If one cake is used for a centre check and four are rejected, only 50 remain for sale. Actual allowances must come from the recipe’s measured yield. This example deducts only one tester; if several loads or tiers need separate test cakes, add those pieces to the production allowance before promising 50 saleable cakes.
3. Record each separate steamer load and tier position, with the approved water level and fill limits. Steam passages must remain clear. If fifty pieces require several loads, give each its own start and completion checks under the same batch record.
4. Check representative cakes from the slowest-heating positions in every load, including each tier used. Cut a tester to confirm the centre is set without raw batter; smooth outer cakes do not establish that another position is cooked. Record actual findings instead of copying the expected time.
5. Count pieces formed, test pieces, rejected pieces and saleable pieces separately. Assign a unique production code, such as 2026-11-05-B01, and write Recipe V1 on that record. The recipe version identifies the formula; the date-and-batch code identifies this cook.
6. Keep deviations on the batch card until evaluated. If an authorised change becomes the new reference, issue V2 with its date and reason, archive V1 and tell every cook which version is current. Update ingredient/allergen information before serving a changed formula.

Sources: Source 3 Source 1

Reconcile batter, testers and saleable pieces

The distinction between reference and exception is practical. If fifty pieces were promised and only forty-six pass quality inspection, the missing four affect both customer commitments and true unit cost. If a new flour brand thickens batter, the change belongs on the exception card until tested; it should not quietly alter the reference recipe that a second cook follows. This makes the seller’s kitchen easier to operate and easier to troubleshoot without requiring a complex application. The homemade puto costing guide can turn the actual saleable count into a cost per piece, including the test cakes and losses.

The cards should answer two questions without guesswork: “Which approved recipe was used?” and “What happened in this batch?” For example, a flour-brand substitution belongs on the actual batch record and must be reviewed before it becomes an approved version. The FSA’s ingredient-record guidance supports keeping recipes and ingredient information current; the particular V1/V2 card layout is this guide’s proposal. Source 3

Carry only verified changes into the next version

Review several batches for recurring causes of loss: differing fill weights, extra tiers, a changed flour or excessive waiting before packing. Change one material variable at a time when testing a correction. If only 46 pieces are saleable, record 46 and resolve the short order; never relabel the count as 50.

What the records establish

A version number does not validate shelf life or a commercial food-safety system. Keep the established handling plan with the recipe. For this rice-cake baseline, chill promptly in shallow portions, ideally within one hour, refrigerate at 4°C or below and use within 24 hours; reheat only once until steaming hot. Record the actual times and conditions. Source 2 Source 1