What marshals do on Bield
Marshals support the race organiser — not any individual runner. Their job is to staff posts on the course: aid stations, road crossings, kit checks, tail-walking sweeps, medic points, and safety positions. Bield's marshal role matches volunteers to posts and records their gigs; it doesn't carry any arrangement about pay.
Marshalling arrangements, including any expenses, are between you and the organiser. Bield facilitates the match and the communications; it doesn't process payment between users.
Marshal vs. Supporter — what's the difference?
| Role | Who they support | How they join |
|---|---|---|
| Marshal | The race organiser — staffs a post on the course | Volunteer interest submitted on a race; organiser assigns a post |
| Supporter | A specific runner — informal race team member (spectator / family / friend) | Invited by the runner via a non-forwardable personal link |
Getting set up as a marshal
- Enable the Marshal role Go to Me → Your roles and toggle Marshal on.
- Set your coverage areas Me → Areas you cover — draw or select regions you're willing to travel to. Organisers searching for marshals near a course use this to find you. It also activates the “Inside my zones” race filter.
- Set your availability Add your available dates so organisers know when you're free before reaching out.
Volunteering for a race
- Browse races Go to Races. Race cards and race pages show marshal-friendly CTAs when you have the Marshal role enabled. Use the Inside my zones filter to find races in your areas.
- Submit your interest On the race page, tap the volunteer interest button. A short form (no wizard) asks basic details — which posts interest you, any relevant experience, your contact details for the organiser.
- Wait for assignment The organiser triages all interest and assigns volunteers to specific posts. When you're assigned, your engagement updates to invited status with the post details.
Prerequisites for volunteering
- The Marshal role must be enabled on your account.
- Organisers may specify minimum requirements (e.g. first-aid certificate, own transport) in the race briefing — check the race page for any stated requirements before submitting.
Race day workflow
Your marshal panel on the race page walks through your day in sequence. Each step unlocks the next.
- Confirm your assignment When you receive your assignment with status invited, tap Confirm to accept the post. Status moves to confirmed. Prerequisite: you must be in invited status — you can't confirm an unassigned interest.
- Check in on post On race day, when you're physically at your post, tap I'm on post. Status moves to on post. The organiser sees live post coverage on their volunteer board.
- Mark completed When your stint is done (last runner passed, post closed), tap Mark completed. Status moves to completed and the gig is recorded to your profile.
Call-for-help pings
Organisers can send geo-targeted “call for help” pings to volunteers near a post that needs coverage. If you're near the course on race day — even if not formally assigned — you may receive a ping. Accept or decline from the notification.
Split timing (checkpoint passes)
If the organiser has split timing enabled for the race, checkpoint gates record runner passings automatically. As a marshal at a checkpoint, the organiser's interface allows manual recording of a runner's bib when they pass. This is the prerequisite for accurate split data in results.
Marshal post statuses
Your marshal engagement moves through these states:
| Status | What it means | What triggers it |
|---|---|---|
| Interested | You've submitted volunteer interest | You tap “Volunteer for this race” |
| Invited | Organiser has assigned you to a specific post | Organiser assigns you in their volunteer board |
| Confirmed | You've confirmed the assignment | You tap “Confirm” on your marshal panel |
| On post | You're physically at your post on race day | You tap “I'm on post” |
| Completed | Your stint is finished | You tap “Mark completed” |
| Departed | You left post before the race window ended (e.g. emergency) | You or the organiser records an early departure |
| Unoccupied | Post has no active marshal — visible to the organiser as a gap | Organiser marks the post unoccupied, or no one has checked in |
| Cancelled | Your assignment was cancelled | Organiser cancels the assignment (e.g. post no longer needed) |
Supporters
A Supporter is different from a marshal: Supporters join a specific runner's race team by personal invitation, not via the volunteer-for-a-race flow. They are typically friends, family, or spectators who want to follow and cheer the runner.
How to become a Supporter
- Receive a runner's invite link The runner generates a non-forwardable personal link from their engagement and sends it to you directly (message, email, text — any channel they choose). Only the first person to open the link can claim the invitation.
- Open the link and sign in If you're already on Bield, sign in. If not, you'll be prompted to create an account — it's free and takes a minute.
- Accept the invitation Tap accept. You'll appear on the runner's engagement as their Supporter, alongside any pacers and committed crewers.
There are no prerequisites for being a Supporter — you don't need the Marshal role and don't need to set up a profile. As a Supporter you can see the runner's bib number, checkpoint ETAs, and live checkpoint progress (when split timing is enabled). You can also send shout-outs — short messages timed to fire when the runner reaches a specific checkpoint.
Supporters do not receive outcome feedback on any incidents the marshal reports. Incident reports go to the race organiser only — they are not surfaced to the runner's support team.
Incident reporting
Marshals can log incidents at their post during a race — for example, a runner in distress, a course-marking problem, or a safety concern. Incident reports go directly to the race organiser.
How to report an incident
- Open the race on race day From your marshal panel, tap Report incident.
- Select a reason A quick-pick list covers the most common categories: Runner in distress, Runner requested support, Course marking issue, Safety hazard, Weather/environmental concern, Medical emergency, and Other. Pick the closest match; you can add a free-text note.
- Submit The report is sent immediately to the organiser's Race Day panel. Your name, post location, and GPS coordinates at the time of submission are included automatically.
No outcome feedback to reporter. Once you submit an incident report, you will not receive a response or status update through the app. The organiser reviews reports and acts on them directly. If you need to communicate further, use the race-day messaging thread or phone the organiser's emergency contact shown in your race briefing.
For genuine emergencies, always call the emergency services (999 in the UK, 112 in Europe) first. Bield incident reporting is a supplement to, not a replacement for, emergency service calls.
Bib capture
If the organiser has split timing enabled, checkpoint marshals can record runners passing their post directly from the app. This feeds live split data into the results and keeps the leaderboard accurate.
Access: organiser race editor → Marshal Capture tab (role-gated to marshals assigned to that race)
Prerequisites: Split timing must be enabled for the race and you must be actively checked in at your post (status: On post).
How to record a passing
- Open the Marshal Capture tab on the race page You'll see a large bib number input field optimised for quick entry on a phone.
- Enter the bib number and tap Record Passing The record appears immediately (optimistic UI) — you don't need to wait for server confirmation before entering the next bib.
- Undo if needed You have a 15-minute window after recording to undo a passing if you mis-entered a bib. After 15 minutes the record is locked.
Marshal resupply request
If your post is running low on supplies during the race, send a resupply request directly from your marshal panel. The organiser sees it immediately in their Resupply Queue panel on their Race Day desk.
Access: race-day marshal panel → Resupply request button
- Tap Resupply request, add a brief note about what you need, and send.
- The organiser sees your request, your post location, and the time it was raised.
- There is no back-channel in the app — if the organiser arranges a drop, they may message you directly or contact you by phone.
Marshal leave notification
If you need to leave your post temporarily or cannot continue, always flag it in the app before you go. The organiser sees the leave event in their Marshal Leave panel and can arrange cover.
Access: race-day marshal panel → Leave post button
| Option | What it means |
|---|---|
| RETURNING | You're stepping away briefly and will be back. The post shows as temporarily unmanned. |
| NOT_RETURNING | You cannot continue. The organiser is alerted to find replacement cover. |
Always flag a leave. Never walk away from a post without notifying the organiser through the app. If the situation is urgent, also contact the race director directly using the emergency contact in your race briefing.
Volunteer certificate
After completing a marshalling gig, you receive a downloadable volunteer participation certificate recording your contribution to the race.
- Available once the event completes and the organiser has published results.
- Download it from your engagement — look for the certificate download button.
- You'll also receive an email link with the certificate attached.
- Certificates record the race name, your role, and the date.
What's in your race briefing
When the organiser sends your briefing PDF (generated from their Reports tab), it contains everything you need to arrive prepared and stay safe on the course.
Briefing contents
- Your post location and what3words address (///word.word.word) for precise navigation
- Assigned start and end times for your stint
- Race emergency contact details
- What to do if you need to leave your post
- Incident reporting instructions
Download your marshal briefing PDF from your engagement page, or from the email the organiser sends when they distribute briefings. Print it or save it offline — phone signal at remote posts can be unreliable.
Common questions
Do I get paid for marshalling?
Any arrangement about expenses is between you and the organiser — Bield doesn't process payment between users. Many marshalling gigs are purely voluntary; others involve travel or meal reimbursement. Clarify with the organiser when you submit your interest.
What post types can I be assigned to?
Aid stations, road crossings, kit checks, tail-walking sweeps, medic points, and general safety positions. The organiser sets up posts from their race management dashboard and assigns volunteers to them.
I can no longer make the race. What should I do?
Contact the organiser as soon as possible — use the messaging thread on the race page or their contact details from the race. Let them know early so they can find a replacement. You can also update your status on your marshal engagement panel.
Can I be a marshal and also run a different race on the same weekend?
Yes — Bield tracks all your roles and engagements separately. Clashes in your calendar are your responsibility to manage; Bield doesn't enforce availability.
My post is running short on supplies. What do I do?
Use the Resupply request button in your marshal panel. This sends an alert directly to the organiser's Race Day desk. They'll see it in the Resupply Queue and arrange delivery.
I need to leave my post early. What's the right way?
Tap Leave post in your marshal panel and choose RETURNING or NOT_RETURNING. This alerts the organiser so they can arrange cover. Always notify via the app — and contact the race director directly if the situation is urgent.
How do I get my volunteer certificate?
Once the event completes and the organiser has published results, your volunteer participation certificate should be available from your engagement. You'll also receive an email link. If you don't see it after results are published, contact the race organiser.