A mobile-first PWA for school bus driver vehicle inspection reports. Drivers complete a no-defect inspection in one tap — All Clear, four-digit PIN, submitted. Defects route to your mechanic by SMS and email within seconds. Auto-generated per-bus dossiers reach your transportation supervisor on the first of every month.
Built to the FMCSA eDVIR Final Rule effective March 23, 2026. Operating under 49 CFR §§ 390.32, 396.11, and 396.13. Live at Okanogan School District (Washington) since May 2026.
The system has three roles, one shared dataset, and no extra software anyone has to learn. A driver who passes inspection is finished in one screen. A mechanic who gets a defect alert has it on their phone before the bus leaves the yard. A supervisor who needs a monthly DVIR dossier opens an email on the first of the month.
Not per seat. Not per driver. Not per inspection. Twenty dollars per bus, billed monthly. A district running ten buses pays $200/month. A district running fifty pays $1,000. The math is supposed to fit in your head — because the budget conversation you will have with your superintendent is supposed to fit on one line.
Included at $20/bus/month: unlimited drivers, supervisors, and mechanics on the account; pre-trip and post-trip e-DVIRs; real-time defect alerts; mechanic dashboard with full lifecycle; out-of-service lockout; monthly per-bus dossier to the supervisor; versioned legal attestation; your own Google Sheet owned by your district.
Minimum: 10-bus minimum ($200/month entry point). Annual prepay: 10% off (one month free). No hardware. No multi-year contract. No setup fees.
The FMCSA eDVIR Final Rule took effect March 23, 2026. One-Touch DVIR was architected to that rule and deployed to its first production garage in May 2026 — on infrastructure that already satisfied § 390.32 (electronic signatures), § 396.11 (DVIR content), and § 396.13 (driver review). Districts coming on board now inherit a system built to the new rule, not retrofitted to it.
The full citation chain belongs together. § 390.32 is what makes the four-digit PIN a lawful signature on an FMCSA-required document — drop it and the rest of the chain weakens. Every page on this site, every leave-behind, every public answer to a Transportation Director cites all three sections plus the Final Rule together.
"Drivers picked it up on day one — adoption has been the easiest part."
— Larry Scroggins, Transportation Supervisor, Okanogan School District
Okanogan School District (Washington) went live in May 2026 with One-Touch DVIR running on infrastructure they own — Google Sheet, Apps Script, Netlify site, all under district control. Transportation Supervisor Larry Scroggins manages PINs; Fleet Mechanic Fausto Munez works the defect dashboard. The district displaced a $30/seat/month prior tool at rollout.
Larry takes peer reference calls from other Transportation Supervisors evaluating the system. Email bob@ramventuresolutions.com to arrange one.
Larry's supervisor view, March 2026.
One driver, one bus, one no-defect inspection. The whole thing — open the PWA, tap All Clear, enter PIN, submit, see the confirmation, view the entry in the inspection log — takes under five seconds. Watch it once and you have seen the entire driver workflow.
You are going to ask whether this is really FMCSA-compliant, what happens when a driver loses signal, who owns the data, what the procurement story looks like, and what happens when something breaks at 5 a.m. on a school day. Those answers and four more are on the FAQ page.
Yes — under 49 CFR § 390.32 (Electronic Documents and Signatures). This rule explicitly authorizes electronic signatures on any FMCSA-required document, including the DVIRs required by 49 CFR §§ 396.11 and 396.13. The FMCSA eDVIR Final Rule effective March 23, 2026 cross-references § 390.32 as the operative e-signature authority. A supervisor-assigned 4-digit PIN, applied by the driver at submission, satisfies the rule.
The PWA logs the inspection locally with a UUID and shows the driver a not-yet-confirmed status with a Retry button. When signal returns, the driver taps Retry and the same UUID re-submits — the backend rejects duplicates, so no double-logging is possible. There is currently no automatic background retry; retry is manual. This is a known limitation in rural low-signal environments.
Your district. Every customer deployment writes to a Google Sheet owned by the district, not by Ram Venture Solutions. If you stop paying, the system stops writing to the sheet — but the sheet and every historical inspection it contains remains in the district's Google Workspace, in a format any auditor can read without proprietary tooling. No vendor lock-in by design.
There is no support ticket between you and a real answer — because there is no support team.
Bob McElderry is the founder, the developer, the operator, and the person who picks up the phone. He is also an active school bus driver, so the fastest path is email — phone calls return same day after his afternoon route.
✦ ACCEPTING NEW DISTRICTS · WSPTA-channel introductory rate available