CRW SMS: start here

Riders

Download or print this guide (PDF)

Text 573-279-2739 from the phone on your CRW registration. Save it in your phone before the ride, for example as "CRW Ride Text."

1. When you arrive, text HERE

That checks you in. If the reply says to find the ride leader, find the ride leader. That is normal, and they can check you in by hand.

If the ride has chat groups, your reply may suggest one. Text JOIN 2 (or the number you want) to join, or GROUPS to see the list.

2. Hurt or in danger? Call 911

Call. Do not text. The CRW number is not an emergency line, and nobody answers it live.

3. When you finish, text FINISH

The reply asks how the ride went. Please answer. Your feedback is saved with the ride and your group, and it helps us improve rides and keep riders safe.

Leaving early? Text LEAVE RIDE. It records that you left. It does not ask anyone for help.

Supported events only

Some big events have volunteer support crew. Text SUPPORT to see if crew is available. If it is, text #SUPPORT with where you are and what is wrong, like #SUPPORT mile 42 near the church, broken chain. Plain words like help or flat do not open a support request. They are ordinary texts, so they can go to ride chat instead.

Once you text #SUPPORT, your texts go to support, not ride chat, until you text RESOLVED. If you cannot text, call the CRW number and leave a voicemail. It is a recording, not a person. If you cannot get an answer, call 911 for an emergency or tell the ride leader.

Also handy

• MY RIDES: your current ride and where texts will go.
• MENU: all options. SAFETY: the CRW safety page.
• All commands: cheat sheet.

Back to guide choices

Ride leaders: basic guide

Download or print this guide (PDF)

CRW SMS number: 573-279-2739

You already check riders in. CRW SMS makes that easier and gives the whole club more. The goal is safety and community: one number reaches every rider, on every route, with every leader in the loop.

This guide covers an ordinary ride, which is most rides. Supported events, centuries, and planned groups are in the advanced guide. Want one page to print? Use the one-pager.

The one rule

Hurt or in danger: call 911. Call, do not text. The CRW number is not an emergency line. Nobody reads texts to it live.

Good, better, even better

Alongside, you can reach everyone. Once riders have texted HERE, a text to the ride reaches them: ALERT for a problem or a change, plain ride chat for friendly news like "ice cream after the ride at [place]." Ride chat reaches riders who have not yet texted FINISH or LEAVE RIDE, so send it before they finish and say it out loud too.

Say this at check-in (about 90 seconds)

1. Check in

"Before we roll, please pull out your phone. Text the word HERE to 573-279-2739. Give it a moment. If you get a confirmation, you're checked in. If it tells you to see a leader, come find me."

2. Emergencies (every ride)

"Now the part that matters most. If someone is hurt or in danger, call 911. Call, don't text. Please do not call or text this number for an emergency. It is not answered by a person. Call 911 first, then tell me or the nearest rider."

3. Getting help (ordinary ride, no crew)

"There is no support crew on the text line today. If you have a flat or a mechanical, or you're lost, tell the group or call me. [My cell is ______.] If you spot a hazard the whole ride should know about, text ALERT and a few words, like: ALERT glass in the shoulder at mile 12."

4. Close

"Save this number now. One more time: hurt or in danger, call 911. Hazard for the group, text ALERT. Before you head home, text FINISH and tell us how the ride went. Questions? Find me."

Expecting volunteer crew on the text line? Read the supported-event version of part 3 from the advanced guide.

During the ride

• ROSTER: who has checked in. ROSTER OUT: who is still on the road.
• ALERT message: a short safety note to checked-in riders. SMS asks you to confirm; reply YES ALERT. Limit: 3 per phone every 2 minutes. ALERT does not call 911 or get medical help.
• Plain text from you goes to the ride chat for checked-in riders. If the ride has planned groups and you have joined one, it goes only to that group.

At the end

