Records & documentation curriculum · Module 03

Photo and video documentation

The third lesson on the Records & documentation track — the conventions that make the media archive a record the audit can reproduce rather than a working set the team remembers. In-frame identifiers, the five-field photo log, static bookends on a video clip, a still-frame capture alongside each clip, and project-archive persistence so an audit-time reviewer can locate the photograph the report references without calling the technician.

Your progress

Track each section as you finish it

Five sections — intro, photo log, video bookends, 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 media-document conventions? Foundations 05 frames the entry-level vocabulary — take Foundations 05 — Documentation, field reporting & deliverables first.

Module 03 · Progress
Your progress
Loading progress…
Intro

Why this lesson exists

A photograph without an identifier in the frame is an unanchored image; a video clip without static bookends is a moving image; a photo archive without a log is an unstructured blob. The convention the field uses turns each one into a record — independently matchable, queryable on demand, and reproducible on a defensibility review.

Intended audience
The lesson is written for the field team about to author or author-read the media archive that ships alongside the typed report.
  • Field technicians about to commit photographs and clips to a typed report — the moment the archive has to be queryable because the report writer is not on the same crew as the technician.
  • Report writers and project engineers who assemble closeout packages and need the archive indexable by segment ID on demand — the moment a photograph without a log entry is not in the deliverable.
  • Owner-side oversight and municipal staff reviewing photographs at handover — the moment an un-anchored photograph cannot be matched without a side-channel and is no longer evidence.
Learning objectives

By the end of the lesson you should be able to capture a photograph with an in-frame identifier, capture a video clip with static bookends, maintain the five-field photo log, and persist the archive to a managed project endpoint — without reaching for a checklist.

  1. 01Embed a visible identifier in the frame of every photograph — a chalkboard with the photo number and date, or a printed tag held in the shot — so the photograph is independently matchable to a sketch segment without side-channel lookup.
  2. 02Open every video clip with a few seconds of static surface reference (the survey monument visible, the segment ID on a tag, the timestamp embedded), run the sweep, then close with a brief duration of the same reference — the static bookends that make the clip reproducible on a defensibility review.
  3. 03Maintain the five-field photo log: photo number, timestamp, segment ID, technician identifier, and a one-line caption describing the visible content. A photo without an entry in the log is not in the deliverable.
  4. 04Capture a still-frame alongside each video clip so a reviewer can quote the static surface reference without scrubbing through the entire video.
  5. 05Persist photographs and clips to the managed project archive by end-of-day — chain-of-custody metadata, versioned storage, and backup strategy make the archive defensible; personal-phone storage alone does not.
The photo log

Five fields, one index, queryable on demand

The photo log is the smallest artefact that scales a photo archive from 'the team remembers' to 'a reviewer can find the photograph for a segment on demand.' Three fields are mandatory; two more close out the metadata.

Photo number
Mandatory

Maps the log entry to the photograph file (typically the EXIF file sequence or the camera-assigned number). Without the number the log entry is orphan to the file.

Timestamp
Mandatory

Maps the log entry to a sweep in the equipment log. The timestamp is what aligns the photograph with the per-segment method-stack annotation on the typed report.

Segment ID
Mandatory

Maps the log entry to a sketch block and the corresponding finding line on the typed report. The segment ID is also what the per-PDF signature block cites.

Technician identifier
Recommended

Closes out the chain of authorship. A photograph without a technician identifier is a candidate image, not a record.

One-line caption
Recommended

Tells the reviewer what the photograph shows. A photograph without a caption forces the reviewer to guess which angle matches the report's reference.

In-frame identifier — the frame is what a future reviewer has access to

Two artefacts belong inside the photograph frame. A chalkboard with the photo number and date, or a printed tag held in the shot, makes the photograph independently matchable to a sketch segment without a side-channel lookup. The convention is "the identifier belongs in the frame" because the frame is what a future reviewer has access to. Sticky- note matching is fine when the technician writes the report, but the field review at handover or claim proceeding is not the technician — a separate reviewer needs to read the identifier without asking the original author.

Video clip bookends

Static surface reference at the start and the end

A video clip without static bookends is unanchored to the field event it captured. The convention is to start with a few seconds of static surface reference (the survey monument visible, the segment ID written on a tag, the timestamp embedded), run the sweep, then close with a brief duration of the same reference.

PART 01
Open bookend
~3 to 5 seconds of static surface reference
  • Survey monument visible in frame (numbered tag held in shot or natural monument in the background).
  • Segment ID written on a tag and held in the shot.
  • Timestamp embedded — either an in-frame timestamp card, a printed slip, or a chalkboard with date + time.
PART 02
Sweep body
Variable — the sweep itself
  • Receiver trace or GPR sweep visible as it crosses the segment.
  • No narration that depends on ambient audio for the sweep parameters (parameters go on the title card).
  • Direction-of-pass visible to a reviewer — sweep direction is a reading cue the audit reads against.
PART 03
Close bookend
~3 to 5 seconds of the same static surface reference
  • Same monument visible that opened the clip — gives the reviewer a "before / after" anchor.
  • Same segment ID if it changed during the sweep — the audit reads the start and end anchors together.
  • Sweep terminus marked — a flag, a chalkboard, or a verbal cue on the title card.
