Fleet records that ride with the work order, not in a separate tool.

Vehicles, trailers, and equipment as first-class assets. VIN, unit number, plate, registration, insurance documents, title and lien, ownership notes, GVWR, lifecycle dates, shop and group assignment. The asset record an admin manages from the office is the asset record a driver reads in the cab.

• Document vault attached to the asset for registration, insurance, title, and lien filings.
• Lifecycle states for in-service, in-shop, out-of-service, and disposed.
• Group and shop assignment so multi-yard operations route work to the right bay.

Driver Vehicle Inspection Reports with structured pre-trip and post-trip flows, driver signature, and mechanic sign-off on any reported defect. Defects post against the asset record on the spot. Repair certification closes the loop without a paper binder.

• Configurable templates per asset class so a tractor and a service van do not share the same checklist.
• Photo evidence and audio notes attach to the defect, not to a phone camera roll.
• Mechanic sign-off and repair certification wired to the same work order that fixed the defect.

Annual DOT inspection records under FMCSA 396.17. Inspector, date, certification number, decal, and supporting photos kept on the asset record. Due-date watch surfaces vehicles approaching their annual window before the sticker expires.

• Annual inspection due-date watch with configurable lead-time alerts.
• Inspector identity, certification number, and decal captured against the record.
• Per-asset compliance packet exportable for an audit or a roadside stop.

Per-vehicle mileage capture from device feed, manual entry, or DVIR-prompted reading. Mileage rolls into PM triggers, into per-job cost, and into per-vehicle cost-per-mile. Exportable in the shapes a fuel-tax preparer expects — without claiming to be an IFTA filing tool.

• Multi-source capture: GPS device, manual reading, DVIR prompt, work-order odometer.
• Reconciliation alerts when sources disagree — the office is not chasing a 200-mile delta.
• Exports for the fuel-tax preparer; we do not pretend to file the return for you.

GPS device tracking for vehicles equipped with a Guspora-compatible tracker. Last known position, breadcrumb history, and current driver assignment surfaced against the same asset row the office reads. Provider-agnostic — bring the device you already trust.

• Last known position, current driver, and ignition state on the asset record.
• Breadcrumb history queryable for a route, a shift, or a calendar window.
• Built to extend to additional telematics surfaces; honest about per-vendor maturity.

Define geofences for yards, customer sites, supplier lots, and service zones. Vehicle entry and exit events are stamped on the trip record and are queryable from the asset history. Useful for arrival evidence, dwell time, and after-hours audits without a separate tracker app login.

• Polygon and radius geofences tied to customer sites, supplier lots, and yards.
• Entry and exit events stamped on the trip record with timestamp and driver.
• Dwell-time queries for billable on-site time and after-hours audits.

PM programs by date, mileage, or engine hours. Schedules attach to the asset, not to a calendar reminder. Due, upcoming, and overdue PM surface on the shop board and convert into work orders without a re-key. Skipped intervals are recorded, not silently lost.

• PM programs scoped by asset class so the right interval rules apply by default.
• Triggers by date, by mileage, by engine hours, or by combination.
• Skipped intervals captured with reason — the office can see what slipped and why.

Shop stock and truck stock under one ledger. Bin locations, vendor pricing, reorder points, and warranty-aware part replacement so a covered failure is not re-billed to the customer. Receive against the purchase order, scan the part out to the work order, and the on-hand count stays honest.

• Shop stock and truck stock as one ledger; on-hand counts move with the work.
• Bin locations, vendor catalog references, and reorder points per part.
• Warranty-aware replacement so a covered failure is not silently re-billed.

Purchase orders for parts, outside repair work, and tires. Approval routing with NTE thresholds, vendor catalog reference, partial receipts, and invoice match. The PO that opened the part is the PO the accounting close reads — no second copy in a file cabinet.

• Approval routing with not-to-exceed thresholds and category-aware approvers.
• Partial receipts and back-order handling without forcing a duplicate PO.
• Three-way match (PO, receipt, invoice) feeds the accounting close cleanly.

Driver opens a roadside event from the cab. Location, symptom, and photos go to dispatch and the shop simultaneously. A vendor tow or mobile mechanic gets dispatched against the same record, the work order is opened, and the asset history captures the whole event.

• Driver-initiated roadside event with location, symptom, and photo evidence.
• Vendor tow or mobile mechanic dispatched against the same asset record.
• Whole event — call, vendor invoice, repair, return-to-service — on one history.

Drivers tied to vehicles for a shift, a route, or a long-haul leg. The assignment carries forward to DVIR signatures, GPS attribution on the trip record, and the per-vehicle history. The fleet manager can answer "who had the truck on the 14th" without an email chain.

• Shift-level, route-level, or open-ended assignment patterns.
• Carries to DVIR, GPS attribution, and per-trip history.
• Audit-friendly: every vehicle event has a driver attached when one was assigned.

Per-position tread depth, pressure, install date, and replacement history on every wheel. The dashboard tones rows red when a steer tire is at or below FMCSA 393.75's 4/32" minimum (or 2/32" elsewhere) so a marginal tire is caught before the next pre-trip — not after a roadside inspection.

• Per-axle, per-position records — steer, drive, trailer.
• FMCSA 393.75 minimums highlighted on the rollup.
• Inspection and retire actions wired to the work order that put the tire on or pulled it off.

Open defects on vehicles still under warranty surface in a queue with unfiled / filed / recovered / denied counts plus recovered-dollar tally. A defect filed under warranty captures the actor and the timestamp on the record. Money the shop is owed stops sitting in a spreadsheet nobody opens.

• Per-tenant rollup of unfiled, filed, recovered, and denied claims.
• Recovered-dollar tally on the dashboard so the office can see the program work.
• Filed actions stamp actor and timestamp server-side for audit defense.

DOT roadside inspection events captured against the asset — state, location, agency, inspector, report number, level, result, out-of-service status, and violations. The inspection that the truck stops for in the morning is the inspection the fleet manager pulls up that afternoon, on the same record.

• State, agency, inspector, report number, level, and OOS captured per event.
• Violations stored as structured data, not pasted into a notes field.
• Per-asset history — every roadside on the same row as DVIR and PM.

For inspection-service contractors that work on vehicles their customers own — DOT inspection shops, mobile mechanics, fleet-services SPs — vehicles can be attached to a customer record. The customer portal gets a read-only view of the vehicles, DVIRs, defects, and roadside events on file. The contractor reads the same row the customer sees.

• Vehicles attach to a customer; the customer sees them in the portal.
• Read-only customer view of DVIRs, tires, roadside, and defects.
• Compound tenant + customer scoping is the security gate.

Vehicles can be assigned to a set of geofences for the day or the route. A cron-driven evaluator emits enter / exit alerts on transition. Useful for "this truck never made it to the customer site" and "this truck spent two hours at a non-customer location" without a separate tracker app.

• Polygon and radius geofences attached per vehicle.
• Enter / exit transitions emit acknowledged alerts.
• Alerts sit on the same dashboard the rest of the fleet rolls up to.

Native mobile DVIR built to the published API contract — pulls the catalog, captures pre-trip and post-trip with photo evidence, posts an idempotent submission so a retried packet does not double-write, and signs off mechanic actions on replay without flipping a clean record into a 400. Drivers who lose signal don't lose the inspection.

• Idempotent submit on client_submission_id keyed by partial unique index.
• Catalog pull endpoint so the mobile checklist mirrors the server.
• Mechanic signoff is replay-safe — the second tap returns 200, not 400.