Locator Daily Production and Tickets Worked Log
Track each locator shift with a daily production and tickets worked log that captures tickets cleared, average time per ticket, miles driven, and carryovers for the next shift. Use it to document workload, handoffs, and end-of-day output in one place.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Utilities · Damage Prevention · Field Operations
Overview
The Locator Daily Production and Tickets Worked Log is an end-of-day task template for utility locating crews who need a clean record of what was completed during a shift. It focuses on the core production details that matter in the field: tickets worked, tickets cleared, average time per ticket, miles driven, and any tickets that must be carried over to the next shift.
Use this template when you need a repeatable daily record for route performance, handoff continuity, or supervisor review. It is especially useful for crews that cover large service areas, work mixed priority tickets, or need to explain why some work remained open at the end of the day. The log supports a simple, verifiable summary of output without turning the shift report into a narrative essay.
Do not use this template as a substitute for a full incident report, damage report, or safety inspection form. If the shift involved a strike, near miss, or compliance event, that should be documented in the appropriate follow-up record. This template is also not the right place for vague status notes; each entry should be specific enough to answer yes/no questions about what was worked, what was cleared, and what was left for the next shift.
Standards & compliance context
- This template supports OSHA-style operational recordkeeping by creating a consistent shift log for field work and handoff review.
- If your team handles regulated utility locating work, use the log alongside local damage-prevention procedures and any required verification step for completed marks.
- Do not use this log to replace incident, injury, or utility damage reporting where separate legal or regulatory documentation is required.
- If your organization has SLA-based response targets, the log can help show whether tickets were handled within the expected window without overstating completion.
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
- Create one log for each locator shift and prefill the date, crew member, route area, and DRI before the shift starts.
- Record each ticket worked during the shift with a clear status so you can distinguish tickets cleared from tickets carried over.
- Enter the average time per ticket and miles driven at the end of the shift using the same calculation method every day.
- Add any carryover tickets with a short blocking note so the next shift knows what prevented completion.
- Review the log with a supervisor or lead locator, then file any follow-up action for unresolved tickets, route issues, or recurring delays.
Best practices
- Keep each checklist item atomic so one line covers one ticket outcome, one route metric, or one carryover reason.
- Use the same definition of 'cleared' across the team so the log stays comparable from shift to shift.
- Record carryovers immediately at the end of the shift instead of reconstructing them from memory later.
- Separate blocking issues from non-blocking notes so supervisors can see what stopped completion versus what merely slowed it down.
- Use a consistent method for average time per ticket, such as total work time divided by tickets worked, and do not change it midstream.
- Capture miles driven from the same source each day, whether that is the vehicle odometer, route app, or dispatch record.
- Escalate repeated carryover patterns to the supervisor so route planning can be adjusted instead of repeatedly absorbing the same delay.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template is for utility locators to record end-of-shift production in a consistent way. It captures the tickets worked, tickets cleared, average time per ticket, miles driven, and any tickets carried over. That makes it easier to review workload, spot bottlenecks, and hand off unfinished work cleanly.
Is this meant to be filled out every day or only when there is a problem?
It is designed as a daily log, not an exception report. Filling it out every shift gives you a reliable record of normal production as well as delays, reroutes, and carryovers. If you only use it when something goes wrong, you lose the baseline needed for planning and performance review.
Who should complete the log?
The locator who worked the shift should usually complete it as the DRI, since they know which tickets were cleared and which remained open. A supervisor can review it at the end of the day or during shift handoff. If your team uses a lead locator, that person can also consolidate logs for the crew.
What should count as a ticket carried over to the next shift?
A carryover should be any ticket that was received but not fully cleared before the shift ended. Use the log to note why it was not completed, such as access issues, weather, traffic, or a blocking field condition. That helps the next locator prioritize the work without repeating the same investigation.
How does this help with prioritization?
The log gives you a simple way to compare workload across shifts and identify where tickets are stacking up. You can use it alongside ASAP versus SLA-based prioritization to separate urgent work from routine volume. It also helps supervisors see whether delays are caused by ticket volume, travel distance, or time spent on complex sites.
Can this template be customized for different utility teams?
Yes. You can add fields for route zone, ticket type, locator name, supervisor review, or notes on special conditions. Some teams also add a verification step for completed marks, photo documentation, or call-backs so the log matches local operating procedures.
What are common mistakes when using a production log like this?
The most common mistake is mixing multiple outcomes into one note, which makes the log hard to audit later. Another pitfall is recording only cleared tickets and ignoring carryovers, which hides unfinished work. Teams also sometimes estimate average time per ticket loosely instead of using a consistent method, which makes comparisons unreliable.
How does this compare with an ad-hoc end-of-day note?
An ad-hoc note is easy to forget, hard to compare, and usually missing one or two key fields. This template standardizes the same checklist items every day so the record is easier to review, trend, and hand off. It also reduces back-and-forth when a supervisor needs to confirm what was completed on a given shift.
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...
-
Discover why an employee text alert system is essential for frontline safety, faster emergency response, and two-way communication across your entire workforce.
-
Only 13% of employees use their intranet daily. Learn 9 proven moves to drive frontline adoption above 90% with mobile-first design and governance.
-
Why frontline training fails without rehearsal, and how AI roleplay, live voice practice, and coaching close the gap between learning and doing.
-
Overcome enterprise-wide AI deployment challenges with scalable GenAI strategies that cut costs, boost adoption, and deliver measurable ROI.
Ready to use this template?
Get started with MangoApps and use Locator Daily Production and Tickets Worked Log with your team — pricing built for small business.
