Records & documentation curriculum · Module 01

ASCE 38 utility quality levels

The first lesson on the Records & documentation track — the four ASCE 38 utility quality levels the closeout line carries: Quality Level A (potholed), Quality Level B (multi-method confirmed), Quality Level C (records + one method), and Quality Level D (records only). Each level has an audit artefact set the finding line has to ship next to it so the consumer can reproduce the evidence on a defensibility review. The lesson assumes Foundations 05 is in hand — the field-sketch vocabulary and the entry-level ASCE 38 framing — and adds the closeout depth: the canonical cases per level, the audit artefacts per line, and the bounded-negative rewrite. Module 02 next.

Your progress

Track each section as you finish it

Five sections — intro, conceptual framework, bounded negatives, common errors, knowledge check — plus a practice exam and the next module card. Sign in to mark sections complete; progress shows up on your dashboard and across sessions.

New to closeout depth? Foundations 05 — Documentation, field reporting & deliverables is the prerequisite.

Module 01 · Progress
Your progress
Loading progress…
Intro

Why this lesson exists

The cost of an untagged finding line is that the consumer cannot tell a potholed-and-surveyed segment from a record-and-pray one. A claim proceeding, a municipal review, or a contractor walk-off decision turns on which level the segment carries — and the level only ships if the locator writes the level on the line and ships the audit artefacts that go next to it. This lesson teaches the canonical ASCE 38 cases, the artefacts per case, and the bounded-negative rewrite.

Intended audience
The lesson is written for someone about to author or audit the closeout of a multi-utility or campus engagement — the documentation package the consumer reads before any excavation begins.
  • Senior field technicians about to author or sign off on the typed report from their own sketches — the moment a sketch becomes a record the calibration log has to back it.
  • Project engineers and contract managers preparing to evaluate documentation submittals from a private locator against the ASCE 38 standard the contract cites.
  • Owner-side oversight staff reviewing as-built records and evidence-tier annotations against a municipal records tier or a claim proceeding.
Learning objectives

By the end of the lesson you should be able to assign an ASCE 38 quality level to a finding line, ship the audit artefacts the level requires, and rewrite a bounded negative without reaching for a checklist.

  1. 01Assign an ASCE 38 quality level (A, B, C, or D) to a finding line based on the method stack that produced it and write the level stamp onto the line next to the method-stack annotation.
  2. 02Ship the three audit artefacts A and C and D lines have to carry — the pothole log for A, the records-source citation + confirming reading + datum tie for C, the records-only stamp + not-defensible annotation + TBC depth for D.
  3. 03Distinguish a multi-method QL-B confirmation from a records + one method QL-C entry by the method-stack annotation that rides next to each line, and re-grade a line that loses its calibration log reference by one quality level.
  4. 04Rewrite a bounded negative with the four fields the defensibility audit reads against — the method stack, the sweep length tied to a monument-to-monument measurement, the calibration point, and the frequency applied at the time of the pass.
  5. 05Apply APWA colour code for utility class (red for electric, blue for water, etc.) on every segment, and stamp the ASCE 38 level as a separate annotation in the same legend rather than as a colour override.
Conceptual framework

The four ASCE 38 quality levels as a ladder

The four levels are a ladder, not a ranking — every segment carries the level where it was earned. A QL-A potholed stub, a QL-B multi-method confirm, a QL-C records + one method entry, and a QL-D records-only trace can sit on the same findings map; the reader needs the level stamped on every line, and the audit artefact set on every line, before any excavation crosses the corridor.

The four levels below are the framework the rest of the lesson leans on. Each level has a criterion (what method gave you the evidence), an audit artefact set (what the line has to ship next to it to make the evidence reproducible), and a corrective move (what downgrades the line at audit if the artefact set is missing).

The artefact sets match the method-stack annotations that appear in the field report, the bounded-negatives that appear in the records tier, and the per-PDF signature blocks the contractor and the municipal reviewer read against. A line stamped QL-A without a pothole log is structurally a QL-B; a line stamped QL-B without a calibration log reference is structurally a QL-C. The corrective move is always the same shape: drop one rung until the artefacts ship.

