Before You Dig: Utility Locate Photo Log

The locate ticket is not the whole safety plan.

It is the start of the field record.

Small contractors get this wrong because 811 feels like a single task: call, wait, see paint, dig. That is too thin for real field work. A fence crew drilling post holes, a plumber exposing a sewer lateral, a landscaper trenching irrigation, a concrete crew cutting for a drain, a tree service grinding near utilities, or an electrician running underground conduit needs more than a ticket number in somebody's text messages.

The job file should prove five things:

1. the planned dig area was specific enough for a locator to understand;
2. the ticket matched the real address, scope, depth, date, and work area;
3. the crew checked responses and marks before breaking ground;
4. the crew preserved, photographed, and questioned marks when conditions changed;
5. the work order told the crew when to stop instead of improvising around buried utilities.

That is what a utility locate photo log does. It connects the work request intake, site assessment checklist, work order, job hazard analysis, daily report log, and service report into one defensible record.

If your current process is "the office called it in," your field paperwork is missing the part that matters most: what the crew actually saw before the auger, trencher, shovel, saw, or mini-excavator touched the ground.

Start with the rule, then build the record

For construction excavation, OSHA's 29 CFR 1926.651 requires the estimated location of utility installations that may reasonably be encountered to be determined before an excavation is opened. It also requires contacting utility companies or owners within established or customary local response times, and when excavation approaches the estimated location, determining the exact location by safe and acceptable means.

That is not just a "call 811" reminder.

It is a planning sequence:

PHMSA's excavation damage prevention rule language for 49 CFR Part 196 makes the same point for regulated pipelines: before and during excavation, excavators must use an available one-call system, wait for the operator to mark pipeline facilities when pipelines are in the area, take practicable steps to prevent damage, and use one-call again as needed. If pipeline damage occurs, the excavator must report it promptly to the operator, and if a release occurs, call 911.

The paperwork lesson is simple: build the job file so it can show what you knew, when you knew it, what you checked, and why the crew either proceeded or stopped.

A vague ticket creates a vague locate

The national 811 before-you-dig service explains the basic information needed before contacting 811: address, county, nearest cross street, project type, and exact area on the property where digging is planned. Federal one-call program rules at 49 CFR 198.37 also point to the core data a state one-call program must require from excavators: who is notifying, who the excavator is, the specific location, starting date, and description of the intended excavation.

That is the minimum.

A useful contractor ticket is more specific.

Use the site assessment checklist to gather that before the ticket is submitted. Then put the ticket number and scope summary on the work order so the crew can confirm the ticket matches the job they are about to perform.

If the ticket says "front yard" and the work order says "rear alley," the crew should not dig. That is not a paperwork nit. That is a mismatch between the locate request and the work being performed.

This is the same discipline as two-truck dispatching: the schedule should not release a crew to a job until the work order has the real constraints. For digging work, "locate status unknown" is a dispatch constraint, not a note for later.

White-line the work area before you ask someone else to mark it

The Common Ground Alliance's Best Practices guide includes delineating the area of proposed excavation as an excavator practice. The point is practical: a locator cannot reliably mark the right area if the ticket describes the wrong area or a huge vague area.

For small jobs, white-lining can be simple:

• white paint along the fence run;
• white flags at post-hole centers;
• white stakes at the corners of a trench;
• a marked route from panel to charger, pump, sign base, gate motor, drain, or landscape bed;
• an electronic map or polygon when the state 811 center supports it;
• photos attached to the internal job file showing the marked area before the locator arrives.

The APWA Uniform Color Code is the common field language for temporary marks. White identifies proposed excavation. Pink is temporary survey marking. Red, yellow, orange, blue, green, and purple identify different utility types. Follow the state 811 center and local rules for exact marking requirements, because the color chart does not replace state law, utility instructions, or the ticket response.

For the photo log, white-lining is the first set of photos:

Do this before the ticket is submitted when possible. If the office submits the ticket first and the crew white-lines later, make the work order show which version of the work area controls. A locator's marks are only as good as the work description they were asked to respond to.

Photograph the locate response before the first cut

