Operator handbook · Ventor · v1

How Ventor works

For crews moving from pen-and-paper to a shared dashboard. Print this for the follow vehicle's glove box.

Section

Start here

5-minute tour for new crew

start · 5 min read

Quick start — 5 minutes, no jargon

Sign in. Land on the right screen. Know what to tap. Built for crew who've never used a dashboard.

What Ventor replaces

The whiteboard in the follow vehicle. The WhatsApp scroll-back. The printed cue sheet on Kabir's handlebars. One screen, whole crew, always in sync.

Step 1 · Sign in (1 min)

  1. Open ventor.fit on your phone or laptop.
  2. Tap Sign in. Enter the email Vishal or Sapna invited.
  3. You'll get a magic-link email — tap the link to log in. No password to remember.
  4. First time only: pick a name + tap Save.
Didn't get the invite?

Ping Sapna or Vishal on the crew WhatsApp. They'll add you in 30 seconds via Admin → Roster.

Step 2 · You land on War Room

War Room (the home tab) is everything you need at a glance — where Kabir is right now, any alerts, both vehicles, weather ahead, stop requests in flight.

  • Scroll top to bottom. That's it. No hunting.
  • Footer (always visible at the bottom): distance done, distance to go, average speed, TS progress.
  • Red banner = something needs attention (vehicles too far apart, open alert).
  • Quiet = everything's on plan.

Step 3 · Find your job tab

Driver / shiftCrew + Vehicles + your phone's /track page
Food / hydrationNutrition (tap the quick-log buttons)
Sleep planningSleep + Weather (rest in bad-weather windows)
Race rules / penaltiesCompliance + Time Stations
Crew chiefWar Room + Comms + Admin
Family / spectatorShare ventor.fit/spectator/kabir-raam-2026

Step 4 · Set km + °C (for Indian crew)

  1. Tap your avatar (top right corner).
  2. Find Units toggle.
  3. Tap once → switches the whole app to km + °C.

Step 5 · Use the ? button anytime

There's a ? icon next to your avatar at the top. Tap it on any screen and you'll see the help article that matches that page. Or tap the Ask AI tab and type a question in plain English — like 'what does the red banner mean'.

When in doubt

Tap the ? button. The drawer that opens always knows what page you're on. Free help, no judgment.

Glossary you'll see a lot

TSTime station. There are 54 between Oceanside and Atlantic City.
Stop requestHow crew tells Kabir to stop. Gives him 15 min heads-up.
Follow / LeapfrogThe two support vehicles. Must stay within 30 min of each other.
Headwind / TailwindWind vs route direction. Red = bad (slow), green = good (boost).
Shuttle zoneTS9 Sedona + TS52 Delaware Bridge — Kabir gets driven across, no riding allowed.
Fast-path stopMech or medical reason — no 15-min wait, dispatch now.
Promise

If you can use WhatsApp, you can use Ventor. The buttons say what they do.

Section

During the race

What to do, screen by screen

live-ops · 4 min read

War Room — the live dashboard

What every panel on the home tab means, top to bottom.

War Room is your situational awareness in one screen. Scroll top to bottom; do not lose time hunting for info.

Top header

  • Race state pill — PRE / LIVE / FIN / CUTOFF.
  • Elapsed clock — total time since the official RAAM start (Eastern Daylight Time, locked).
  • Cutoff clock — countdown to the 288-hour solo cap.
  • Alerts bell — current open alerts; tap to skim.

Body

  • Separation banner (only when needed) — red if Follow ↔ Leapfrog vehicles drift more than 30 minutes apart.
  • Position card — Kabir's current mile, current TS, current speed, age of last GPS fix.
  • Alerts list — open compliance + race alerts, ranked by severity.
  • Weather glance — temperature + wind component for next stretch.
  • Stop request panel — see active stops + create new ones (15-min rule).

Footer

The bottom strip is fixed — distance done, distance to finish, average speed, TS progress, elapsed, target delta. It follows you on every screen so you never lose the basics.

Habit to build

Glance at War Room every shift change. 10 seconds tells you if everything is on plan.

live-ops · 3 min read

Stop requests — the 15-minute rule

How to ask Kabir to stop without breaking his rhythm. Mech and medical bypass the wait.

Kabir's request: any unplanned stop must give him a 15-minute heads-up so he can plan effort, food, hydration, and bathroom around it. Mechanical or medical issues bypass this — they dispatch immediately.

