Research that never reaches the crew doesn't protect anyone
The gap between good pre-dig research and a safe dig is usually a communication step, not a research step. The office does the work — pulls records, requests the locate, notes the private-line concern — and then that work sits in an email thread the supervisor never forwards. A crew-ready report is the document that closes that gap: it turns what the office knows into something a field crew can review in five minutes before they touch a shovel.
This builds directly on the research process in what contractors should check before digging near underground lines. That article covers what to find. This one covers how to package it so it actually gets used.
What belongs in the report
A crew-ready report needs six things: the job location and work area, known underground infrastructure, locate status, flagged risk areas, attached drawings or site plans, and a contact for questions. That's it — the goal is a document a supervisor can review in the truck, not a research archive.
Keep it simple enough to scan and detailed enough to explain why certain areas need extra attention. A line that just says "verify before digging near the workshop" is more useful in the field than three paragraphs of context nobody has time to read at 7am.
- Job location and the exact work zone
- Known underground infrastructure from desktop research
- Official locate status: requested, completed, or still pending
- Flagged risk areas — private lines, old structures, unclear records
- Attached site plan, drawing, or photo reference
- A named contact for questions once the crew is on site
Building the report: a repeatable sequence
The same five steps work whether this is the first report you've written or the fiftieth. Running them in order is what keeps the report from turning into a document dump.
- 1
Write the summary first
Two or three sentences: where, what's planned, what the crew needs to know before anything else.
- 2
List what's known vs. uncertain
Separate confirmed information from anything that still needs verification on site.
- 3
Attach the supporting drawing or plan
A site plan or annotated photo, not a folder of unlabeled files.
- 4
Add the locate status
Ticket reference, request date, and whether it's complete — visible, not buried in email.
- 5
Send it before mobilization
Early enough that questions can be resolved before the crew is standing on site.
Flag known and unknown risks separately
A useful report draws a clear line between what's confirmed and what's still a question. Known lines, old drawings, private-service concerns, and conflicting records should all be called out by name — not folded into a general "be careful" note that tells the crew nothing specific.
Unknown does not mean safe. If a private line couldn't be confirmed one way or the other, the report should say so plainly, and the crew should know that area needs verification — potholing, an owner conversation, or a pause — before mechanical excavation happens near it.
Attach drawings with context, not just files
Attach the plans, drawings, screenshots, and photos that support the report, and connect each one to a short explanation of why it matters. "See attached site plan" is weaker than "see attached site plan — flagged area is the northeast corner near the old shed."
A site plan drawn in SiteBuildHub or a photo turned into an editable draft with Photo-to-Site-Plan works well here specifically because it can carry labels and dimensions directly on the drawing, instead of relying on a separate paragraph to explain what the picture shows. If a file is outdated or approximate, label it that way on the drawing itself — a clearly flagged old drawing is safer than a clean-looking one nobody questions.
A real example: a two-line report that mattered
A landscaping crew was set to install a drainage line along a side yard. The report the supervisor received was short: work zone marked on an attached site plan, public locate completed and clean, one flagged line reading "owner mentioned old sprinkler system, no documentation — hand-dig first 10 feet from the hose bib."
That single flagged line was the entire value of the report. The crew hand-dug the flagged section, found a shallow abandoned irrigation line exactly where the owner had guessed, and rerouted the trench slightly to avoid it. Nothing about that outcome required a long document — it required the one detail that mattered being written down and handed to the right person before the machine started.
Where the report should live
Keep the report with the project record — not a one-off attachment that disappears once the job is invoiced. SiteBuildHub's Reports feature is built for exactly this: a report connected to the same project record as the drawings, notes, and locate status, so it's still findable if a similar job comes up at the same address later, or if a question comes up during a warranty call.
This also matters for the next contractor at the same property, even if that's a different trade or a different visit entirely — a well-kept report is a head start for whoever plans the next dig there.
Send it early enough to matter
Send the report early enough for the supervisor and crew to actually review it — not as the truck is pulling onto the site. If a question comes up while reading it, there needs to be time to clarify the work area, request more information, or adjust the plan before anyone starts digging.
A report shared after the crew has already arrived still has some value, but it loses the thing that makes it useful in the first place: the chance to catch a problem while it's still cheap to fix.