File Maintenance Records and Inspections by Truck
A truck goes down in another state and the shop asks what was done to it last. The answer is in a repair invoice from a different shop, filed under the month somebody paid it.
The short answer
Maintenance records organize by unit, because every question asked of them is about a truck. The unit number or the VIN is on the repair invoice, the annual inspection and the driver vehicle inspection report, so a workflow can use the Read Details from File step to pull it off and the Move step to file the document under that truck. The Rename step puts the date and the type of work at the front of the name, which turns a folder into a service history that reads in order.
Steps this uses
Before and after
What actually changes
As they arrive
- INV-88213.pdf
- receipt.pdf
- scan.pdf
- annual.pdf
After the workflow
- Units/104/2026-06-02-pm-service-a.pdf
- Units/104/2026-07-19-tires-steer-pair.pdf
- Units/117/2026-07-22-annual-inspection.pdf
- Units/117/2026-08-01-dvir-brake-adjustment.pdf
Four invoices from three shops, filed under the trucks they were done on rather than the day they were paid.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
When a repair invoice, inspection report or DVIR arrives, read the unit number and the date off it, rename it date-first with the type of work, and file it under that truck.
One folder per unit, for the life of the truck
Unit number in the folder name, and the VIN in it somewhere too, because the unit number is yours and the VIN is what a shop or a buyer will use. The folder should outlive the truck, since the service history is worth most on the day you sell it.
Date first, then what was done
A folder named by unit with files named date-first reads as a service history straight from the list view. That is the view somebody wants while a truck is sitting at a shop waiting on an answer.
Take the unit number off the invoice
Shops name their invoices after themselves. The unit number is inside the document, usually alongside the VIN and the odometer, and the Read Details from File step is what gets it out.
Route the ones with no unit on them
A tire invoice covering four trucks, or one carrying only a VIN nobody recognises, has no clean answer. The Ask AI About the File step sends those to review rather than filing them under a guess.
The unit is the only key that lasts
Shops change, drivers change, and the person who paid the invoice leaves. The truck stays, and every question asked later is about the truck: what was done, when, what did it cost, is the annual inspection current. Filing by vendor or by month answers none of those without a search. Filing by unit answers all of them by opening one folder.
The history is worth money at the end
A documented service history is the difference between selling a used truck on its mileage and selling it on its record. That file is built one invoice at a time across years, and it only exists if the invoices were filed under the truck as they arrived. Reconstructing it afterwards from a shared drive full of shop-named PDFs is not realistic, which is why the filing has to happen at the moment each invoice lands.
What it does not do
It files documents under the unit they belong to and names them so the folder reads chronologically. It does not schedule preventive maintenance, track parts inventory, or warn you that a service interval is due, which are all fleet maintenance software jobs. It does not read an odometer into a database. It makes the paperwork findable underneath whatever you use to run the maintenance itself.
Limits
What to know before you build it
It can work through what is already there
This one runs on a schedule over a folder you point it at, so the documents sitting in it now are read and filed alongside the ones that arrive later. A large backlog is an overnight job rather than an instant one, because each document is read rather than pattern-matched.
It needs a connected account
This workflow reads files out of an email inbox, so it cannot run until that account is connected. Connecting one is on the Max plan, or on any team workspace. There is no version of this particular workflow that runs on the free plan, because the files it organizes never arrive in The Drive AI on their own.
FAQ
Common questions
How should fleet maintenance records be organized?
One folder per unit, named with the unit number, and every file named date-first with the type of work. That gives a readable service history per truck and matches the only question anybody asks of these documents, which is what has been done to this truck.
How long do inspection records have to be kept?
Driver vehicle inspection reports are kept three months and the annual inspection report fourteen months. Those are retention minimums rather than filing rules, and keeping them longer costs nothing once they are filed under the unit they belong to.
What if an invoice covers more than one truck?
That is the case worth handling deliberately. A single invoice for tires on four trucks has no one home, so it goes to a review folder rather than being filed under whichever unit happened to be named first. Putting a copy under each unit is the other reasonable answer and is a decision worth making once.
Does this replace fleet maintenance software?
No. Maintenance software schedules the work, tracks intervals and holds the cost data. This organizes the documents that come back from the shops, which in a small fleet usually live in an inbox and a folder called scans. The two sit alongside each other.
A service history that builds itself.
Every invoice under the truck it was done on, named by date and by work.
5 GB free · No credit card required