One-Touch DVIR was built to the FMCSA eDVIR Final Rule effective March 23, 2026, and to the underlying authority that makes an electronic signature lawful in the first place — 49 CFR § 390.32. This page publishes the full citation chain, our attestation text, and how each rule is implemented in the product.
Most "FMCSA compliant" claims cite only one or two of the rules below — usually just § 396.11. We cite all four together:
Washington State operators: WAC 392-145 and WAC 446-65 apply additionally. Both are consistent with the federal chain above.
What the rule requires: an electronic signature must be uniquely identifiable, under the sole control of the signer, attached to the record, and accompanied by a record of consent.
How One-Touch DVIR implements it: Every driver is issued a 4-digit PIN by their Transportation Supervisor. Submission requires the PIN. Every submission is server-timestamped and logged in a write-only compliance ledger. The first time a driver signs in — and every time the legal attestation text changes — the driver must accept the attestation before they can submit. Acceptance is recorded in a separate consent log with agreement version, timestamp, bus, district, and UUID.
What the rule requires: the DVIR must identify the vehicle, list defects or "no defects," include the driver's name, and be signed.
How One-Touch DVIR implements it: Every inspection log row contains server timestamp, driver name, PIN, bus identifier, district, inspection type, result, defect list, notes, GPS coordinates, attestation duration, and user-agent. The PIN is the signature attached to the row.
What the rule requires: the next driver must review the prior DVIR before operating the vehicle.
How One-Touch DVIR implements it: The driver-facing screen shows open items inline. Any bus marked Out-of-Service triggers a full-screen lockout. The attestation includes review of prior open items.
What the rule does: authorizes electronic DVIRs, cross-referencing § 390.32 for signature lawfulness and § 396.11/396.13 for content and review.
How One-Touch DVIR was prepared: architected to the Final Rule before the effective date. Deployed to our first production garage in May 2026 on infrastructure that already met the rule.
This is the text every driver accepts at first sign-in and re-accepts whenever it changes. Current version: v1.1, updated May 2026.
By entering your PIN, you are giving your affirmative consent to create, sign, and retain all Pre-Trip, Post-Trip, No New Defects Found, and Defect reports in electronic form only. Your PIN is your legal electronic signature. It uniquely identifies you as the driver of record. You agree to keep your PIN confidential; any report submitted with your PIN is your act and is legally binding. Important ESIGN Disclosures (required before you consent): - You have the right to receive a paper copy of any record at any time at no charge. Paper copies are available from your supervisor. - You may withdraw your consent to electronic records at any time by notifying your supervisor in writing. Withdrawal will not affect the validity of any records already created. However, after withdrawal, future inspections must be completed on paper until a new agreement is signed. There is no fee for withdrawal. There are no other conditions or consequences other than the need to use paper forms going forward. - You can update your electronic contact information (email or phone) at any time in the app or by notifying your supervisor. - To use this application you need only a modern web browser on a smartphone, tablet, or computer with reliable internet. You can print or save any record as a PDF at any time. - This consent applies to all Pre-Trip, Post-Trip, No New Defects Found, and Defect reports you submit through this application for the entire time your driver profile is active on this device. By entering your PIN and tapping "I Agree & Sign" you certify that: - You have personally performed a complete physical pretrip or posttrip walk-around inspection of the vehicle as required by WAC 392-145-041. - You have reported (or will report) any defects or deficiencies discovered. - When you select "No New Defects Found," you are making an explicit, legally binding certification that no defects or deficiencies were discovered during this inspection. This electronic signature and record are made pursuant to the federal ESIGN Act (15 U.S.C. § 7001), FMCSA regulations (49 CFR §§ 390.32, 396.11, and 396.13 as updated by the March 2026 final rule), the Washington Uniform Electronic Transactions Act (RCW Chapter 1.80), and applicable pupil-transportation law (WAC 392-145-041 and RCW 46.61.380). All records are retained by the school district or carrier in accordance with applicable records-retention requirements, independent of your profile status. This agreement remains in effect for all sessions on this device until your driver profile is modified, at which point you will be asked to re-confirm.
v1.1 · effective May 2026 · Source: Legal/LEGAL_AGREEMENT_TEXT_Ver_1.1.md
Every driver is required to re-accept any new version before their next submission. When v1.2 lands, every driver sees v1.2 on their next sign-in. The change history lives in the consent log forever.
On the 1st of every month an automated dossier is emailed to the Transportation Supervisor with per-bus inspection history — generated by an Apps Script time trigger, not a person.
Yes. Built to the FMCSA eDVIR Final Rule effective March 23, 2026, operating under 49 CFR §§ 390.32, 396.11, and 396.13.
49 CFR § 390.32. The rule authorizes electronic signatures provided the signature is unique, under sole control, attached to the record, and accompanied by consent. Our PIN-and-attestation flow meets all four conditions.
The Transportation Supervisor can look it up or assign a new one from the Driver_PINs sheet.
Doing so would violate § 390.32(b)'s sole-control requirement. The legal attestation includes acknowledgment that the PIN is theirs alone.
The inspection is held locally with a Retry button. Same UUID on retry prevents duplicates. No automatic background retry — retry is manual.
Yes. The Google Sheet is provisioned in your district's Google Workspace. You can revoke our access at any time.
WAC 392-145 and WAC 446-65 apply additionally. Both are consistent with the federal chain.
Your inspection records are in a Google Sheet that your district owns. Every prior record is preserved, signed, timestamped, and exportable.
Email [email protected] with the citation and the question. You'll get a response from Bob — not a support ticket — usually within a business day.