Excavator Pre-Locate Meet Ticket Coordination Form

This form documents the pre-locate meeting for an excavation job. It captures the meet ticket number, site details, who was present, what marking method was agreed, and the acknowledgment from the excavator and facility owner. Use it to reduce misunderstandings before the locator starts marking.

Complete it at the on-site meet before any locate work begins, or immediately after the parties agree on the marking plan. It should be finished before the locator leaves the site so the instructions and scope are still fresh. If conditions change later, create a new record or add a revised note rather than relying on memory.

The submitter is usually the person coordinating the meet, such as the excavator representative, project lead, or locator coordinator. The excavator and facility owner should review the agreed instructions and provide acknowledgment, while the locator confirms the marking plan. Keep the roles clear so the audit trail shows who agreed to what.

Include the marking method, the exact scope to be marked, any access limits, and special site conditions that affect how the locate is performed. If only part of the site needs marking, use conditional logic or progressive disclosure so the form captures only the relevant area. Avoid vague language like "mark utilities as needed" because it creates disputes later.

It creates a clear audit trail of the pre-locate agreement, which is useful when work scopes are disputed or when you need to show that instructions were communicated. The form also supports minimum-necessary data collection by focusing on job and site details rather than unrelated PII. If your workflow stores names or signatures, make sure the submission notice explains what happens after submission and who can access the record.

Common mistakes include leaving the marking scope too broad, skipping attendee names or roles, and failing to note special site conditions that affect visibility or access. Another frequent issue is collecting too many free-text notes instead of using structured fields for dates, times, and marking methods. A missing acknowledgment timestamp can also make the record harder to rely on later.

Yes. You can add conditional fields for road crossings, private property access, night work, or multi-lot sites without turning the form into a long catch-all. Keep required fields limited to what is needed for the meet ticket record, and use optional notes for site-specific details. That keeps the form usable while still preserving the information you need.

Yes. This form can feed a ticketing system, work order log, or locate workflow so the acknowledgment and marking instructions are stored with the job record. It also works well with photo uploads, timestamping, and role-based routing for review. If you connect it to other systems, keep the field names stable so the audit trail remains easy to search.

Email and text threads are easy to lose, hard to standardize, and often omit the exact marking agreement. This template gives you a single record with the same fields every time, which makes review and follow-up much easier. It also reduces back-and-forth by prompting the team to confirm the details before the locate starts.