Invite every rider to text FINISH. A rider who never does is treated as done two hours after the ride's end time. Riders who head off early can text LEAVE RIDE. It only records the departure, and most riders who leave are simply done, so do not treat it as a sign of trouble.

When it does not work

Nothing you do today goes away.

More

All commands: cheat sheet. Why we built it: the guides index.

Back to guide choices

Ride leaders: printable one-pager

Download or print this guide (PDF)

CRW SMS number: 573-279-2739. Save it in your phone as "CRW Ride Text." Safety and community: one number reaches every rider, on every route, with every leader in the loop.

Emergency or anyone in danger: CALL 911. Call, do not text. The CRW number is not an emergency line. Nobody answers it live.

Say this at check-in (about 90 seconds)

1. Check in

"Before we roll, please pull out your phone. Text the word HERE to 573-279-2739. Give it a moment. If you get a confirmation, you're checked in. If it tells you to see a leader, come find me."

2. Emergencies (every ride)

"Now the part that matters most. If someone is hurt or in danger, call 911. Call, don't text. Please do not call or text this number for an emergency. It is not answered by a person. Call 911 first, then tell me or the nearest rider."

3. Getting help: ordinary ride, no crew (most rides)

"There is no support crew on the text line today. If you have a flat or a mechanical, or you're lost, tell the group or call me. [My cell is ______.] If you spot a hazard the whole ride should know about, text ALERT and a few words, like: ALERT glass in the shoulder at mile 12."

3. Getting help: supported event, crew signed up (text SUPPORT first; if it says crew is available, read this instead)

"This ride has support crew. For a flat, a mechanical, or if you're lost, text #SUPPORT, then where you are and what's wrong, like #SUPPORT mile 42 by the church, broken chain. A text that just says 'help' won't ask the crew for help. A crew member may text or call you back. Once you text support, your texts go to support, not ride chat, until you text RESOLVED. If you can't text, call this number and leave a voicemail. That is a recording, not a person. Urgent means 911."

4. Close

"Save this number now. One more time: hurt or in danger, call 911. Hazard for the group, text ALERT. Before you head home, text FINISH and tell us how the ride went. Questions? Find me."

What riders should do

During the ride

• ROSTER shows who checked in. ROSTER OUT shows who is still on the road.
• ALERT message asks you to confirm. Reply YES ALERT. Limit: 3 per phone every 2 minutes.
• No reply, wrong phone, balance owed, or forgot phone: use Wild Apricot Admin.
• Support requests go to CREW volunteers, not to you, unless you joined CREW.

Full detail: ride leader guide.

Back to guide choices

Ride leaders: advanced guide

Download or print this guide (PDF)

For supported events, centuries and other large rides, and planned groups. Read the basic guide first. Most weekly rides do not need this page.

Which one am I leading?

Supported events

Support exists only while volunteers have signed up on the shared crew line. A volunteer texts CREW, picks the event, and replies YES CREW. That opens 24 hours of coverage. An event tag, name, size, or leader assignment does not turn it on. Confirm before you promise riders anything. Volunteers have their own crew guide.

• Riders text #SUPPORT with a location and a problem. It goes to the crew, not to you, unless you joined the crew yourself.
• A rider who cannot text can call the CRW number and leave a voicemail. That is a recording, not a person, and it is transcribed and texted to the crew.
• Once a rider sends #SUPPORT, their texts go to support, not ride chat, with no timer, until they text RESOLVED or GROUP.
• The crew expiring, closing, or emptying does not end a rider's request.

The supported-event script

Read parts 1 and 2 of the basic script, then this instead of part 3:

"This ride has support crew. For a flat, a mechanical, or if you're lost, text #SUPPORT, then where you are and what's wrong, like #SUPPORT mile 42 by the church, broken chain. A text that just says 'help' won't ask the crew for help. A crew member may text or call you back. Once you text support, your texts go to support, not ride chat, until you text RESOLVED. If you can't text, call this number and leave a voicemail. That is a recording, not a person. Urgent means 911."

