Put a laptop and a screen at the finish area. A participant walks up, and their result appears as broadcast-quality TV graphics - name, time, place, splits - on a screen you designed yourself. No app to install, no queue at the results tent.
The Result Stand is a small kiosk runtime: an idle "attract" screen that invites people in, and a result screen that renders the athlete's data into a layout you built. Both are designed in the same drag-and-drop editor - upload a background, drop placeholders, done.
Direct interaction - a camera detect or a manual entry - takes priority over the background read feed, so someone standing at the kiosk is never interrupted by the next runner crossing the line.
Pick a reading location; a new chip read there shows that runner for N seconds, then the screen returns to idle. A freshly opened stand never replays the whole race - it only shows reads that arrive after it opens.
A guide box on screen reads the number plate the athlete presents - cooperative, close-range OCR with a digit-only filter, multi-frame voting and a confidence threshold. A "Got 1234 - that you?" confirm step guards against showing the wrong athlete.
A numeric keypad for the simplest path - and the always-available fallback. If the camera can't get a clean read, the keypad surfaces automatically so nobody walks away empty-handed.
The dedicated editor is the part timers love: a live canvas on the left, a palette of fields on the right. Drag in the bib, finish time, ranks, category, splits or stage times, set the typography, and save it as a reusable template - or start from the built-in "Classic Finish" design.
{{bib}}, {{time_net}}, per-stage split fields - over your uploaded background. The right rail adds fields (event, runner, splits), controls hold-duration and the display language, and chooses which races the stand serves.
The flow is deliberately short - most of it is design, not configuration.
A finish-line screen has to be trustworthy. The stand handles the messy real-world cases gracefully instead of guessing.
Bibs can repeat across competitions. When a number is genuinely ambiguous, the stand asks which race before showing anything - otherwise it goes straight through.
Registered but not finished? The stand shows a friendly "on course / last seen at…" message. DNS, DNF, DSQ and lap statuses each get their own clear state instead of a blank screen.
In-browser recognition keeps camera frames on the laptop - nothing is uploaded or stored. The lookup honours each athlete's privacy flags, and the stand is a token-gated link, rate-limited against bib fishing.