Loading...
operations

Subsurface Utility Engineering Quality Level A Test Hole Report

Record ASCE 38-22 Quality Level A test hole data in one place, including pothole dimensions, exposed utility details, survey coordinates, and field certification. Use it to document utility locations with enough detail for design, excavation planning, and audit trail review.

Trusted by frontline teams 15 years of frontline software AI customization in seconds

Built for: Civil Engineering · Utilities · Construction · Transportation

Overview

This template captures the field record for a Subsurface Utility Engineering Quality Level A test hole, with the details needed to show exactly what was exposed, where it was found, and how it was verified. It includes submission metadata, site and utility identification, pothole method and dimensions, exposed utility characteristics, optional additional utility records, survey coordinates, and attachments such as photos and sketches.

Use it when a utility has been physically exposed and measured, and you need a traceable report for design, coordination, or construction planning. The template is especially useful when the project depends on accurate horizontal and vertical location data, when multiple utilities may be present, or when the field record must support an audit trail. It helps teams keep field notes, survey data, and certification in one structured form.

Do not use it for a simple utility mark request, a desktop utility summary, or a general site inspection that does not involve an exposed utility. It is also not the right fit if you cannot provide coordinate information, if the utility was not verified by test hole, or if the report would require collecting more PII than necessary. Keep the form focused on the minimum necessary data, use conditional logic for multiple utilities, and require only the fields that are needed for your workflow.

Standards & compliance context

  • Use data minimization by collecting only the project, utility, and survey details needed to verify the exposed utility location.
  • If field notes or attachments may include names, phone numbers, or other PII, include a clear disclosure about how that information will be used and stored.
  • Maintain an audit trail for who prepared and certified the report so the record supports internal review and downstream design decisions.
  • If the report is shared across teams, keep coordinate conventions and survey method labels consistent to support usability and reduce transcription errors.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice

This section ties the report to the project and date so the test hole can be tracked and retrieved later.

  • Report purpose
  • Project name (required)
  • Test hole ID (required)
  • Report date (required)

Test Hole Location

This section identifies exactly where the pothole was opened and which utility was being verified.

  • Site address or nearest intersection (required)
  • Test hole location description (required)

    Describe the pothole location relative to fixed features, stationing, offsets, or landmarks.

  • Utility type (required)
  • Utility owner/operator

    Enter the utility owner or operator if known. Avoid personal names unless needed for the project record.

Test Hole Method and Dimensions

This section records how the hole was made and the physical size of the excavation for later review.

  • Excavation method (required)
  • Pothole depth (required)

    Enter the measured depth of the test hole.

  • Depth units (required)
  • Pothole diameter or width

    Enter the approximate diameter for a round pothole or width for an irregular opening.

  • Diameter/width units
  • Backfill status (required)

Exposed Utility Details

This section captures the verified utility attributes that make the report useful for design and conflict resolution.

  • Utility material (required)
  • Utility size / diameter

    Record the observed size or diameter. Use a numeric value with units if available.

  • Utility condition (required)
  • Utility depth at exposure (required)

    Measured depth from the surface to the exposed utility.

  • Utility depth units (required)
  • Were multiple utilities exposed in this test hole? (required)

Additional Utility Records

This section keeps extra utility exposures separate when one pothole reveals more than one line or asset.

  • Additional exposed utilities

Survey Coordinates

This section provides the measured location data that turns a field observation into a design-grade record.

  • Horizontal coordinate system (required)
  • Northing / Y coordinate (required)
  • Easting / X coordinate (required)
  • Vertical datum (required)
  • Elevation (required)
  • Coordinate units (required)
  • Survey method

Attachments and Certification

This section preserves supporting evidence and confirms who prepared the report and whether the data was certified accurate.

  • Field photos

    Upload photos showing the test hole, exposed utility, and reference points if available.

  • Survey sketch or marked-up plan
  • Additional notes

    Include any relevant observations, limitations, or discrepancies between expected and observed utility location.

  • Prepared by

    Optional field for the person completing the report. Avoid collecting unnecessary PII.

  • I certify that the information provided is accurate to the best of my knowledge. (required)

How to use this template

  1. 1. Enter the submission notice details, including the report purpose, project name, test hole ID, and report date so the record can be tied to the correct job.
  2. 2. Fill in the test hole location fields with the site address, a clear location description, the utility type, and the utility owner to identify what was exposed and where.
  3. 3. Record the excavation method, pothole depth, diameter, units, and backfill status immediately after the hole is completed so the dimensions match field conditions.
  4. 4. Add the exposed utility details, including material, size, condition, and depth at exposure, and use the multiple utilities section only when more than one utility was found.
  5. 5. Capture the survey coordinate system, datum, northing, easting, elevation, units, and survey method, then attach photos, a sketch, notes, and the preparer certification before submitting.
  6. 6. Review the completed report for missing units, inconsistent coordinates, or unclear utility descriptions, then release it to design, survey, or construction teams as needed.