The four levels can sit on the same map
Mixing the four levels on one findings map is the rule, not the exception. The level stamp on each line is what makes the map readable; the artefact set on each line is what makes the map defensible.

A corridor might carry QL-A on a potholed gas stub, QL-B on a multi-method communication run, QL-C on a records + one method water lateral, and QL-D on a 1980s records-only trace the GIS dropped. The reader needs the level stamped on every line — without it, the highest-evidence lines carry the lowest evidentiary weight under a defensibility review.

A
Potholed
QL A
Horizontal and vertical accuracy are established by physical exposure at the point — every fitting, valve, or crossing exposed and measured at depth on a survey tie to a fixed monument.

Audit artefactsPothole log: depth at exposure, host-medium note, surveyor monument tie, timestamp the pothole was performed and the technician identifier.

B
Multi-method confirmed
QL B
Horizontal position is determined by two or more geophysical methods agreeing on the segment within the project error budget — typically two EMI passes plus a GPR or acoustic reference probe at the same locus.

Audit artefactsMethod-stack annotation that names each method (e.g. "9 kHz + 33 kHz EMI + GPR + reference probe") with a per-method timestamp, and the calibration log reference for the equipment that produced the stack.

C
Records + one method
QL C
Existing records (as-builts, GIS, prior locating reports) correlated with at least one geophysical method on the segment, and a datum tie that lets the consumer repeat the cross-check on a future pass.

Audit artefactsRecords-source citation: the as-built filename, the GIS layer revision date, or the prior-locating-report reference. Confirming-method reading: a numeric (depth in metres, hyperbolic reflection angle) tied to the field pass. Datum tie: a fixed-monument reference and the cross-section coordinate that lets the cross-check be repeated.

D
Records only
QL D
Information comes from as-built records alone — no field confirmation on this engagement, no upgrades applied, no pothole performed.

Audit artefactsExplicit "records only" stamp next to the segment ID. Explicit "not defensible until potholed" annotation that flags the level for the consumer. Depth field that reads as TBC (to be confirmed) rather than as a numeric depth.

ASCE 38 quality-level ladder (A through D)ASCE 38 quality-level ladder: the four levels stacked from highest evidentiary weight (A, potholed) down to lowest (D, records only). Each rung lists the criterion the level requires and the kind of deliverable it produces.ASCE 38 · quality-level ladderhighest evidentiary weight at the topAPotholedHorizontal & vertical accuracy established by physical exposure at the point.deliverablesPotholed confirmation at every major fitting, valve, and crossing interval.BMulti-method confirmedHorizontal position determined by multiple geophysical methods agreeing at the segment.deliverablesGPR + EM + acoustic reference probe stack on a confirmed segment.CRecords + one methodOne geophysical method correlated with existing records (as-builts, GIS).deliverablesRecords-aligned sweep entry with one confirming method and datum tie.DRecords onlyInformation from records alone, no field confirmation.deliverablesAs-built-drawn segment with explicit "records only" annotation.A ladder, not a ranking — every finding line carries the level where it was earned.
ASCE 38 assigns each finding one of four quality levels based on the method that confirmed it. The ladder is the shareable artefact: a segment tagged at A carries a different evidentiary weight than one tagged at D, and the consumer should never have to infer that weight from the technical narrative.
High-confidence vs. records-only segment comparisonSide-by-side comparison: a high-confidence segment confirmed by potholing + GPR + EM (left) carries a method stack and a bounded-positive annotation; a records-only segment (right) is drawn from as-built records without field confirmation and carries an explicit "records only" tag.Records with positives · records-onlythe deliverable shape changes per quality levelHigh-confidence (A–B)records with field confirmationpotholeQL AGPR + 9 kHz + 33 kHz EMacoustic reference probe · QL Bbounded-positivedepth 1.30 m · concrete hostRecords-only (D)as-builts · no field confirmationAS-BUILT1996 · GIS #UNKno method stack — records onlydepth "to be confirmed at pothole"records-onlynot defensible · pre-potholeThe deliverable that ships a high-confidence segment looks nothing like the one that ships a records-only segment · the quality level is on the page.
A confirmed segment is a finding: it carries a method stack, a bounded-positive depth, and a QL stamp. A records-only segment is a placeholder: it carries an as-built stamp, an explicit "records only" tag, and a clear annotation that the segment is not defensible until a pothole completes the upgrade to A. Mixing the two without the stamp is what makes a report unreadable to a contract administrator.
Bounded negatives

