Ayo Werks is map-first: after you sign in, you work from the full-screen map rather than a permanent sidebar.

• Organization menu — Use the radial org control on the map to switch which company or Public Data view you are working in. Switching orgs reloads tickets and map data for that org.
• Ticket Hub (top-left) — Open the ticket list to search, filter, sync, assign work, manage projects, and open ticket details.
• Data Hub (top-left) — Manage annotations, data layers, photos, documents, and events.
• Map — Tap a ticket bubble or polygon to open its detail panel. On desktop, the status filter bar shows per-status counts and filters what appears on the map.
• Account menu — Open Settings, User Guide, Admin (if allowed), or log out.

Tech users may see a simpler map-focused experience (Ticket Hub and some filters can be hidden) so they can focus on assigned field work.

The map is the main workspace. Ticket markers cluster at wider zooms; at closer zoom levels, ticket boundaries appear when geometry is available.

• Select a ticket — Click a polygon or 811 bubble to highlight it and open the detail panel (same tabs as Ticket Hub detail).
• Status filter bar (desktop) — Click a status count to show or hide tickets of that status on the map. Counts mirror Ticket Hub stats.
• Layer panel — Switch basemaps and toggle overlays such as Tickets, Drone Maps, and Photos.
• Address search — Jump the map to an address or use current location when the browser allows it.
• Org switch — Changing organization closes open ticket panels and reloads that org’s tickets so you do not keep looking at another company’s data.
• Keyboard shortcuts — R resets to your default overview zoom; + / − zoom in or out. Arrow keys pan the map (3× faster with Shift); click the map first so it has focus.

Ticket Hub is the place to manage your org’s tickets in a list, with search, filters, stats, and detail view.

• Tickets tab — Browse, search, and filter tickets. Open a row to see full detail beside (or below on mobile) the list.
• Projects tab — Group tickets by job name and manage shared compliance (see Projects).
• Sync — The refresh control runs an external list sync (recent days, extending when overdue). You can start another sync after the current one finishes; it only blocks while a sync is already running.
• Import — Bring tickets in from an external source when your role allows it.
• Create project — Create a new project when your role allows it.
• Bulk actions — Select rows to update selected tickets from external services, clear the selection, or (when available) renew or delete.
• Assign — Assign tickets to crew members from the list or detail view when you have permission.

Projects live in Ticket Hub (not in the map popup). They group tickets that share a USAN job name, including blank projects you create before tickets arrive.

• New project — Reserves a job name. Later USAN imports with a matching job name join that project automatically.
• Project view — See linked tickets and edit shared compliance fields when you own the org. Shared/partner tickets are view-only for compliance.
• Needs attention — A project is flagged when compliance dates are missing or due, or when any linked ticket is Not Ready, Review Required, or Expiring Soon.
• Jump to ticket — Click a ticket in the project view to open it on the Tickets tab.

The map popup and Ticket Hub detail pane share the same four tabs. A yellow status dot appears on a tab when that area needs follow-up.

• Details — Core fields, assignment, dates, and related ticket info.
• Responses — Operator / utility response rows. Dot when a response is not ready or needs review.
• Photos & Events — Ticket-area photos and related events. Dot when the org's photo/drone compliance requirement for the current revision is not met.
• Notes — Org team notes. Opening the tab loads notes and marks them read. Owner-org members can add notes; shared/partner tickets are read-only. Dot when you have unread notes.

Default which tab opens first can be changed under Settings → Tickets.

Statuses are calculated when tickets load or refresh. The polygon color matches the status badge in the ticket list. Colors below match the map pins.

• Ready The ticket is not expired, all known operator requirements are satisfied, and any required ticket-area photos are complete (or workflow is acknowledged).
• Not Ready 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.
• Expiring Soon The ticket is not expired but its expiration calendar date is within the days your organization sets in Admin → Workflow (default 5). Not Ready takes priority over Expiring Soon.
• Review Required User-side follow-up after operators have done their part—for example, an operator response that needs review, or the 2-photo requirement for the current ticket revision is not met. It is not used when the gap is simply missing response rows vs expected stations.
• Expired The ticket expiration date has passed.
• Cancelled The upstream enquiry was cancelled, and the ticket is not yet expired.

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

