Documentation, field reporting & deliverables
The fifth foundations lesson for anyone stepping onto a residential or small-commercial scope after the Foundations 02 surface pre-sweep and Foundations 03 equipment vocabulary are in hand. The lesson covers what the field team hands off when the engagement closes — the field sketch (north arrow, offset scale bar, project ID block, legend), the measurement tie convention anchored at a fixed monument, the per-segment ASCE 38 quality level written onto the field reader at the time of the locate, the photo capture that survives project handover, the dispatching path to a contractor or to a municipality, and the findings map / field report / recommendations memo three-tier deliverable shape. The lesson here assumes the demarcation framing from Foundations 01, the surface vocabulary from Foundations 02, the equipment vocabulary from Foundations 03, and the frequency log Foundations 04 has just produced — and adds the documentation discipline that wraps a defensible report around those four cumulative vocabularies.
Track each section as you finish it
Five sections — intro, conceptual framework, procedures, common errors, knowledge check. Sign in to mark sections complete; progress shows up on your dashboard and across sessions.
New to the curriculum? See the full training catalog to browse every available course.
Why this lesson exists
A field sketch without the four block annotations, a measurement tie anchored to a building corner, a per-segment quality level stamped at QL-A on the cover page, a photo log saved to the camera roll, a single flat deliverable sent to both the contractor and the municipality — each of these is the documentation mistake an early-career scope produces, and each is what the closeout cannot defend when the next crew, contractor, or inspector arrives. This lesson is the wrap for Foundations 04: the per-conductor frequency log and the depth estimate F04 has just produced are what the field sketch, the measurement ties, and the ASCE 38 quality-level assignment record against. F05 is what hands a defensible report off from the field crew to whatever audience shows up next.
- Entry-level field technicians taking their first closeout of a residential or small-commercial scope and learning the four block annotations, the fixed-monument anchor, the per-segment ASCE 38 quality level shorthand, and the photo convention that travels with the sketch.
- Customer-side intake staff answering the kick-off call who need a vocabulary for what the closeout actually produces — findings map for the contractor, field report for the municipality, recommendations memo when the report drives follow-on decisions.
- Project managers and oversight staff who need to read the field sketch and the per-segment quality-level assignment on a closeout report and trust that the deliverable tier the audience received is the one that audience needed.
By the end of the lesson you should be able to author a field sketch and a deliverable on a typical residential or small-commercial scope without confusing a blank block for a sketch, a building corner for a fixed monument, or a flat one-tier-report for an audience-shaped deliverable.
- 01Draw the four annotations that go on a field sketch before any locate is recorded — north arrow, offset scale bar, project identifier block, and the legend entries (utility categories and ASCE 38 quality levels) — and explain why each one belongs on the page before the field work starts, not after.
- 02Anchor measurement ties to a fixed monument (property-line cleanout, curb stop, valve box, monumented right-of-way marker) rather than to a building corner, and chain ties via running PPOD-to-PPOD offsets so the next crew can reproduce the locate without re-deciding where the original anchor was.
- 03Assign ASCE 38 quality levels A through D per segment at the time of the locate, not on the cover page at closeout — QL-A only where a pothole opened; QL-B where two independent methods agreed; QL-C where records plus one method agreed; QL-D where records only is the available evidence.
- 04Capture photo evidence keyed to the mark numbers on the sketch — a desktop-readable photo log, an offset-anchored photo position, and a defined lens-and-frame convention the next crew can reconstruct — and explain why the photo log is what survives the handover, not the camera-roll.
- 05Pick the right deliverable tier per audience — the findings map for a contractor who needs to dig, the field report for a municipality clerk who needs a public record, the recommendations memo for a higher-level reviewer who needs to drive follow-on decisions — and spot the six documentation mistakes that show up on early-career scopes.
Field-sketch conventions and ASCE 38 quality-level authorship on the field reader
Every field sketch the closeout hands off carries the same four block annotations — north arrow, offset scale bar, project identifier block, legend entries — and every measurement tie the closeout references is anchored at a fixed monument rather than a moving building corner. The quality-level assignment is per-segment, written at the time of the read, and photos are keyed to mark numbers in a project-ID photo folder — not the camera roll.
The field sketch is the artefact the next reader reconstructs from. A sketch without the four block annotations is a freehand screenshot: no north arrow means the next reader cannot orient the marks, no offset scale bar means measurements cannot be re-laid, no project identifier block means the marks cannot be merged with the rest of the deliverable, no legend entries means the symbology cannot be defended. Writing the block before any locate mark goes onto the page is the discipline every field sketch carries, and the discipline the defensibility audit at closeout verifies.
The measurement tie convention anchors every offset at a fixed monument — a property-line cleanout, a curb stop, a valve box, or a monumented right-of-way marker — and chains ties via running PPOD-to-PPOD offsets in order. Building corners move; monuments do not. The chain is what lets the next crew reproduce the locate without re-deciding where the original anchor was. ASCE 38 quality levels assigned per segment — A only where a pothole opened, B where two methods agreed, C where records plus one method agreed, D where records only — compose the line-by-line authorship on the field reader at the time of the read. A line-by-line assignment per conductor is what readers expect, not a blanket stamp on the cover page. Photos keyed to the mark numbers in a project-ID folder — with the corridor cross-section included in corridor overviews — make the photo log a handover artefact the next crew can reconstruct the read from.
A locator who anchors ties to the corner of the house is producing a sketch that cannot be reproduced after the next remodel — every offset is an interpretation, not a measurement. The corrective move on a fresh scope is to pick the monument at the start of the walk and chain every PPOD-to-PPOD tie off it in order; on a completed sketch, the corrective move is to re-anchor each tie to the nearest fixed monument before the report goes to the customer. The defensibility audit asks the same question regardless: which monument anchors the ties, and can the next crew re-measure from that same monument?
From the pre-field documentation hypothesis to the closeout dispatch
The on-site workflow for documentation discipline follows three short phases — pre-field documentation hypothesis (which monument, which photo convention, which per-segment quality-level plan), on-site documentation discipline (block-on-page-first, mark-as-you-read, photo-as-you-go, continuous sketch update), and closeout, dispatch, and the deliverable tier (findings map for contractor, field report for municipality, recommendations memo for higher-level review).
- Choose the fixed monument for the measurement ties before mobilisation: a property-line cleanout, a curb stop, a valve box, or the nearest monumented right-of-way marker. Plan to anchor every PPOD-to-PPOD tie to that monument, in order, so the next crew can re-measure from the same starting point.
- Decide the on-site quality-level plan per conductor before mobilisation: which conductors will be potholed (target QL-A, reserved for short runs where a vacuum-excavation is planned), which will be confirmed by two independent methods (target QL-B), which will be confirmed by records plus one method (target QL-C), and which will live in records-only mode (target QL-D). The plan is what the field reader writes onto the locate marks at the time of the read.
- Pick the photo convention: lens (fixed-focal, single-lens), frame (a single mid-marker photo plus a corridor overview per block), encoding (mark number visible in the frame, monotonic increasing across the project), and storage (project ID-name folder, no camera-roll). The convention is what makes the photo log a handover artifact rather than a gallery.
- Decide the deliverable shape per audience: one findings map for the contractor, one field report for the municipality, one recommendations memo when the report is expected to drive follow-on work. Decide the tiers before the on-site pass so the closeout reads back the same shape.
- Draw the sketch block first — north arrow, offset scale bar, project ID block, legend entries — before any locate mark goes onto the page. The block is the four annotations each sketch carries and the discipline that prevents a freehand screenshot.
- Mark every locate point as soon as the receiver reads it: offset from the fixed monument running along the corridor, the per-segment quality level (QL-A/B/C/D) written next to the mark, the mark number that matches the photo convention, and any running-frequency choice inherited from Foundations 04 that justified the read. Field-authored is the corrective move against closeout reconstruction, which loses the reasoning.
- Photograph each locate mark with the mark number visible in the frame, the corridor cross-section visible in the corridor overview, and the photo file keyed to the project ID-name folder. The photo log is what the next reader uses to reconstruct the read; the camera-roll is not.
- Update the sketch continuously as the corridor progresses — every offset, every quality level, every photo reference — so the closeout reads back the same annotations the field crew authored at the time of the read. A sketch revised at the hotel that night is not the field sketch; it is a reconstruction.
- Issue the findings map for contractor dispatch: CAD or PDF plan, the marks with their per-segment quality levels, the offset dimensions keyed to the chosen monument, and a photo set keyed to the mark numbers. The contractor reads this to plan the dig and verify before crossing each mark; the tier is what survives the next day.
- Issue the field report for municipality dispatch: prose narrative — what was located, what method, what the readings were, what surfaces were inspected, what the limits of the locate are — keyed to the right-of-way and to the inspector who needs to re-read the work five years later. The tier is a public record, not a dig plan.
- Issue the recommendations memo for the customer or higher-level reviewer when the report needs to drive follow-on decisions: a re-locate schedule, a vacuum-excavation plan, a recommendation that part of the scope be rediscovered from records. The tier is reserved for cases the findings map and the field report cannot serve alone.
- Run the defensibility audit at closeout: north arrow present, offset scale bar present, project ID block present, legend entries present, every mark readable in the field at the 99/98 step, every photo referenced on the sketch present in the photo log. The audit is the verification step on the report the engagement framework promises.
The single sentence that travels with every residential or small-commercial closeout: “The field sketch and the per-segment quality-level assignment are written onto the page at the time of the locate, anchored at a fixed monument the next crew can re-measure from, and dispatched as the deliverable tier the audience needs — the findings map for the contractor to plan the dig, the field report for the municipality to keep as a public record.” That sentence, in the kick-off email and on the closeout summary, prevents both the “the report is one-size-fits-all” deliverable mistake and the “we did not write down the monument” reproducibility surprise after mobilisation. It is small, it is plain, and it does most of the documentation-discipline work the team needs to do outside of the field report.
Phase 1 — pre-field documentation hypothesis — sets the DOCUMENT precondition: which monument, which photo convention, which per-segment quality-level plan. Phase 2 — on-site documentation discipline — confirms the documentation discipline against the marks on the ground, anchored at the fixed monument, photographed at the time of the read, ASCE 38 quality level written next to each mark. Phase 3 — closeout, dispatch, and the deliverable tier — is the verification step on the report the framework promises: findings map for contractor, field report for municipality, recommendations memo when the report drives follow-on decisions.
Open the engagement frameworkThe records-versus-records-only ladder on the left is the visual cue the entry-level audit reads: a record in the database is not the same as a record plus an on-site geophysics confirmation, and the difference is what produces the QL-C versus QL-D distinction on the field reader. A report that conflated the two would tell the reader that a QL-D target is “located;” a report that separates them tells the reader that the QL-D target falls back to records-only and the only sure re-confirmation is a re-locate against the next geophysics pass.
Dispatching is the moment the deliverable tier matters: a contractor who needs to dig tomorrow reads a findings map, not a field report; a municipality clerk who needs to keep a public record reads a field report, not a recommendations memo. Sending the same flat document to both readers is the entry-level audience mistake F05 exists to prevent — the right tier per audience is what the dispatch at closeout selects.
Six documentation mistakes worth flagging
The lesson collects the entry-level documentation calls we see show up on early-career scopes — the kind the four block annotations on the sketch prevent before mobilisation, and the kind a line-by-line per-segment quality-level assignment, an anchored measurement tie at a fixed monument, and an audience-shaped deliverable tier prevent at handover.
A technician comes back from a campus scope with a full set of locate marks, but the sketch has no north arrow, no offset scale bar, no project identifier block, and no legend entries. The next crew cannot tell where north is, what scale to read against, what project the marks belong to, or what the symbology means.
Force the four block annotations onto the sketch before any locate mark is drawn: north arrow, offset scale bar, project identifier block, legend entries. The block is the discipline each sketch carries; without it the sketch is a freehand screenshot that fails the defensibility audit before any mark is examined.
On a residential scope, the locator ties every offset to the corner of the house because the corner is the closest visible reference. Two years later, after a remodel, the corner has shifted and the offsets cannot be reproduced — the sketch is unrepeatable and the deliverable is no longer defensible.
Anchor every measurement tie to a fixed monument — a property-line cleanout, a curb stop, a valve box, or a monumented right-of-way marker — and chain ties via running PPOD-to-PPOD offsets from that monument. The corrective move on a completed sketch is to re-anchor each tie to the nearest fixed monument before the report goes to the customer.
A team returns from a multi-utility campus scope with field notes that read "all utilities located at ASCE 38 QL-A." On review, no segment was potholed; every segment was confirmed by records plus one geophysics method — by definition QL-C, not QL-A. The report overstates what the field did and fails the defensibility audit on a reader who asks for the pothole evidence.
Walk each conductor back through the work and assign QL-A only where a pothole actually opened (size, material, depth confirmed at the open hole); QL-B where two independent methods agreed; QL-C where records plus one method; QL-D where records only. Note the reason for each downgraded line. A line-by-line assignment per conductor is what readers expect.
A technician captures 200 photos across a corridor scope and saves them to the device camera roll. At closeout, the photos are mixed with the technician's personal camera roll and the project folder is missing — the contractor asks for the photos and the report has no way to deliver them in mark-number order.
Use a project ID-name folder from the first photo of the day. Each frame carries the mark number, the corridor cross-section (in corridor overviews), and the convention chosen in the pre-field documentation hypothesis. The photo log is the artefact the next crew reconstructs from; the camera-roll is not.
A team issues a single "locate findings" document to both a contractor and a municipality clerk in the same week. The contractor says the document is too prose-heavy to plan a dig; the municipality says it is too thin on the narrative to be a public record. The deliverable fails both readers.
Split the deliverable into the three tiers — the findings map for the contractor, the field report for the municipality, and the recommendations memo for the higher-level reviewer when the report needs to drive follow-on decisions. Each tier is annotated for the audience it serves and reads back the same field sketch underneath.
A team arrives back at the hotel hours after the on-site pass and rebuilds the sketch from a notebook of partial notes and a memory of the corridor. The reconstruction drops the per-segment quality level, drops the photo mark number, and misses the offset from the fixed monument at two key points.
Author the sketch on the page at the time of the read — every offset, every quality level, every photo reference — and update it continuously as the corridor progresses. A sketch revised at the hotel that night is a reconstruction, not a field sketch; it is not the artefact the next reader reconstructs from.
Self-check — four questions, reveal as you go
A short authored self-check covering the documentation decisions that show up on the first closeout of any residential or small-commercial scope. Reveal an answer to read the rationale; reset between customers with Hide all.
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 you lay out the next sketch block or choose the next dispatching audience.
0 of 4 answers revealed. State is kept on this device only.
- 01
You draft a field sketch for a residential scope. What four annotations belong in the sketch block before any locate is added to the drawing, and why does each one go on the page before the field work starts?
- 02
A technician in training proposes to "tie measurement offsets to the corner of the building" rather than anchoring them at a fixed monument on the right-of-way. Why is this a high-risk approach, and what is the corrective move?
- 03
A junior locator comes back from a multi-utility campus scope with field notes that say "all utilities located at ASCE 38 QL-A." Why is that almost certainly wrong on a typical campus, and what level should each utility class be assigned against instead?
- 04
A contractor asks for "the locate findings" and a municipality clerk in the same week asks for "the locate findings." Should both receive the same deliverable, and what three-tier shape does the answer split into?
Where to take this lesson
Foundations 05 (track-order) wraps the entry-level documentation discipline around the demarcation framing from F01, the surface vocabulary from F02, the equipment vocabulary from F03, and the frequency log from F04. The natural next moves are the Foundations 04 return loop (the frequency log F05 reads against) and the Foundations 02 return loop (the surface vocabulary F05 photo-logs against), or Advanced Module 03 (the documentation discipline at audit scale across multi-day, multi-stakeholder engagements).
Each foundations module ships with its own lesson page, knowledge check, and a stand-alone vocabulary set so the track stays useful even if you arrive mid-sequence.