Field-sketch standards
The second lesson on the Records & documentation track — the per-block sketch convention the field uses at closeout, not the all-day roll. Six artefacts per block (the five in-frame plus the sign-off), per-feature geometry rather than continuous-ribbon flattening, side-column hand-off notes for the report writer, and the timestamp alignment to the equipment log that anchors a sketch block to a single sweep. The lesson assumes Foundations 05 is in hand — the field-sketch vocabulary — and adds the closeout-depth discipline that makes the sketch a record the audit can reproduce.
Track each section as you finish it
Five sections — intro, six artefacts per block, side-bar hand-off notes, 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 the per-block sketch convention? Foundations 05 — Documentation, field reporting & deliverables frames the entry-level vocabulary.
Why this lesson exists
A field sketch that gets handed off as the documentation deliverable is not a deliverable — it is the technician's working memory. The deliverable is the typed findings map + field report + recommendations memo tier assembled from the sketch, the tagged sweep data, and the bounded negatives. This lesson teaches the per-block convention that makes the sketch ready to be assembled into the typed report — and reproducible on a defensibility review.
- Field technicians about to commit their sketches to a typed report — the moment a sketch needs the per-block convention because the report writer is not on the same crew as the technician.
- Report writers who assemble the typed findings map from incoming sketches — the moment the tier-bundle has to ship with the segment ID the sketch bears so the reader can reconstruct at audit time.
- Project engineers and oversight staff who evaluate sketch submittals against the per-block convention — the moment a sketch without the five artefacts goes back to the field for re-drawing.
By the end of the lesson you should be able to draw a per-block sketch that ships the five artefacts, sign the block at the bottom before closeout, and align the block timestamp with the equipment log within the window a single-sweep anchor requires.
- 01Annotate a per-block field sketch with the five-artefact set — North arrow, scale bar, datum tie, sweep-start timestamp, method-stack label — so the block is self-contained for the audit.
- 02Stamp the method-stack annotation on every segment line so the reader can reproduce the ASCE 38 quality level without referring to the equipment log.
- 03Sign and date the block at the bottom so the block becomes a record: technician identifier, date, time the block was completed — three fields, one act of authorship.
- 04Draw every fitting, every offset, and every valve as distinct geometry rather than continuous-ribbon flattening — three rules that turn a sketch into a reproducible record.
- 05Align the block timestamp with the equipment log sweep-start within the window that anchors a single sweep — and split the block if a sweep-boundary crosses two sweeps.
What every per-block sketch has to ship
Five artefacts sit inside the per-block frame (North arrow, scale bar, datum tie, sweep-start timestamp, method-stack label); one sits at the bottom of the frame (sign-off: technician + date + time). Together the six artefacts turn the sketch from a working drawing into a record the audit can reproduce.
Inside the per-block frame on the upper-left, drawn at the same orientation as the project datum (true north, not magnetic).
Lets a reader orient the block without referring to the page header or to the rest of the engagement. The north arrow is orientation, not decoration.
Inside the per-block frame on the upper-right, calibrated to the local control monuments.
Gives the reader a per-block scale rather than a page-level scale. On multi-block pages the page-level scale erodes when blocks draw at different scales.
Inside the per-block frame in the upper header row, naming the fixed-monument reference and the cross-section coordinate.
Anchors the block in the project datum. The tie-in the reader locates without scrolling back to the page header — the per-block convention exists to remove that scroll.
Inside the header row, alongside the datum tie and the method stack label.
Anchors the block in the equipment log. A block cannot be over 30 minutes from the equipment log sweep-start, or the level on the line erodes by one quality rung.
Inside the upper header row, with one label per block — not per segment.
Names the instruments and passes the field ran across the block. The label reads against the per-segment method-stack annotations the report writer adds next to each finding line.
At the bottom of the per-block frame: technician identifier, date, time the block was completed.
Transitions the block from working artefact to record. The triangle of three fields establishes the chain of authorship the audit reads against.
Per-block artefacts let the reviewer read each block as a self-contained artefact. The North arrow orients the block; the scale bar calibrates distances the report writer will use; the datum tie anchors the block in the project datum; the sweep-start timestamp anchors the block in the equipment log; the method-stack label sets the per-block methodology the report writer will cite next to the line; the sign-off establishes the chain of authorship. Six artefacts, one block, one record.
Stashing hand-off notes for the report writer
Three categories of side-column notes belong on the per-block sketch in a column that does not overlap the drawing: calibration points, control-monument references, and APWA paint codes visible nearby. The report writer reaches for these at report-authoring time, days or weeks after the field ran.
- Monument M-12 used as dielectric calibration on host material at SP-7.
- Pothole at curb-stop, depth 0.88 m at 12:24, used as QL-A tie for segment S-04.
- Monument M-12 (NE corner of building 4) — reference for S-01 / S-02 / S-04.
- Monument M-18 (curb-side) — reference for S-05 / S-07.
- Yellow paint (gas) at flag G-04 across the corridor — flagged on adjacent sweep.
- Red paint (electric) on the east edge across the alignment of segment S-02.
Six sketch-discipline mistakes worth flagging
The lesson collects the calls we have flagged on post-closeout debriefs — the kind that quietly turn a defensible sketch into an audit-time reconstruction. Each has a clear signal on the sketch block and a corrective move the team can run before sign-off.
A multi-hour engagement yields a single tens-of-metres-long sketch with one page-level header. Finding lines are scattered across the roll and stamped with sketch-segment labels that do not match the equipment log.
Draw a per-block sketch — a bounded rectangular frame per work area — and stamp each block with its own North arrow, scale bar, datum tie, sweep-start timestamp, and method-stack label. The block is the unit of audit, not the page.
A block carries four of the five artefacts (North arrow, scale bar, datum tie, sweep-start timestamp) but no method-stack label. The drawing is real but the methodology is invisible.
Add the method-stack label in the upper header row, alongside the datum tie and the sweep-start timestamp. A block without a method-stack label forces the report writer to scan the equipment log to recover which method produced the line.
A gas service lateral is drawn as a continuous ribbon of dashes with no visible fitting, no offset, no valve cover — the visible field geometry is squashed into a single token.
Draw distinct geometry for every visible field feature — every fitting as a point, every offset as a labelled break, every valve cover as a circle tied to a monument. Three rules, one sketch artefact.
The technician intends to fill in the technician identifier, the date, and the time at end-of-day, but the block enters the closeout package un-signed — no chain of authorship on the bottom of the block.
Sign the block at the bottom before the closeout assembler pulls it into the typed report. Three fields, one act of authorship. The block is the record; the record requires a signature.
A page-level header carries the engagement ID, the date, and a page-level scale bar. Per-block sketches on the page miss the per-block North arrow, scale bar, datum tie, and timestamp.
Stamp the page-level header with orientation only (engagement ID, date, page number), and stamp the per-block artefacts on every individual block. Page-level headers are orientation; per-block artefacts are audit.
Side-column notes — calibration points, control-monument references, APWA paint codes — overlap the drawing area and force the report writer to thread geometry with metadata.
Stash the side-column notes in a column that does not overlap the drawing. A side-column note in the drawing area is clutter; a side-column note in the metadata column is a positive artefact the report writer reaches for at report-authoring time.
Self-check — four questions on the per-block convention, reveal as you go
A short authored self-check covering the per-block discipline decisions the audit reads against: the five-artefact set, the method-stack label, the sign-off triad, and the per-feature geometry rule.
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 closeout.
0 of 4 answers revealed. State is kept on this device only.
- 01
A crew returns from a multi-utility campus sweep with a continuous running sketch covering the entire engagement day. The next day, a reviewer tries to use the sketch as evidence in a defensibility audit. Why does the running sketch fail the audit?
- 02
A technician forgets to add the method-stack annotation to a sketch. The sketch shows the geometry of three located segments clearly, but it does not say which geophysical method stack produced each segment. Why is that omission a closeout failure, not a craft oversight?
- 03
A technician has started a new block of the field sketch and drawn the segment lines, but the sweep is still going on. They leave the sketch un-signed and un-dated at the bottom of the block, intending to fill the metadata in at end-of-day. What is the risk if the block goes into the closeout package un-signed and un-dated?
- 04
A technician draws a block sketch with a continuous ribbon of dashes to represent a gas service lateral. The dashes do not show offsets, fittings, or valve locations, even though the field team found a 1.5 m offset mid-run and a curb-side valve at the meter. What is wrong with that level of detail on a block sketch?
Graded field-sketch standards 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.
The Module 02 practice exam covers the per-block convention, the five-artefact set, the method-stack label stamp, the sign-off triad, the per-feature geometry rule, and the side-column hand-off notes. Take it after the four-question knowledge check.
Coming up on the Records & documentation track
Module 02 stops at the per-block signature on the field sketch. The next two lessons walk the rest of the closeout package: the photo and video archive, and the deliverable format split between the contractor and the municipality.
Module 02 ships with its own knowledge check and graded practice exam. Take Module 01 first if the ASCE 38 quality-level assignment is new to you — the per-block convention assumes the level stamp on the line next to the method-stack label.