How to file a request

  1. Open War Room. Find the Stop requests panel.
  2. Tap + Request stop.
  3. Pick a reason chip — Loo, Food, Mech, Medical, Sleep, Media, Other.
  4. Add an optional note (e.g. 'driver needs coffee, 5 km ahead').
  5. Tap Send. The 15-minute counter starts. Mech + Medical chips dispatch instantly.

Lifecycle of a request

pendingCounter ticking. Rider has not acknowledged yet.
acknowledgedRider tapped ✓ — knows the stop is coming.
dispatchedRider has stopped. Crew is now executing.
cancelledCrew cancelled (e.g. found alt, rider declined).
Rule of thumb

If you'd otherwise just shout it on the walkie, file a stop request instead. The whole crew sees it, the rider sees it, the timeline keeps a record.

live-ops · 4 min read

Vehicles + live tracking

How Follow + Leapfrog vehicles stay synced + how to push GPS from a phone.

Two vehicles, one rule: stay within 30 minutes of each other at current speed. The app enforces this and flags drift in red on War Room.

Tracking from a crew phone

  1. Open /vehicles on the on-duty crew phone.
  2. Tap Track from this phone on the right vehicle (Follow-1 or Leap-1).
  3. Allow location permission.
  4. Pick the Driver and Navigator from the dropdowns.
  5. Tap Start tracking. Pings post every 30 seconds while the tab is open.
  6. Add to home screen for native-feel persistence.
Why phone GPS is enough

Phone GPS is more accurate than the Garmin tracker for support vehicles. Garmin is the secondary source. RAAM live tracker is rider-only.

If pings stop arriving

  • Phone went to sleep — keep the tab visible, or use Add to Home Screen.
  • Permission was revoked — re-allow in browser settings.
  • No signal — pings buffer briefly then drop. Move to the next ridge.
  • Vehicle marked inactive — only chief can reactivate via /admin/roster (coming soon).
live-ops · 3 min read

Reading the weather + headwinds

Open-Meteo data per time station + signed wind component. Plan sleep around bad weather, not in spite of it.

Weather is fetched from Open-Meteo every 15 minutes for the rider position and the next six time stations. The app classifies wind into headwind / tailwind / crosswind based on the segment bearing — not the raw direction.

Wind component reading

+ value (green)Tailwind. Push harder, take less food.
− value (red)Headwind. Drop into aero, conserve effort.
near zeroCrosswind — Follow vehicle drives closer to block.

Auto-action triggers

  • Headwind > 15 km/h → WARN aero tuck + reduce 5%
  • Temp > 35 °C → AMBER pre-cool + ice socks
  • Temp < 7 °C → INFO stage warm layers in follow
  • Precip > 2 mm → WARN rain shell + check tire grip
Tactical sleep

When a 4-hour bad-weather block is forecast, time a 60-minute sleep break inside it. You lose less by resting in the storm than by riding through it.

live-ops · 3 min read

Time stations + the GPX route

54 time stations + section flags + the canonical GPX file.

RAAM 2026 has 54 time stations. Each one is on the live map with a colored ring showing the section's rule constraint.

Section flag colors

RedRacers only (Oceanside parade start).
OrangeNo aux vehicles (TS6→9 Skull Valley fallback).
PurpleShuttle zone (Sedona, Delaware Memorial Bridge).
BlueMandatory direct follow (TS10→13 Navajo Nation).
YellowLeapfrog daytime only.
CyanTime-zone change (TS10, TS23, TS38).
SlateAltitude pass (Wolf Creek, La Veta, Cuchara).
GrayLong stretch with no services.
TS6→TS9 (~150 mi)

Aux vehicle must take alternate route. Pre-stage fallback parking points. If Follow has a mechanical, Aux has to be reachable inside 30 minutes — plan accordingly.

live-ops · 3 min read

Comms — WhatsApp + Discord

Main WhatsApp group is the source of truth. Discord is for RAAM officials.

Three WhatsApp groups: Main (chief + on-duty leads), Shift-1, Shift-2. The app syncs only with Main — shift groups stay informal.

MainTwo-way sync with /comms timeline. Anything posted here logs in the app.
Shift-1 / Shift-2No app sync. Crew banter. Read-only mirror is fine.
DiscordOfficial RAAM channels only — race control, mandatory updates.
Don't lose the walkie

Walkies live in pockets, never on the car roof. The auxiliary vehicle does a perimeter check before any departure (helmet, vest, sling bag, walkie).

