Define the inspection record and establish its references

01.01

Start with the decision the record will support

A highway inspection record often outlives the activity it describes. A drainage structure may be covered, a delivery label removed, or the original observer reassigned. The useful record therefore connects a particular activity to a location, time, source requirement, observation, and unresolved question. This course develops that connection through an original fictional road-drainage case. It teaches documentation reasoning, not construction methods or technical acceptance criteria.

Before visiting the work, identify what your assignment requires you to observe or collect and who will use the result. 'Review drainage work' is too broad for the case. 'Record the delivery evidence and unresolved drawing references for inlet I-07 during the morning visit' identifies an achievable documentation product. It does not imply a review of every drainage asset, an approval of the material, or authority to direct the contractor.

01.02

Keep three kinds of information distinct

A requirement reference tells the reader where to find the applicable instruction or criterion. An observation describes what a person saw, measured, read, or received. A disposition records a decision made through the project's assigned process. These can appear together, but one should not silently stand in for another. A specification reference alone does not prove performance; a photograph alone does not establish acceptance.

Use a reference register to identify the document, revision, issue date, location, and reason for including it. Confirm applicability through the project's established document process. Do not invent a universal order of precedence when sources conflict. The contract and responsible project personnel govern that question. In this course, document disagreements become explicit clarification tasks. FHWA's reporting guidance provides background on factual observations and supporting records; the case methods here are original exercises.

01.03

Read the fictional North Run reference packet

The entire NR-26 North Run Road drainage rehabilitation case is invented for training. Its documents are not actual design instructions, specifications, or approvals. The observation area includes inlet I-07 at station 18+20 and a separate culvert C-02. These identifiers distinguish assets; they are not design criteria. Keep the packet available for later modules.

• D-201, drainage plan revision B, issued 12 October: the structure at station 18+20 is labeled I-07.
• D-202, drainage schedule revision A, issued 28 September: the entry for station 18+20 is labeled I-17. The packet provides no explanation for the difference.
• SP-DR-01, fictional documentation note revision 0: the case register is to connect receiving entries to receipt identifiers, material descriptions, quantities with units, and available lot references. It supplies no technical acceptance limits.
• S-014 revision 2, material submission issued 14 October: a review-response cover exists, but the packet contains no material acceptance or substitution decision.
• DT-448, supplier ticket dated 19 October at 08:35: eight precast drainage components, lot L-72, destination staging area B.
• MD-031, supplied material document: identifies lot L-27. Its relationship to DT-448 is unresolved.
• DR-019, observer Iris's draft for 19 October: visit from 09:00 to 09:25; six components observed at staging area B. At 09:10 foreman Owen reports two were moved earlier to stockpile C. Iris did not observe that movement.
• PH-101, context image: inlet I-07 and its approach. PH-102, close-up received from Leah: location and capture time unconfirmed. Both were initially associated with observation OBS-019.

01.04

Identify roles before assigning conclusions

For the exercise, Iris records observations, the document coordinator manages references, the materials reviewer evaluates material documentation within the assigned process, and the designated drawing responder addresses the label discrepancy. These are case roles, not universal job authorities. On a real project, determine who holds each responsibility and how instructions or decisions are recorded.

Record a source without upgrading it. Attribute the foreman's account as reported information and log a review cover as received. Neither becomes an observation or approval merely by appearing in your report. If authority or scope is unclear, preserve the communication and identify the clarification needed.

01.05

Design the handoff before collecting more records

A compact evidence map can begin with columns for question, location, source, current finding, missing information, and responsible role. Start with the questions the packet raises: which structure identifier applies; why the observed and ticketed counts differ; which lot document applies; and where PH-102 was captured. These questions need different evidence and may close at different times.

Plan how the next reader will retrieve the originals from the authorized project location. Test the links and keep revisions visible. Later modules add information so you can update the evidence map without rewriting what was known earlier.