A useful smoker cook log captures cause and effect. It records the setup, a few meaningful readings, the changes you made, and the result. It does not need a temperature every five minutes or a paragraph about every lid opening.
The best test is simple: could you use this record to plan a similar cook six months from now?
Record the starting conditions
Before the food goes on, capture:
- Food and weight
- Cooker and fuel setup
- Planned pit target
- Internal target or other finish checks used by your method
- Planned phases
- Serving-time goal if there is one
- Weather only when it is likely to matter
- The estimate you accepted or the different duration you chose
Keep these as a snapshot. Editing an equipment profile later should not rewrite what happened on this cook.
Log events that changed the cook
An event earns a place in the log when it explains a later reading or result. Examples include:
- Food added
- Lid opened for a meaningful task
- Fuel added
- Vent adjusted
- Food moved to another zone
- Wrapped or unwrapped
- Basted, spritzed, or glazed
- Phase completed
- Cook paused or cooker problem noted
- Rest or hold started
Add a short reason when it is not obvious. `Opened lid` is weak. `Moved ribs away from the hot edge after darkening` will help next time.
Take readings with context
For a manual log, consistency matters more than volume. Record pit and food readings at useful checkpoints. Identify the item and probe when several foods are cooking.
A reading becomes more informative when it sits beside an event. A pit drop after a long lid opening means something different from a pit drop with no visible intervention.
Do not treat one probe value as a safety verdict. Probe placement, calibration, and the food itself matter. Use appropriate independent checks.
Finish with the result
The outcome is where a log becomes a learning tool. Record:
- Actual finish and serving time
- Planned versus actual duration
- Overall rating
- Texture, moisture, bark, smoke, and seasoning notes that fit the food
- What worked
- One change for next time
- A photo if it will help you recognise the result
Keep the next-time note specific. `Improve bark` is a wish. `Leave the surface uncovered during the final phase and compare the result` is a test.
What not to record
Skip data that you will not interpret later. A complete weather report, every tiny fluctuation, and repeated notes that say `still cooking` add noise.
Also avoid rewriting the plan after the cook so it looks correct. Preserve the starting estimate, later changes, and actual result as separate facts. The gap between them is the lesson.
A compact cook log template
Plan
- Food and weight:
- Cooker and fuel:
- Pit target:
- Serving window:
- Planned phases:
- Starting estimate and decision:
During the cook
| Time | Pit | Food | Item or probe | Event and reason |
|---|---|---|---|---|
Result
- Actual duration:
- Rest or hold:
- Rating:
- What worked:
- Change next time:
BBQ Replay keeps this structure on the iPhone. It supports manual readings, events, phases, notes, photos, independent concurrent cooks, and planned-versus-actual history without requiring an account.
Related guide: How to Compare BBQ Cooks and Improve the Next One
Time and temperature guidance is advisory. Verify food safety and doneness independently using appropriate guidance, your equipment, and your own judgement.