Building a Tournament Update Log That Holds Up Over Time
Tournament updates arrive in fragments. A result posts in the middle of a day, a chip count shifts between levels, and a storyline gets reframed a week later when the final table airs. Fans who follow poker closely often find that their memory of a run is shaped more by the order they encountered information than by what actually happened. A simple written log can fix that. It gives you a single place to record what was reported, when it was reported, and where it came from, so that your understanding of a player's tournament path rests on a timeline rather than on whichever clip circulated most recently. This article walks through how to build that log and how to use it when you read tournament updates on shaundeebpoker.com or anywhere else.
Decide what the log is for before you start
A tournament log can serve several purposes: following one player across a season, comparing performances at a single event series, or keeping track of a broader field of players you care about. The purpose determines what you record. A season tracker needs event names, dates, buy-in levels, finishing positions, and notes about the stage reached. A storyline tracker needs more context, such as what a player said about their approach or how a public narrative developed over several weeks.
Write one sentence at the top of the document describing the goal. For example: 'Track Shaun Deeb's reported tournament results and the storylines attached to them for one series.' A clear sentence keeps you from adding columns you will never use and from skipping details you will later wish you had.
Choose the fields that make updates comparable
Most useful logs share a core set of fields: date reported, event name, date of play if different, stage reached (for example, bubble, money, day two, final table, or final placement), the update's source, and whether the information was a live report, a recap, or a later confirmation. Keeping the source and update type separate matters, because a live post made mid-event may later be superseded by a final result, and you want both visible.
Add a short notes field for the context a bare result leaves out. A finish at a deep stage of a large field means something different from a finish at a smaller event with fewer entrants, and a note about field size prevents you from reading two numbers as if they were equivalent. Record the number of entrants when it is reported, and leave the cell blank when it is not. Blank cells are honest; guessed numbers are not.
Separate live updates from confirmed outcomes
Live tournament coverage is valuable because it is fast, but speed creates errors. Chip counts can be reported at one level and changed later. Eliminations can be announced before the paperwork is final. A good log distinguishes provisional entries from confirmed ones. Mark a row as provisional when it comes from a live feed, a social post during play, or a single unverified remark, and update the same row when a recap or official results page confirms or corrects it.
Do not delete the provisional entry when you confirm the result. Instead, add a second row or a revision note. This preserves the history of how your understanding changed, which is useful if you later notice that a narrative built on an early report never matched the final outcome.
Track storylines as their own thread
Tournament results and tournament storylines are related but not identical. A storyline might be a player's return after time away, a notable run from a short-stacked position, or a rivalry that gets discussed across several events. Keep storylines in a separate tab or section so that a single dramatic result does not overwhelm your sense of the broader pattern.
For each storyline, record the first date it appeared, the event where it was discussed, and what claim was made. Then record whether later results supported, complicated, or ended it. Many poker narratives feel stronger in the moment than they look when laid out in sequence, and a storyline tab makes that gap visible.
A short checklist before you trust an update
Before adding an update to your log or repeating it to someone else, run through a few questions. Is the date of the report clear, and is it separate from the date of play? Does the source state what it observed, or does it interpret an outcome without showing the basis? Has a later report, such as a final results listing or an event recap, confirmed the detail? Is the update about a result you can verify, or about a feeling or prediction that belongs in the storyline tab instead?
If you cannot answer these questions, log the item as unverified and move on. A log with fewer confirmed entries is more useful than one padded with unchecked claims. Over a full season, the discipline of marking uncertainty will give you a far more reliable picture of any player's tournament path than memory or highlight clips alone.