What an off-road club needs to run events.

Updated May 2026 · Trail Convoy Team

The pre-run checklist real clubs use, in the order they use it. Skip a step and you discover at the trailhead why it was on the list.

The difference between a club that runs events and a club that says it runs events is a checklist. Every successful off-road club has one — sometimes written down, more often in the head of the one officer who carries the operational weight.

Here is that checklist, written down. Steal it. Customize it. Use it on every run until you do not need to look at it anymore.

Eight steps, every run.

  1. Pick the route and vet it

    Scout the trail recently if possible, or talk to someone who has. Note the difficulty rating, expected duration, known hazards, water crossings, cell coverage gaps, and bail-out points.

  2. Set vehicle requirements honestly

    Publish exactly what a vehicle needs to make it through. Lockers? Minimum tire size? Recovery gear? Skid plates? Better to lose two RSVPs in advance than spend the day winching them.

  3. Open RSVPs with a cap and waitlist

    A cap protects the trail and the convoy size. A waitlist captures interest cleanly. RSVPs should include the rig, the driver, any passengers, and confirmed sign-off on the waiver.

  4. Collect waivers in advance

    Per-event waivers, signed before the run starts. Digital is faster, captures the audit trail, and means the trailhead is for airdown, not paperwork.

  5. Publish the comms plan

    Primary radio channel, backup channel, lead and sweep call signs, what frequency the group monitors. If you use GMRS, include the license note for anyone who needs it.

  6. Hold a driver's meeting at the trailhead

    Five to ten minutes. Route, hazards, comms, hand signals, recovery plan, expected pace, headcount confirmation. Everyone hears the same words at the same time.

  7. Run the convoy with a defined lead and sweep

    Lead picks the line and sets the pace. Sweep stays behind the slowest vehicle and never leaves them. Middle vehicles maintain visual or radio contact with the one behind them.

  8. Debrief and log

    Headcount at the end. A short note in the channel — who came, what happened, what to remember for next time. Log any incidents to a permanent record (even close calls). Patterns in that log are how a club gets safer.

What every vehicle should carry.

The mandatory list — not the wishlist. Publish this with every RSVP and verify at airdown.

  • Recovery: rated recovery points (front and rear), kinetic strap or rope, shackles or soft shackles, traction boards, gloves.
  • Comms: a working radio on the club's channel (CB, GMRS, or whatever your club has standardized on).
  • Repair: tire repair kit and air source, basic tool roll, a spare tire of the correct size that has actually been checked.
  • Safety: a real first-aid kit, fire extinguisher, fully-charged phone, water for at least 24 hours, warm layer.
  • Navigation: the day's GPX downloaded for offline use. Cell coverage on most trails is wishful thinking.

Some clubs make recovery gear inspections part of every airdown. Some only do it for new members or technical runs. Both work — the wrong answer is "we trust people to bring it."

Lead, sweep, and the middle.

Lead

Picks the line. Sets the pace. Has the most current route knowledge. Owns the comms cadence — calls out hazards, regroups at junctions, decides when the convoy holds vs proceeds.

Sweep

Last vehicle in the convoy. Stays behind the slowest rig and never leaves them. Has the strongest recovery setup and (ideally) the most experienced trail driver. The sweep is the safety net the whole convoy depends on.

Middle

Maintains visual or radio contact with the vehicle behind them. If you lose the rig behind you, you stop and wait until they reappear or the sweep calls in. This single rule prevents most convoy fragmentation.

Trail leader (a role, not a position in line)

The person responsible for the day — usually the lead, but not always. Owns the go/no-go call, the driver's meeting, and any decision the group disagrees on. Bigger clubs rotate this role to develop a bench.

Common questions about running events.

How far in advance should we announce a trail run?

Three to six weeks works for most clubs. Closer than two weeks and members cannot plan; further than eight weeks and RSVPs go stale. The exception is destination/overnight events, which need 8–12 weeks for hotel and time-off planning.

How many vehicles should be in a convoy?

Eight to twelve is the sweet spot for most clubs. Below five and a single breakdown ends the day; above fifteen and the convoy stretches so far that radios stop working and the sweep cannot help the lead. Larger groups split into "flights" of 8–10 with separate lead and sweep per flight.

Do we need to vet vehicles before a run?

For technical runs, yes. The standard practice is to publish vehicle requirements with the RSVP (stock vs lifted, lockers required or not, minimum tire size, recovery gear) and have trail leaders confirm at airdown. The waitlist is your friend — let people self-select out, do not turn them away at the trailhead.

What should be in the pre-run driver's meeting?

Route overview, known hazards, radio channels, hand signals, recovery protocols, who the lead and sweep are, what to do if you get separated, and a quick gut-check that everyone's vehicle is run-ready. Five to ten minutes. Skip it and you spend the day fixing avoidable problems.

What happens if someone breaks down mid-trail?

Stop the convoy. The sweep stays with the disabled vehicle, the lead pulls the rest into a safe holding spot, and the group decides together: repair, recover, or bail. Never split the convoy without an explicit plan and radio contact between groups.

How do we handle weather or trail conditions changing?

Set go/no-go criteria before the run and publish them with the RSVP — "if NWS forecasts >0.5" of rain 24h before start, we postpone." Decisions made in advance survive contact with reality; decisions made in the parking lot at 6am do not.

Should we charge for events?

Members usually free; non-members usually a small fee ($10–$25 covers insurance overhead). Bigger events with food, swag, or venue costs need their own budget. Make the fee, what it covers, and the refund policy visible on the RSVP.

What should we do at the end of every run?

Three things: account for every vehicle that started, log any incidents (even minor ones — the pattern matters), and send a short debrief to the channel. The clubs that get safer over time are the ones that treat every run as a data point.

Keep reading

Every step of this checklist, in one platform.

RSVPs with caps and waitlists. Per-event waivers. Vehicle profiles tied to members. Multi-flight convoys with separate lead and sweep per flight. Radio channels published with the run. Plus your full club website, hosting, secure certificates, and a custom domain at no extra fee. Every feature on every plan. Built for the way real clubs actually operate.