Rewriting silence as a finding

An unbounded negative is silence, not a finding. A bounded negative carries the method that bounded the absence — method stack, sweep length, calibration point, frequency — so the consumer can read what the field actually ran and reproduce the read at a future pass.

Segment rewrite · bn-01
Unbounded (silence)

"No successor utility noted on segment S-04." (silence — no method, no sweep, no calibration, no frequency).

Bounded (deliverable)

"No metallic target detected on segment S-04 by 9 kHz + 33 kHz EMI dual-pass + GPR sweep bounded by tie-lines every 4 m (240 m total), calibration point monument M-12, frequency 9 kHz + 33 kHz applied at lowest transmitter power that read the target conductor on the parallel run at the corridor midpoint."

Segment rewrite · bn-02
Unbounded (silence)

"Nothing visible along the corridor edge." (silence — no instrument, no sweep, no reference).

Bounded (deliverable)

"No conductive target detected along the east corridor edge by passive EM sweep (50 Hz + CP radio band) bounded by trace length 180 m and tie-lines every 5 m, calibration point dielectric reading taken on the local host material at survey point SP-7."

Common errors

Six quality-level mistakes worth flagging

The lesson collects the calls we have flagged on post-closeout debriefs — the kind of mistake that quietly erodes an otherwise defensible package. Each one has a clear signal on the closeout line and a corrective move the team can run before sign-off.

Stamping a finding line without an ASCE 38 level
Signal in the report

A segment entry reads "Utility present — confirmed by field sweep" without an A, B, C, or D label on the line.

Corrective move

Stamp the line with an explicit level (A, B, C, or D) and the method stack annotation that produced the line. Untagged findings force the consumer to infer the evidentiary weight from context, which is exactly the failure mode ASCE 38 was written to prevent.

Calling a records-only segment QL-C
Signal in the report

A segment carries an "as-built plan + field check" stamp on the line but the field check did not actually run a confirming geophysical method.

Corrective move

A QL-C entry requires a records citation plus a confirming-method reading on the segment. Without the confirming method, the line is QL-D — records-only with the three artefacts (records-only stamp, not-defensible annotation, TBC depth).

Conflating APWA colour code with the quality level
Signal in the report

A draft map colours every segment in APWA red, without distinguishing a QL-B multi-method confirm from a QL-D records-only entry — the colour carries utility class but doubles as a confidence signal in the legend.

Corrective move

Use APWA colour code for utility class on every segment (red electric, blue water, green sewer, etc.). Stamp the ASCE 38 level as a separate annotation in the same legend. Colour and evidentiary weight are two different signals and should not share a code on the map.

Writing "no successor utility" without a bounded negative
Signal in the report

A report carries "no successor" notes for several segments. Method stack, sweep length, calibration point, and frequency are absent on every one.

Corrective move

Rewrite every negative as a bounded negative with the method stack, the sweep length tied to a monument-to-monument measurement, the calibration point, and the frequency applied at the time of the pass. Unbounded negatives are silence, not findings; the defensibility audit will not pass until every negative is bounded.

Shipping a finding line without a calibration log reference
Signal in the report

A line names a geophysical method in the method-stack annotation but does not cite the calibration log reference (the equipment model, serial number, calibration date, or calibration log entry).

Corrective move

