How to Build a Fleet Asset Directory From Scratch (And Keep It Current)
- 2 days ago
- 5 min read
A fleet asset directory is the foundation everything else in fleet management depends on. Here's how to build one from scratch — and set it up so it stays accurate without constant manual work.
Every fleet management system, every maintenance program, every cost report — all of it depends on one thing being right: the asset directory.
If vehicle records are incomplete, mileage is outdated, or half the fleet is missing from the database entirely, everything built on top of those records is unreliable.
Building a proper fleet asset directory isn't complicated, but it does require a deliberate approach. Here's how to do it in a way that produces something accurate and usable — not a half-finished project that creates more work than it saves.
Start with what you have
Most fleets starting a new fleet management system aren't starting from zero. There's usually some combination of:
The goal of this phase is to gather everything that exists in one place before deciding what's missing. Pull the spreadsheet. Pull the telematics vehicle list. Pull whatever registration documents are accessible. You're building an inventory of your inventory.
01 Step 1: Establish your vehicle list
Before entering any data, you need a definitive list of vehicles you're going to manage. This sounds obvious, but it's a real decision point for fleets that have vehicles in different departments, locations, or stages of commissioning and decommissioning.
Recommendations:
Start with active vehicles only
Don't include vehicles that are decommissioned, awaiting disposal, or being held as spare parts sources. Get active fleet management working first, then add historical data as time allows.
Include everything that needs scheduled maintenance or compliance tracking
That often means non-road equipment (generators, pumps, trailers) alongside on-road vehicles.
Decide your unit numbering system before entering data
If you're currently using vehicle license plates as identifiers, decide whether to continue with that or establish a fleet-internal unit number. Changing this later is painful.
02 Step 2: Enter core identification and specification data
For each vehicle on your list, enter the fields that won't change and that are needed to identify the vehicle unambiguously:
This step can move quickly if you have registration documents in hand. For a fleet of 30–50 vehicles, a focused effort of a few hours should complete this foundation.
03 Step 3: Configure PM schedules immediately — don't wait
This is the step most people defer, and deferring it is the most common implementation mistake.
The reason to configure PM schedules before you have everything else perfect is simple: every day that passes without scheduled maintenance running in the system is a day a service interval could be missed. The PM schedule is the most time-sensitive setup task. Do it first, or at the same time as data entry — not after.
For each vehicle, configure:
In EKOS, once your telematics integration is connected - Samsara, Geotab, or Teletrac Navman - odometer readings start updating automatically, and your PM schedules start running from real mileage data immediately. |
04 Step 4: Upload documents
Attach the documents you have to the appropriate vehicle records. Priority order:
Registration certificate (regulatory risk if not accessible)
Insurance ID card
Any current inspection certificates with expiration dates
Warranty documentation
Specialty permits or licenses
Don't let missing documents stall the project. Upload what you have, note what's missing, and collect gaps over the following weeks as documents come up for renewal.
05 Step 5: Connect your telematics and fuel data
Once the vehicle records are established, connecting live data sources transforms the directory from a static database into a living operational tool.
Telematics integration
EKOS connects directly to Samsara, Geotab, and Teletrac Navman. Once connected, odometer readings and engine hours update automatically, keeping PM schedules accurate without manual entry.
Fuel site and fuel card integration
If your organization uses EKOS to manage fuel sites or fuel cards, transaction data is automatically associated with the vehicle that fueled — populating fuel cost history on each asset record without any additional step.
This is the point where the asset directory stops being a project and starts being infrastructure.
What not to worry about in the first 30 days
The most common reason fleet asset directory projects stall is the pursuit of completeness before launch. Don't let these things delay getting the system operational:
Complete historical maintenance records: Enter PM schedules and start capturing new work orders. Historical records can be backfilled over time.
Perfect cost data going back multiple years: Current and forward is what matters immediately.
Decommissioned vehicles: Get active fleet working first.
Condition scoring or depreciation calculations: These are valuable but not blocking.
"A fleet asset directory that's 80% complete and operational is worth more than a perfect one that's three months away from launch."
— EKOS Fleet Implementation
Get it running, and improve it as you go.
Keeping it current after launch
The long-term value of a fleet asset directory depends on it staying accurate over time. The practical ways to ensure that:
Use work orders for every repair and service, no matter how small: When work orders close in EKOS, they automatically add to the vehicle's maintenance history and cost record.
Complete digital inspections on every inspection cycle: Failed items that generate work orders keep the defect and repair history connected.
Let the telematics integration handle mileage: Don't create a manual mileage entry process — it will fall behind. The telematics connection keeps it current automatically.
Review and update document expiration dates as renewals come in: Registration renewals, insurance updates, and inspection certificates should be updated in the system when they're received.
Frequently asked questions
What is a fleet asset directory?
A fleet asset directory is a centralized database of all vehicles and equipment operated by a fleet, with each asset having a complete record of specifications, documents, maintenance history, cost data, and operational status.
How do I set up fleet management software?
Start with your active vehicle list. Enter identification and specification data, configure PM schedules, upload available documents, then connect your telematics integration for automatic mileage updates. Don't try to backfill all historical data before going live — get the system running and improve it over time.
How long does it take to build a fleet asset directory?
For a fleet of 20–50 vehicles, core setup (vehicle records, PM schedules, document uploads) typically takes two to three focused working days. Connecting telematics and getting automatic mileage updates running adds a few hours. Historical data backfill is ongoing and lower priority.
THE BOTTOM LINE
Build it deliberately. Let it maintain itself.
Lock down the active vehicle list, enter core data, configure PM schedules first, then connect telematics and fuel — and the directory stops being a project and becomes the infrastructure everything else runs on.
ONE PLATFORM, FUEL AND FLEET
Set up your fleet asset directory in EKOS
Vehicle records, PM schedules, document storage, and automatic mileage updates from your telematics, all in one place. Start your 30-day free trial.
