Writing a Captain Cooks session record of what was planned and decided
You have finished a session at Captain Cooks and want a short record that is genuinely useful later. The point is not to predict what happens next or to relitigate every spin. It is to capture the original plan, the decisions you actually made, and where the two diverged, so the record explains the completed action on its own terms.
Separate the plan from the decisions
The most common weakness in a session record is that the plan and the decisions blur into one narrative. You write what you intended, then describe what happened in the same breath, and a later reader cannot tell which statements were made before the session and which were made during it. Keep them apart. The plan belongs in one short block, written as intentions: limits you set, how long you meant to play, which parts of the Captain Cooks lobby you intended to use, and any rule you gave yourself about stopping. The decisions belong in a second block, written as events: what you actually chose, when you changed course, and what prompted the change. Separating the two makes the record auditable, because anyone reading it can see whether a decision was consistent with the plan or a departure from it.
Being specific about the nature of each entry matters as much as the separation. A plan entry is a statement of intent and cannot be wrong; a decision entry is a statement of fact and can be checked against your memory, your notes or the account history. Do not dress a decision up as a plan by writing it in the conditional. If you raised a limit or ended earlier than intended, record that as a decision with its reason, not as something you had always meant to do. The record is more useful when it admits departures than when it presents a tidy story in which everything went to plan. A short record that shows one clear divergence teaches you more than a long one that shows none. Long, polished narratives tend to hide the interesting part, which is usually the moment the session stopped following the script.
A worked example of a short record
Suppose your plan was to spend a set amount, play for about an hour and stop when that amount was gone. Your decisions, in reality, were to start in the slots area, move to a table game after twenty minutes because the slot session felt flat, and finish forty minutes in after reaching your spending limit early. A weak record says only that you played at Captain Cooks for forty minutes and stopped. A useful record has three lines: the plan as written before starting, the two decisions with their reasons, and a note that the session ended ahead of the planned duration because the limit arrived first. That is enough for a later reader to reconstruct the shape of the session without any speculation about what might have happened. While looking at the options around https://bodybyscience.net/, record the original plan and actual decisions as distinct information.
Now look at what this example deliberately leaves out and why. It does not estimate whether the table game was a better choice, and it does not suggest what to play next time. Both would be predictions dressed as observations, and you are reviewing a completed action, not forecasting. It also does not include every individual bet, because a session record is a summary of decisions, not a transaction log; the account history already holds the detail. What it does include is the one piece of missing evidence that matters: the exact time the limit was reached, noted as unverified if you are reconstructing from memory. Marking a gap plainly is better than filling it with a plausible guess, because a guess in a record becomes a false fact the next time you read it.
Decide what the record needs before you close it
Once the draft exists, apply a simple test before treating the record as finished. Read each line and ask whether it is a plan, a decision or a gap. Lines that are none of these are probably commentary and can be cut. Then check the gaps: for each one, ask whether it changes the story. If a missing detail would not alter how you understand the completed session, leave it as a noted gap and move on. If it would, identify the smallest proportionate step to resolve it, such as checking your Captain Cooks account history for the session’s start and end times, or confirming a deposit record against your own bank statement. That is verification of a past event, not preparation for a future one, and it should be limited to the facts the record actually depends on.
Proportion matters here. A record of a short session does not need forensic completeness, and chasing every timestamp turns a five-minute task into an afternoon. Set a boundary in advance: resolve gaps that affect the plan-versus-decision comparison, and mark the rest as unverified. If the account history and your memory disagree, record the disagreement rather than silently choosing one. That single habit keeps the record honest and stops small uncertainties from hardening into false certainty. When the gaps that matter are resolved or clearly flagged, the record is done. Close it with the date and a one-line summary of the completed action, then stop writing. A record that ends cleanly is more trustworthy than one that trails off into speculation about what you might do differently.
A useful record of a finished Captain Cooks session is short, factual and honest about what it cannot show. Write the plan, the decisions, the divergences and the missing evidence in plain sentences. Then decide whether anything needs verifying before the record is treated as complete. That is a proportionate close to a completed action, not a forecast of the next one.