You open the lobby at 8 p.m., see three tournaments with registration open, and jump into all three. Half an hour later you’ve got two satellites running on top of them, the fourth tournament you actually wanted to play starts when your brain is already slowing down, and the last one wraps up at 1 a.m. Your tournament selection was fine: what was missing was spreading those entries out over the day.
A time-block schedule flips the order of your decisions. First you set the windows of the day when you’ll register and how many tables you can handle in each one, then you fill those windows with tournaments that fit. The schedule pays off because the same tournaments now fit into your day without a ten-table peak at 10 p.m. and without dead time at 3 p.m. The sections below build that schedule from scratch: blocks, overlap, table cap, empty windows, time zones, and what to save so you can repeat it next week.
What is a time-block schedule, and what doesn’t the lobby show you?
A time-block schedule is your list of tournaments laid out on a timeline: every entry has a start time, a late reg close time, and an estimate of how long it could run. The lobby shows what’s starting now. The schedule shows what you’ll have on your hands three hours from now.
An online poker client’s lobby is sorted by what the site cares about: highlighting what’s opening registration, the biggest guarantee, what’s about to close. It answers just one question, “what can I register right now,” and it answers it for one site only. If you play on two or three sites, you’ve got two or three lobbies that don’t talk to each other, and none of them knows you already have four tournaments running.
Your poker schedule is what handles the running total. It puts tournaments from different sites on a single clock, marks their likely duration, and shows you the point in the day when everything piles up. That’s the job a tournament schedule manager does, and it’s why players who grind for hours at a time stop making decisions inside the lobby: the decision to register gets made earlier, with the whole day on screen.
One practical detail changes how useful the schedule is: log the late reg close time, not just the start time. The start time tells you when the table opens. The end of late registration marks the start of the heavy stretch, when nobody else can enter and all your tournaments start demanding decisions at the same time.
How do you split the day into registration blocks instead of one-off entries?
Pick two to four fixed windows in the day for registering, and treat each one as a window that opens and closes. Outside those windows, you don’t register, even with a good tournament on screen.
A block has three pieces of information: open time, close time, and table cap. Example for someone who plays at night: block 1 from 7 to 8:30 p.m., block 2 from 9 to 10 p.m., nothing after 10 p.m. The tournaments registered in block 2 are the last ones in for the day, so they’re the ones that decide when the session ends in the worst case. Full-time players apply the same logic with three blocks: one in the afternoon, one in the early evening, and a short one for late reg only.
The reason to close the window is simple math. Every new registration pushes the end of your session back, because a regular-speed tournament keeps going for hours after registration closes. A tournament registered at 11:30 p.m. can keep you busy into the early morning, since what you’re adding to your day is all the remaining time in that tournament, not the thirty minutes you had in mind.
Within the block, the selection criteria are the same as always: format, structure, and buy-in that fit your bankroll, which the guide on how to choose which tournaments make your schedule covers in detail. The difference is that each candidate now competes for a spot in a capped block instead of landing on an endless list.
How do you spot tournament overlap before you click register?
Draw each tournament as a horizontal bar across the day’s clock and look at three points: where the registration periods cross, where late regs close together, and where the decisive stages coincide. The overlap that hurts is the third one.
Overlapping registrations don’t cost much: clicking three buttons in five minutes is trivial. The problem shows up one to two hours after late reg closes, when fields have shrunk and every table starts demanding short-stack decisions. If three tournaments close registration at 9 p.m., your difficulty peak lands around 10 p.m., and that’s when you’ll be making bubble all-in decisions on three screens at once.
Concrete fix: two regulars and a turbo all opening at 8 p.m. create a triple peak at 10 p.m. Swap one of the regulars for another that opens at 9:30 p.m. and the peak splits, one around 10 p.m. and another around 11:30 p.m. The total number of tournaments in the day is the same, and the number of hard decisions per minute drops. Getting those decisions wrong is expensive because chip value stops being proportional near the money, the effect that ICM describes: busting on the bubble because you couldn’t give the spot enough attention is a straight loss of EV.
How many registrations fit in a block before the tables pile up?
The cap that matters is simultaneous tables at the block’s peak. The number of registrations only matters as the path to that peak, and you can estimate it before clicking: count how many tournaments in the block should still be alive ninety minutes after the last registration closes.
The rough math goes like this: add up the tournaments in the block, set aside the turbos and hypers, which finish earlier, and assume some of the regulars bust before the peak. What’s left is your likely range of simultaneous tables. If your comfortable limit is six tables, registering eight tournaments in a thirty-minute window puts you over the limit on a lot of days.
When the math blows up, there are two adjustments. Cutting registrations from the block is the direct one. Changing structure is less obvious: swapping a long-structure regular for a hyper that finishes in about an hour changes the shape of the peak, because the extra table exists for less time. Changing the start time works the same way, since the same tournament half an hour later no longer adds to the peak.
That cap deserves to be measured, not estimated from memory. Write down your simultaneous tables at the worst point of every session for two weeks and compare them with your results: the point where your hourly rate stops going up is your real cap, and it can be a lot lower than the number of tables you can physically click through.
Where should you leave empty windows on purpose in your schedule?
Leave one empty window between blocks, in the middle of the day, and another at the end, after your last registration block. They do two jobs: absorb deep runs and guarantee a physical break.
A schedule with no slack only works on days when you bust early. On a good day, when two tournaments go deep, the extra time has to come from somewhere: from the next tournament, played on autopilot, or from your sleep. The empty window is where that time comes from at no cost.
Example: if your last block closes registration at 10 p.m., leave 11 p.m. to 12:30 a.m. with nothing scheduled. If you’re still alive, that window is your final table space. If you busted, the window becomes the end of your workday and you quit early, without firing a consolation entry just to fill the time.
The middle window is for eating, getting up, and reviewing the day. It has to sit at the point where the previous block should already have wrapped up most of its tables, not in the middle of it. For short breaks within a block, what you have is the tournaments’ own scheduled breaks, which tend to fall on the same minute across different sites and are worth marking on your schedule like an appointment.
How do you handle tournaments in different time zones on the same schedule?
Convert everything to your local time once, when you build the schedule, and write the local time on it. Converting at the moment you register is where mistakes happen.
International series publish their calendars in the site’s time, which is usually a reference time zone different from yours. That creates two problems. The first is the same tournament showing up with different times in different materials, and you register the 7 p.m. one thinking it was 7 p.m. local. The second is daylight saving time: many countries change their clocks twice a year and others, like Brazil, don’t, so a schedule saved in March can be off by an hour in November.
Concrete fix: on your schedule, the time column is always local, with the original time in parentheses next to it as a reference to check against the lobby. Day to day, the alternative is to start from a list that’s already converted, like today’s tournament schedule by site, and save manual conversion for when you’re building your week from a series calendar.
Tournaments that run past midnight need extra care. A tournament that starts at 11:30 p.m. in your time zone and has four hours of registration belongs to the early hours of the next day, and that’s the day it should go on your schedule, in the matching block. If you count that tournament on Tuesday, you end up with a Wednesday that looks light on the spreadsheet and turns out heavy in practice.
Fixed schedule or rebuilt every day: what changes in your results?
A fixed schedule gives you routine and lets you compare weeks. A schedule rebuilt every day makes better use of calendars that change, like series calendars. The setup that works for most players is a fixed skeleton with variable content: blocks and table cap stay put, the tournaments inside them change.
| Criterion | Fixed schedule | Schedule rebuilt every day |
|---|---|---|
| Prep time per day | Close to zero after the first build, just occasional tweaks | A few minutes to half an hour, every day, to scan the calendar |
| Routine predictability | High: on Monday you know what time Thursday ends | Low: the end of the session shifts based on what you registered that day |
| Taking advantage of new calendars or series | Low: tournaments that show up outside your blocks get left out | High: each day is built from whatever’s running that day |
| Overlap risk | Lower, because the overlap was solved once and stays solved | Higher, because every new combination of start times has to be checked again |
| Ease of measuring results | High: volume is stable, so swings in results have fewer possible causes | Low: volume and selection change together and are hard to separate |
| Fit with a fixed-hours job | Good: blocks are set around your calendar and don’t compete with it | Poor: tournament start times tend to drive the decision and spill into the rest of your day |
The difference really shows when you’re evaluating a bad month. With a fixed schedule, volume is constant, so a drop in results has only a few possible explanations: selection, play, or variance. With a schedule rebuilt every day, you never know if the month was worse because of the tournaments you picked, volume that fluctuated, or a table peak that went over your cap in half your sessions.
How do you save a schedule that worked and repeat it next week?
Save your schedule by day of the week, in three layers: the blocks, the tournaments in each block, and what actually happened. Without the third layer, you’re just repeating the same mistakes more precisely.
Splitting by day of the week is necessary because Tuesday’s calendar isn’t Sunday’s: Sunday has bigger fields, longer structures, and later finishes, so the final block needs to close earlier, not later. A single schedule for all seven days forces you to choose between wasting Sunday or overloading Tuesday.
The log of what happened can be short. Peak table count, whether you registered outside a block, which block ran late, and what time you actually quit: four lines a day are enough for next week’s version to be an edit, not a rebuild.
A spreadsheet can handle that first version. The limit shows up when you play on more than one site and the calendar changes every week, because keeping start times, buy-ins, and guarantees updated by hand eats up the time the schedule was supposed to save. That’s the work a tournament tool takes over, by giving you a calendar that’s already filtered and in your time zone.
Before deciding where to keep your schedule, it’s worth separating what each type of software does, because building a schedule, tracking hands, and studying are different problems that rarely live in the same program. The poker tools comparison puts those categories side by side and helps you avoid buying a tracker expecting it to organize your day.
Conclusion
The decision that drives a time-block schedule comes before any tournament: how many simultaneous tables you play well and in which windows of the day. Once those two numbers are set, the rest is fitting pieces in, and the lobby goes back to being what it is, a catalog to check after your schedule has already told you what fits where. Flip that order and you end up with a day decided by tournament start times, which were picked by the site, not by you. Start with two blocks, a table cap measured in your own sessions, and an empty window at the end of the night. That’s the minimum, and it already changes the shape of your day.
Frequently asked questions
How do I build my first time-block schedule in practice?
Start with the blocks, not the tournaments: pick two windows in the day when you can play without interruption, set the time each window stops taking registrations, and set a table cap for each one. Only then look for tournaments that start within those windows and will probably finish before your cutoff time.
Where do I find the tournament list, and how do I filter by game type and buy-in before registering?
The site’s own lobby is the primary source and lets you filter by game, format, and buy-in range, and it shows start time and late reg close time. External lists that aggregate multiple sites are for the step before that, when you’re still deciding which tournaments go into your blocks, because they let you compare start times from different sites on the same clock.
Can I get a notification before a tournament starts?
It depends on the site and the app: some offer alerts when a tournament starts or registration opens, others only offer early registration, which already locks in your seat. Check on the site you use before building a schedule that counts on that alert, and treat the alert as backup, because a schedule that only works with a notification is poorly spaced out.
What is grinding, and what does a schedule have to do with it?
Grinding is putting in volume in a repeated, planned way, focused on results over months rather than a single night. The schedule is the tool that makes that volume sustainable, because it spreads your entries across capped blocks instead of cramming everything into the time slot where the site put its biggest tournaments.
Does a time-block schedule make sense if I only play two or three tables?
It does, and the benefit shows up somewhere else: instead of lowering your peak table count, the schedule protects your bedtime and stops impulse registrations late at night. If you’re just starting out, it pairs well with a simple selection criterion, like the one in the guide on how to choose your first tournaments, and the result is a two-hour routine you can repeat all week.
What’s the right number of simultaneous tables?
There’s no universal number, and you find yours by measuring: write down the peak table count and the result of each session for a few weeks, and look for the point where more tables stop improving your hourly rate. That point is the cap worth writing into every block of your schedule, and it changes when you switch formats, because hypers demand more attention per minute than regulars.
