Race day on Bield
Race day tools on Bield are split by role. Organisers get a registration desk (admissions + parking). Marshals on post can record bib passings at checkpoints when split timing is enabled. The race’s Active status fires automatically once the start date and time are reached.
Prerequisites apply to each tool. The admissions desk and parking panel are available to organisers for any race in Active status. Split timing (checkpoint capture) must be enabled in the race’s Features tab before race day — it cannot be turned on retroactively once the race has started.
| Tool | Who uses it | What it does | Prerequisite |
|---|---|---|---|
| Admissions desk | Organiser | Search or scan entrant bibs; mark arrived; see live counts | Race in Active status |
| Parking control | Organiser | Toggle parking-paid per entrant; track unpaid | Race in Active status |
| Bib / QR scan | Organiser | Camera-based barcode or QR read — same result as typing the bib | Chrome on Android (camera access); iOS / Firefox fall back to manual entry |
| Marshal check-in | Marshal | Tap “I’m on post” to log physical arrival; organiser sees live post coverage | Marshal assigned and confirmed for a post |
| Checkpoint capture | Marshal Organiser | Enter a bib number when a runner passes — recorded as a checkpoint passing for results | Split timing enabled in Features tab |
| Bib allocation | Organiser | Assign bib numbers to entrants from the Race Day tab; view allocated vs unallocated | Race in Active or Published status |
| Incident reporting | Marshal | Quick-pick incident report (runner in distress, safety hazard, etc.) sent to organiser with GPS location | Marshal assigned and on post |
| Live progress | Runner | Runners’ support teams (Supporters, pacers, crewers) can view live progress as checkpoint passings come in | Split timing enabled; passings recorded by marshals |
Bib allocation
Organisers can assign bib numbers to entrants from within Bield — useful if you want bibs visible in your Bield engagement list and shareable with runners' support teams before race day.
- Go to the Race Day tab → Bibs From your race editor, select the Race Day tab and then Bibs.
- Allocate individually or in bulk Type a bib number next to an entrant's name, or use Auto-assign to number all unallocated entrants sequentially from a starting number you choose.
- Bibs are immediately visible to the runner Once assigned, the bib number appears on the runner's engagement page. Their Supporters, committed pacers, and crewers also see it automatically.
Bib assignment in Bield is for informational sharing — it is separate from any timing chip or official race bib managed by your timing company. The two are independent.
Admissions & race-day check-in
The admissions panel is the registration desk in your pocket. It is available from the race editor under the Race Day tab once a race reaches Active status.
- Open the Race Day tab Go to your race in the organiser dashboard and select the Race Day tab. You’ll see two panels: Admissions and Parking. Select Admissions.
- Find an entrant Type a name or bib number into the search box. Results filter as you type. Alternatively, use the Scan bib button to open the camera scanner (see Bib & QR scanning below).
- Mark as arrived Tap the check-in button next to the entrant’s name. Their status updates immediately. Running totals at the top of the panel show arrived / total entrants in real time.
- Undo a check-in Tap the undo button (available for 15 minutes after check-in) if you made an error. The count reverts.
Who is in the admissions list? The list is built from everyone who has added the race to their Bield engagements. It does not replace your entry list — runners who registered on your own ticketing site but haven’t added the race on Bield will not appear here. Use it alongside your entry CSV, not instead of it.
Parking control
The Parking panel gives you a one-tap paid / unpaid toggle per entrant — useful at events where parking is managed separately from entry.
- Find an entrant by name or bib (same search as admissions).
- Tap the Parking paid toggle to record payment. The timestamp is saved automatically.
- Untoggle to reverse if needed.
- The panel shows a running count of paid / unpaid across all entrants.
Parking status is separate from race check-in. An entrant can be checked in but unpaid on parking, or vice versa. Use each panel independently.
Bib & QR scanning
The Scan bib button in the Admissions and Parking panels activates the device camera to read a barcode or QR code printed on a runner’s bib. This avoids manual typing at busy check-in desks.
| Browser / device | What happens |
|---|---|
| Chrome on Android | Camera opens; BarcodeDetector API reads barcodes and QR codes in real time |
| Safari on iPhone / iPad | BarcodeDetector not supported — camera button is hidden and manual bib entry is shown instead |
| Firefox (any platform) | BarcodeDetector not supported — manual entry shown |
The scan loop runs continuously until you tap Stop scan or switch panels. Each successful scan runs the same check-in or parking-paid logic as a manual entry — the result is immediate with optimistic UI.
NFC (Android / Chrome only). There is also an NFC tab in the Race Day panel for organisations that use NFC tags on runner wristbands. This requires Android + Chrome and an NFC-capable device. It is not available on iOS — the tab will explain this when displayed on an unsupported device.
Marshal check-in on race day
Marshals confirm their physical arrival at their post by tapping I’m on post in their volunteer panel. This is covered in the Marshals & volunteers guide, but here is the race-day flow at a glance:
- Open the Bield app and find your race Your assigned race appears in Me → My races. Tap it to see your post assignment.
- Tap “I’m on post” This confirms you’re physically at your checkpoint. Status moves from Confirmed to On post.
- The organiser's volunteer board updates live Organisers see a real-time view of which posts are covered, which are still empty, and who has checked in. They can send a “call for help” ping to volunteers near any uncovered post.
- At the end of your stint Tap Mark completed when the last runner has passed and your post is closed. The gig is recorded to your marshal profile.
Checkpoint capture (split timing)
When the organiser has enabled split timing in the race Features tab, marshals at checkpoints can record runner passings by entering the runner’s bib number. This creates a timestamped split record that feeds into the results.
Must be enabled before race day. Split timing must be toggled on in the race’s Features tab before the race begins. It cannot be added retroactively after the race is in Active or Completed status. If you enable it after some runners have already passed a checkpoint, passings before the enable will not be recorded.
How to record a bib passing (marshal)
- Open the race and go to “Marshal Capture” The Marshal Capture tab only appears when split timing is enabled AND you are confirmed at a marshal post for the race (or you are the organiser).
- Your checkpoint is auto-selected Bield resolves your active post to the nearest checkpoint. If you are the organiser, you can select any checkpoint from the dropdown.
- Enter the bib and tap “Record Passing” The passing is added to the list immediately (optimistic UI) and confirmed via the API. The timestamp is taken at the moment you tap.
- Undo a passing (within 15 minutes) Each recorded passing has an undo button for 15 minutes after entry. After that window, only the organiser can correct it from the Results tab.
Duplicate passings
If you enter a bib that is already recorded as passing this checkpoint, Bield shows a “duplicate” warning and does not create a second record. This prevents double-counting when a runner pauses at a post.
Splits in results
After the race, the organiser publishes results and the split times appear on each runner’s result page. If you import results via CSV, the splits are merged with the imported finishing time.
Live progress for support teams
When split timing is enabled and marshals are recording bib passings, a runner’s support team — their pacers, crewers, and Supporters — can see a live checkpoint-by-checkpoint progress view on the race page. Each passing shows the checkpoint name, time of passing, and cumulative distance covered.
What “live” means. Progress updates whenever a marshal records a passing. There is no automatic GPS tracking of runners on the course — updates depend on marshals at each checkpoint recording bibs as runners come through. Between checkpoints the map shows the runner’s last known position (the previous checkpoint) until the next record comes in.
Who can see live progress
- The runner — can see their own progress from their engagement page.
- Supporters (and pacers, crewers) — see the runner’s progress from the engagement they’re linked to.
- Organiser and race team — see all runners’ progress in the Results tab during the race.
Live progress is only available when split timing is enabled for the race. Without it, the race page shows the planned course and checkpoint details but no live updates.
Incident reporting (marshals)
Marshals can submit a quick incident report directly from their on-post panel during a race. The report is sent to the organiser’s Race Day dashboard immediately.
How to report an incident
- Tap “Report incident” in your marshal panel The button is visible once you are in On post status.
- Choose a reason from the quick-pick list Reasons: Runner in distress, Runner requested support, Course marking issue, Safety hazard, Weather/environmental concern, Medical emergency, Other. You can add a short free-text note.
- Submit Your name, post assignment, and GPS location at submission time are automatically attached. The organiser sees the report in real time.
No outcome feedback to the reporter. Once submitted, you will not receive a status update through the app. If you need further communication, use race-day messaging or the organiser’s emergency contact from your race briefing. For genuine emergencies, call emergency services first (999 UK / 112 Europe).
Common questions
Can I enable split timing on the morning of race day?
In principle yes — split timing can be toggled on at any point before the race enters Completed status. However, any passings that happen at a checkpoint before you enable it will not be recorded. To capture every passing, enable split timing well before the start time, ideally when you first publish the race.
The camera scanner isn’t working on my iPhone at the registration desk. What do I use?
iOS Safari does not support the BarcodeDetector API, so the camera scan option is not shown on iPhone and iPad. Use the manual bib entry field instead — it’s just as fast if you have a handheld USB or Bluetooth barcode reader connected to a keyboard input, or if you read the bib number by eye.
A runner passed my checkpoint but I forgot to record it. Can I add it after?
Contact the race organiser. Organisers can manually add or edit split records from the Results tab after the race is in Completed status. Marshals’ 15-minute undo window only applies to passings they personally entered.
My volunteer board shows a post as “Unoccupied” even though the marshal is there. What happened?
The marshal likely has not tapped I’m on post yet. Ask them to open Bield, find the race, and tap the button. Their status will move from Confirmed to On Post immediately and your board will update.
Can anyone on the public see live checkpoint progress?
Live checkpoint progress is visible to the runner and to people in their race team (Supporters, pacers, crewers who have been invited by the runner). It is not publicly broadcast to all visitors of the race page. The race page shows the published results once the race is completed and the organiser publishes them.