Shaun Deeb Poker: Reading Event Schedules and Entry Lists Like a Fan

Shaun Deeb Poker editorial ·

A winning hand of blackjack (21) with a large pile of poker chips on the table. Like much of our work, we have put all these images in the public domain. Feel free to use them but please credit out site as the source if you do: TaxRebate.or
Illustrative image. Images Money · CC BY 2.0 · Cropped and resized. Image source

Shaun Deeb Poker publishes updates, tournament storylines, player branding material, and coverage connected to the PokerBlast network through shaundeebpoker.com. For a fan trying to follow that material well, the most useful skill is not memorizing results but understanding the structure behind them. Tournament outcomes depend on the event format, the size of the field, the blind levels, and the number of players who advance. Learning to read those framing details lets you judge a story about a tournament run on its actual merits rather than on its tone. This article walks through a method built around three sources of structure: the event schedule, the entry list, and the blind and payout framework. None of these tools guarantees an accurate reading of any single run, but together they give a fan a set of questions to ask before accepting a narrative.

Start With the Event Schedule, Not the Headline

A tournament update is easier to interpret once you know where it fits on the calendar. Tournament series often run multiple events over several weeks, with different buy-ins, formats, and start times. A player may appear in a dozen events in a single series and skip several others. Before reading a story about a result, look up the published schedule for the series in question and note the event number, the buy-in, the format (for example, no-limit hold'em, pot-limit omaha, or a mixed game), and the day it was played.

Schedules also explain why coverage looks uneven. A player who plays the high-buy-in events may appear less often in updates than one who plays many smaller events, simply because the field sizes and prize pools differ. Recognizing that pattern prevents you from reading a gap in coverage as a gap in activity. A quiet week may reflect a schedule with few events of interest, not a withdrawal from competition.

When you can, record the schedule in a simple table with columns for date, event name, buy-in, and the outcome you have seen reported. Over a season this table shows you which results have been reported and which have not, which is more informative than any single post.

Read Entry Lists and Field Size as Context

A result carries different weight depending on the size of the field. Finishing deep in a 60-player event means something different from making a day-two run in a 5,000-player event, because the chance of advancing differs enormously. Before accepting a description of a run as impressive or disappointing, find the number of entrants and the number of players who paid out. Many series publish this information after an event concludes, and comparing it to the reported finish gives you a rough sense of the achievement.

Entry lists can also reveal who else was competing. A strong field in a particular event explains why a deep run was difficult, while a thin field may mean the same finish carried less competitive weight. Ask whether the story you are reading includes this context. A post that celebrates a finish without mentioning the field size is asking you to supply the judgment yourself, and that is a reasonable thing to notice.

Field size is also a useful check on hype. When a result is described in superlatives, put the number of entrants and the number of paid places next to the claim. If the numbers do not support the language, the language is doing the work the facts should do.

Use Blind Levels and Chip Counts to Judge Pace

Live tournament updates often report chip counts, blind levels, and the number of players remaining. These details tell you how a run was going at a given moment. A player with a large stack at a high blind level is in a different position from one with a short stack and the same number of chips in big blinds, since the second player is under pressure to act sooner. When a story mentions a chip count, convert it into big blinds if you can. That single step turns a raw number into a measure of how much room a player had.

Timestamps matter as well. Updates posted in real time are not always posted in order, and a fan following a live event can end up reading a later development before an earlier one. Keep a simple log of the time each update was posted and the level it describes. This habit, sometimes called a timeline method, helps you rebuild the sequence of a run accurately rather than relying on whichever post appeared most recently.

The main caution is that chip counts are snapshots. A player's position can change quickly, and a mid-level update does not tell you how the run ended. Wait for the final reported result before forming a conclusion about a tournament.

A Short Checklist for Reading Any Poker Update

Before you accept a tournament story, work through a few questions in order. First, what event is this, and when was it played? Second, how large was the field, and how many players were paid? Third, what were the blind levels and the player's stack in big blinds at the most recent reported point? Fourth, what time was the update posted, and does it describe the latest known state of the event? Fifth, does the story state what is known and what is inferred, or does it blur the two?

Sixth, consider the framing. Is the story focused on the player's actual results, or on branding, personality, or future expectations? Stories about player brands can be entertaining and informative about how a player presents themselves, but they answer different questions from results reporting. Seventh, check whether the material is connected to a sponsor, a network, or a promotional relationship. Coverage from a network that includes a player's own channel may still be useful, but knowing the relationship lets you weigh it accordingly.

None of these questions guarantees an accurate picture, but each one narrows the gap between what is reported and what happened. Used consistently, this checklist turns a feed of updates into a body of evidence you can actually assess.

Building a Season Record You Can Trust

The strongest way to follow a poker player over time is to keep your own record rather than relying on memory or on whatever a feed happens to surface. A season log can be a spreadsheet or a notebook with one row per event. Record the date, the event, the buy-in, the field size, the reported finish, and the source you used. Add a column for whether the result was confirmed by a second source. Over several months this record shows patterns that no single update reveals, such as which formats a player favors or how consistently they reach later stages.

Keep the log honest by recording gaps as well as results. If a player entered an event but no result was reported, write that down rather than leaving the row blank or filling it with a guess. Gaps are information. They tell you where your sources were silent, which makes future conclusions more careful.

A log like this will not predict future results, and it should not be used to make financial or betting decisions. Its value is interpretive: it lets a fan read the story of a season against a clear and verifiable record. That is a durable form of understanding, and it rewards the patience that poker coverage often tests.