Pickups, dumps, trailers, yellow iron — a construction fleet is mixed by nature, and most software only understands the half with license plates. FleetStream tracks all of it, and puts the cost where the work happened.
The pickups live on the highway.
The iron lives on the job.
The costs live in six spreadsheets.
That last part is fixable.
An excavator doesn’t have an odometer worth reading, so FleetStream’s PM intervals run on miles, days, or engine hours — per service, from one reusable catalog. Work orders run open-assign-perform-close, in your shop or at a vendor’s. A down excavator idles a crew; the PM that prevents it costs an afternoon.
Which skid steer is on which job, what it has cost this quarter, and whether the identical one is sitting idle — one profile per unit holds status, holder, history, and cost, with assignment history kept automatically. Utilization analysis flags what’s idle before someone approves buying another one.
Equipment cost reaches project P&Ls as a real number, not a plug. Maintenance, fuel, and operating spend distribute by cost center, type, or individual asset — attributed to whoever held the asset when the cost hit — so the next bid inherits data instead of last year’s guesses.
FleetStream doesn’t care whether an asset has a license plate.
Mixed fleets are the design case. Vehicles and equipment live side by side, and PM intervals support engine hours for assets without meaningful mileage.
Yes. External repairs are first-class: vendor-supplied parts and flat shop labor are documented on the work order without pretending your technicians did the work.
FleetStream has native connectors for Samsara, Motive, Geotab, Verizon Connect, and FleetComplete, and works as the management layer above whatever devices you run.
FleetStream is built for fleets of 50–1,000 assets; the sweet spot is 100–500. At 60 and growing you are squarely in range.
Bring a fleet list — trucks, trailers, iron, all of it. We’ll walk it through FleetStream instead of showing you a canned demo fleet.