How to Correct a Pizza Bake Log Without Losing the Original
A correction should show what changed and why. Keep the original bake-log entry, add a correction with its own date, and distinguish a recovered measurement from a later recollection. You do not need an elaborate system: a small table beside your existing notes can do the job.
This guide supplies that table. It is a record-keeping method, not a tested recipe or a way to establish what caused a bake result. For the wider logging context, see how to log a bake. If you changed the formula itself, keep that change in a separate substitution record.
Decide whether you are correcting or adding
A correction replaces a statement you now know was wrong. An addition supplies information that was missing. A reinterpretation changes your explanation of an observation. Label the action, because those three operations tell a future reader different things.
Suppose your original note says “surface reading unknown.” Finding a photograph of an instrument display may let you add a reading, provided you can connect the photograph to this attempt and identify what was measured. Remembering that the oven seemed hot supplies a later recollection; it does not recover a missing measurement.
If you cannot establish which attempt a photograph belongs to, leave that uncertainty visible. A precise number attached to the wrong record is less useful than an honest unknown.
Keep one stable identifier for the attempt
Give each attempt a short identifier and keep it when you correct the note. The identifier is a label, not a timestamp or an outcome score. If several pizzas came from the same dough, use separate observation identifiers when the distinction matters to your records.
Keep the original text in place or save an unchanged copy. Put a visible note beside the affected field directing readers to the correction. In a spreadsheet, a second tab named Corrections is enough; in a notebook, a dated note with the original page reference works.
The point is to avoid two conflicting records that both look current. A reader should be able to identify the original entry and the correction without guessing which file name came last.
Copy this correction table
This is a blank schema you can copy into a spreadsheet. The header is the artifact; it deliberately contains no invented bake data.
correction_id,attempt_id,recorded_at,action,field_name,original_text,replacement_text,evidence_reference,evidence_kind,remaining_uncertainty
Use these fields as follows:
- correction_id: a unique label for this correction.
- attempt_id: the unchanged label of the attempt being amended.
- recorded_at: when you made this correction, including a timezone when needed.
- action: correction, addition or reinterpretation.
- field_name: the exact field affected.
- original_text: what the original entry said, including “unknown” when applicable.
- replacement_text: your revised wording; it may still say unknown.
- evidence_reference: a photograph, source note or other record you can actually find.
- evidence_kind: contemporaneous record, later recollection or inference.
- remaining_uncertainty: what the evidence still does not establish.
If text includes a comma, quote that cell when saving CSV. Keep timestamps as text if your spreadsheet changes their formatting unexpectedly. Use your own file's import preview to confirm that every header still has its own column.
A synthetic correction, with limits
The following is a fictional documentation example, not a Boccalone bake or a claim about any equipment.
An attempt labelled Practice-A originally says “mixing date: Tuesday.” The writer later finds their dated note saying “mixed Wednesday.” They preserve the original entry, mark the action correction and cite that note. If the dated note itself was written from memory days later, evidence_kind should say later recollection.
The revised record can explain the date discrepancy. It cannot establish a missing mixing duration, an unrecorded temperature or why the pizza behaved a particular way. Do not fill those gaps simply because one part of the note is now clearer.
For arithmetic and formula notation, use the separate formula worksheet. A documentation correction should not silently change the formula you originally copied.
Handle conflicting evidence explicitly
Sometimes two records disagree. Keep both references and write down the disagreement rather than choosing the value that makes a preferred explanation work.
You can mark replacement_text “unresolved” and explain the conflict. If you later resolve it, add another dated correction instead of editing away the earlier uncertainty. This produces a trail another reader can follow.
A corrected value may make comparisons possible, but it does not make the attempts controlled or prove a cause. Record whether the correction changes your interpretation and what other variables remain unknown.
Before you share or reuse the record
Check that the attempt identifier still matches, the original text remains available, the new wording has an evidence reference, and recollections are labelled. Remove personal information from shared files and check that private photographs or links are not exposed.
Keep the correction alongside the record it changes. For source and evidence boundaries, see how Boccalone chooses sources and the bake-record method. A readable correction is a useful result in its own right; it does not need to promise a better bake.
For the broader symptom-led framework, see pizza troubleshooting; a log helps document the question and does not itself prove the diagnosis.