Common errors

Six media-archive mistakes worth flagging

The lesson collects the calls we have flagged on post-closeout debriefs — the kind that quietly turn a defensible archive into an unanchored set. Each has a clear signal and a corrective move the team can run before closeout.

Shipping photographs without an in-frame identifier
Signal in the archive

A photograph of a located segment carries no chalkboard, no printed tag, no embedded timestamp; the photograph is matched to the sketch only by the technician's memory.

Corrective move

Embed a visible identifier in every frame — chalkboard with photo number + date, or a printed tag held in the shot. The identifier is independent of any side-channel index and survives a future reviewer who never met the technician.

Opening a video clip with the sweep itself
Signal in the archive

A video clip starts when the receiver trace starts moving and ends when it stops. The clip has no static bookend at the start or the end.

Corrective move

Open with 3 to 5 seconds of static surface reference (monument, segment ID, timestamp), run the sweep, then close with the same reference. Static bookends are what make the clip reproducible on a defensibility review.

Returning from the field with hundreds of photographs and no photo log
Signal in the archive

A crew returns from a multi-day engagement with hundreds of photographs. The photographers can describe what is in each photograph but cannot sort them by segment ID, by date, or by technician on demand.

Corrective move

Maintain the photo log on the engagement — every photograph gets an entry with at least the three mandatory fields (photo number, timestamp, segment ID), and the technician identifier + a one-line caption close out the metadata. A photo without an entry is not in the deliverable.

Relying on a personal phone as the long-term archive
Signal in the archive

A crew stores photographs and clips on a personal phone and uploads them at end-of-day. The phone is the only storage between capture and closeout.

Corrective move

Persist to the managed project archive by end-of-day. The archive has versioned storage, chain-of-custody metadata, and a backup strategy. Personal-phone storage is volatile and cannot be defended against a chain-of-custody review.

Capturing a video clip without a still-frame alongside
Signal in the archive

A crew captures a video clip with static bookends but does not export a still-frame next to the clip — reviewers must scrub through the clip to recover the surface reference.

Corrective move

Export a still-frame capture alongside each video clip. The still-frame carries the static surface reference (monument, segment ID, timestamp) in a single frame a reviewer can quote without scrubbing the video.

Recording critical sweep parameters on ambient audio alone
Signal in the archive

The audio track on a video clip carries the technician's verbal annotation of the sweep parameters, but street noise overlaps parts of the annotation.

Corrective move

Annotate the clip with a brief title card at the start — a static frame that names the segment ID, the sweep parameters, and the date. The visual frame audits the clip; the title card carries the parameters; the audio track is a side channel.

Knowledge check

Self-check — four questions on the media archive conventions, reveal as you go

A short authored self-check covering the closeout calls the audit reads against — in-frame identifiers, static bookends on a video clip, the five-field photo log, still-frame captures, and project-archive persistence.

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.

  1. 01

    A technician captures a photograph of a located segment and writes the photo number on the field sketch next to the segment, but does not embed a visible identifier (a chalkboard with the photo number and date, or a printed tag) in the frame of the photograph. Why is that omission a documentation problem?

  2. 02

    A crew captures a six-second video clip of a GPR pass across a target. The video shows the receiver trace sweeping across the conductor, but does not say which direction the pass was going, what the surface reference was, or what timestamp the sweep corresponds to. Why does a video clip without that metadata fail the deliverable test?

  3. 03

    A crew returns from a multi-day engagement with hundreds of photographs but no photo log. The photographers can describe what is in each photograph but cannot sort photographs by segment ID, by date, or by field crew, on demand. What is wrong with that handoff?

  4. 04

    A crew photographs the surface of a located segment from twenty different angles but only captions three of them. The reviewer trying to read the report at handover cannot tell which angle matches which finding. Why does the un-captioned photograph collection underweight the evidence?

Practice exam

Graded photo and video documentation 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 03 practice exam covers the in-frame identifier, the static bookends on a video clip, the five-field photo log, the still-frame-capture convention, the project-archive persistence rule, and the audio-versus-title-card discipline.

Start the Module 03 practice exam
Next module

Coming up on the Records & documentation track

Module 03 stops at the media archive. The final lesson walks the deliverable shape: how the archive feeds the contractor-actionable tier and the municipal-records tier separately, with the segment-ID namespace contract that binds the two.

Live
Module 04
Deliverable formats
The deliverable companion — how the photography and video archive feeds the contractor-actionable tier and the municipal-records tier separately, with the segment-ID namespace contract that binds the two.
Live
Module 01
ASCE 38 utility quality levels
The companion lesson on the ASCE 38 quality-level stamp on the closeout line, the audit artefacts per line, and the bounded-negative rewrite.
Live
Module 02
Field-sketch standards
The companion lesson on the per-block sketch convention — five artefacts per block, sign-off at the bottom, and the timestamp alignment to the equipment log.
Curriculum note

Module 03 ships with its own knowledge check and graded practice exam. The lessons build in sequence: ASCE 38 quality levels first, then the per-block field-sketch convention, then the photo and video archive, then the deliverable format split.

Back to the track landing