Writing a Fair Go session record that captures plan and decisions

A Fair Go session record that separates your plan from what you actually decided

A short session record is only useful if it lets you see, later, where your original plan met the decisions you actually made at Fair Go. The trouble is that a summary alone often hides the definition underneath it. You need to know whether you are writing a plan log or a decision log before the record can help you judge what happened.

The distinction between a plan log and a decision log

When you sit down to write a short record of a Fair Go session, the first choice is what the record is for. One interpretation treats it as a plan log: you write down what you intended before you started, such as a spending limit, a time boundary, or a list of games you meant to try. The value of that record is comparison. Later, you can hold the plan next to what happened and see whether you stayed inside your own boundaries. The definition here is forward-looking: the record exists to test intention against behaviour. If your summary says only that you played for a while and stopped, you have lost the plan, and the record cannot support that comparison. The test for this interpretation is simple: does the record contain a statement of what you meant to do before you began? If not, it is not a plan log, however tidy it looks.

The second interpretation treats the same short document as a decision log. Here the focus is on the choices you actually made during the session: when you changed a limit, why you moved from one game to another, or what prompted you to stop earlier or later than you expected. The definition is backward-looking, and its purpose is to explain outcomes rather than test intentions. A decision log is useful when you want to understand your own reasoning under pressure, because it records the moment a plan changed rather than the plan itself. The test for this interpretation is whether the record names at least one actual decision and the reason for it. A summary that says you finished ahead or behind tells you the result but not the decision, so it fails this test. Before you write, decide which question you want the record to answer, because a single short document rarely serves both purposes well.

A worked example of the same session written both ways

Imagine you planned a Fair Go session with a fixed spending amount and a rough time limit, and you intended to stick to one type of game. In a plan-log version, the record might read: intended to spend a set amount, intended to stop after a set period, intended to stay with one game type. That is a complete plan log even if the session itself is not described, because its job is to preserve the intention. Now suppose that during the session you moved to a different game type after a short while and continued past your time boundary by a small margin. The plan log still works: you can compare the three intentions with the three outcomes and see two divergences. What the plan log does not tell you is why you moved or why you continued. It shows the gap but not the reasoning, which is exactly the limit of this interpretation. Before making a decision involving fairgo, record the original plan and actual decisions as distinct information.

The decision-log version of the same session would leave out most of the original plan and instead record the turning points. It might say: switched game type because the first one felt too slow, extended time because a bonus feature was in progress, stopped when the spending amount was reached. Each line names a decision and a reason, which is the definition of a decision log. Notice that this version does not need the original plan to be useful, though the plan helps you see which decisions were departures. If you tried to merge both versions into one short summary, you would likely produce something like: played a set amount, changed games, stopped at the limit. That summary is accurate but thin, because it neither preserves the intention clearly nor explains the decisions. The example shows why you should pick one interpretation and write it fully rather than compress both into a summary that supports neither.

Deciding which record to keep for your next Fair Go session

Use the purpose of the record to choose the interpretation. If your aim is to check whether you keep your own boundaries, write a plan log: state your intended spending amount, your intended time boundary, and any game-type intention before you begin, then add a short outcome line after you finish. That structure lets you compare intention with behaviour without needing to explain every decision. If your aim is to understand your own choices when they change, write a decision log: note each moment you altered a limit, switched games, or changed your stopping point, and add the reason in a few words. The decision log is more useful when your plans tend to shift mid-session, because it captures the shift rather than only the gap. Ask yourself which failure you are more likely to repeat, ignoring a plan or failing to notice a change, and let that answer choose the format.

Whichever you choose, keep the record short enough that you will actually write it. A plan log needs only three or four lines before the session and one line after. A decision log needs one line per turning point, and most sessions have only a few. Do not mix the two formats in the same short document unless you clearly label which lines are intentions and which are decisions, because a reader returning to the record later will otherwise confuse the plan with the outcome. If you are unsure which interpretation fits, write the plan log first, since it is faster and gives you a baseline. After two or three sessions, review whether the record answered your question. If it showed gaps but not reasons, switch to a decision log. If it showed reasons but no baseline, switch back. The record is a tool, and its format should follow the question you actually want answered.

Neither interpretation is wrong, but you must choose one before the record can guide you. If your summary already states the outcome, add the definition that supports it. If it only states the plan, mark clearly where actual decisions diverged. That is the resolution of the opening situation: the record becomes useful once you know which question it answers.