ROADGAME

Athletic transportation, finally organized

Stop finding out about
bus problems
on game day.

RoadGame turns the sports schedule into confirmed transportation. Import your games, request buses from your existing vendors, collect replies by email or text, see which trips are at risk, and keep coaches updated — without another spreadsheet chase.

Apply for the pilot → See how it works

Today at a glance

1 Schedule import — Arbiter, rSchoolToday, or a Google Sheet CSV.
0 Vendor logins. They reply from email or SMS magic links.
1 Ranked risk list — the trips most likely to cause a fire drill.
All One trip record: every request, reply, change, and coach update.

What goes wrong

The schedule is not the problem. The follow-up is.

Most problems start small: a vendor hasn’t replied, a change lives in the wrong email thread, or a coach doesn’t know the bus number yet. RoadGame is built for the messy middle between "the game is scheduled" and "the team is on the bus."

Problem 01 Buried

Vendor replies get buried.

Bus requests go out by email, text, phone call, or whatever worked last time. Then someone has to remember who answered, who declined, who needs a nudge, and which confirmation belongs to which trip.

Problem 02 Too late

Coaches get updates too late.

A changed pickup time or driver name is only useful if the right coach sees it before departure. RoadGame sends the practical details by SMS at the moment they matter.

Problem 03 Unnamed

Friday feels risky, but the risk is hard to name.

With forty trips on the board, you shouldn’t have to scan every row to find the three that need attention. RoadGame ranks the open threats so you know what to fix first.

How RoadGame works

From schedule import to confirmed departure.

RoadGame works with your existing schedule and vendors. No new vendor portal, no coach app to roll out — just a clearer way to request, confirm, notify, and prove what happened.

  1. Start of the week

    Import the athletic schedule.

    Upload a CSV from Arbiter, rSchoolToday, or Google Sheets. RoadGame stages the trips, keeps key details together, and gives your team one place to work from.

  2. When trips need buses

    Request transportation from your vendors.

    Send bus requests by email and SMS. Vendors use a secure magic link to confirm, decline, or send a counter-offer. They don’t need an account.

  3. Before game day

    Work the ranked Threats feed.

    RoadGame flags trips that still need attention: no vendor reply, missing driver details, capacity concerns, timing conflicts. The highest-risk trips rise to the top.

  4. Game day

    Text coaches the details they need.

    Coaches receive SMS updates with the bus number, driver name, pickup details, and ETA when available. STOP and HELP are supported, and delivery activity is logged.

  5. After the trip

    Keep the record for next time.

    Every trip keeps an audit trail: what was requested, who replied, what changed, what coaches received, and how each vendor performed. At renewal, you have evidence instead of memory.

A missed bus almost never starts with one big mistake. It starts with one unanswered request, one stale spreadsheet, or one coach who never got the update.
RoadGame pilot note

2026-27 pilot

Bring RoadGame into
your department
for pilot season.

RoadGame is pre-launch, opening an early pilot for the 2026-27 season. It works with your existing schedule and current vendors. If your school or district is interested, apply below and we'll be in touch.

Apply for the pilot

Tell us a bit about your department and we'll follow up.