Why can’t I see a subcontractor’s dispatch records when searching by subcontractor, but their records appear when I search by route tag?

This usually happens when the subcontractor is starting routes but not starting individual sites in the mobile app.

In Yeti, dispatch records and service history are only created when a site is actively started. If a subcontractor begins a route but does not select and start each site, those services will not appear when filtering by subcontractor in Dispatch Records: Search.

When this occurs, you may notice:

• Dispatch records appear when searching by Route Tag, but not by Subcontractor
• Missing or rejected services
• Little to no photo uploads
• Minimal or missing location breadcrumbs in route history

How to confirm this

1. Go to Route History Reports for the subcontractor.
2. Open routes with missing dispatch records.
3. Check whether sites were selected during the route.
   • If sites were not started, service records will not exist for those visits.

Common cause

Some subcontractors assume that starting a route automatically starts all sites, which is not the case. Each site must be manually selected and started in the mobile app.

Additional troubleshooting steps

• Confirm the subcontractor is using the latest version of the mobile app.
• Ask the subcontractor to verify they are:
  • Starting each site individually
  • Completing the service
  • Taking required photos before closing the site