Large rides and centuries

• Check-in opens 3 hours before the start and closes 3 hours after. An ordinary ride is 2 hours each way.
• A long ride stays active until about two hours after its end time, so riders still out late keep their ride context.
• There is no default all-event chat. Use ALERT for urgent news and groups for smaller conversations.
• A verified leader who has checked in and is in the main chat can send event-wide chat. Once you join a route or pace group, your ordinary texts go only to that group, so the other routes do not see them. To reach every route, use ALERT.

Groups

Plan them before the ride so check-in can suggest the right one.

• GROUP PLAN: open planning for a ride you lead.
• GROUP ADD 50 mi / 16-18 / 8:30: add a group. Distance and pace help check-in suggest it.
• GROUP COPY LAST, then YES COPY GROUPS: copy names from the last clean recurring ride.
• Riders: GROUPS lists them, JOIN 2 joins group 2, HERE G2 checks in and joins at once.

Roster filters

ROSTER NOTIN shows riders not checked in. ROSTER SHORT, MEDIUM, LONG, or 75+ filters by distance (under 30, 30-49, 50-74, 75 and up). ROSTER ROUTE 30-49 and ROSTER PACE 16-18 take ranges. ROSTER ? shows help. Distances come from the ride description.

More than one leader

Leaders and co-leaders on a ride share the same roster and tools: READY opens the leader hub, and ROSTER REFRESH or READY REFRESH refreshes a stale roster. CALL OFF RIDE is leader-only. CLONE copies a ride and needs global Ride Leader membership.

Full command list: cheat sheet.

Back to guide choices

Crew volunteers

Download or print this guide (PDF)

For supported events only. Most rides have no crew on the text line.

You are a volunteer who covers the text support line for a CRW event: the person who gets a rider's "broken chain at mile 42" and decides whether to call them back. You do not need to be a CRW member or a registered rider. You need a phone that can text.

CRW SMS number: 573-279-2739

Emergencies are not handled by text. Anyone hurt or in danger calls 911. If a request describes an injury or danger, tell the rider to call 911. Every support message ends with "Emergency: call 911."

What you are signing up for

• Riders text #SUPPORT with a location and problem. It goes to everyone on the crew.
• Riders who cannot text can call the CRW number and leave a voicemail. It is transcribed and texted to the crew.
• You also receive event-wide ALERT messages.
• Replying CLAIM is optional. If nobody claims, the request still reached the whole crew.

There is one shared crew at a time, tied to one event.

Join the crew

From your own phone, text the CRW number:

1. Text CREW.
2. If no crew is open, you see up to five public events from CRW's event list. Reply with your event's number, or text CREW <event-id>. If a crew is already open, you see its event and when it ends.
3. Check the event name, then text YES CREW.

Opening a crew starts 24 hours of coverage. The confirmation shows when it ends, in Eastern time. Others join by texting CREW. Joining later does not extend it.

During your shift

A support request looks like this:

CRW ride support
<event name>

Rider: <name>
Phone: <rider's full phone number>
Message: mile 42 near the church, broken chain
CLAIM - optional, tell rider you can follow up
Emergency: call 911.

A voicemail request shows Call back: and a Transcript:. The transcript is automatic and can be wrong, so call back to confirm.

To take a request: text CLAIM. The rider is told you can follow up, and the first claim wins. Then call or text the rider at the phone number shown. If it is an emergency, tell them to call 911. Claiming is a courtesy, not a lock: if you cannot follow through, tell the rest of the crew yourself.

Crew commands

Keeping coverage going