Best practices

  • Use a date picker for report date and numeric inputs for depth, diameter, and elevation so the record is easy to validate and compare.
  • Require units for every measured field and keep coordinate system, datum, and survey method visible together to avoid unusable location data.
  • Use conditional logic to show additional utility records only when multiple utilities are exposed, instead of forcing crews through unnecessary fields.
  • Photograph the pothole, exposed utility, and surrounding context before backfill so the images match the measured record.
  • Describe utility condition with specific terms such as damaged, intact, corroded, or unknown rather than vague comments that cannot guide design decisions.
  • Keep the location description precise enough that another crew can find the same test hole without relying only on memory.
  • Limit free-text notes to exceptions, site constraints, or unusual findings so the form stays structured and searchable.

What this template typically catches

Issues teams running this template most often surface in practice:

Missing coordinate datum or coordinate system, which makes the location hard to use in design software.
Recording depth or diameter without units, which creates ambiguity in the final report.
Using a generic utility description instead of identifying material, size, and condition.
Failing to note whether more than one utility was exposed in the same pothole.
Leaving backfill status blank, which can matter for site restoration and follow-up work.
Uploading photos without a clear link to the test hole ID or report date.
Writing the location description too broadly, so the test hole cannot be relocated later.

Common use cases

Civil Designer Verifying a Water Main Conflict
A civil design team needs a survey-backed record of a water main exposed near a proposed storm drain run. This template captures the pothole dimensions, utility depth, and coordinates so the designer can adjust the alignment with confidence.
Utility Coordinator Documenting Multiple Exposures
A utility coordinator opens one test hole and finds both telecom and electric facilities. The additional utility records section keeps each exposure separate while preserving a single audit trail for the location.
Transportation Project Survey Package
A roadway project requires Quality Level A verification before lane closure planning. The survey coordinate fields and attachment section make it easy to hand the report to survey and construction teams without rework.
Contractor Field Verification Before Excavation
A contractor needs a clear record before digging near a known utility corridor. The form documents excavation method, backfill status, and exposed utility condition so the crew can plan the next step safely.

Frequently asked questions

What is this template used for?

This template is used to document a Quality Level A utility test hole, also called a pothole, after a utility has been physically exposed. It captures the location, excavation method, dimensions, utility material and condition, and surveyed coordinates so the record can support design and construction decisions. It is meant for field crews, surveyors, and utility coordinators who need a traceable report rather than a loose set of notes.

When should a Quality Level A test hole report be completed?

Complete it immediately after the utility is exposed and measured, while the field conditions are still visible and the coordinates can be verified. It is especially useful before excavation, during design verification, or when a utility conflict needs precise location data. If the utility was not physically exposed, this template is not the right fit.

Who should fill out and certify this report?

The field technician or utility locator can enter the excavation and utility details, while the surveyor or qualified reviewer should confirm the coordinate data and certify accuracy where required. The exact signer depends on your internal workflow and project requirements. If your organization separates field capture from survey certification, this template supports that handoff clearly.

What makes this different from a standard utility locate form?

A standard locate form usually records marked utility lines or general observations, while this report documents a physically verified utility position with measured depth, dimensions, and survey coordinates. That makes it more suitable for design-grade records and for resolving conflicts where approximate markings are not enough. It also creates a cleaner audit trail for how the location was confirmed.

What fields are most important to customize for our workflow?

Most teams customize the coordinate system, survey method options, utility owner list, excavation method choices, and certification language. You may also want conditional logic for multiple utilities exposed, or required photo uploads when the pothole is backfilled. Keep the form focused on the data you will actually use, following data minimization and progressive disclosure.

How often is this report used on a project?

It is typically completed each time a new test hole is opened and a utility is exposed. On larger projects, multiple reports may be created across different locations as design progresses or conflicts are investigated. If your work involves repeated utility verification, this template can be cloned for each test hole and tied to the same project record.

What are the most common mistakes when using this template?

Common mistakes include leaving out the coordinate datum, using free text where a date picker or numeric field should be used, and failing to note whether multiple utilities were exposed. Another frequent issue is recording utility depth without stating the units or survey method. The report works best when every measured field is specific and the photo/sketch attachments match the written record.

Can this template be integrated into a larger project workflow?

Yes. It can be linked to project intake, utility coordination, survey deliverables, and construction planning records. Many teams also connect it to document storage for photos and sketches, or to an approval workflow so certification happens before the report is released. The template is structured so it can feed downstream design and field coordination without retyping the same data.

How should we roll this out to field crews?

Start by standardizing the required fields, coordinate conventions, and photo expectations before field use. Then train crews on when to capture a single utility versus multiple utilities, how to note backfill status, and how to describe the pothole location clearly enough for later review. A short pilot on one project usually reveals which fields need conditional logic or clearer labels.

Go deeper on the topic

Related concepts
  • A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Subsurface Utility Engineering Quality Level A Test Hole Report with your team — pricing built for small business.

Get Started