Writing a session record that separates the plan from what actually happened

You open your notes after a Captain Cooks session and see the same label, such as ‘bonus round’ or ‘feature’, used for two different moments. That label collision is common, and it can make a short record misleading. This article shows you how to distinguish the original plan from the actual decisions you made, so your record stays useful without extra effort.

Why the same label can describe two different stages

You might assume that a label like ‘feature’ always refers to the same point in a Captain Cooks session, but that assumption often fails. In practice, the same word can describe both an intention and an outcome: you planned to trigger a feature, and later you recorded that a feature occurred. The label is identical, but the stage is different. When you write a short record, this collision becomes a problem because a reader, including your future self, cannot tell whether the note describes what you meant to do or what actually happened. The mistaken inference is that matching labels mean matching stages. In reality, a label is just a tag, and its meaning depends on context. If you do not separate plan from decision, your record may suggest you made a choice you only intended to make, or that you followed a plan you actually abandoned. This is not about the game itself but about how you document your session. The fix is to treat every entry as either a plan item or a decision item, never both under the same label. That distinction is the foundation of a useful record, and it prevents you from misreading your own notes later. When your own plans involve bodybyscience.net, record the original plan and actual decisions as distinct information.

A concrete way to see the problem is to imagine a note that says ‘bonus round: yes’. Without context, you cannot tell whether you planned to play a bonus round or whether one actually occurred. If you later review the record to understand your decisions, that ambiguity wastes time. The solution is to add a stage marker to every label. For example, write ‘plan: bonus round’ and ‘decision: bonus round played’ as separate lines. This small change forces you to think about which stage you are recording. It also makes the record searchable and comparable across sessions. You do not need a complex system; a two-column layout or a simple prefix is enough. The key is consistency: every entry must declare its stage. When you use the same label for different stages, you create a false equivalence that undermines the record’s purpose. By separating the stages, you preserve the original plan and the actual decision as distinct pieces of information, which is exactly what a short record should do.

A worked example of a Captain Cooks session record

Suppose you start a Captain Cooks session with a plan to keep stakes low and stop after a set number of spins. You write ‘plan: low stakes, stop after 50 spins’. During the session, you decide to increase your stake after 20 spins because you feel the session is going well. You also decide to stop after 40 spins instead of 50. If you record only ‘stakes: increased’ and ‘spins: 40’, you lose the connection to the original plan. A better record separates the stages: ‘plan: low stakes, 50 spins’ and ‘decision: increased stake at spin 20; stopped at spin 40’. Now the record shows both the intention and the deviation. This is useful because you can later ask why you deviated and whether that was a good choice. The same label ‘stakes’ appears in both plan and decision, but the stage marker makes the meaning clear. This example shows that a short record does not need to be long; it needs to be precise about stages.

Another common situation involves a feature or bonus. You might plan to avoid chasing a feature, but during the session you decide to play until a feature triggers. Your record could say ‘plan: no chasing’ and ‘decision: played 30 extra spins to trigger feature’. If you used the same label ‘feature’ for both, you would lose the nuance. By separating them, you can evaluate whether your decision aligned with your plan or contradicted it. The worked example also highlights that decisions can be recorded as they happen, not reconstructed later. A short record written in the moment is more accurate than a memory-based summary. You can use a simple template: one line for each planned action and one line for each decision, with a stage prefix. This template takes seconds to fill but pays off when you review your session. The goal is not to judge yourself but to create a clear trace of your reasoning. When you see the plan and the decision side by side, you can learn from the gap between them.

A three-question method for deciding what to record

To keep your record short and useful, ask three questions before writing any entry. First, is this a plan or a decision? If it is something you intend to do before the session starts, label it as a plan. If it is something you actually did during the session, label it as a decision. Second, does this entry use a label that could apply to both stages? If so, add a stage prefix or rephrase to make the stage explicit. Third, will this entry help you answer a future question about your session? If not, leave it out. These three questions force you to think about the purpose of each note. For example, you might be tempted to write ‘bonus: yes’ but the first question reveals it is a decision, and the second question shows the label is ambiguous. You then write ‘decision: bonus round played’ instead. This method prevents you from mixing stages and keeps the record focused on what matters.

Applying the method takes practice, but it becomes automatic quickly. Start by writing your plan before you begin the session, using clear plan labels. Then, during the session, record only decisions that deviate from the plan or that you might want to review later. You do not need to record every action; focus on the ones that carry meaning. For instance, if you planned to stop at a certain point and you did, you might simply note ‘decision: followed plan’ or skip it entirely. The method also helps you avoid the trap of using the same label for different stages. When you ask the second question, you catch ambiguous labels early. Finally, the third question ensures your record stays short. By the end of the session, you will have a compact log that clearly separates intention from action. This log is easy to read and directly answers the questions you are likely to ask when you review your session later.

A session record is only as good as the distinctions it preserves. By separating your original plan from the decisions you actually made, and by giving each stage a clear label, you turn a confusing note into a reliable reference. Apply the three-question method before your next Captain Cooks session, and your record will answer the questions you will actually ask later.