Find any unit in any yard - row and stall, not a dot on a map
A GPS coordinate inside a forty-acre lot is a search area, not a location. Parq.ai resolves position to lot, row, and stall and holds it on the VIN with the unit’s phase, blocking gate, and dwell. Ask where a vehicle is, and the answer is a place and a status, not a walk of the lot with a clipboard.
1,400+locations1.2M+status events620,000+timeline entries
Why vehicles go missing even with tracking in place
Fleets rarely lose vehicles for lack of a tracking system. The system answers a different question than the one being asked. Telematics reports where a vehicle is on earth. Inside a yard that is noise: every unit returns roughly the same coordinate, and the dot cannot show whether the vehicle is staged for release, in a recon bay, or blocked in by two rows.
The second failure is custody. A unit changes hands at intake, the wash bay, the shop, and the dock. Each handoff lets position go stale, and without a signature there is no moment you can point to where responsibility moved. The third failure is human: row assignments live on a whiteboard, in a group text, or in the head of whoever parked it, and then a shift ends.
What Parq holds instead
A single source of truth per VIN, fed by events already happening. The intake scan sets the unit at a specific stall. Every handoff is signed on the record, so custody has a name and a timestamp. A dwell clock runs per phase, so a stalled unit surfaces on its own. Anything blocking flow lands in an exception queue, not in someone's memory.
The map and the asset register both read from that single source of truth: the map shows clustering and site load, and the register filters and exports by client, carrier, location, and status. Neither is a separate database to maintain.
What this looks like in your operation
Rental and mobility fleets. The question is almost always "what can go out today," and the honest answer depends on where the ready units physically are. Position plus readiness state on one record turns that from a phone call into a filter.
Auto logistics and remarketing. You are holding other people's assets across sites and sub-markets. Being able to name the row a consignor's unit is standing in - and produce the custody trail that put it there - is the difference between a routine status call and a claim.
Last-mile and delivery. Volume is high, dwell is short, and the cost of a misplaced van is an unstaffed route the next morning. Stall-level assignment at intake is what makes a pre-dawn dispatch possible without a search.
AV and robotaxi operations. Units cycle between charging, cleaning, sensor calibration, and service with no driver to ask. The record has to be the only source, because there is nobody in the vehicle to call.
When you may not need this
If you run one lot, one shift, and a unit count one person can hold in their head, keep the whiteboard. Parq earns its place when units spread across sites, pass between vendors you do not employ, and are touched by more than one shift. That is when memory stops scaling, and nobody notices until something is lost.
Frequently asked questions
Telematics reports drive data and a coordinate. Parq records the stationary facts a vehicle cannot report: its lot, row, and stall, its phase, its blocking gate, and its dwell. Most operators run both and join the drive data to each VIN.
No. Position comes from the events already touching the unit - the intake scan, the stall assignment, and the custody signature at each handoff. Where you already have GPS or telematics providers, that data joins the single source of truth through the integrations layer.
The move is a custody handoff on the record: origin, carrier, destination, signature, and timestamp. The unit does not disappear in transit and reappear later - the manifest and the receiving scan are two events on one continuous VIN history.
Terms used on this page are defined in the fleet operations glossary, including dwell time, chain of custody, exception queue.
Thirty minutes, screen-shared. We take one of your vehicles through every gate in the live product.