Ready-to-post pieces for race directors. Copy the text, download the square graphic as a JPG, post. Already-published posts are marked.
10 posted · 15 still to post
Still to post: Sign-up form, Lanyards, Insights, Runner ETAs, Mobile, and the 10 new-feature posts below.
Post 1 · Roster
PostedEvery race director I speak to runs their volunteers out of a spreadsheet. Rows of names. A tab per marshal point. A colour code only you understand. Then someone drops out at 9pm on the Friday and the whole thing unravels. mrshl keeps the bit that works — the grid — and fixes the bit that doesn't. → Spreadsheet view with inline editing and keyboard navigation → Paste your existing volunteer list straight in from Excel or Google Sheets → Every row is tied to a real shift at a real point on your course, so gaps show themselves → Change a shift and the assignments stay attached You keep working the way you already work. The course just stops being a guess. #racedirector #endurancesports #trailrunning #eventmanagement
Post 2 · Briefs
PostedThe night before a race, one job eats the evening: marshal briefs. Name, point, shift times, what3words, parking, who to call, which WhatsApp group. Copy, paste, rename the file, repeat 300 times. Miss one and someone stands in the wrong field at 6am. mrshl generates every brief automatically, personalised per volunteer: → Their point on a map, with their exact arrival and release times → Estimated runner arrival based on your race's pace bands → Parking link, walking directions, emergency contact, radio channel → Their point's WhatsApp group link → Print the whole set as A4 or as lanyard cards → Versioned, so you can see exactly what each person was sent An evening's work becomes a click. #racedirector #volunteermanagement #ultrarunning #eventops
Post 3 · Race day
Posted05:40 on race morning. First runners in 80 minutes. The question that decides your day: is every point covered? Most of us answer it with a phone tree and a bad feeling. mrshl gives you one live board: → Check volunteers in as they arrive, from your phone → Any point short of people goes orange immediately → No-shows flagged so you can move someone before the gun → Filter by operational zone — On Route, Event Village, Start/Finish → Everyone's contact number one tap away You stop guessing where the hole is and start filling it. #racedirector #racemorning #eventoperations #endurancesports
Post 4 · Volunteer pool
PostedYour best volunteers aren't strangers. They marshalled the same junction three years running, they know where the gate sticks, and they'd say yes again if you asked. Most systems forget them the moment the event closes. mrshl keeps a volunteer pool across your whole account, not per event: → Pull last year's team into this year's race in seconds → Role tags — Registration, Timing, Event Village — so the right person lands in the right position → See who's returning and who's new → Waitlist when a shift is full, so keen people aren't turned away — you offer the spot when one opens Recruitment gets easier every year instead of starting from zero. #volunteermanagement #racedirector #communitysport #eventplanning
Post 5 · Comms
PostedVolunteer comms is where events quietly fall over. Half your team never saw the parking change. Two people got the message twice. Nobody's sure who's been told. mrshl drafts it and tracks it — you press send: → Segment by point, role, zone or status: everyone unconfirmed, everyone at the Event Village → Personalised message per volunteer with their own point and times → Opens WhatsApp with the text ready — you stay in control of what goes out → Group broadcast and event summary written for you, editable before you send → Every message logged, so you can see who's been contacted No more "did we tell them?" #racedirector #eventcomms #volunteers #endurancesports
Post 6 · CrewMate AI
PostedMost AI in event software writes you a paragraph. CrewMate does the work. It sits on every screen while you build your race, watching the setup and telling you what's still missing — then fixing it when you say go. → A live readiness score out of 100, with the exact gaps behind it → Points with nobody rostered, shifts short of people, races missing pace bands, no emergency contact → Tap "Fix this" and it builds the missing shifts from your event defaults → Groups forty points into sensible zones and writes the zone logistics once → Drafts your waiver, builds your sign-up form, sets up your brief layout → Small tidy-ups happen instantly. Anything bulk waits on your approval It's not a chatbot bolted to a dashboard. It's a second pair of hands. #racedirector #ai #eventoperations #endurancesports
Post 7 · Undo
PostedThe reason race directors don't trust automation: what happens when it gets it wrong at 40 points? So we built the answer in first. Every job CrewMate runs on your event is recorded permanently — what it created, what it changed, what it removed. → Open the activity list and see every job, in plain English → Tap undo on any past job, including ones from last week → Records it created are removed, values it changed are restored, anything deleted comes back → Bulk changes always ask before they run Automation you can reverse is automation you'll actually use. #racedirector #eventtech #trustbydesign #volunteermanagement
Post 8 · Course map
PostedA marshal point isn't a row in a spreadsheet. It's a specific junction, on a specific bend, at 34.2km on the long course and 11.8km on the short one. mrshl starts with the course, not the list: → Upload a GPX per race and the route draws itself, with distance and elevation → Drop marshal points, aid stations, crew stops and start/finish on the map → Each point gets its distance into every race it sits on, calculated for you → what3words and a location link on every position, straight into volunteer briefs → Import an existing Google My Maps course in one go Your course stops living in three different files. #racedirector #trailrunning #gpx #coursedesign
Post 9 · Zones
PostedForty marshal points. The same parking instructions typed forty times. Then the car park moves and you edit forty records. mrshl groups positions into operational zones — On Route, Event Village, Start/Finish, Aid Stations — and the detail flows down: → Meet location, briefing location, arrival window, walking directions, vehicle restrictions → Set it once on the zone, every point in it inherits it → Override on a single point when that junction really is different → Zone briefing copy lands on every brief in the zone → Filter your roster, comms and race-day board by zone Set up scales with your race instead of against it. #eventoperations #racedirector #volunteermanagement #ultrarunning
Post 10 · Sign-up form
To postVolunteer recruitment usually means a Google Form, then a manual copy into a spreadsheet, then an email asking which point they wanted. mrshl gives you one public link that does the whole job: → Volunteers browse real open shifts, grouped by zone, with times and what the role involves → Spots left shown live. Full shifts offer the waitlist instead of a dead end → "Open to any shift" for people happy to be placed → Your branding, your accent colour, your event's own words — Marshal, Crew, whatever you call them → Build your own questions, reorder the standard ones, make them required or hide them → Waiver accepted and snapshotted at sign-up They sign up. They're on your roster. No re-typing. #volunteermanagement #racedirector #eventplanning #communitysport
Post 11 · Run clubs
PostedHalf your volunteers don't arrive alone. They come as a club, a running group, a family, a corporate team — and they want to be put on the same point. Most systems treat them as unrelated strangers. mrshl doesn't: → Volunteers name their run club at sign-up, or join one already on the event → One person can add their group's members in a single go → Assign a whole club to a point or zone in one action → Message the club as a unit → See which clubs turn out for you year after year Look after the groups and recruitment does itself. #communitysport #runclub #volunteers #racedirector
Post 12 · Lanyards
To postA brief in an inbox is a brief nobody has at 6am in the rain. So mrshl prints the essentials onto lanyard cards, tiled onto plain A4: → Name, role, point, shift times → what3words and emergency contact → Section leader's number → Choose which fields appear — hide the ones your event doesn't use → Cut lines, no bleed into the fold, whole set in one print job Volunteers stop asking you what they're doing, because it's hanging on their chest. #racedirector #volunteers #eventops #endurancesports
Post 13 · Insights
To post"Are we fully staffed?" is the wrong question. The right one is: which points, which shifts, which zones — and how short? mrshl answers it visually: → Fill gauge across the whole event, updating as people sign up → Vacancies broken down by point and zone → Sign-up trend, so you know if this year is tracking behind last → Status breakdown: applied, confirmed, briefed, checked in → Repeat volunteer numbers — retention you can actually quote to sponsors Decisions on numbers, not on the feeling you had in the shower. #eventdata #racedirector #volunteermanagement #eventplanning
Post 14 · Runner ETAs
To postIt's the first thing a marshal asks and the hardest thing to answer by hand: when will runners actually get to me? mrshl works it out from your race, not from a guess: → Set a front-runner pace and a sweeper pace per race → Every point's distance into every route is calculated from your GPX → Each brief shows the estimated first and last runner at that exact position → Multi-lap and multi-pass courses handled per pass → Shifts can end on a condition — "when the back marker passes you" — instead of a fake time Marshals know how long they're really standing there. Fewer drop-offs. #trailrunning #racedirector #eventoperations #ultramarathon
Post 15 · Mobile
To postRace morning is not a desktop activity. It's one hand, a phone, gloves off, 4% battery. mrshl was built for that first and the laptop second: → Check volunteers in, mark no-shows and reassign from your phone → Big tap targets, works properly with the notch and one-handed → Volunteers open their brief on a phone with a map and one-tap directions → Available as a native iOS and Android app as well as the web → Everything loads fast on a field with two bars of signal The tool works where the race actually happens. #racedirector #mobilefirst #eventoperations #endurancesports
Post 16 · New · Race Day Live
To postA volunteer at registration is not yet a marshal at a junction. There might be a briefing, kit collection and a twenty-minute walk between those two things. Race Day Live in mrshl now lets marshals tap “I'm in position” directly on their personalised brief. No extra login or app download. → Arrival is recorded against their assignment → Event Control sees their status on the live board → Time on position is displayed → “Stood down” records when they leave Organiser check-in stays separate. Because “they're here” and “that point is covered” answer different questions. Missing confirmation still needs checking: it could mean poor signal, not an empty junction. A brief used to be instructions going out. Now it can bring an update back. #RaceDirector #RaceDay #VolunteerManagement #EventOperations
Post 17 · New · Live release
To post“The last runner should be through by 2pm.” That's an estimate. It isn't a stand-down instruction. The new live release controls in mrshl keep that distinction clear. → Supported release conditions can show an estimated countdown on the marshal's brief → An overdue estimate tells them to wait for Event Control → An authorised organiser can release an in-position marshal from the live board → The marshal sees that authorisation and confirms departure with “Stood down” The countdown uses race planning data. It isn't live runner tracking, and it never grants permission to leave. Useful estimates. A clear decision. A recorded departure. That's a better handover than hoping everyone interprets the scheduled finish the same way. #RaceDirector #MarshalBriefing #EventOperations #TrailRunning
Post 18 · New · Live timeline
To postA full day's staffing plan is useful. Knowing where you are in it is better. The latest mrshl update adds a live “Now” line to the race-day shift timeline. You can see the current time alongside shift coverage and in-position counts, rather than mentally translating the clock into a row of shift times. → Refreshes every 15 seconds while the view is open → Uses your organiser-configured timezone → Works alongside zone filtering and multi-day selection → Click a shift bar to jump to its point on the live board The marker appears for today, when the current time is within the displayed range. Planning other days stays uncluttered. Particularly useful around handovers: what's ending, what's starting, and what needs your attention now? #RaceDay #RaceDirector #EventOperations #VolunteerManagement
Post 19 · New · Signal resilience
To postThe most remote marshal point is rarely the one with the best mobile signal. Race Day Live in mrshl now saves arrival and stand-down taps on the device, then submits them in order when the connection returns. The original tap times are preserved. Pending updates and the last live sync time are visible too. There is also a cached-brief fallback: a brief opened on the same device within the last 48 hours can be shown if it cannot be loaded, clearly labelled with its last-loaded time. Important distinction: this does not make every page or map work offline. Event Control won't receive a pending update until it syncs. Keep your event's communication fallback in place. But a temporary loss of signal shouldn't mean losing the arrival update altogether. #TrailRunning #RaceDirector #RaceDay #EventTechnology
Post 20 · New · Mobile race day
To postOn race morning, you shouldn't have to scroll past setup guidance to find check-in. The latest mobile update to mrshl puts the operational tools first. → Event name, check-in shortcut, staffing export and zone filter stay ahead of the planning details → The timeline and live board take priority → Setup tools sit behind a closed-by-default panel → The check-in search header stays within reach as you scroll → Event sections use a compact, horizontally scrollable tab strip The planning tools haven't disappeared. They're simply no longer competing for the first screen when you're trying to run the event. It's not the loudest kind of product update. It's the kind you appreciate with a queue of volunteers in front of you. #RaceDirector #MobileDesign #EventOperations #RaceDay
Post 21 · New · Bulk allocation
To post“Put me wherever you need me.” Brilliant. Now multiply that by a whole group of flexible volunteers and a course full of gaps. mrshl now lets you review proposed shift allocations for several flexible volunteers before confirming them from the roster. → Review the proposed placements together → Confirm when you're happy with the plan → Capacity and existing event assignments are checked again before saving → See who was assigned, who was skipped and why anything couldn't be confirmed This isn't about handing the decisions to a black box. It's about making several considered placements without repeating the same admin one person at a time. Flexible volunteers offer you options. The new allocation flow helps turn those options into a clear plan. #VolunteerManagement #RaceDirector #EventPlanning #EventOperations
Post 22 · New · Bulk shifts
To postYou've added your course points. Now comes the repetitive bit: creating similar shifts at each one. Same role. Same hours. Same headcount. Different junction. The new bulk shift creator in mrshl lets you select several course points and set shared shift details together. → Choose the points → Set the common shift details → Review the proposed shifts before saving → See the creation results You still decide where the shared details make sense. Points with different requirements don't need to be forced into the same batch. Not every useful feature needs to be dramatic. Sometimes it just needs to remove the job you've already done twelve times this evening. #RaceDirector #CoursePlanning #VolunteerManagement #EventTech
Post 23 · New · Event copying
To postLast year's event is a useful starting point. Last year's check-ins are not. The updated event-copy flow in mrshl lets you review the setup and new race and shift dates before creating the event. → Carry across branding, zones, points, shifts, forms and brief designs → Choose which volunteers to bring across, or copy the setup without them → Move race and shift dates to the new event date Assignments, check-ins, volunteer consent, form responses, brief history and email automations/history aren't copied. Copying doesn't send volunteer emails either. Reuse the planning work. Start the new event's operational records fresh. That's the difference between a useful head start and inheriting a set of assumptions nobody checked. #RaceDirector #EventPlanning #VolunteerManagement #EnduranceSports
Post 24 · New · Import review
To postA spreadsheet import shouldn't be a leap of faith. The updated volunteer imports in mrshl give you a column-matching step and a preview before you save. → Check sample values against the suggested fields → Change matches and ignore columns you don't need → Correct names, phones and emails in the preview → Review possible duplicates and invalid rows → See imported and skipped totals when it finishes For pasted rosters, ambiguous point or role matches are left for you to review rather than silently choosing a shift. Duplicate warnings don't automatically merge or skip anyone. You stay in control of what the warning means. The aim is simple: spot the wrong column before it becomes the wrong volunteer detail. #EventData #RaceDirector #VolunteerManagement #EventPlanning
Post 25 · New · Setup checklist
To postSetting up a race involves several connected jobs. Remembering which one you left unfinished shouldn't be another one. mrshl now has a five-step setup checklist covering races, course points, shifts, the sign-up preview and your saved brief layout. → Progress reflects saved setup, not manual ticks → “Next” takes you to the next unfinished task → Opening the sign-up preview as an authorised organiser records that step → Copied events still need their own sign-up preview There's also a mobile-friendly first-event guide with visual demonstrations to help new organisers work through the process. One important boundary: “core setup complete” is not a race-day readiness assessment. You still need to review staffing, instructions and your operational plan. A clearer route through setup, without pretending a checklist can run the race for you. #RaceDirector #EventSetup #VolunteerManagement #EventPlanning