A ranking formula is only as good as the results fed into it. Most disputes are not about the formula but about data: a wrong date, a misspelled name, a duplicate athlete, a result recorded in the wrong weight class. Federations that get data right have fewer disputes and faster verification.
Collect official results at source
- Use standard result sheets at every event: bout number, athletes, corners, weight class, result, method, round, time, officials' signatures.
- Collect them before officials leave the venue.
- Publish results within days.
One register of events
Every event should have one record, with name, city, date, organiser and level. Duplicate event records split results and confuse verification. At KBN, events are coded and applicants' unknown events are created as custom events without a level until HQ decides.
One register of athletes
- One athlete, one ID. KBN's motto is "One fighter. One ID. One verified record."
- Match names exactly to identity documents; record transliteration variants.
- Merge duplicates rather than keeping two records. At KBN, merging duplicate fighters is a super-administrator action.
Consistent classifications
| Error | Fix |
|---|---|
| Same event entered twice with different names | Keep one event record; link all bouts to it |
| Athlete recorded under two spellings | Merge records; store the variant |
| Method recorded as KO when the sheet says TKO | Always copy the official sheet |
| Bout in wrong weight class | Use the official weigh-in and bout weight |
| Date format confusion (day/month) | Use unambiguous dates, e.g. 16 May 2026 |
| Amateur bout recorded as professional | Take the category from the event ruleset |
Verification
Verify each result against an independent source before it counts. At KBN, results from athletes and referees enter as pending and count only after verification, with rejections carrying a reason.
Corrections
Mistakes will happen. Have a documented correction process: who can correct, what evidence is needed, and a log of every correction. At KBN, corrections are made through audited decisions and the engine recalculates the tables; points are never edited by hand.
How results are verified after an event →
A standard result sheet
| Field | Example |
|---|---|
| Event name and date | National Championship, 16 May 2026 |
| Bout number | 7 |
| Division | Amateur Men's Kickboxing Welterweight |
| Red corner | Full name, club, country |
| Blue corner | Full name, club, country |
| Result | Red win |
| Method | TKO (referee stoppage) |
| Round and time | R2 1:47 |
| Officials | Referee, judges, supervisor (signatures) |
Using a standard sheet at every event makes verification fast and consistent.
Myths and facts
| Myth | Fact |
|---|---|
| Small errors do not matter | A wrong date can move a result into a different time-value band |
| Duplicates are harmless | They split records and distort rankings |
| Corrections should be quiet | Corrections should be logged and explained |
| The formula fixes bad data | The formula is only as good as the data |
Example: a date error
A bout entered as 3 November instead of 11 March (a day/month mix-up) can move a result from 100% to 50% time value, or the reverse. Unambiguous dates prevent this.
Measuring data quality
Federations can track a few simple indicators each quarter:
- Share of events with official result sheets collected on the night.
- Average time from event to published results.
- Number of duplicate athlete records found and merged.
- Share of results rejected for data errors.
- Number of corrections after verification.
Improving these numbers speeds up verification and reduces disputes.
Training volunteers
Results officers and data volunteers need a short briefing: how to fill the standard sheet, how to write unambiguous dates, how to record methods exactly and who to ask when something is unclear.
Names across scripts
Athletes' names may appear in different scripts and spellings across passports, posters and result sheets. Store the name exactly as on the identity document, record known variants, and match on more than one attribute (date of birth, club, weight class) when checking whether two records are the same person.
Frequently asked questions
QWhy not let athletes enter their own results directly?
They can submit them, but results must be verified against official evidence before they count.
QHow should we handle athletes with names in different scripts?
Record the name as on the identity document, and store variants used on fight cards.
QWhat should we do about duplicate athlete records?
Merge them into one record, keeping all verified bouts.
QCan points be corrected manually?
At KBN, no. Corrections are made to the underlying bout or event decision, and the engine recalculates.
Figures in this article are computed from the KBN register at the time of reading. View, like and share counters on this demo site are sample values.