Open Data Hub from the top-left button next to Ticket Hub. Use it to browse and manage field data that is not only the ticket list.

• Annotations — Map drawings and notes tied to locations.
• Layers — Data layers you can turn on for the map.
• Photos — Org photos (also see Photos & Map Layers).
• Documents — Files attached for the org or job context.
• Events — Related field events tied to tickets or locations.

Use search and filters in Data Hub to narrow results. Refresh reloads the current Data Hub view.

• Ticket photos — Add or review ticket-area photos from the Photos & Events tab. Your organization sets how many photos (and optionally drone maps) are required before marking Ready.
• Capture — Prefer in-app camera when possible so GPS tagging is preserved. Choosing files from the device gallery may omit location.
• Map photo overlay — With Photos turned on in the layer panel, photos load for the current map view at zoom 16+. Zoom in before expecting photo pins.
• Drone / aerial overlays — Toggle Drone Maps in the layer panel when imagery exists for the area and date range.

Open Settings from the account menu. Changes apply to your signed-in user.

• Profile — Name, phone (used as default contact mobile when creating USAN tickets), email, language (English or Spanish), and your role in the current organization.
• Personalization — Theme and related display preferences.
• Map — Default basemap, units, and default zoom.
• Tickets — Default ticket list filter, which detail tab opens first, and Ticket Hub detail height on mobile.

Your role is set per company (organization). It controls what you can see and do in that org. Your role for the current company is shown under Settings → Profile. Switching companies can change which role applies.

• Operator — Day-to-day ticket work for that company (import, sync, assignees, and notes) when enabled. Cannot create, renew, remark, amend, or submit related USAN ticket actions — those are for company admins and managers when enabled. Can add and edit company data (photos, annotations, events, layers) but cannot delete data. Can change who is assigned to a project.
• Manager — Office/lead role: when create/renew features are enabled for the org, can create tickets, renew, remark, amend, and related USAN submits. Can edit and delete company data. Cannot access the Admin Panel or manage users and org settings.
• Admin — Company admin: manage users and settings, assign tickets and projects, and set other members to Operator, Manager, Admin, or Tech. When create/renew features are enabled for the org, admins can create tickets, renew, remark, amend, and related USAN submits. Can edit and delete company data.
• Tech — Field role: sees only tickets assigned to you that are not expired (partner tickets from other companies are hidden). Simpler map-focused UI. Can refresh tickets, acknowledge workflow steps, add notes, and add company data; can edit only data you created. Cannot create or renew tickets, import tickets, or delete data.

Ask a company admin or your supervisor if you need a different role.

When you select the Public Data organization, the app focuses on discovering shared content in the current map view rather than a full private Ticket Hub workflow.

• Use Search to find shared tickets, photos, layers, and aerial imagery in the view.
• Zoom to level 16+ before searching so results are tied to a useful map extent.
• Ticket Hub and some status filters may be hidden in this mode—use map search and overlays instead.

Ayo can keep recently loaded ticket data available when your connection drops. On desktop, the status indicator in the ticket stats bar shows offline (wifi-off), syncing, or USAN activity. On mobile, an offline indicator appears near the top-left map controls.

• Tickets and polygons already loaded for the current org may remain viewable offline.
• Assigned ticket packs may be prepared so field users can keep working without a live connection.
• Actions that need the server (sync, import, create, renew, most uploads) stay disabled until you are back online.
• When connectivity returns, cached data can sync; if something looks wrong after reconnecting, refresh Ticket Hub or reload the page.

• Stale tickets — Run Ticket Hub sync, or open a ticket and update it from external services. Switching org and back also reloads that org’s list.
• Sync button busy — Wait for the current sync to finish; then you can run sync again.
• Missing photos on the map — Zoom to 16+, turn on the Photos overlay, and confirm photos exist for that area.
• Aerial / drone imagery missing — Zoom in far enough and check that imagery exists for the selected date range.
• Wrong org’s tickets — Confirm the organization menu selection; switching orgs reloads data for that org only.
• UI language — Change language under Settings → Profile. Spanish copy is a first pass and may still be refined.