FREQUENTLY ASKED QUESTIONS

$20 per driver per month. Not per bus, not per seat — per driver. Five-driver minimum, which puts your floor at $100/month. Unlimited buses, supervisors, and mechanics are included at that rate. No hardware to buy, no setup fees, no multi-year contract.

If you prepay 12 months up front, you get 10% off — effectively one month free.

Full pricing detail, including how we compare to Zonar / Samsara / Whip Around in real district numbers, is on the Pricing page.

Yes. One-Touch DVIR was built to the FMCSA eDVIR Final Rule effective March 23, 2026, and operates under 49 CFR § 390.32 (electronic signatures), § 396.11 (DVIR content), and § 396.13 (driver review) — all four citations together, not just one.

The 4-digit PIN that drivers enter is the legal signature, authorized by § 390.32. Every inspection is server-timestamped, logged in a write-only ledger, and accompanied by a versioned attestation in a separate consent log. If your auditor wants the rule-by-rule implementation walkthrough, that's on the Compliance page.

For Washington State operators, WAC 392-145 and WAC 446-65 apply additionally — both are consistent with the federal chain.

None. Drivers use the phone in their pocket. Supervisors and mechanics use the laptop or phone they already use for everything else. The product is a Progressive Web App (PWA) — it installs to a phone's home screen from a web link, no app store involvement.

There is no telematics box to bolt under the dashboard, no dedicated tablet to issue, no cradle, no cable, no charger spec. Districts running Zonar or Samsara typically have a $300–$800 per-bus hardware bundle in their first-year quote. Our equivalent line item is $0.

Almost none. You don't need an IT department to roll this out. Specifically:

• Drivers tap a link, choose "Add to Home Screen," and they're done. No app store. No MDM profile.
• Supervisors get a Google Sheet provisioned under their district account. They open it in a browser. That's the dashboard.
• Mechanics get the same sheet. Status changes happen in dropdowns. No login system to administer.
• PINs are managed by the Transportation Supervisor in a sheet tab. No identity provider to integrate with.

The whole onboarding for a typical district fits in roughly 30 minutes of supervisor time. We do the provisioning end of it — your IT contact does not need to be on the call.

Districts with a stricter IT policy occasionally want a written security write-up before they sign. We have one, and we'll send it. The short version: data lives in your district's own Google Sheet under your district's own Google account; we don't host a separate database; there is no third-party identity store.

Okanogan School District, Washington — live in production since May 2026. Transportation Supervisor Larry Scroggins, Fleet Mechanic Fausto Munez. Larry was previously paying $30 per seat per month with another vendor; he displaced that tool with One-Touch DVIR at $20 per driver per month and removed the hardware line item entirely.

One prior in-house instance at the founder's own crew, archived in May 2026 after validating the architecture under daily real-world use.

The Okanogan deployment is the actively developed instance and the customer reference. Larry has agreed to take phone calls from peer transportation supervisors evaluating the system. Email bob@ramventuresolutions.com if you'd like an introduction.

A second case study will be published when the second commercial district lands. We don't pretend to a customer list we don't have.

The signature follows the PIN, not the phone. A driver can use any phone — their replacement phone, a sub driver's phone, a loaner from the garage — and sign in with their PIN. There is no device registration step, no "this phone is paired with this account" trap.

If a driver's phone is lost or stolen, the practical steps are:

1. The driver tells the Transportation Supervisor.
2. The Supervisor resets the driver's PIN in the Driver_PINs sheet (it's a two-column sheet — change a number, save).
3. The driver enters the new PIN on the next phone they pick up.

The old PIN is now inert; any submission attempted with the old PIN will be by the driver who now owns it, which is the driver themselves — there is no one else to compromise. PINs are not stored on the phone.

Lost or stolen phones do not expose inspection data, because the inspection data lives in your district's Google Sheet, not on the phone. The phone is a thin client.

The driver gets a Retry button. The inspection is held locally on their phone, marked as unsubmitted, and the driver re-submits when signal returns. The same UUID is reused on retry — so re-submitting the same inspection cannot create a duplicate row in your compliance log. This idempotency is built into the backend.

One honest disclosure: there is currently no automatic background retry. The driver has to tap Retry. This is documented in our internal backlog as a known gap for rural low-signal environments. In practice at Okanogan it has not been a daily problem, but if your routes go through dead zones we want you to know about it before you sign, not after.

If the bus is in an Out-of-Service state, the driver sees the OOS lockout screen regardless of network condition — that screen renders from local state and does not require a fresh server roundtrip.

The switch usually takes about a week. Here's the sequence we've used:

1. Day 1. You email Bob with your bus count and target start date. We send a one-page agreement.
2. Day 2–3. Agreement signed. We provision your Google Sheet, your Apps Script instance, and your Netlify-hosted app. Per-garage configuration (alert email, supervisor SMS, mechanic SMS) is set in Script Properties — never hardcoded.
3. Day 4. 30-minute call with your Transportation Supervisor to set up PINs for your drivers.
4. Day 5–7. Drivers install the app to their home screens during their pre-trip routine. We monitor the first few days of submissions and confirm everything looks right end-to-end.

You can run the old vendor in parallel during the transition if your contract allows — we're not jealous about it. Most districts find that after one full week of dual-running, drivers stop opening the old tool. Once you're confident, you cancel the old vendor on its own schedule.

Data migration: if you need to retain inspection history from your prior tool, export it from that tool (most vendors give CSV exports) and we'll attach it to your new Google Sheet as a "Historical_Imports" tab so your full record stays in one place. There is no charge for this.