Control Table Staff (Graphiqueur)

Most boulodromes sit at the edge of mobile coverage, and venue Wi-Fi is often a single overloaded router. If the draw engine depends on the cloud, a five-minute outage blocks 50 matches and ripples across the rest of the day.

The graphiqueur needs the same engine to keep working on the local device, queue changes for sync, and produce printed start lists at every stage so the event can continue on paper if all electronics fail. Paper backup is also a federation requirement at sanctioned events.

The control table app ships the draw engine locally, runs all generation on-device and syncs results when connectivity returns. Each generated round automatically queues to the connected ESC/POS or A4 printer with start lists, court assignments and referee sheets in the federation's preferred layout, giving a paper fallback the federation will accept and a recovery point if the device itself fails mid-event.

Late entries arrive minutes before the cut-off, payments fail and reappear, and a single seeding correction can shift 30 matches across multiple courts and rounds. Without audit logs the graphiqueur cannot prove later that the published draw was correct, and disputes about who-played-whom escalate to the jury and consume hours of post-event review.

Single-click rebracketing keeps the schedule on track when the queue at the desk is twenty captains deep; the audit log keeps the result defensible weeks later.

Each entry change writes an immutable event with operator, timestamp and reason. The bracket regenerates deterministically from that history, so any version can be reconstructed.

Late entries, withdrawals and seeding edits each surface a single rebracket action with preview. The audit log exports alongside the final results as part of the federation submission.

Between rounds the venue is loud, captains gather at the control table, the public address is calling teams to the bar terrace and the director is asking when the next bracket will be ready. The graphiqueur needs to generate, validate and publish in a window of 5 to 10 minutes, working in two languages and with an overflowing inbox of late results.

A preview that surfaces seeding clashes, court double-bookings and referee conflicts before publication prevents the embarrassing recall of a printed list and the cascading delays that follow.

Rapid-draw mode generates a candidate bracket, runs validation against a configurable rule set (no rematch within poules, balanced rest, court-distance rules, referee availability) and surfaces warnings inline with one-tap fixes. The graphiqueur resolves or accepts each warning and publishes; the new round simultaneously hits the public board, court tablets, the player app and the connected printers.