live-ops · 2 min read

Leaderboard — competitor positions

Filter to Kabir's age cat, see gap to leader + gap to Kabir.

RAAM live tracker scraper writes to /leaderboard every 30 s once race starts. Pre-race it shows a seeded plausible Solo Men <50 lineup so the UI isn't empty.

Filter chips

AllEvery racer + every team across all divisions.
My catSolo Men <50 only — Kabir's category.
SoloSolo divisions only.
ActiveRacing right now (drops finished + DNF + DQ).

Reading the row

  • Crown = leader. Orange highlight = Kabir.
  • Gap to leader is always negative (-X km behind).
  • Gap to Kabir is signed — red = behind Kabir, green = ahead.
  • Status pill: pre / racing / finished / dnf / dq.
  • Last ping = how recent the RAAM tracker updated this racer.
Why age category matters

Solo Men <50 cutoff is 288 hours. Different age groups have different cutoffs — comparing Kabir to a Solo Men 60+ racer is misleading. Use the My cat filter.

Section

Data + devices

GPS, weather, vehicles, sensors

data · 3 min read

Bikes + tool catalog

Four bikes, all Shimano Dura-Ace Di2 R9200. Manuals one tap away.

Open /bikes for the full fleet view. Each bike has a use-case so the crew knows which one to hand off when.

Addict (matte black)Climbs + rolling endurance
Foil RC (white/silver)Aero flats — Kansas, Indiana, NJ run-in
Foil RC (blue)Backup aero, identical spec
Plasma TT (teal/purple)TT aero — restricted handlers (Joby, Varun, Vishal, Satish)
Carbon wheels

Only crew with the verified handler skill should mount, dismount, or change tires. See the Crew skill matrix when it ships.

Manuals

  • Per-bike Scott manual — open from the bike card on /bikes.
  • Shimano Di2 dealer manual — shared across all bikes, in the Shared manuals section.
  • Pair with the Shimano E-TUBE Project Cyclist app for shift-mode tuning.
data · 2 min read

Crew skill matrix

Self-attest + chief-verify so stop-request routing knows who to dispatch.

Open /crew, scroll past the tracker. Skill matrix grid has rows = crew, columns = 12 skills (mech / driving / ops).

Two-stage attestation

  1. Self-attest: you tap the sky-blue circle for any skill you can do.
  2. Chief-verify: Kabir or Sapna tap the green shield after seeing you do it in Oceanside training.

Coverage badges

Red0 crew verified. Hire / train fast.
Amber1 crew verified. Single point of failure.
Emerald2+ verified. Safe coverage.
Why this matters mid-race

Stop-request fast-path for mech only dispatches crew with verified tubeless-patch + tire-change. If you haven't ticked + been verified, you won't get paged — you'll be standing around while a flat eats time.

Section

Before + after

Setup, debrief, settings

lifecycle · 2 min read

Settings — units, theme, account

How to switch units, change theme, sign out.

Units

Avatar menu → Units. Toggle imperial (mi, °F) ↔ metric (km, °C). The whole app converts at display time. RAAM data + GPX stay in imperial under the hood.

Theme

Top bar moon/sun icon. Dark by default, with auto night mode 19:00–07:00 that deepens contrast for in-car readability.

Sign out / switch team

Avatar menu shows your team. If you belong to more than one, switch from there. Sign out clears the session.

lifecycle · 2 min read

Emergency / SOS

Red button at the top. What it does, when to use it.

Use only for actual emergencies

Crash, medical event, lost rider. Not for flat tires or wrong turns — those are stop requests.

The SOS button is in the top bar (red). Tapping it:

  1. Records who pressed it + their last GPS
  2. Inserts a CRITICAL alert in the timeline
  3. Mirrors to Discord (RAAM HQ visible) and to the comms log
  4. Opens a confirm-or-cancel modal — you have 5 seconds to back out

After firing, the chief follows the SOS SOP: dial 911 (US) or local emergency, mark rider position, set up safe zone, log resolution in the alert when done.

lifecycle · 2 min read

Pre-race checklist

23 seeded items across Paperwork, Vehicles, Bikes, Nutrition, Tech.

Open /pre-race. The checklist is grouped by category and tracks 4 states: Open → In progress → Done → N/A. Cycle by tapping the icon on each row.

Workflow

  1. Skim all 23 items the day you sign in.
  2. Set anything you're personally responsible for to In progress.
  3. Mark Done as you complete in Oceanside.
  4. Mark N/A for items that don't apply (e.g. RV stuff if you have no RV).

