Locate Ticket Re-Mark Request Log
Track re-mark requests when paint or flags are no longer visible, then record what was re-requested and when markings were restored. Use it to keep locate work traceable and reduce missed follow-up.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Utilities · Construction · Municipal Public Works · Telecommunications
Overview
The Locate Ticket Re-Mark Request Log is a workplace form for recording when existing utility locate markings are no longer visible and a re-mark must be requested. It captures the original ticket number, when the request was made, how it was submitted, which utilities were re-requested, where the re-mark is needed, and when the markings were restored.
Use this template when a site has faded paint, missing flags, weather-related loss of visibility, or a contractor needs a documented follow-up on an active locate ticket. It is especially useful for dispatch, damage prevention, and field coordination because it creates a simple audit trail from request to restoration. The form also helps teams avoid duplicate calls, missed follow-up, and confusion about whether the site was actually re-marked.
Do not use this log as a general incident report or a full excavation permit record. It is not meant to replace the original locate ticket, a safety checklist, or a broader project tracker. Keep it focused on the re-mark event itself, and use the notes field only for details that help the next person complete the work. If your process involves multiple crews or repeated visits, this template gives you a consistent way to track each request without relying on email threads or memory.
Standards & compliance context
- This log supports an audit trail by documenting the request, follow-up, and restoration timeline for locate re-marks.
- Keep the form aligned with data minimization by collecting only the fields needed to route and close the re-mark request.
- If the template is exposed to contractors or the public, make required and optional fields clear and ensure the form is accessible under WCAG 2.1 AA.
- Use clear status values and completion notes so the record can support internal accountability and dispute review.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Ticket Identification
This section ties the re-mark request to the original locate record so the follow-up can be traced without ambiguity.
-
Locate Ticket Number
Enter the original locate ticket number associated with the re-mark request.
-
Date Re-Mark Was Requested
Select the date the re-mark request was submitted.
-
Time Re-Mark Was Requested
Optional time the re-mark request was submitted.
-
Request Method
How the re-mark request was received.
Re-Mark Details
This section explains why the re-mark was needed and exactly which utilities and locations require attention.
-
Reason for Re-Mark Request
Select why the re-mark was needed.
-
Utilities Re-Requested
Select all utilities that needed to be re-marked.
-
Re-Mark Location Description
Describe the area where the markings were no longer visible. Include cross streets, address range, or site reference as needed.
-
Additional Notes
Add any other details relevant to the re-mark request or follow-up.
Restoration and Follow-Up
This section closes the loop by recording when the markings were restored and whether any action remains open.
-
Date Markings Were Restored
Select the date the re-mark was completed.
-
Time Markings Were Restored
Optional time the re-mark was completed.
-
Restoration Status
Current status of the re-mark request.
-
Completion Notes
Document any completion details, delays, or exceptions.
How to use this template
- Enter the original ticket number, request date, request time, and request method as soon as the re-mark is needed.
- Record the reason for the re-mark, the utilities re-requested, and the exact remark location so the field crew can find the site without guessing.
- Add any access issues, partial visibility problems, or site-specific context in additional notes, keeping the entry limited to information needed for the follow-up.
- Update the restoration date, restoration time, and restoration status when the markings are confirmed as restored.
- Write completion notes that explain what was done, who confirmed it, and whether any further action is still open.
Best practices
- Use the original ticket number exactly as issued so the re-mark request can be matched to the correct locate record.
- Choose a request method field that reflects the real channel used, such as phone, email, portal, or dispatch, instead of free text.
- Describe the remark location with enough precision for a crew to act on it, such as street segment, corner, or site reference.
- Keep utilities re-requested as a multi-select list so you can capture every affected utility without creating duplicate entries.
- Mark restoration status immediately after confirmation, not later from memory, to preserve an accurate audit trail.
- Limit additional notes to operational facts and avoid unnecessary PII or unrelated project commentary.
- If the site needs another visit, create a new request entry rather than overwriting the original restoration record.
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 logs requests to re-mark utility locate tickets when existing paint or flags are no longer visible. It captures the ticket number, request details, the utilities re-requested, and the date and time markings were restored. Use it to create a clear audit trail from the re-request through completion.
Who should fill out the Locate Ticket Re-Mark Request Log?
It is usually completed by locate coordinators, field supervisors, utility damage prevention staff, or dispatch personnel who manage re-mark follow-up. The person entering the record should know the original ticket number and be able to confirm when the restoration was completed. If multiple teams touch the process, assign one owner for the final status field.
How often should this log be updated?
Update it each time a re-mark is requested and again when the markings are restored. If your crew revisits the same site multiple times, create a new entry or clearly separate each request so the timeline stays accurate. Do not wait until the end of the week if the log is used for active field coordination.
What fields are most important to keep accurate?
The ticket number, request date and time, utilities re-requested, remark location, and restoration status are the core fields. Those fields make it possible to trace the request, route the work, and confirm completion. Additional notes are useful for access issues, partial restorations, or site-specific context.
Does this template support compliance or audit needs?
Yes, it supports a basic audit trail by showing when a re-mark was requested and when markings were restored. That record can help with internal accountability, utility coordination, and dispute resolution. If your process involves regulated work, keep the log aligned with your organization’s retention and documentation rules.
What are common mistakes when using this log?
Common mistakes include leaving out the original ticket number, using vague utility names, and recording restoration without a date and time. Another issue is describing the location too broadly, which makes it hard for crews to find the exact area. The log works best when each entry is specific enough for a field team to act on without guessing.
Can this template be customized for different crews or regions?
Yes, you can add fields for crew name, dispatcher, jurisdiction, or GPS reference if those details matter to your workflow. You can also adjust the utilities list to match the providers in your service area. Keep the form focused on the minimum necessary fields so it stays quick to complete.
How does this compare with handling re-marks in email or chat?
Email and chat can work for one-off requests, but they are harder to search, audit, and close out consistently. This template gives you a structured record with the same fields every time, which reduces missed follow-up and unclear ownership. It is better when you need a repeatable process rather than an informal message thread.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
-
Mobile capabilities help local government field teams stay connected, access SOPs offline, and boost productivity anywhere.
-
See how MangoApps Community Suite improves customer experience through visual communication, onboarding, collaboration, and knowledge management in one...
-
MangoApps is named a Leader in the IDC MarketScape for Content Management in Authenticated Digital Workspaces. See what sets our intranet platform apart.
Ready to use this template?
Get started with MangoApps and use Locate Ticket Re-Mark Request Log with your team — pricing built for small business.
