811 Locate Ticket Intake and Triage Workflow
A locate ticket intake and triage workflow for 811 requests that screens coverage, scores risk, and assigns the ticket to an available field locator before the response deadline.
Trusted by frontline teams 15 years of frontline software
Built for: Utilities · Telecommunications · Municipal Operations · Construction Support
Overview
This template handles the front end of an 811 locate process: it receives a new ticket, checks whether the requested dig site falls inside your service area, applies a routing risk score, and assigns the work to an available field locator. It is built for teams that need a repeatable way to move tickets from intake to dispatch without losing track of the legal response clock.
Use it when your operation receives a steady stream of locate requests and needs to decide, quickly and consistently, whether a ticket is yours, how urgent it is, and who should own it next. It is especially useful when multiple utilities share territory, locator availability changes throughout the day, or some tickets require supervisor review before assignment.
Do not use this template as a substitute for field verification, final compliance logging, or a full damage prevention program. It is also not the right fit if your team handles only a handful of tickets per week and can triage them manually without delay. The workflow is meant to reduce missed handoffs, out-of-area assignments, and deadline pressure by turning intake into a clear execution plan with defined steps, exception handling, and assignment logic.
Standards & compliance context
- Use the workflow to support, not replace, your local 811 response obligations and utility-specific locate procedures.
- Keep the assignment record tied to the original ticket ID so you can show when the request was received, screened, and dispatched.
- If your operation handles regulated assets such as gas or electric lines, route high-risk cases to the appropriate qualified reviewer before field work begins.
- Retain exception and override logs according to your internal records policy and any applicable damage-prevention retention requirements.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
How to use this template
- Connect the 811 intake source, service-area boundary data, locator roster, and deadline fields so the workflow can evaluate each ticket as it arrives.
- Map the incoming ticket fields into the input schema, including ticket number, location, requested date, asset type, and any priority flags you use for routing.
- Run the coverage check first, then score the ticket for risk, and send out-of-area or ambiguous tickets to an exception queue instead of assigning them automatically.
- Assign in-scope tickets to the best available locator based on territory, workload, and skill match, and post the assignment to your dispatch or task system.
- Review the triage log daily for missed coverage, stale availability, and tickets nearing the response deadline, then adjust the scoring rules or roster data as needed.
Best practices
- Keep your service-area boundaries current, because stale GIS data is the fastest way to assign the wrong ticket.
- Use a simple risk model that changes routing behavior, such as escalating high-impact assets or repeat-damage corridors to a senior locator.
- Separate coverage exceptions from assignment exceptions so out-of-area tickets do not get buried in the normal queue.
- Refresh locator availability before each intake cycle if your team works shifts, on-call rotations, or split territories.
- Log the reason for every manual override so you can spot recurring boundary, staffing, or data-quality problems.
- Set confirm gates on any step that would reassign, close, or reject a ticket to avoid accidental destructive actions.
- Include a fallback path for incomplete addresses or ambiguous dig locations so the workflow can continue with human review instead of stalling.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this 811 locate ticket intake and triage workflow cover?
It covers the first pass after an 811 ticket arrives: intake, service-area validation, risk scoring, and assignment to a field locator. The workflow is designed to decide whether the ticket can be handled, how urgent it is, and who should receive it next. It does not replace the actual locate work in the field or the final compliance record.
Who should run this workflow?
This workflow is usually run by dispatch, utility operations, damage prevention, or a locate coordinator. In smaller teams, one coordinator can own both triage and assignment. In larger organizations, the intake step may be automated while a supervisor handles exceptions and out-of-area tickets.
How often should this template run?
It should run every time a new 811 ticket is received, since the legal response clock starts with the ticket. Many teams also use it in a scheduled review loop to catch unassigned or escalated tickets before the deadline. If your volume is high, the workflow can be event-driven with a backup queue review.
What inputs do I need to customize it?
You typically need the ticket number, service address or dig location, utility service area boundaries, risk rules, locator availability, and any SLA or deadline fields from the 811 center. Some teams also add asset type, excavation type, and prior damage history to improve scoring. The template is meant to be adapted to your local operating rules.
How does the risk score help in triage?
The risk score helps prioritize tickets that are more likely to need faster review, senior locator attention, or tighter follow-up. For example, high-impact assets, dense urban corridors, or repeat-damage areas may be routed ahead of routine requests. The score should support assignment decisions, not replace human judgment when the case is unclear.
What are the common mistakes when using this template?
A common mistake is assigning tickets before confirming the service area, which creates rework and missed deadlines. Another is using a vague or overly broad risk score that does not change routing behavior. Teams also run into trouble when locator availability is not kept current, because the workflow can only dispatch accurately if the roster is reliable.
Can this workflow integrate with dispatch, GIS, or ticketing systems?
Yes, it is a good fit for integrations with ticket intake systems, GIS boundary checks, workforce scheduling, and dispatch tools. The workflow can pass the ticket ID, location, risk level, and assigned locator to downstream systems. It can also post exceptions to a queue or notify a supervisor when a ticket falls outside coverage.
How is this different from handling 811 tickets manually?
Manual handling depends on people checking inboxes, maps, and rosters one by one, which increases the chance of missed deadlines and inconsistent routing. This template standardizes the decision path so every ticket is screened the same way. It also creates a repeatable record of why a ticket was assigned, escalated, or rejected.
Related templates
Go deeper on the topic
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
-
A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...
-
See how connected 1:1 tracking, employee audit history, and LMS completion records turn scattered processes into verifiable workforce documentation.
-
See how bank branch managers use MangoApps scheduling to fill shifts, communicate policy updates, and eliminate last-minute coverage chaos.
-
See how customers use MangoApps Projects Module to collaborate, track progress, and share knowledge across teams.
-
MangoApps in Okta Integration Network automates user provisioning, SSO, and access management for stronger security and less admin work.
Ready to use this template?
Get started with MangoApps and use 811 Locate Ticket Intake and Triage Workflow with your team — pricing built for small business.