CGA's Best Practices include documentation of marks. The practical idea is that dated pictures, video, or sketches with distances to fixed objects help show where marks were placed before excavation started.

That is not just for claims.

It helps the crew dig the right job.

At minimum, the photo log should capture:

Use the daily report log or service report to summarize what the photos show:

Ticket 26-048912 reviewed at 7:18 a.m. Work area white-lined along east fence return and rear alley line. Gas marked yellow from meter to alley, approximately 4 feet west of proposed post line. Telecom marked orange near rear gate. Water and electric posted no conflict. Photos 1-14 saved before digging. Crew hand-digging within tolerance zone per company policy and state 811 requirements.

That paragraph is more useful than "locates done."

It tells the owner, dispatcher, crew lead, customer, insurer, and future estimator what actually happened.

Positive response is a status, not a guess

Many small jobs go wrong between "ticket submitted" and "all clear."

The crew sees a few paint marks and assumes everybody responded. The office sees one email and assumes the whole ticket is complete. A customer says the previous contractor already called. A GC says the site is cleared. A landscaper sees old paint from last month and thinks it still applies.

Do not let the crew excavate on assumptions.

CGA's Best Practices include positive response as part of the locate process. State systems differ, but the business rule for a small contractor should be consistent:

The work order needs a locate status block.

If your state 811 system provides online positive response, screenshot or PDF the status and attach it to the job file. If the response is phone-based, write the response details in the work order. If a required response is missing and the job cannot start legally or safely under your state process, move the crew or change the day's work.

That may feel expensive at 7:00 a.m.

A utility strike is more expensive.

The Common Ground Alliance's 2024 DIRT Report keeps showing the same handoff failures: no notification, failure to maintain clearance after marks are verified, no response, inaccurate or incomplete marks, and faded or lost marks. A photo log does not fix every one of those problems, but it forces the crew to slow down at the points where small shops usually rely on memory.

No conflict does not mean no risk

"No conflict" means the responding facility owner or operator is telling you they have no facilities in the requested work area for that ticket, based on their information.

It does not mean:

• there are no private lines;
• old abandoned lines are mapped correctly;
• the ticket described the right area;
• every utility owner has responded;
• marks from another ticket apply to your job;
• the crew may dig outside the described area;
• the excavator can ignore visible field clues.

Private utilities are a major small-job trap. State 811 centers describe the same handoff in practical terms: member utilities usually mark facilities they own or operate up to their responsibility point, while customer-owned lines beyond the meter, cleanout, building, or service connection may be outside the public locate. The customer may still have private underground power to a detached garage, low-voltage lighting, irrigation, septic, propane, pool lines, drain tile, security wiring, or owner-installed conduit.

State examples make the point concrete. Virginia 811 lists house-to-meter water lines and house-to-cleanout sewer lines as private examples. Kentucky 811 gives the same practical rule: if the utility is installed from the meter to another location on the property, you may need a private locator.

Put private-utility questions in the work request intake and site assessment checklist:

• Are there detached buildings, gates, signs, wells, pumps, pools, or landscape lighting?
• Are there irrigation valves, sprinkler heads, control boxes, or buried drip lines?
• Has the property had additions, previous trenching, old tanks, septic work, or abandoned utilities?
• Does the owner have plans, as-builts, surveys, inspection reports, or old invoices?
• Is a private utility locator required before the quote is final or before the work order releases?

Then carry the answer into the quote estimate and statement of work. If private locating is excluded, say so clearly. If it is included, identify who orders it, who pays, what area it covers, and how the crew receives the report.

This is where locate paperwork overlaps with hidden conditions and scope gaps. A buried private drain, abandoned line, unmarked irrigation main, or old electrical feed may be a field condition that changes price, schedule, safety, and responsibility. The answer should be a documented stop-and-price workflow, not a crew argument in the yard.

The crew needs a morning-of-dig checklist

Do not leave the locate review in the office.

The crew lead should complete a short morning-of-dig check on the work order or job hazard analysis:

