01
Field team needs orientation
- Investigation
- Organize designated findings and relevant site context.
- Usable record
- Utility map or marked plan.
- Decision supported
- Coordinate planned work against documented findings.
Documentation your engineering team can build on
Utility mapping and engineering-level documentation. Data you can use: pre-construction intelligence, not only paint on the ground.
Formats
Documentation formats clients can use
Our documentation is tailored to match the needs of your project, from KMZ files to pre-construction intelligence reports with congestion mapping and verification recommendations.
Captured with RTK GPS precision and structured for downstream project teams.
- 01KMZ files
- 02Pre-construction intelligence reports
- 03Congestion mapping
- 04Verification recommendations
- 05Utility maps
Confidence classification explained
Findings are confidence-classified so project teams know how much weight each line can bear.
ASCE 38-aligned methodology
Field evidence
Located and observed directly in the field.
Record evidence
Correlated with records and surface indications.
Verification recommended
Flagged where further verification protects the decision.
Record design
Match the deliverable to who will use it
A useful subsurface record is shaped by the next decision. The appropriate format depends on whether the recipient needs field orientation, spatial data, coordination context, or a documented recommendation.
02
Downstream team needs spatial data
- Investigation
- Position findings with RTK GPS precision where scope supports it.
- Usable record
- KMZ or mapped data deliverable.
- Decision supported
- Bring field evidence into project review tools.
03
Congestion or uncertainty affects planning
- Investigation
- Interpret evidence, classify confidence, and identify limitations.
- Usable record
- Pre-construction intelligence report or congestion mapping.
- Decision supported
- Decide where design coordination or verification is needed.
| Project condition | Investigation | Usable record | Decision supported |
|---|---|---|---|
| Field team needs orientation | Organize designated findings and relevant site context. | Utility map or marked plan. | Coordinate planned work against documented findings. |
| Downstream team needs spatial data | Position findings with RTK GPS precision where scope supports it. | KMZ or mapped data deliverable. | Bring field evidence into project review tools. |
| Congestion or uncertainty affects planning | Interpret evidence, classify confidence, and identify limitations. | Pre-construction intelligence report or congestion mapping. | Decide where design coordination or verification is needed. |
- What the record includes
- The findings, their spatial and project context, confidence language, and the deliverable formats defined in scope.
- What the record does not claim
- It does not convert incomplete evidence into guaranteed depth, exact location, or certainty the investigation cannot support.
- Who uses it
- Contractors, engineers, developers, facility teams, municipalities, utilities, excavators, and homeowners according to project need.
- Why it matters
- The record carries field evidence into planning, coordination, verification, and pre-excavation decisions.
Verification
Verification that records reflect field reality
Utility verification and confidence-classified findings help document subsurface infrastructure so records reflect field reality.
Prepared for contractor and engineering firm workflows
- Planning inputs
- Defensible records
- Pre-construction decisions
- Schedule protection
Documentation already prepared and structured for how contractors and engineers actually work. For contractors
Utility mapping documentation FAQ
What formats can the deliverable support?
Deliverables can be tailored for project workflows, including KMZ files and pre-construction intelligence reports with congestion mapping and verification recommendations.
How is confidence classification used?
It states how much weight a finding can bear so teams do not treat uncertainty as exactness.
What does ASCE 38-aligned methodology mean here?
It keeps the documentation method clear without presenting uncertainty as a guarantee.
How do project teams use the record?
They use it as planning input for contractor and engineering firm workflows before decisions move downstream.
Plan a Subsurface Investigation
Talk with SafeLine about the mapping, verification, and documentation your project needs before decisions move downstream.