Choose your organization from the map menu, open Ticket Hub for the ticket list, or use map bubbles to inspect active tickets.

Use Ticket Hub to sync external tickets, search and filter results, assign work, and review ticket details. The sync button can be pressed again after a run completes; it only blocks while another sync is already in progress.

Ticket statuses are calculated when tickets load or refresh. The polygon color matches the status badge in the ticket list.

• Ready is green. The ticket is not expired, all known operator requirements are satisfied, and any required ticket-area photos are complete or overridden.
• Not Ready is red. An operator response is still not ready, fewer responses were received than expected for the known station list, or the ticket is still waiting on operators in that sense. Operator overrides to Ready are treated as Ready.
• Expiring Soon is red. The ticket is not expired but its expiration calendar date is within the next 5 days. Not Ready takes priority over Expiring Soon.
• Review Required is yellow. User-side follow-up after operators have done their part per the app’s rules—for example, an operator response status that needs review, or the 2-photo requirement for the current ticket revision is not met. It is not used for still waiting on more operator responses when the gap is missing response rows vs expected stations.
• Expired is gray. The ticket expiration date has passed.
• Cancelled is gray. The upstream enquiry was cancelled.

When multiple rules apply, the app uses this order of precedence: Cancelled, Expired, Not Ready, Expiring Soon, Review Required, then Ready.

Important: Ayo is designed to help crews understand 811 responses more clearly, but it does not decide whether a crew is ready to dig. The field crew is ultimately responsible for reviewing the ticket, site conditions, utility responses, and applicable procedures before digging.

Click a ticket polygon or 811 bubble to select it, highlight it on the map, and open its detail panel. At closer zoom levels, ticket boundaries appear when available.

In the Public Data organization, use Search to find shared tickets, photos, layers, and aerial imagery in the current map view. Zoom in to level 16+ before searching.

If data looks stale, refresh the Ticket Hub or reload tickets for the current organization. If aerial imagery is not visible, confirm the map is zoomed in far enough and that imagery exists for the selected date range.

Ayo Werks is a shared workspace for excavation tickets and map-based field work: one place to organize locates, photos, layers, and 811 responses between the office and the crew.

Ayo is shaped by real field workflows and ongoing input from crews, locators, and partners who use it every day. Thank you to everyone who shares feedback and helps improve the tool for the wider community.

Interactive maps are powered by Leaflet, an open-source JavaScript library for mobile-friendly maps. Basemap and imagery credits also appear in the map attribution control.

Last updated: May 31, 2026