Print the handbook glove-box copy

Open /handbook → browser Save as PDF or hit Print. The Race Documents section at the end has all the official RAAM PDFs (route book, rules, GEAR book, pre-race clearance, team duties). Carry in every vehicle.

Bonus — add your own items

Tap +Add item on the panel. Useful for crew-specific tasks like 'bring my own helmet' or 'stash spare contact lenses in follow-1 glove box'.

lifecycle · 2 min read

Push alerts on your phone

Get pinged the second a fast-path stop request is fired.

Avatar menu → Notifications → tap Enable push alerts. Your browser asks permission, then the app subscribes.

What you get pinged for

  • MECH · STOP NOW — fast-path mechanical stop request fired.
  • MEDICAL · STOP NOW — fast-path medical stop request fired.

Non-emergency stops (loo, food, sleep, media, other) do NOT push — they appear in War Room with the 15-minute countdown.

Phone-specific

iOS SafariMust Add to Home Screen first, open from icon, then enable. Apple requirement.
Android ChromeWorks in regular tab. Toggle anytime.
Desktop ChromeWorks while browser is running, even when tab is closed.
Disabling

Same toggle in account menu turns push off. Or block at browser/OS level any time.

Section

Reference

Glossary, troubleshooting, contacts

reference · 2 min read

Glossary

Acronyms and shorthand.

TSTime Station — official mile marker, 0 to 54.
RAWRace Across the West — first 940 miles of RAAM.
AuxAuxiliary support vehicle — secondary to Follow.
LeapfrogVehicle jumps ahead, sets up handoff, then follow vehicle catches up.
Direct followVehicle drives behind rider continuously, day + night.
Five-foot ruleVehicle must be at least 5 feet right of fog line when stopped.
Cutoff288-hour finish deadline for Solo Men Under 50.
EDTEastern Daylight Time — official RAAM clock.
Five-foot ruleMin lateral clearance when crew vehicle stops on the shoulder.
GEAR BookRAAM's official rule + route document, published yearly.
Di2Shimano electronic shifting on all bikes.
reference · 4 min read

Troubleshooting

Things that go wrong + the fix.

I can't see any data

Pre-race, most screens are empty by design — they fill in once GPS pings + log entries start. If you're mid-race and screens are blank: log out, log in, check Supabase status with the chief.

Vehicle pings stopped

Phone went to sleep, permission revoked, or signal dropped. Open /track/<id> on the on-duty crew phone, re-grant location, tap Start.

Wrong units

Avatar → Units → Switch. Affects the whole app instantly.

Can't sign in

Magic-link expires after 1 hour. Request a new one from /login. If still stuck, ask the chief to re-issue your invite.

Stop request stuck on pending

The countdown shows 'ready' once the 15 min are up — that's the cue for the crew to actually pull over. Tap → on the row to mark dispatched. If the rider declined, tap × to cancel.

Race documents · official

Print + carry offline

Synced from the RAAM 2026 race packet. Every follow + aux vehicle must have these on a phone (offline) or printed in the glove box.

  • 2026 Route Book (FINAL)RAAM officialOffline required

    Mile-by-mile cue sheet · 54 time stations · section rules (no-aux, shuttle, leapfrog) · alternate routes for RVs and aux vehicles.

    55 pages · 325 KB
  • 2026 RAAM RulesRAAM officialOffline required

    Full rulebook · time, cutoffs, penalties · support vehicles · racers · crew · media · route · start · finish.

    37 pages · 388 KB
  • 2026 GEAR Book — Pre-Race GuideRAAM officialOffline required

    Race details · scheduling · check-in · communications · route navigation · finish logistics.

    43 pages · 3.9 MB
  • Pre-Race Instructions + Clearance FormsRAAM officialOffline required

    Check-in protocol · photo session · self-inspection forms · clearance to race checklist. Print + sign before Oceanside.

    39 pages · 10 MB
  • Team Kabir — Roles & DutiesTeam KabirOffline required

    Internal SOP · who does what · pre-race, race, post-race responsibilities per crew role.

    1 page · 73 KB
  • Survival tips from veteran crews — sleep, food, comms, navigation, dealing with rider crashes / breakdowns.

    1 page · 3.4 KB
Generated from src/lib/help/articles.tsx · Ventor handbook · keep this copy in the follow vehicle.