1. Confirm the address, unit, lot, alley, easement, or work area.
2. Confirm the ticket number and legal start window.
3. Confirm all required responses are complete under the state process.
4. Walk the white-lined dig area.
5. Compare utility marks to the proposed work.
6. Look for unmarked utility clues.
7. Photograph marks before equipment setup disturbs them.
8. Identify tolerance zones and the required hand-dig, vacuum, pothole, or exposure method.
9. Confirm equipment path, spoil pile location, trench protection, traffic exposure, and overhead hazards.
10. Name the stop-work points before starting.

NIOSH's Trenching and Excavation Safety guidance, updated in 2026, puts 811 contact and utility marking inside the larger planning picture: competent person, soil evaluation, safe spoil and equipment placement, protective systems, and utility identification. That matters because many locate problems happen alongside other excavation hazards. The crew may be watching paint while ignoring spoil placement, traffic, ladder access, trench depth, or water intrusion.

Use the safety inspection checklist when the dig is simple. Use the job hazard analysis when the work has a serious hazard: trench depth, unstable soil, traffic, overhead lines, energized equipment, gas line proximity, confined access, or a customer site rule.

The work order can carry the short field instruction:

Do not auger until ticket 26-048912 is verified complete and mark photos are attached. Use the required safe digging method inside marked tolerance zones. Stop if orange telecom mark cannot be followed past rear gate, if yellow gas mark conflicts with post location, if unmarked private irrigation is discovered, or if customer asks to move fence line outside white-lined area.

That is a safety briefing the crew can actually use. It also connects directly to the work order safety briefing workflow.

What belongs in the photo log

Build the photo log around the questions someone will ask later.

If a utility is hit, a line is exposed, a customer disputes delay, an inspector asks what happened, or a crew has to return after rain washed out paint, the file should answer:

• Which ticket controlled this work?
• What exact dig area was requested?
• What did the site look like before excavation?
• Which operators responded?
• Where were the marks compared with the planned work?
• Were any marks missing, unclear, faded, or disturbed?
• Did the crew preserve or request re-marks?
• Did the crew expose utilities safely near conflict points?
• What changed after the work started?

Use this structure:

For a one-day fence or irrigation job, this may be one page plus photos.

For a multi-day sewer, drainage, utility, concrete, or site-work job, it may live in the construction daily report log with a separate photo folder. The format matters less than the habit: one ticket, one work area, one photo sequence, one decision trail.

When the marks do not match the work

The most important field note is sometimes "stop."

Stop when:

• marks are missing for a utility that should obviously be present;
• a mark ends before the work area ends;
• colors overlap and the path is unclear;
• paint is faded, washed out, paved over, covered, or moved;
• the crew is asked to dig outside the ticketed work area;
• the customer changes the fence line, drain route, post location, trench, or equipment pad;
• site conditions point to private utilities not covered by the ticket;
• an exposed line is not where expected;
• a line is damaged, nicked, scraped, pulled, or unsupported;
• the crew cannot maintain required clearance or safe digging method;
• the ticket is expired or the work has moved to a new area.

Then document the stop:

If the field fact changes the scope, use a signed change order before the crew turns a safety issue into free redesign. If the plan no longer matches the ground, use the same field discipline from When the Plans Don't Match the Field: pause, document, decide, approve, then continue.

Trade examples

Fence installation

A fence work order should not just say "install posts."

It should carry the locate ticket number, post line, depth, gate-post exceptions, property-line note, white-line photos, utility response status, and customer approval for layout. If the customer moves the fence three feet closer to the alley after the locate, that is not a harmless tweak. It may be a new dig area.

Field note:

Customer requested moving east return from original white line to inside flower bed. Crew stopped before digging. New area not covered by ticket photos. Office to update 811 ticket and send revised work order. No post holes opened.

Plumbing sewer repair

A plumbing work order for sewer excavation should include the drain path, cleanout, proposed trench, depth estimate, equipment access, spoil location, traffic exposure, utility marks, and whether hand-digging or vacuum exposure is required near conflicts.

Field note:

