Write field notes that someone else can follow

Give the next reader a starting point

A field note should work for a teammate who was not beside you. Start with the project identifier, observation date and time, your name or role, and a precise location. Use the project's stationing, structure numbers, or agreed area names consistently. A note saying 'drainage work continued' leaves the next reader searching for the activity and its extent.

Define the visit's limits. 'Observed inlet I-07 from the north approach between 10:10 and 10:30' describes a bounded observation, not every operation all day. Include the context your reader needs; leave out unrelated activity.

Use fact, source, and action

Fact: describe the particular activity or condition you observed. Source: identify the photo, drawing revision, delivery record, or named communication supporting the entry. Action: record the question or follow-up, the responsible role, and its current status. An action may be 'awaiting response'; it does not need an invented resolution.

Adapt the drafting aid to the task. Some entries need no follow-up; others need several owners. Make clear what you know and what needs attention.

Observed: 'Two pipe sections visible at staging area A.'
Reported: 'Foreman expects four more tomorrow; delivery not verified.'
Action: 'Materials coordinator to reconcile DT-228 with the receiving log.'

Make uncertainty specific

A useful limitation names the missing information. Compare 'details unclear' with 'ticket number unreadable in the supplied image; clearer copy requested.' The second statement gives the next person a defined task. Avoid filling gaps with likely values just to make a form look complete.

A ticket quantity, an observed count, and a reported installed quantity describe different evidence. When accounts differ, retain both references and identify the question instead of blending them into one total. Technical conclusions follow the project's assigned review process.

Keep the timeline understandable

Make the entry during the visit or promptly afterward. FHWA's inspection guidance emphasizes timely observations and a clear distinction between facts and opinions. If information arrives later, identify the later entry and its source instead of making it appear contemporaneous.

Distinguish observation, reporting, and entry times when they differ. Follow your project's correction procedure. A clarified location or corrected transcription should leave the reader able to understand the change, its author, and its basis.

Read the entry as a handoff

Use one topic per entry when activities need different follow-ups. Link supporting files through stable identifiers. Read the entry without its attachments: can you identify the location, understand the observation, and find the next action? Add missing context while the memory is fresh.

Then open the evidence. A filename is little help if the file is missing or inaccessible. Check that outstanding actions identify an owner and next review point. Finishing the report does not complete the tasks inside it.

Fictional training example

Worked example: Maple Creek drainage renewal

Fictional training scenario. On project MC-04, an inspector records: '16 October, 10:20 a.m., inlet I-07, north approach. Two delivered pipe sections observed in staging area A. Photo PH-014 shows their location. Delivery record DT-228 lists these two sections. Foreman said four additional sections are expected tomorrow; that delivery has not been verified.'

The follow-up reads: 'Materials coordinator to reconcile today's delivery record with the receiving log. Status: pending. Reference daily report DR-016.' This identifies a documentation task without declaring material acceptance or guessing tomorrow's progress.

At 2:15 p.m., a clearer receipt arrives. The inspector adds a dated update linking the replacement scan and describing what it clarifies. The morning observation stays tied to 10:20 a.m.; the later document does not turn the inspector into a witness to a delivery they did not see.

Try it yourself · Fictional scenario

Practice: repair a vague daily entry

Fictional exercise. Your draft says: 'Culvert work done. Four units delivered. Sam says all ready.' You visited staging area B on project MC-04 at 11:05 a.m. and saw two units. Receipt DT-231 lists four. Foreman Sam reported that two were moved before your visit. You have not checked their destination. Photo PH-019 shows the two units you observed.

Your task

Rewrite the observation in two or three sentences, preserving its limits.
Identify the reported information and the unanswered question.
Draft a follow-up for the materials coordinator without declaring installation or acceptance.

Use your own notes or a sheet of paper. Compare your response with the example below when you are ready.

Reveal a sample response

'MC-04, staging area B, 11:05 a.m.: two units observed; see PH-019. DT-231 lists four units delivered. Foreman Sam reported that two units were moved before this visit; their destination has not been verified.'

'Materials coordinator to reconcile DT-231 with the receiving and movement records. Status: pending. Confirm the destination and record the supporting reference at the next handoff.' The exercise provides no basis for 'work done' or 'all ready,' so those conclusions are omitted.

Keep in mind: A useful note can contain uncertainty as long as the evidence and next question are clear.

Your practical checklist

Project, author, observation time, and location are identifiable.
The scope and limits of the visit are clear.
Observed and reported information are distinguished.
Counts and quantities retain their source and units.
Evidence opens, and later additions have clear chronology.
Each unresolved follow-up has an owner and honest status.