• Coverage ends 24 hours after it opened or was last renewed. About an hour before, active crew get a warning text (sent between 6 AM and 10 PM Eastern): "CRW support for [event] closes at [time]. Reply KEEP CREW for another 24 hours, or CLOSE CREW if support is finished."
• KEEP CREW cannot revive an expired crew. After it ends, someone starts a new one with CREW.
• If you are the last one to leave, support is unstaffed. A new #SUPPORT text or call is told no crew is available, and to call 911 in an emergency.
• Before CLOSE CREW, hand off anything you claimed. If you are just done for the day and others are covering, use LEAVE CREW.

The rider's side of a request

A rider's request has no timer. It stays open until they text RESOLVED or GROUP, and until then their texts go to support, not ride chat. The crew expiring or emptying does not close it, and if nobody is left their next update is told it could not be delivered. When you finish helping, tell the rider to text RESOLVED. Ending it does not notify you.

Questions

Nobody answered a rider. Claiming is optional. Check your phone, claim, and call them. Texts can be delayed.

I want to stop all CRW texts. Reply STOP. That unsubscribes you from all CRW SMS, including crew requests. To stop covering one event, use LEAVE CREW.

Commands in full: cheat sheet.

Back to guide choices

Administrators

Download or print this guide (PDF)

For CRW staff and Wild Apricot admins. Engineers who deploy or debug the system should use the operations runbook.

CRW SMS number: 573-279-2739

What this is

CRW SMS is the ride-day layer on top of Wild Apricot. Riders text the number to check in, say they finished, and give feedback. Leaders text it to see who is here and to reach the whole ride. Wild Apricot stays the source of truth for members, events, registrations, waivers, and payments. SMS cannot waive a bill or override a registration.

It is not an emergency line. Nobody reads texts to it live. Every rider-facing message says to call 911 in an emergency. Do not promote the number as a way to reach CRW in a crisis.

What to keep right in Wild Apricot

SMS is only as accurate as these records.

• Rider phone numbers. Riders are recognized by the phone on their profile. The most common ride-day failure is a rider texting from a different phone.
• Leader and co-leader assignments on each event, set before ride day. Leader tools are tied to the specific ride.
• Event description with route distance. Roster filters read it. SMS does not guess a distance from the event title.
• Event end time. Set a real end time on each event. An unfinished check-in stays active until two hours after the event end. With no end time on the event, it lapses 24 hours after the start instead, so a long ride or century needs its true end time to stay active until the last rider is in.
• Waivers and payments. SMS blocks check-in while Wild Apricot shows an unpaid balance. Fix it in Wild Apricot.

Check-in windows

Ordinary ride: 2 hours before the start through 2 hours after. Century or large ride: 3 hours each way.

Ride-day help

Manual check-in in the Wild Apricot Admin app covers anything SMS cannot.

Supported events

Support on the text line exists only while volunteers have signed up. No event tag or admin setting turns it on. Recruit volunteers, send them the crew guide, and have one text CREW, choose the event, and reply YES CREW. Coverage lasts 24 hours and is renewed with KEEP CREW. Before the start, a leader or admin texts SUPPORT to confirm crew is available.

Keep the emergency wording consistent

Anything you publish should say the same thing as the guides index: hurt or in danger, call 911; the CRW number is not an emergency line. The website safety page source is in `docs/site-pages`.

Privacy basics

Riders opt in by texting the number; STOP unsubscribes them. Ride chat and alerts go to checked-in riders who opted in. A support request shows the crew the rider's name and full phone number. SMS activity is logged for operations.

When something looks wrong

Source versus live

These guides describe the repository source, not what is deployed. The shared crew flow needs a coordinated Supabase and Twilio release. Before an event, confirm the release state with the runbook, then text SUPPORT and CREW from a test phone.

Back to guide choices

Full command reference

Everyone

Text:

