Skip to main content

How FileFlo works · Demonstration data

See howFileFlo works.

A step-by-step walkthrough in text. For carriers, follow one driver's file from the first upload to the audit packet, shown with demonstration data on a test carrier. For Part 135 operators, request a walkthrough with your quote.

01 · The file

One driver, one file.

A test carrier enters its USDOT number. FileFlo reads its FMCSA record and builds each driver's qualification file in the order 391.51 lists it, every requirement cited and marked on file or missing. The gap report names each missing record, the rule that requires it and who owes it, with new-entrant automatic-failure items first.
Shown with demonstration data on a test carrier.

02 · Records in

Sent from the driver's phone.

The driver uploads a CDL and a medical card through their own phone link. FileFlo reads both, dates each to its expiry and files each to the rule it satisfies: the CDL under Part 383 with its class checked, the medical card under 391.43 with the 24-month ceiling. A multi-record PDF is split and a re-sent file is de-duplicated.
Shown with demonstration data on a test carrier.

03 · Held, with the fix

A medical card, held for review.

Two review items on a test carrier's Today list: a DOT medical card held because it names a different person (49 CFR 391.45), and a CDL held because no class is printed (49 CFR Part 383). Each is marked Needs a fix. Demonstration on a test carrier. Not a customer.
The medical card carries another person's name. FileFlo holds it and opens one review item that names the rule it failed and the fix: the driver's own card, uploaded through the same link. The requirement stays open until a record passes. A second record shows the same care: a CDL with no class printed is held under the Part 383 class rule, with its own review item.
Shown with demonstration data on a test carrier.

04 · The packet

The file as an inspector sees it.

The inspector view of a sealed packet from a test carrier: the sealed date, the fingerprint, who it was prepared for, the key to how each record is known and how it stands, and a count of records held under separate controlled access. Demonstration on a test carrier. Not a customer.
  • The audit packet: every requirement with its citation, each person's missing records named, and each document's standing beside where it came from.
  • A sealed inspector link: a frozen snapshot with its fingerprint, an expiry, an access cap, revocation and a log of every access.
  • The inspector view, without the carrier's gap notes and risk math, with drug and alcohol records shown as a count.
  • A public page where anyone holding the packet can check its fingerprint and confirm it is the one the carrier issued.
Shown with demonstration data on a test carrier.

Where your team comes in.

  • Nothing goes out to drivers until the carrier switches each routine on and chooses who hears, how and when.
  • The carrier's providers order the MVR, run the Clearinghouse query and administer the drug and alcohol program; FileFlo files each result.
  • Records can also be emailed to the carrier's own inbox address for the office to review before filing.

The same build, from your USDOT number.

The Audit-Ready Setup, $499 once: your gap report, your driver files and your packet with its inspector link, and 30 days of Core. Your 14 calendar days start once we have your USDOT number, the name of at least one driver and one usable record, and they never pause. If your files are not organized and audit-retrievable by the end of them, the $499 comes back.

Ask for the Setup, $499 Check my DOT record

The button opens a short request form, and a person at FileFlo answers in writing with the terms.

What the Setup buys, what it needs and what happens after you pay