How to Handle Walkovers and Byes in Sparring Brackets (Without Breaking the Draw)

A walkover sounds simple — fighter does not show, opponent advances. In practice it is the single most common reason a sparring bracket falls apart. Here is exactly how to handle byes and walkovers so your draw stays fair and your day stays calm.

The difference between a bye and a walkover

A bye is built into the bracket from the start. A 13-fighter category needs 3 byes to round up to 16. Byes are awarded at the bracket-generation stage, ideally to the top seeds.

A walkover is when a fighter who was supposed to compete does not show up — at registration, between rounds, or right before their fight. Their opponent advances without contest.

Confusing the two is where chaos starts. A bracket-aware tool keeps them separate. A spreadsheet does not.

Where to place byes in a bracket

Byes should always go to the top seeds. The order, for a 16-bracket with 3 byes:

1. Top seed (slot 1) gets a bye
2. Second seed (slot 16) gets a bye
3. Third seed (slot 9 — opposite half from slot 1) gets a bye

This is the standard 'difference of powers of 2' seeding. Done by hand it is fiddly. Done by a bracket generator it is automatic.

If you award byes randomly, two top seeds can end up in the same quarter and meet in round 2. This is bad for the fighters and bad for the spectacle.

Walkover handling — the right policy

Pick a policy before the day, write it on the entry form, and stick to it on the day:

• No-show at registration — fighter is removed entirely. Bracket regenerates with one fewer entry. Do this before brackets are printed.
• No-show between rounds — opponent advances by walkover. Recorded as 'WO' in results.
• Withdrawal due to injury — opponent advances by walkover. Injured fighter still receives any medal already secured (e.g. quarter-finalist).
• Disqualification — separate category. Opponent advances. Medal eligibility depends on your federation rules.

Why your software needs to handle this

If you have to delete a fighter from a spreadsheet and manually re-shuffle the bracket, you have lost. The system needs to support: marking a fighter as withdrawn, automatically advancing the opponent, recording the walkover in the result history, and updating the live fixture board for coaches.

TKD Manager handles all four with a single button. The bracket UI is built around the assumption that fighters will withdraw — because they always do.

Worked example: 13-fighter category, 1 walkover

Category has 13 entries. Bracket pads to 16 with 3 byes given to the top three seeds. Round 1 runs. In round 2, fighter #6 fails to show — opponent (fighter #11) advances by walkover. Fixture board updates everywhere. The next round runs as normal with no manual reshuffle needed.

The whole interaction takes about 4 seconds in a real bracket tool. In a spreadsheet, it takes 5 minutes and risks corrupting the rest of the round.