Building a tournament schedule that holds

Most tournaments that overrun were never going to finish on time - the arithmetic was wrong before anybody arrived. Here is the formula, three worked schedules and the mistakes that add an hour to an evening.

The formula for a round

A round takes longer than the time control suggests, because both players use their time and because rounds do not end when the last game does.

Round length

2 × base time + increment over a typical game + 5-10 minutes between rounds. For 15+10 that is about 40 minutes; for 10+5, about 27; for 5+3, about 15.

Two corrections that people leave out and then wonder where the hour went:

  • The last game decides the round. Rounds are as long as the slowest pair, not the average.
  • Registration and the opening. Thirty minutes before round one, realistically, and the prize-giving takes fifteen at the end.

Which gives the practical rule: decide the finishing time first, then pick the control and the number of rounds to fit - choosing a time control.

An evening tournament

The commonest format: a weekday evening, three to three and a half hours from arrival to prizes.

TimeWhat happens
18:30Doors open, registration desk works
18:50Entries close, pairing generated
19:00Opening announcement, round 1
19:30Rounds 2-3
20:40Break, 15 minutes
20:55Rounds 4-5
21:50Prize-giving
22:05Optional: twenty minutes going through one game

That is five rounds of 10+5. Seven rounds of 15+10 does not fit into the same evening, and promising both is the single commonest scheduling error.

A full-day tournament

  • Seven to nine rounds of rapid, or five rounds at a longer control.
  • A real lunch break. Forty-five minutes to an hour, after round three or four - not a token fifteen.
  • Short breaks between the other rounds. Ten minutes, and stick to them.
  • Start later than you think. A 9:00 start on a Saturday loses people; 10:00 or 11:00 fills the room.
  • Finish with daylight to spare if the audience includes children - a junior event ending at nine in the evening is a mistake you make once.

For a day event the break matters more than any other decision: attention collapses around round four, and a proper meal resets it - food and breaks.

Two days and festivals

  • Split unevenly. More rounds on day one, fewer on day two - people are fresher, and a shorter Sunday means fewer withdrawals.
  • Publish both days at once. Somebody deciding whether to enter needs to know when Sunday ends.
  • Expect losses overnight. Some of the field will not return on day two; plan the pairing so it survives that rather than treating it as a surprise.
  • Allow a late entry window on day one, and close it firmly. Late entries on day two break the standings.
  • At a festival, run parallel events rather than one long one. A blitz in the evening and a rapid in the afternoon draw different people than one nine-hour tournament - festival formats.

How to announce it

  • Publish the finishing time, not only the start. People plan around the end of an event, and its absence costs you entries from anybody with a train to catch.
  • Give arrival time separately from round one. «Doors 18:30, first round 19:00» prevents a queue at the desk at 18:58.
  • State the break. People decide whether to eat beforehand.
  • Announce round times aloud, with the return time. «Round four at 20:55» rather than «in a few minutes».
  • Post any change immediately. A schedule that slips silently is worse than one that slipped and was announced - where to post it.

Mistakes that add an hour

Rounds counted at one time control
the arithmetic uses base time only and ignores that both players spend it
No time for registration
the desk is still working when round one was supposed to start
Zero minutes between rounds
looks efficient on paper, never happens in a room
No break at all
past three hours people leave rather than finish
Starting late «because two more are coming»
the whole evening shifts, and the people who arrived on time pay for it
Prize-giving unplanned
fifteen minutes that were not in anybody's arithmetic

And if it is running late anyway, do the arithmetic at round three rather than round five: cutting a round or shortening the control is a decision people accept when it is announced early and resent when it is sprung on them at ten o'clock - when things go wrong.

Rounds that start on time

Pairings are generated in seconds and results go in from players' phones, so the gap between rounds is the break you planned rather than the one the paperwork forced.

Frequently asked questions about scheduling

How long does a round take?

About twice the base time plus the increment over a typical game plus five to ten minutes between rounds. For 15+10 that is roughly forty minutes; for 10+5 about twenty-seven. Remember the round ends with the slowest pair, not the average one.

How many rounds fit into an evening?

Five rounds of 10+5 fit comfortably into three hours including registration and the prize-giving. Seven rounds of 15+10 do not fit the same evening - promising both is the commonest scheduling error.

Do I need a break?

On anything over three hours, yes: ten minutes between rounds and one longer break of fifteen to thirty minutes. On a full-day event make it a proper forty-five-minute lunch after round three or four - attention collapses around there.

What should the announcement include?

Arrival time and round one separately, the expected finishing time, and when the break is. The finishing time matters most: people plan around the end of an event, and leaving it out costs entries.

What do I do if the tournament is running late?

Recalculate at round three rather than round five, then cut a round or shorten the control and announce it immediately. People accept a change made early and resent one sprung on them at ten in the evening.

The tournament app

Anyone can be the organizer

There are no club or arbiter roles in the app: the create button is available to everyone. You can announce a tournament today and run it this weekend.

  • Swiss
    when there are more than ten players and nobody should be knocked out
  • Round robin
    when the field is small and fairness matters most
  • Free meetup
    when you simply want to get together and play

More than a bot: the app, FIDE rules and a TRF report

  • The app. Besides the bot there is an app - inside Telegram and simply at vibechess.ru/app: what is on in your city, the player list, a live table, the current round, your profile and game history - everything that is awkward to read as chat messages.
  • Pairings by FIDE rules. Pairings are computed by bbpPairings, an open-source engine implementing the Dutch system: score groups, floats on an odd field, colour alternation, no rematches and no two byes in a row.
  • A TRF report. A finished tournament exports as a single file in the FIDE data exchange format - the one arbiter software and federations accept. Your profile stores the FIDE ID, national federation code, title, sex and date of birth for it.
  • Free. All of the above, with no subscriptions, paid plans or limits on the number of tournaments and players.

Full overview

Missing a feature? Message the developers

The bot is constantly improved based on real tournaments. If you need a feature that isn't there yet, message the developers right inside the bot with the /support command. Many features appeared exactly because organizers asked for them, and useful ideas get added quickly.