OKANOGAN SCHOOL DISTRICT
Larry Scroggins, Transportation Supervisor at Okanogan School District in north-central Washington, came to us with a list of what he needed from a digital DVIR. Seven items, in his own words. This page is what we delivered against each one — named, dated, and live in production.
WHAT LARRY WAS WORKING WITH BEFORE
Okanogan SD runs a rural school bus fleet in north-central Washington. Before One-Touch DVIR, Larry's drivers were on a digital DVIR product that cost the district $30 per seat per month. The hardware and software were bundled. The monthly reports were a problem he had to solve himself — assembling individual records from the vendor's dashboard, formatting them for his files, then doing it again the next month. The drivers tolerated the product. The mechanic didn't get real-time defect alerts. The whole arrangement worked, in the sense that it was technically compliant, but Larry's day was spent compensating for what the tool didn't do.
What Larry wanted was simpler. He wrote down what "simpler" meant. That list became the spec we built to.
LARRY'S SEVEN ASKS, AND WHAT WE DELIVERED
1. "Make it simple. One touch."
Delivered. A driver completes a no-defect pre-trip or post-trip inspection by tapping No New Defects Found, entering their 4-digit PIN, and tapping submit. Under five seconds on the no-defect case, which is roughly 99% of inspections in a well-maintained fleet. No menus. No screens to swipe through. No "did you check the wipers" stepwise checklist for a driver who already checked the wipers.
2. "Deliver my monthly reports — don't make me build them."
Delivered. On the first day of every month, an Apps Script time trigger fires automatically and emails Larry a per-bus DVIR dossier covering the prior month's inspection history. No printing. No compiling. No end-of-month scramble. The first production cycle of this report runs June 1, 2026 — generated by a server-side trigger that doesn't need anyone to remember to run it.
3. "Drivers need to know the repair status."
Delivered. Every driver's home screen shows the live defect status for their assigned bus. What's been reported, who reported it, when, and where the mechanic has it in the lifecycle — New Defect → In Progress → Parts Ordered → Out-of-Service → Clear. No more drivers asking each other in the yard whether the brake issue was ever fixed.
4. "Give my mechanic a simple back-end."
Delivered. Fausto Munez, Okanogan's fleet mechanic, manages the entire defect lifecycle from one sheet. Status dropdown. Mechanic notes field. Action date. When Fausto updates a defect, the driver's next pre-trip screen reflects it. No separate "mechanic app," no second login, no separate phone notification system to administer. One sheet, one source of truth.
5. "Keep it legal — including the new April ruling."
Delivered. One-Touch DVIR was built to the FMCSA eDVIR Final Rule effective March 23, 2026 and operates under 49 CFR §§ 390.32, 396.11, and 396.13 — the full citation chain, with § 390.32 (electronic signatures) named alongside § 396.11 (DVIR content) and § 396.13 (driver review) on every reference. The Washington-specific WAC sections (392-145, 446-65) are satisfied in the same flow. Full rule-by-rule implementation walkthrough is on the Compliance page.
6. "Save us money."
Delivered. Larry was paying $30 per seat per month with his prior tool. Okanogan now runs on One-Touch DVIR at $20 per driver per month, with no hardware bundle and no setup fee. Across his fleet, that's a measurable monthly reduction — and a structural change to how the budget line is shaped: one number per driver, on a month-to-month basis, with no multi-year contract.
(Note on units: the displacement is from a per-seat product to a per-bus product. The savings number depends on Larry's specific seat-to-bus ratio. Districts evaluating One-Touch DVIR against their own per-seat or per-bus incumbent will see the math directly when they get a quote — we'll work it from your fleet size, not from a generic table.)
7. "My crew has to actually use it."
Delivered. Daily use since rollout. In Larry's own words:
That's not a marketing line. That's what he said when asked how the deployment was going. It's the single most important sentence in this case study, because every product in this category claims drivers will love it. Larry has the receipts: every-day usage, no support tickets, no driver complaints, no shadow-paper inspection sheets being run in parallel.
WHAT'S RUNNING IN THE BACKGROUND AT OKANOGAN, RIGHT NOW
Beyond the seven items on Larry's list, here are the things the system is doing for Okanogan that don't show up on a feature comparison chart but that matter when an auditor walks in:
- Real-time SMS alerts to Fausto when a defect is submitted. SMS delivery is via Telnyx (switched from Twilio in May 2026 after Twilio failed to deliver reliably for our account — an operational detail we mention because it's the kind of small fix that determines whether the alert system actually works).
- Versioned legal attestation under ESIGN Act + § 390.32. When the legal text changed in May 2026 to v1.1, every Okanogan driver re-accepted the new version before their next submission. The consent log has every acceptance, with timestamps and UUIDs.
- Forced re-attestation gate. When v1.2 lands someday, Okanogan won't have to think about it. The system handles it the same way.
- UUID submission deduplication. A driver who taps submit twice, or who retries from a poor-signal area, cannot create duplicate inspection records. This matters at audit.
- Out-of-Service driver lockout. When Fausto marks a bus OOS, the next driver to open the app for that bus gets a full-screen "Do not operate" lockout. They cannot dismiss it to start an inspection.
- District-owned data. The Google Sheet that holds every Okanogan inspection lives in an account Larry's district owns. If we vanished tomorrow, the compliance ledger would still be there.
BUILT AROUND A REAL SUPERVISOR'S DAY. NOT A SOFTWARE VENDOR'S ROADMAP.
The case study you just read isn't a sales narrative. It's the public version of a list a real Transportation Supervisor handed us in early 2026. Every item is named. Every item is delivered. The supervisor's name is on the page. The district's name is on the page. The pricing is on the page. The pull quote is verifiable — Larry will take calls from peer supervisors evaluating the system.
If your district is evaluating One-Touch DVIR and would value a peer reference call with Larry, email bob@ramventuresolutions.com and we'll arrange one with Larry's prior consent.