• MENU: open the main menu.
• HELP: carrier-style CRW SMS help text. For the command menu, text MENU.
• RIDES: see upcoming CRW rides.
• MY RIDES, MY RIDE, or STATUS: see your current/upcoming rides and where ordinary texts will route right now. Reply with a listed number for ride details; that also selects the ride for follow-up commands. When only one ride is listed, SMS uses a singular Your CRW ride screen and still accepts 1 for details.
• HERE: check in when you arrive. CHECK IN also works.
• YES or JOIN: confirm the ride most recently selected from RIDES. If the ride requires a waiver, review the link and reply I AGREE; a paid registration reply includes the balance and payment link returned by CRW.
• HERE G2: check in and join a listed chat group in one text. CHECK IN G2 also works.
• FINISH: mark your ride complete.
• LEAVE RIDE: mark that you left early.
• UNREGISTER: remove yourself from a ride.
• SAFETY: get the CRW safety page.
• MEDIA: get the CRW media-share page.
• MORE: open the expanded menu. Reply with any displayed number, including 7 when a checked-in ride also offers the CREW option.
• FEEDBACK GREAT, FEEDBACK OKAY, or FEEDBACK PROBLEM: send quick feedback.

When STATUS can prove one checked-in current ride, its routing line follows the same rules as ordinary chat: an ordinary ride with no group uses main chat, a large or century ride with no group uses commands, a resolved active subgroup uses that subgroup, and a large ride uses main chat only for a verified event leader with a valid main-chat membership. If the active ride is ambiguous or a supporting read fails, or a non-Century route depends on an unavailable event distance, STATUS omits the routing line instead of guessing from rider distance.

Ordinary unrecognized text during the check-in window may check you in. After you are checked in, ordinary text may go to ride chat or your active group chat.

If SMS says CRW shows an unpaid balance, use the payment link in the message. After payment clears, text HERE again. Ride-day check-in cannot waive or create a bill.

If check-in lists multiple rides, reply with the ride number to save the selection, then text HERE again. The numeric reply alone does not check you in.

If SMS says a paid ride ticket needs staff review, the rider is registered in Wild Apricot but the ticket invoice was not available through SMS. Use the Wild Apricot registration/payment page or ask staff to review the missing invoice.

On the active Ride menu, FINISH and LEAVE RIDE are explicit typed commands, not bare-number actions. Numbers still work for safe selections such as choosing rides, MORE, and post-FINISH feedback.

If a rider tries HERE or CHECK IN and SMS has a fresh complete registration row, it can check them in without doing another live scan first. If that row is stale, missing, or incomplete and SMS cannot confirm live registration or check-in status right now, the reply says that confirmation is unavailable and does not check the rider in. If live status is reachable and SMS does not see that phone on the check-in list, the reply tells the rider to find the ride leader and includes cached ride leader names when available.

Chat And Groups

Normal rides:

• Without planned groups, HERE joins the main SMS ride chat.
• If groups are set up, HERE checks the rider in and may recommend a group from registration distance or pace. If it cannot recommend one, it lists the groups. The rider texts JOIN plus the group number, or GROUPS for the full list.
• Planned-group rides do not auto-place riders into a hidden main chat. Group chat starts when the rider chooses a group.
• Ordinary chat goes by direct SMS fan-out only to checked-in riders who have opted in by texting CRW SMS for that ride.

Check-in confirmation does not wait for chat setup. Chat/group enrollment continues immediately after the reply; if GROUPS does not show the expected membership after a short delay, use JOIN plus the group number.

Large rides:

• HERE turns on ride alerts and updates.
• Riders do not have a default all-event ordinary chat.
• Verified ride leaders can send ordinary event-wide chat after checking in.
• Use GROUPS for smaller opt-in chat groups.
• Riders use ALERT for event-wide safety messages.

Commands:

• GROUPS or CHAT: list chat groups for your active ride.
• GROUPS ?: show chat-group command help.
• GROUPS 11 or GROUPS 21: page through longer group lists.
• START GROUP route / pace / start: start a route or pace group.
• JOIN plus the group's number from the GROUPS list: join that group. For example, JOIN 2 joins group 2. HERE G2 also works when checking in; CHECK IN G2 remains an accepted alias.
• Bare JOIN needs context: use GROUPS, then JOIN plus a listed group number for chat groups; use RIDES, then choose a ride for registration.
• MY GROUP: see your active group.
• LEAVE GROUP: leave your active group. On normal rides, ordinary texts return to the main ride chat; on large rides, ordinary chat waits until you join another group.