Orange telecom mark crosses proposed trench at 14 feet from cleanout. Crew exposed by hand before machine excavation. Depth and location photographed. Trench route adjusted 10 inches north with customer approval and supervisor note.

Landscaping and irrigation

A landscaping work order should treat irrigation, lighting, drains, and private electrical feeds as real utilities even when 811 does not mark them. Owner memory is not enough. Photograph valve boxes, controller locations, visible heads, sleeves, low-voltage transformers, downspout drains, and old trench lines.

Field note:

811 responses complete. Owner disclosed private low-voltage lighting after crew walk. Crew marked fixtures and transformer, hand-dug bed edge, and excluded repair of unmarked private lighting from base quote.

Concrete sawcut or flatwork

A concrete work order can trigger digging risk even when the crew thinks it is "just flatwork." Sawcuts, dowel drilling, drain installation, footing excavation, bollards, sign posts, and slab removal can expose or damage utilities. Use the site assessment checklist to flag drains, electrical conduit, gas lines, irrigation sleeves, and abandoned lines before pricing.

Field note:

Sawcut for trench drain moved 18 inches west to avoid blue water mark and owner-requested planter drain. Revised layout photographed. Change order signed before cut.

Tree and stump work

A tree service work order should identify stump grinding depth, root flare work, crane or equipment path, overhead lines, underground service feeds, irrigation, lighting, and utility coordination. A stump grinder can damage more than roots.

Field note:

Stump within marked orange telecom route. Crew stopped grinding at 3 inches below grade in marked zone and requested customer approval for private locate before deeper removal.

Keep the packet with the job, not just the phone

Photos stuck on one employee's phone are not a company record.

Build the packet so somebody else can find it:

• ticket number in the file name or job note;
• photos grouped by job and date;
• wide shots before close-ups;
• captions or notes for unclear marks;
• screenshot of ticket status or positive response;
• work order with crew verification initials;
• daily report or service report explaining delays, stops, re-marks, and changes;
• change order or customer approval when the work area, route, price, or schedule changes;
• incident or near-miss record when something is contacted, exposed unexpectedly, or almost hit.

Tie the packet to billing too. If the crew lost half a day waiting for a re-mark, the daily report log and time-tracking record should explain why. If the customer's requested route moved into a utility conflict, the change order should show the added locate, delay, hand-dig, private locate, redesign, or return-trip cost.

The closeout should be just as clear:

Utility locate ticket, mark photos, exposed-line photos, revised trench route, and customer approval attached. Work completed inside revised approved area. No utility damage observed. Backfill and surface condition photographed. Customer sign-off received.

That is the kind of paperwork that protects the crew, the customer, and the business.

The ticket says you asked before digging.

The photo log proves what the crew did with the answer.

Sources

• OSHA, 29 CFR 1926.651, Specific Excavation Requirements, especially the underground-installation rules before and during excavation
• PHMSA, 49 CFR Part 196 excavation damage prevention rule language, for regulated pipeline one-call, damage-prevention, and release-reporting duties
• Electronic Code of Federal Regulations, 49 CFR 198.37, for minimum state one-call program information requirements
• 811 Before You Dig, for national before-you-dig ticket intake basics and state 811 routing
• Common Ground Alliance, Best Practices online guide, especially white-lining, positive-response review, documentation of marks, locate verification, and marking guidance
• American Public Works Association, Uniform Color Code, for temporary subsurface facility marking colors and proposed-excavation marking guidance
• Common Ground Alliance, 2024 DIRT Report, for excavation-damage cause patterns and damage-prevention context
• NIOSH, Trenching and Excavation Safety, updated January 30, 2026, for excavation planning, competent-person, utility-marking, spoil, route, and protective-system guidance
• Virginia 811, Private Utilities Explained, as one state 811 example explaining why private/customer-owned underground lines may not be marked by member utilities
• Kentucky 811, Private Utilities & Locators, as another state 811 example explaining customer-owned lines beyond the meter and private locating

---

This article is for general information and is not legal, safety, engineering, insurance, or compliance advice. Verify federal, state, local, utility-owner, and site-specific excavation rules with the appropriate authority or professional before acting.