DVIR Reporting done.In under five seconds.

One tap for a clean inspection. Defects alert your mechanic instantly.

“Drivers picked it up on day one — adoption has been the easiest part.”

— Larry Scroggins, Transportation Supervisor, Okanogan
No hardware No contract No paperwork No manual setup
$20/driver/mo Unlimited buses. No hidden fees.
Start risk free
Live driver flow · loops every 21 seconds
The Rule
The full citation chain
49 CFR § 390.32
Electronic Documents & Signatures
Authorizes e-signatures on any FMCSA-required document. This is what makes the 4-digit PIN a lawful signature.
49 CFR § 396.11
DVIR Content
Defines what a Driver Vehicle Inspection Report must contain. Every field is captured, every submission timestamped.
49 CFR § 396.13
Driver Review
Driver review of the prior DVIR before operating the vehicle. Out-of-Service lockout enforces this at the screen.
eDVIR Final Rule
Effective March 23, 2026
Cross-references § 390.32 as the operative e-signature authority. Architected to it from day one, not bolted on.

One signature. Every inspection covered.

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 every operative section. Districts coming on board now inherit a system built to the new rule, not retrofitted to it.

§ 390.32 IN PRACTICE

Signed once. Carried forward.

When a driver first activates their profile, they read and sign a full ESIGN-compliant attestation — the legal text you see here. Their supervisor-assigned PIN becomes their electronic signature under 15 U.S.C. § 7001. That agreement doesn’t expire after one inspection. It remains in force for every pre-trip and post-trip submitted from that device, until their profile changes.

That’s what makes One-Touch real. After setup, drivers tap one button — no PIN re-entry, no re-attestation, no friction. The compliance chain is already established. The system holds it.

The Five Seconds

Open. Tap. Done.

99% of inspections are clean. We optimized for the 99% case. Every screen, every tap, every keystroke was removed unless it earned its place in a five-second budget.

0.0s — 2.5s
Open the app
Driver opens One-Touch DVIR from their phone home screen. No app store. No login screen.
2.5s — 2.9s
Tap All Clear
The big green button. The 99% case. One tap on a no-new-defect walk-around.
2.9s — 4.2s
Submitted
Confirmation overlay. Inspection logged with UUID + device ID.
The Workflow

Three users. One source of truth. Zero paperwork.

The system has three roles and one shared dataset. A driver who passes is finished in one screen. A mechanic with a defect alert has it before the bus leaves the yard. A supervisor who needs a monthly DVIR opens an email on the 1st.

Driver
🚌

What the driver sees

  • Enter your supervisor-assigned 4-digit PIN — one entry, one e-signature, under 49 CFR § 390.32.
  • Open the app on any phone — no app store install.
  • Tap “All Clear” (the 99% case) or flag a defect with notes.
  • Done. Total time on a clean inspection: under five seconds.
Bob McElderry Bus #9 · Pre-Trip
✓ NO NEW DEFECTS FOUND
⚠ REPORT DEFECT
Mechanic
🔧

What the mechanic sees

  • New defect arrives by SMS & email within seconds of submission.
  • Dashboard with full lifecycle: New → In Progress → Parts Ordered → Out of Service → Clear.
  • Flag a bus Out of Service and the driver PWA locks that bus out — full-screen takeover, no override.
Bus Defect Status
#9 Brake fluid leak 🚫 OOS
#14 Mirror cracked 📦 Parts
#23 Stop arm slow 🔧 Progress
Supervisor
📋

What the supervisor sees

  • Auto report generation. Every active bus PDF report auto-emailed to the supervisor at the end of the month. Open email. Print all. Reports done. No more chasing paper. No more configuring report generation.
  • PIN management is supervisor-controlled — drivers never create their own.
  • Every inspection writes to a database your district owns, not a vendor SaaS.
April 2026 Okanogan SD
448Insp.
443Pass
5Fail
98.9%Compl.
📎 14 bus PDFs attached

Getting started is as simple as the app itself.

// What happens next
Step 1
Reach Out

A quick call or email. Tell me your fleet size, your district, and what you’re using now. No pitch, no pressure — just a conversation to see if we’re a fit.

Step 2
Send Your Roster

You provide your bus list, driver names, and contact info for your supervisor and mechanic. That’s it. Everything else is on me.

Step 3
I Build It

I set up your supervisor dashboard, driver PINs, SMS routing, and monthly reports. You get a working system delivered to your inbox — usually 2 business days.

Step 4
It’s Yours

Full ownership transferred with training, documentation, and a direct line to me for ongoing support. No lock-in. No risk.

Production Deployment

Okanogan School District. Every school day since May 2026.

"30 years on a bus, 30 years of paper. With this app I get part of my life back. Thanks Bob!"

— Diane, 30-year school bus driver, Okanogan SD

Okanogan SD went live with One-Touch DVIR running on infrastructure they own. Supervisor Larry Scroggins manages PINs; Fleet Mechanic Fausto Munez works the defect dashboard. The district displaced a $30/seat/month prior tool at rollout — and gained multiple features the other app didn’t have.

Larry takes peer reference calls from other Transportation Supervisors evaluating the system. Email to arrange one →

DistrictOkanogan SD · WA
Live sinceMay 2026
SupervisorLarry Scroggins
MechanicFausto Munez
Replaced$30/seat tool
Data ownerThe district
HardwareNone — bring own phone
Before You Call

What every Transportation Director asks first.

You are going to ask whether this is really FMCSA-compliant, what happens when a driver loses signal, and who owns the data. Here are three of the eight.

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 § 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 queues it. The app re-submits automatically as soon as signal returns — the backend rejects duplicate UUIDs, so no double-logging is possible. A manual Retry button remains as a backup. The one remaining limitation: if the driver closes the app before signal returns, the queued inspection submits on next launch rather than in the background.
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 — 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.
Read all 8 questions →

Ready to talk about your district?

One person. Real answer. Same day. Bob is the founder, the developer, the operator — and an active school bus driver. The fastest path is email; calls returned the same day after his afternoon route.

✦ Accepting new districts
Founder

Bob McElderry

I drive a bus for a small Eastern Washington school district. One day I was talking to my supervisor — he was complaining about paying for a DVIR application that cost too much, was too hard for the drivers to click through, and required him to compile reports at the end of every month. I said, “Certainly there’s got to be a solution out there already.” He said, “Unbelievably, there isn’t.”

So I started researching. I learned most offerings are packaged with commercial systems costing thousands of dollars, and most apps designed for trucking have steep learning curves and extensive setup procedures. None of it was built with rural bus garages in mind. I realized I’d have to build it from the ground up.

I think I’ve come up with a pretty good app that solves our problems — and hopefully yours, too. The bus drivers here really like it. We’ll keep evolving it, adding features, and keeping it priced low, so rural bus garages can access these new technologies without paying punitive commercial prices.

There is no support ticket between you and a real answer. I’m the founder, the developer, the operator, and the person who picks up the phone. Email is the fastest path — calls returned the same day after my afternoon route.