If HERE G2 confirms check-in but says it could not finish joining the group before replying, use GROUPS, then JOIN G2 to retry the chat-group join. The check-in itself is still recorded.

Legacy tester commands NEW GROUP name and JOIN G1 still work.

Safety And Support

• ALERT message: send a short safety alert to SMS opted-in checked-in riders and the current consenting CREW covering your active ride. Alert text is normalized and bounded to 260 characters before it is confirmed or sent. The confirmation includes an indicative rider/crew count when the cache read is available. If CREW is absent, expired, or closed, eligible checked-in riders still receive the event-wide alert; only CREW recipients are removed.
• ALERT GROUP 2 message: send a targeted safety note to group 2. Use the group's number from the GROUPS list.
• #support location + problem: contact the shared CREW support line. Caller check-in age does not disable support. An expired, closed, or unstaffed bridge accepts no new requests; a different event context is not silently reassigned.
• CLAIM, ACK, ACK SUPPORT, CLAIM SUPPORT, or TAKE SUPPORT: optional, from the phone of an active volunteer on the original CREW that received the request, notify the rider that you can follow up and may call/text.

Use ALERT for urgent rider safety notes, hazards, route changes, or severe weather. In an emergency, call 911 first.

SUPPORT, HELP SUPPORT, and RIDE HELP show the same safety and support instructions without opening a support session. Words like help, lost, or flat do not open support by themselves. While a support conversation is open, ordinary texts continue to support without a time limit until the rider texts GROUP/CHAT (or BACK TO GROUP) or RESOLVED (also CLOSE SUPPORT / DONE SUPPORT). These end support routing; they do not confirm that help arrived. If eligible CREW becomes unavailable, support stays open and messages cannot silently become ride chat. A new hashtag after an explicit exit starts a new request, subject to current staffing. When a support recipient replies with any supported claim alias (CLAIM, ACK, ACK SUPPORT, CLAIM SUPPORT, or TAKE SUPPORT), the rider gets a separate support update. This is optional callback coordination; the support request still fans out even if nobody claims. The first claim wins; later claim attempts report who already replied. Claiming is not proof that Twilio delivered every crew SMS.

CREW

One support line has one shared bridge associated with one public event. Volunteers need not be CRW members or registered riders. Event dates, tags, registration windows, and capacity do not open or close coverage.

• CREW: see the current bridge or choose an event for a new one. Use a number from the displayed list, or CREW <event-id> for an exact event. A direct event ID first checks the current bridge: a matching event shows its pinned join/status, while a different event is not opened alongside it. Text CREW to view or join the named current event.
• YES CREW: confirm the named event and join. Opening starts 24 hours of shared coverage; joining again does not extend it. Confirmation shows the absolute expiry in Eastern time. Others can join by texting CREW to this number.
• KEEP CREW: any active volunteer renews coverage for everyone still on the bridge until 24 hours after renewal. It cannot revive an expired bridge.
• CLOSE CREW, then YES CLOSE CREW: any active volunteer may confirm early closure for everyone. Arrange handoff of outstanding requests first.
• LEAVE CREW or EXIT CREW: leave coverage on this line without removing anyone else. The last departure makes it unstaffed; a new join before expiry can restore staffing.

One warning occasion is scheduled before expiry, using the existing 06:00-22:00 Eastern schedule. Reply KEEP CREW to extend coverage; otherwise it expires, even if the warning could not be delivered. New coverage requires a fresh signup and does not inherit the previous volunteers. Already-accepted requests stay tied to their original bridge, never a replacement; leaving or explicitly closing removes recipients from subsequent sends.