Add the calibration log reference next to every line that names a geophysical method. A line without the calibration log reference is not reproducible at audit; the omission downgrades the line by one quality level (B becomes C, C becomes D).

Calling a potholed line "verified" without a pothole log
Signal in the report

A line carries a pothole stamp but no pothole log — no depth at exposure, no host-medium note, no surveyor monument tie, no pothole timestamp.

Corrective move

A pothole is the audit artefact that earns QL-A, not the bare word "verified." A pothole line without a pothole log reads as a QL-B multi-method confirmation at best — the level has to drop until the pothole log ships.

Knowledge check

Self-check — four questions on quality-level assignment, reveal as you go

A short authored self-check covering the closeout calls the audit reads against — the canonical cases per level, the audit artefacts per case, the bounded-negative rewrite, and the calibration-log downgrade.

This is a self-check, not a graded exam. Pick a question, reveal the answer, and use the rationale to decide whether the topic earns another pass before sign-off.

0 of 4 answers revealed. State is kept on this device only.

  1. 01

    A crew has located a suspected gas service lateral at a campus site: 9 kHz EMI shows a clean peak, 33 kHz EMI shows a parallel offset, and GPR returns a hyperbolic reflection on the same locus. What ASCE 38 quality level is the closest match for that confirmation stack, and what makes it that level rather than the next rung up or down?

  2. 02

    The same crew finds a water service stub that the customer requested potholed. The pothole reaches 0.85 m and exposes a 25 mm copper lateral at 0.88 m, with a clear tie-in to a curb-stop visible on the surface. What ASCE 38 quality level is the stub carried at, and what is the deliverable shape the closeout package has to ship next to the stub line?

  3. 03

    An older campus GIS labels a section of irrigation lateral as 100 mm PVC at 0.4 m depth. The on-site GPR pass returns a hyperbolic reflection at 0.45 m on the same locus. What ASCE 38 quality level is that segment carried at, and what does the line on the closeout map have to ship next to the locus to make the assignment reproducible?

  4. 04

    A segment of the corridor carries only an as-built record (a 1980s water main map) and the on-site pass produces neither a geophysical confirmation nor a pothole. What ASCE 38 level is the segment carried at, and what does the field note have to ship so the consumer does not mistake the records-only entry for a confirmation?

Practice exam

Graded ASCE 38 quality levels practice run

A graded practice exam on this module — 8 multiple-choice questions, 4 options each, instant feedback, score summary with a tier label at the end. The four-question reveal-on-click knowledge check above is for reading; this is for testing.

Ready to test

The Module 01 practice exam covers the ASCE 38 canonical cases per line, the audit artefacts per case, the bounded-negative rewrite, the calibration-log downgrade, and the APWA colour / level-stamp separation. Take it after the four-question knowledge check; the tier at the end tells you whether to retake the lesson before Module 02.

Start the Module 01 practice exam
Next module

Coming up on the Records & documentation track

Module 01 stops at the quality-level stamp on the closeout line. The next three lessons walk the rest of the closeout package — the field sketch, the photo and video archive, and the deliverable format split between the contractor and the municipality.

Live
Module 02
Field-sketch standards
The companion lesson on what the field team draws on the sketch block — the per-block convention, the five artefacts per block, the method-stack annotation, the sign-off, and the timestamp alignment to the equipment log.
Live
Module 03
Photo and video documentation
The media-archive companion on what the field team captures on the surface and the survey screen — in-frame identifiers, static bookends on a video clip, the five-field photo log, still-frame captures alongside each clip, and project-archive persistence.
Live
Module 04
Deliverable formats
The twin-pair deliverable companion — the contractor-actionable tier vs. the municipal-records tier, the segment-ID namespace contract that binds the two, the PDF archival default, and the per-PDF signature-block distinction.
Curriculum note

Each lesson ships with its own knowledge check and graded practice exam so the track stays useful even if you arrive mid-sequence. Module numbers align with the practice program hub on /training/records-documentation/practice.

Back to the track landing