Fleet Map Shows Fewer Markers? Check Clusters Before Counting Vehicles

Ask what each symbol represents

A busy depot can contain several tracked assets close together. At a broad map view, a platform may combine nearby asset symbols into a cluster so the map remains readable. Counting visible shapes can therefore answer a different question from counting the assets represented by the view. Start with the legend and the meaning of any number inside a symbol.

Geotab documents clusters that group nearby vehicles and can reveal individual icons when zoomed in. It also describes map markers whose detail changes with available screen space. Those are Geotab examples. Ask the provider to explain the actual representation used in your own fleet view before applying the same interpretation.

Keep the scope fixed while changing the view

Record which fleet or vehicle group is selected, the visible map area, any status filters and the time of the observation. Then change one viewing control at a time. If the demonstration supports it, zoom into the depot and observe whether one grouped symbol separates into several identifiable assets. Keep a note of what changed rather than relying on memory.

Check the list or search result for the same permitted scope. A list may cover more assets than the map area currently on screen, and a status filter may exclude some assets from both. Geotab documents map filters and an asset layer that can be hidden. Your platform may use different controls or counting rules, so ask which selection applies to each displayed total.

Use an approved demonstration or your existing read-only view. Keep a wider access change, vehicle reassignment or device intervention out of this screen review. If an asset falls outside your permitted scope, ask the authorised owner to investigate rather than expanding permissions to make a count agree.

Trace a known asset through the display

Choose one asset already expected in the selected scope. Use its agreed private reference in the platform search and compare the result with the list and map. Ask the demonstrator to show how it is identified inside a group, how overlapping symbols are handled and what happens when you move between a broad and a close view.

A visible marker does not by itself establish that its position is recent. Once the asset is identified, read its position timestamp and the available communication evidence separately. Use the existing timestamp checklist if the question is whether the vehicle location is current. Use the address-label checklist if the map pin and place name appear inconsistent.

If the asset remains absent from the expected list as well as the map, record that observation and its selected scope. The map review alone cannot establish whether the cause is a filter, an access boundary, an asset record or a reporting problem. Pass the evidence to the appropriate owner before deciding that a tracker has failed.

Test a depot example before rollout

Ask for a controlled example containing several approved demonstration assets near one location and another farther away. Agree the asset list first, then review the broad view, the closer view and the matching list. Confirm whether the result is a grouped symbol, overlapping individual symbols or another documented representation.

Example scenario. A reviewer sees one symbol at a depot while an approved list contains several assets there. Zooming into the same area reveals separate asset symbols in the demonstration. This fictional example illustrates a display question. It establishes no SafarTrak capability, test result, accuracy or refresh guarantee.

Record an unexplained difference as unresolved. A successful example covers the demonstrated assets, scope and observation time. Ask whether desktop and mobile views apply the same selections and how a saved view is restored. Repeat a comparison only when its scope or conditions change, and retain the original evidence.

Write down the rule your team will use

Use the blank map-count review sheet to record the view, selected scope, legend interpretation, expected asset count, list result and map observation. Include the observation time with its time zone, the private evidence reference, the responsible role and the next question. Keep real identifiers, routes and location screenshots in your approved private system.

Agree who explains an unresolved display difference and which evidence that person needs. A support handover should state the selected scope and the observed behavior, rather than simply reporting that vehicles disappeared. Keep a count explanation separate from any conclusion about communication health or vehicle activity.

Bring your depot layout and map-reading workflow to a SafarTrak platform discussion. Ask the team to demonstrate the supported views and explain the relevant limits for your actual setup. A useful acceptance note tells dispatch what a symbol and a total mean in the view they use.