Leaders

Text MY RIDES, pick the ride you lead, and the reply becomes the leader hub for that ride. LEADER remains supported: for a selected active ride it points to the hub; otherwise it shows planning tools. Leaders still have all rider commands. On normal rides, ordinary leader text uses the same main ride chat as rider ordinary text.

Leader commands:

• READY: reopen the selected/resolved ride leader hub with roster counts, crew count, chat groups, mode, and freshness. READY REFRESH refreshes the roster cache and returns a short completion receipt; send READY next for the detailed snapshot.
• ROSTER: see a compact count summary and rider check-in state grouped for SMS scanning. Pending riders have no marker. Active markers are C checked in, F finished, and L left early. Chat-group labels are best-effort enrichment; if the chat group read is slow, ROSTER returns the rider state first without waiting for labels.
• ROSTER REFRESH: refresh the Wild Apricot-backed roster cache and return a short completion receipt. Send ROSTER next to read the refreshed counts.
• ROSTER ?: show roster filter help without reading the live roster.
• ROSTER OUT: focus on riders still on the road.
• ROSTER NOTIN: focus on riders not checked in.
• CALL OFF RIDE: start the leader-only ride cancellation workflow.
• GROUP PLAN: plan route/pace/start group shells for an upcoming ride you lead.
• TIPS: open ride leader tips.
• CLONE: start the ride-copy workflow. A successful clone opens group planning for the new draft and copies non-main planned group shells from the source ride when they can be read.

Group planning commands:

• GROUP PLAN eventID: open planning for a specific ride you lead.
• GROUP ADD route / pace / start: add a planned group shell. Include distance and pace when you can, for example GROUP ADD 50 mi / 16-18 / 8:30 or GROUP ADD Amy 33@15-16, so check-in can make better group suggestions.
• GROUP RENAME 3 new name: rename empty planned group 3. Use the group's number from the GROUP PLAN list.
• GROUP REMOVE 3: remove empty planned group 3, by its listed number.
• GROUP COPY LAST, then YES COPY GROUPS: copy group names from the last clean recurring match.

Roster distance filters:

• ROSTER SHORT: less than 30 mi.
• ROSTER MEDIUM: 30-49 mi.
• ROSTER LONG: 50-74 mi.
• ROSTER 75+: 75+ mi.
• ROSTER DISTANCE SHORT, ROSTER DISTANCE MEDIUM, ROSTER DISTANCE LONG, ROSTER DISTANCE 75+: same bucket filters with explicit wording.
• ROSTER ROUTE 62, ROSTER DISTANCE 62, or ROSTER 62 MI: resolve 62 to the matching bucket, shown as LONG (50-74 mi).
• ROSTER ROUTE 30-49: match a numeric distance range.
• ROSTER ROUTE 30 AND 50: match either exact distance.

Roster output reads event-level route distances from the ride description. If the description has one distance, the roster shows that distance once in the header and groups riders by pace. If the description has multiple distances, the roster groups by distance, then pace, and puts unclear rider choices under Distance not set. It does not guess a rider's route from the event title or treat noisy cached rider distances as separate route choices. When the description lists multiple route distances, cached rider distance is used only to choose the nearest listed route. If the description has no route distance, route filters match no riders instead of defaulting to 30 miles.

Within each group, all-pending rosters sort names alphabetically. Once check-in has started, riders sort by status (C, L, F, then pending) and then alphabetically inside each status.

Roster pace filters:

• ROSTER PACE 16: match numeric pace 16.
• ROSTER PACE 16-18: match numeric pace range.
• ROSTER PACE 16 AND 18: match either pace.
• ROSTER PACE CASUAL or ROSTER PACE INTERMEDIATE: match free-text pace labels.

Bare raw numbers like ROSTER 16 return roster help. Use PACE, ROUTE, DISTANCE, MI, +, or a named bucket.

Back to guide choices