On-site registration
A race-day entry desk where the queue keeps moving
Events taking entries on the day always hit the same bottleneck: how fast the person behind the desk can type. Most desk staff are volunteers or crew helping out for the day, not touch typists, working on a tablet or laptop in the sun with a runner standing right in front of them.
And it is not just a name. It is a thirteen-digit ID number, the Thai first and last name, the English first and last name, date of birth, gender, nationality and province — every field read off the card in their hand and typed character by character. That is several minutes per person, and a long queue on race morning genuinely can run into the start time.
The more expensive problem is the typos, because they do not stop at the desk. One missing letter in a name follows the runner onto the results page, the certificate and the result slip they post afterwards. A date of birth out by one year moves them into the wrong age group — and that surfaces when the wrong name is called up to collect a trophy in front of everyone.
All of that correction work lands on the organizer after the event, once the crew has gone home: fixing results, reissuing certificates, replying to comments on the page — and in the age-group case, a trophy that has already been handed to the wrong person.
The usual answer is more desks and more people, which helps the queue but does nothing about the typing, because the extra staff make mistakes at the same rate.
The slowest part of taking an entry on the day is typing the card out field by field. Replace that with a single photograph and the queue shortens immediately on the same desks with the same people. It is extra capacity at the entry point without extra wages or extra floor space.
The entry desk no longer has to be reserved for whoever types fastest. A volunteer who arrived that morning can run it, because the job changes from typing to photographing and checking — so you can staff the point more flexibly and brief people in less time.
A name misspelled at the desk shows up on the results page, the certificate and the result slip. Every wrong one is a correction request after the event plus a reissued document. Reading the name straight off the document removes the cause on the day.
Age groups are calculated from the date of birth, so one wrong year can move a runner into another group and put them on the podium in someone else’s place — the hardest mistake at a race to unwind, because it has already happened in front of an audience. A date read from the document cannot have its digits transposed.
Events that insure their entrants have to send correct ID numbers to the insurer, and one wrong digit means a runner with no cover on race day — which nobody discovers until something happens. The system checks that a Thai ID number really is thirteen digits before it is accepted.
Passport names are the hardest to copy and usually bring the whole line to a halt. Read from the document, the queue keeps moving, and the name on the results and the certificate matches the runner’s travel document rather than the desk staff’s best guess at the spelling.
The image is used once to read the details and is not kept, so there is no stack of copies on the registration table and no archive of ID photos left in the system afterwards — a personal-data obligation that otherwise falls on the organizer as the party holding it.
No card reader and no app to install — any phone, tablet or laptop with a camera that the desk already uses will do. The one thing you have to arrange is internet at the desk, because the reading happens on the server. At venues with unreliable coverage, keep a backup SIM: if the connection drops, the desk falls back to typing.
They are not. The image is sent to be read and deleted immediately; the only thing stored is what appears in the form, which is the same set of details runners enter themselves online. Even the system logs contain no image, name or date of birth. There is no archive of ID photos for you to look after or delete later.
Yes, and we would rather say so up front. Everything that is read appears in the form fields before saving, so staff still compare it against the document in their hand — but that is a few seconds of reading, and far harder to get wrong than typing it out. Fields that are not on the document — the distance entered, shirt size, phone number, emergency contact — are still filled in as usual.
Thai national ID cards, Thai driving licences, passports from any country, and foreign residents’ ID cards. The province field is filled only from a Thai national ID card, as it is the only one of these with an address printed on it.
No, and that is deliberate. The system reads only the characters actually printed on the document; it does not transliterate a Thai name into English, because one name can be spelled several ways and the result may not match the runner’s passport — which becomes a certificate correction later. The English name field is left blank so the runner can be asked directly. (Most Thai driving licences already carry the English name.)
Not yet. The scan button appears only when adding a new runner on site. Existing entries are tied to payments and bib numbers, and overwriting the whole set from a single photo carries more risk than the time it would save, so those records are edited by typing as usual.
Staff can type the details in as normal — nobody is required to be scanned. It does help for the crew to say clearly that the photo is only used to fill in the form and is not kept; a small sign on the desk removes most of the questions.