Which vehicle visited a site? Evaluating FleetTracker Geosearch

FleetTracker can help you answer which vehicle visited a site by working from the location history it records, rather than from driver memory or paper logs. For vehicle tracking site visit history, the useful test is whether you can start from a place and a time window and get back a clear list of vehicles. This page sets out what to check in 2026 before you rely on FleetTracker Geosearch for that job.

Which vehicle visited a site? The short answer

Use a location-first search. Pick the site, set the date and time window, and list every vehicle that was recorded there. Then open the journey for each match and check arrival time, departure time and route.

That is the question Geosearch is aimed at. Because the exact screens, filters and outputs can change, confirm them in a live walkthrough. You can see how the portal behaves on your own vehicles by requesting a demo using the link at the end of this page.

The verdict for a fleet manager: FleetTracker is a good fit for site-visit questions when you need a vehicle-by-vehicle record of where vehicles went. It is not a fit if you need camera footage of what happened on site. FleetTracker does not provide camera footage, video telematics or digital vehicle checks.

Why this matters in 2026

Site-visit questions come up in ordinary operations, usually under time pressure:

• A customer says a van was on their premises at a given time, or was never there.
• A site manager reports damage and wants to know which vehicles entered the yard.
• A contractor invoice claims attendance that you need to check against your own records.
• A depot or landlord asks which vehicles used a shared access road.
• A manager needs to confirm a scheduled visit actually took place.

Without vehicle data, each of these becomes a conversation based on recollection. With it, you can answer in minutes and keep the answer on file.

What FleetTracker records that supports a site-visit answer

Geosearch is only as good as the underlying records. These FleetTracker functions are the foundation, based on the current product description:

• Live GPS tracking shows where vehicles are now.
• Journey history keeps a record of past trips.
• Route playback lets you replay the path a vehicle took.
• Geofencing and supported alerts mark a site boundary and flag entry or exit.
• Mileage data and vehicle utilisation show how vehicles are used over time.
• Automatic Driver Recognition (ADR) links a journey to a driver where it is set up.
• Fleet-management portal, dashboards and scheduled reports keep the output in one place.

If you want the background on the history side, read how journey history supports fleet operations. For the replay side, see how route playback supports fleet management.

How to evaluate Geosearch in a demo

Do not judge it on a clean sample site. Run these checks on your own data.

1. Choose a site you can verify

Pick a location where you already know which vehicles attended on a specific day, such as a customer yard or your own depot. You need a known answer to test against.

2. Test the time window

Search a narrow window first, then widen it. Check that the results change the way you expect. A site visit that straddles midnight is a good edge case.

3. Test the edge of the site

Vehicles pass near sites without entering them. Look at a vehicle that drove along an adjacent road and see how it is treated. Ask how the site area is defined and how precise it can be. Do not assume a boundary size; check what the current tool offers.

4. Open the journey behind each result

A match is a starting point. Open the journey, check arrival and departure, and replay the route. Confirm the result agrees with what you know.

5. Check what you can save or share

See whether the result can be kept in a report or exported in a form you can attach to a customer reply. Ask exactly what the output contains before you plan a process around it.

6. Check who can see it

Confirm which portal users can run location searches, and what they can see. Decide in advance who in your business should have that access.

Geosearch versus the other ways to find a site visit

The practical difference is the starting point. Journey history and route playback work when you already know the vehicle. A location search is for when you know the site and not the vehicle.

Geofences are the better tool for sites you visit often. If a customer site matters every week, set it up properly rather than searching each time. How to set useful fleet geofence alerts covers how to keep alerts useful without flooding your inbox.

Why the answer varies from one fleet to another

The same search can produce very different results across businesses. These are the factors that matter:

• How long ago the visit was. Check how far back your records go before you promise an answer to a customer.
• How precisely the site is defined. A tight yard and a large industrial estate behave differently.
• Whether the vehicle was tracked at the time. A vehicle without a working unit leaves no record.
• Whether drivers are recognised. ADR can link a journey to a driver where it is in use; without it, you know the vehicle but not necessarily the person.
• Shared or pooled vehicles. A pool vehicle that several people use needs a driver record to turn a visit into an answer.

What location data can and cannot prove

Location data shows that a tracked vehicle was at a place during a period. It does not show who did what there, what was delivered or whether the work was done properly.

Treat a result as evidence to investigate, not as a verdict. If a vehicle was recorded at a site, speak to the driver and review the job record before drawing conclusions. If the question is about conduct on site or a collision, video evidence is a different need. Crystal Ball’s SmartCam 4G provides recorded footage accessed on demand through the customer portal, which is a separate product from FleetTracker.

There is also a data-protection side. Where vehicles are driven by employees, location data can relate to identifiable people. Follow the ICO’s guidance on monitoring workers, tell staff what is recorded and why, and use searches for a defined business purpose. If private use is allowed in your fleet, read tracking company vans outside working hours before you search outside normal shifts.

Is vehicle tracking site visit history the same as a timesheet?

No. Site presence is one input to a timesheet check, not a replacement for it. A vehicle can be at a site while the worker is elsewhere, and the reverse is also true. Use it alongside job records.

Can scheduled reports replace a location search?

For routine questions, yes. If you review the same sites every week, a scheduled report is faster than searching each time. FleetTracker automated reports explained sets out what can be scheduled. For a one-off question about a single site, a location search is the quicker route.

Do you need anything else to make it work?

Geosearch depends on FleetTracker being fitted and reporting on the vehicles you want to search. It does not cover vehicles without a unit. FleetTracker is quote-led, so ask Crystal Ball about your fleet rather than assuming a setup.

If your real need is also footage, theft protection or a regulated safety requirement, those are separate products with separate equipment. Name the need first, then choose the product that answers it.

FAQ

One last thing

Run your test on a day when you already know the answer, and write down what the tool returned before you check it. If it matches, you have a process you can trust in 2026. If it does not, you have found the gap before a customer dispute does.

Related guides

• Journey history in fleet operations
• Route playback for fleet management
• Setting useful geofence alerts
• FleetTracker automated reports