1. Purpose and users
The Tracking workspace helps users monitor tracker signal health and active trip movement. It is used by tracking officers, operations controllers, fleet managers, branch managers, and supervisors responsible for transport visibility.
Tracking does not create trips or assets. It reads fleet, branch, tracker, and trip context so users can see whether vehicles are visible, moving, stale, or unmatched.
2. Branch and filter setup
The page starts by loading active branches and then applies the branch the user selected or is allowed to view. Users can filter by signal status, operational state, movement state, and search text.
Search helps find a truck, registration number, tracker identity, trip reference, or relevant movement context. Filters narrow the board so tracking officers can focus on exceptions instead of scanning every vehicle.
3. Tracker signal review
The workspace shows the latest known tracker state for assets that can be matched to the tracking feed. Users review signal age, location summary, movement state, and whether the tracker appears fresh or stale.
A stale signal does not automatically mean the truck is stopped. It means the system has not received a recent enough tracker update. The tracking user should compare the tracker state with operations context before escalating.
4. Active trip context
Tracking connects signal data to active trip context where possible. This lets users compare live vehicle movement with operational expectations such as dispatched, loaded, in transit, border, delivered, or other trip stages.
When a truck has an active trip, the tracking board can help users see whether the movement appears consistent with the trip. If it is not, Operations may need to update the trip, contact the driver, or investigate a delay.
5. Unmatched tracker feed rows
The system can list tracker feed rows that do not match a known asset. These rows are important because they may reveal incorrect tracker registration numbers, alias gaps, spelling differences, or new vehicles not yet configured correctly.
Fleet or administration users should correct the asset tracker identity when a real unit is unmatched. Keeping tracker identifiers clean makes future monitoring and reports more reliable.
6. Background refresh sync
Authorized tracking users can trigger a background refresh sync. The system checks whether a sync is due, then returns metrics such as assets considered, matched, created, updated, and missing.
If a refresh is skipped, the response explains that the sync was not needed yet. This protects the tracking integration from repeated immediate calls while still giving users a way to refresh when appropriate.
7. Daily use from start to finish
A normal tracking workflow starts by selecting the branch, scanning stale or missing signals, searching for high-priority trucks, comparing tracker movement with active trips, refreshing the sync when needed, and escalating real exceptions to Operations or Fleet.
The day ends with clean tracking evidence: which vehicles were visible, which were stale, which had unmatched feeds, and which active trips needed operational follow-up.