The problem with scattered files
Excavation planning often depends on files stored in too many places. A project manager may have the drawing, the estimator may have the screenshot, the supervisor may have the site photo, and the crew may only see a short work order with none of it attached.
When files are scattered, teams waste time asking the same questions twice. Worse, they can miss a note about a known underground line, a private service run, or a locate requirement that existed but never made it into the folder someone actually opened before digging. This is a documentation-organization problem more than a research problem — see what to check before digging near underground lines for the research side of pre-dig planning.
| Scattered files | Centralized project record | |
|---|---|---|
| Where a drawing lives | Whoever created it — email, phone, or a personal folder | One project record everyone can open |
| Finding a specific note | Asking around or searching multiple inboxes | One search in one place |
| Risk of a missed detail | High — a note can simply never reach the crew | Lower — the record travels with the project |
What documents to collect
Collect anything that helps explain the site and the planned ground disturbance: civil drawings, drainage plans, utility sketches, survey files, owner documents, previous repair notes, photos, markups, and screenshots from approved records.
Not every document will be perfect, and that's fine. The value isn't a flawless archive — it's keeping the planning context together in one place so gaps and uncertainty are visible and can be discussed, instead of quietly sitting in a folder nobody reviewed.
Why project context matters more than the file itself
A drawing by itself is easy to misread months later — is it current, is it the version that was actually approved, does it match the work zone for this specific job? A drawing becomes far more useful when it's connected to the project address, the work zone, the proposed excavation, locate status, and any risk notes from the site visit.
That context is also what turns a folder of files into a crew-ready pre-dig report instead of a document dump. The report is the summary; the centralized files are what make the summary possible to write accurately.
How centralized uploads change the workflow
Centralized uploads reduce back-and-forth: the office attaches plans, the supervisor reviews notes, and the crew sees the current planning package before work starts — all from the same record instead of three different inboxes.
SiteBuildHub's Reports feature is built around exactly this — keeping uploads, notes, and research connected to one project record instead of scattered across texts and email. If the starting point is a rough job-site photo rather than a clean drawing, Photo-to-Site-Plan turns that photo into an editable draft you can attach directly to the same record, and a full drawing can be built any time in SiteBuildHub Draft.
Making information field-usable, not just archived
Field crews need clear information, not a document dump. Uploaded files should support a short summary that explains the work zone, known underground infrastructure, locate status, and open questions — the files back up the summary, they don't replace it.
If a file is important, say why in one line. If a drawing is old or approximate, label it that way directly on the record rather than trusting the crew to infer it. Good planning removes ambiguity before the crew begins work, not after someone asks a question on site.
Better records for the next project at the same address
Uploaded plans and notes also create a better record for future work. When the next project at that property starts — a follow-up job, a warranty visit, a different trade entirely — the team can review what was already known, what was questioned, and what was confirmed during earlier planning instead of starting from zero.
The record still doesn't replace official locates or physical verification on the next job either. It gives whoever picks up the project a stronger starting point than an empty folder.