Organising a Club Sportive or Event Day
How to organise a cycling sportive or club event day: the timeline, who to ask about permits and insurance, route and feed stops, volunteer roles, a break-even budget and the ride-day run sheet.
At twenty to four on the afternoon of your first sportive, the car park is nearly empty, the feed-station tables are folded, and someone at event control asks the only question that really matters: "Is everyone back?" If you can answer that in ten seconds from a list, your event was well run. If the answer involves ringing round, it wasn't — however good the route was.
A sportive or club event day is three or four months of admin for one morning on the bike. The ride is the easy part; your members already know how to do that. What sinks first-time events is everything around it: an approval asked for too late, a feed stop that runs dry by eleven, a junction with no marshal, a budget built on hopeful entry numbers. This is the organiser's version — what to decide, in what order, and what to ask the people who actually set the rules where you ride.
Decide what you're actually running
"Event" covers everything from a members' anniversary ride to a 1,000-rider open sportive, and the admin scales with it. Before anything else, decide which one you are organising, because it sets the paperwork, the insurance question and the budget.
| Format | Who rides | Admin weight |
|---|---|---|
| Members' event day (reliability ride, anniversary ride, club challenge) | Members, perhaps a few named guests | Light — close to a big club ride; check your club insurance covers guests |
| Open charity or community ride | The public, usually free or donation-based | Medium — non-members on the road raise insurance and authority questions |
| Sportive / cyclosportive / gran fondo / marcha | The public, paid entry, often hundreds of riders | Heavy — federation registration, local authority involvement, medical cover, a real budget |
The names vary by country and so do the categories. The line that matters most is whether the event is timed or ranked. Timing and results can move an event closer to a race in the eyes of federations and authorities, with different rules attached. Don't promise a results table until you've asked.
For a first event, go small: a members-plus-guests ride on routes you already lead, with one or two hundred riders at most. You'll learn more from a tidy 120-rider day than from a stressful 600-rider one.
Start earlier than feels necessary
Every first-time organiser underestimates the lead time, and almost always on the same item: getting answers from outside bodies. Your committee can plan a route in an evening. An authority can take weeks to reply. Work backwards from event day and put the outside conversations first.
| Task | Weeks before event |
|---|---|
| First contact: federation, insurer, local authority | 16-26 |
| Route design and recce | 12-20 |
| Book venue, toilets, first aid | 10-16 |
| Open entries | 8-12 |
| Recruit and brief volunteers | 4-10 |
| Order food, signs and numbers | 2-4 |
| Final recce and signage | 0-1 |
The practical version: four to six months out, pick a date that doesn't clash with a big local event, and make the three phone calls in the next section. Don't open entries until the answers are back.
Permits, insurance and who to ask
Rules for events on public roads differ by country, by region and sometimes by town, and they change. Nothing here is legal advice. What you can know in advance is who to ask and what to ask them.
| Ask | What to ask |
|---|---|
| Your national federation — British Cycling, FFC or FFVélo, RFEC (often via the regional federation), FCI — or whichever body your club is affiliated to | Does this event need registering with you? What insurance comes with it? Is there a per-rider day licence or fee for unlicensed riders? What changes if it's timed? |
| Local authority and police | Do we need to notify you or get approval, and how much notice do you need? Can we put signs on the roadside? What can marshals do and not do? |
| Your insurer | Are non-members, volunteers and the venue covered? What limits apply? Do you need a copy of our risk assessment? |
| Venue and landowners | Parking, toilets, power, access times, and what happens if it rains on their field |
| First-aid provider | What level of cover suits this size and route, and does the federation or authority set a minimum? |
Three things hold almost everywhere, and they shape the rest of your planning:
- Assume open roads. Full road closures are rare for sportives, slow to arrange and expensive. Design the event so riders follow normal traffic rules, because they'll have to.
- Marshals are usually not traffic police. In many countries a volunteer marshal can warn and guide riders but has no power to stop traffic. Find out what yours may do, and write role cards that match.
- Get everything in writing. An email confirming a phone conversation is worth more than the conversation. File it.
Rider waivers and entry terms belong in the same conversation with your insurer. The basics are in ride waivers and insurance for cycling clubs.
Route: loops, feeds and the last rider
A good event route is a good club route with more people on it, so start from roads your ride leaders already know (the thinking in planning a club group ride route applies directly). Then add the event-specific layer:
- Two or three distances that share roads. For example a short, medium and long option — say around 50, 90 and 130 km — that split and rejoin, so one feed and one set of signs serve more than one route.
- A start and finish that works on foot. Parking, toilets, power, shelter if it rains, and a safe exit onto a quiet road rather than straight onto a main one.
- Turns that don't cross traffic. Where you can, plan turns with the flow — left turns in the UK, right turns on the Continent — and avoid busy junctions where riders have to cut across oncoming lanes.
- Feeds every 40–50 km or so. Closer together in heat or on hilly routes. Place them where there's a wide verge or car park, never on a descent or a blind bend.
- Cut-off times. Decide when each feed closes and what happens to riders who arrive after: a signed shortcut back, or the broom wagon. Publish it in the entry information so it's a rule, not a surprise.
- Signs before, at and after every junction. A warning arrow before the turn, one at the turn, and a confirmation arrow after it so riders know they're still on route. Number every sign so the collection team can count them back in.
Recce the full route again in the final week. Roadworks, a new diversion or a felled tree will find you if you don't find them first.
Feed stations that don't run dry
An empty feed station is the one thing riders will still be talking about next year. Over-cater the first time; leftover bananas are a cheap mistake, an empty table at kilometre 90 is an expensive one.
| Item | Per 100 riders passing one feed (starting estimate) |
|---|---|
| Water | 50–75 litres (a 500–750 ml refill each), more in heat |
| Bananas | About 50, served in halves |
| Sweet food (cake, flapjack, sweets, gels) | 150–200 portions |
| Savoury food (salted crisps, pretzels, small sandwiches) | About 100 portions |
| Kit | Bins, hand sanitiser, track pump, first-aid kit, spare tubes for sale or swap |
Those are starting estimates for planning, not nutrition advice. Write down what's left at the end of the day and next year's order writes itself. Riders still need to carry their own food between stops — the basics are in how to fuel a long bike ride, and it's worth linking in your rider information.
Lay the feed out so riders arrive on one side and leave on the other, bikes parked off the road, with one volunteer at the exit reminding people to look before they pull back out. Most feed-station incidents happen at walking pace, not at speed.
Volunteers: the roles and the numbers
Your route decides your volunteer count, mostly through junctions. Walk the route on the map, mark every point where a rider could go wrong or meet heavy traffic, and staff the worst of them. Everything else follows.
| Role | Volunteers (example) |
|---|---|
| Junction marshals | 10 |
| Feed stations (2) | 8 |
| Registration desk | 4 |
| Car park and start line | 3 |
| Signage team | 3 |
| Event control | 2 |
| Broom vehicle | 2 |
| Mechanic | 1 |
That's 33 people, roughly one for every six riders. Every one of them gets a role card: where to be, from when to when, who to call, what to do if something goes wrong, and when they're stood down. Brief them together on the morning, feed them, and thank them by name afterwards. If your club already has trained ride leaders, they make the best marshals and sweepers — and if it doesn't, an event is a good reason to start (see recruiting and keeping volunteer ride leaders).
Event control: knowing who's still out
Event control is one table, two people and a phone, and it's the heart of the day. Its job is to know at every moment who is on the road and to coordinate when something goes wrong.
- Check riders out and back in. Record every number at the start and at the finish. That list is how you answer "is everyone back?"
- One emergency number on every rider number. Event control's mobile, printed, plus the local emergency number. Test that it gets signal at the venue.
- A broom vehicle or sweep riders on each route. They ride or drive behind the last rider, pick up the stopped, and report position.
- An incident log. Time, place, rider number, what happened, what was done. Your insurer will ask.
- A weather call agreed in advance. Decide the criteria and the decision time before the day, not on the start line — the same logic as a club weather-call policy.
- A start briefing that takes 90 seconds. Signs, feeds, cut-offs, emergency number, road rules. The structure is in the pre-ride safety briefing script.
The event closes when the broom is in and the last number is checked back — not when the last rider you can see has finished. Then ring every marshal point and stand them down.
Money: a break-even budget
Split every cost into two piles. Fixed costs don't change with entries: venue, toilets, first aid, federation and insurance fees, signs, publicity. Variable costs rise with each rider: food, rider numbers, any finisher's gift, payment fees and, in some countries, a per-rider day licence or insurance fee for unlicensed riders — ask your federation.
Then the break-even sum is one line: fixed costs ÷ (entry fee − variable cost per rider). A worked example, with illustrative numbers rather than real prices: fixed costs of €3,000, variable costs of €8 a rider and a €25 entry leave €17 per rider towards the fixed costs. You break even at 177 riders.
| Paid entries | Event result (€) |
|---|---|
| 100 | -1300 |
| 150 | -450 |
| 200 | 400 |
| 250 | 1250 |
| 300 | 2100 |
Run your own numbers with a pessimistic entry count, not the one you hope for. Then decide three things before entries open: an entry cap your volunteers and feeds can handle, a refund and transfer policy, and what happens to entry fees if you have to cancel on the day. Write all three into the entry terms.
Ride day and the day after
A run sheet turns a hundred small jobs into a timeline everyone can see. An example for an 8am start:
- Before dawn: signage team rides or drives the route checking every sign; setup crew builds registration and the finish area.
- 06:30 — volunteer briefing; role cards handed out; marshals leave for their points.
- 07:00 — registration opens; event control live.
- 07:50 — rider briefing at the start.
- 08:00 — long route away, then the shorter routes in waves.
- Mid-morning — feed stations at peak; event control tracking the broom vehicle.
- Feed cut-offs — riders behind time sent to the shortcut.
- Last rider in — broom confirms, numbers checked, marshals stood down by phone.
- Same afternoon — every sign collected and counted back in.
Collecting signs the same day isn't optional — forgotten arrows on lampposts are the fastest way to lose goodwill with a local authority. Within a week, hold a debrief with the core team, send a three-question survey to riders, thank volunteers publicly in your club channel, close the accounts and write a one-page "next year" note while it's fresh. That note is the most valuable document the event produces.
Most riders on your sportive will one day be riders on your club run. If the weekly ride isn't yet the polished thing the event promised, the first group ride playbook is where to start.
FAQ
How far ahead should we start organising a sportive?
Four to six months for a first event, longer if your local authority asks for more notice. The outside conversations — federation, authority, insurer — set the pace, so make those calls first and don't open entries until you have answers in writing.
Do we need to close the roads?
Almost never for a sportive: most run on open roads, with riders following normal traffic rules. Road closures are slow and costly to arrange. Ask your local authority what applies, and design the route and marshal plan for open roads.
How many feed stations does a sportive need?
A common rule of thumb is one every 40–50 km, closer together in heat or on hilly courses. Riders should still carry food and drink between stops.
How many volunteers do we need?
It depends mostly on how many junctions need a marshal. In our worked example, a 200-rider event with two feeds needed 33 volunteers — about one per six riders — but your route decides the real number.
How do we set the entry fee?
Work out fixed costs and variable cost per rider, then check the break-even number of entries at your proposed fee using a pessimistic estimate. If break-even needs more riders than you can realistically expect, raise the fee or cut fixed costs before you open entries.
Run your club on CyclingClub.cc
Routes, group rides, members, and a shop — free for clubs up to 1,000 members.
Create your club