Prepare for a productive civil project site visit

Define what the visit should produce

Start with the record you need afterward. 'Visit the drainage project' describes an activity but gives little direction. 'Document the delivery records available for inlet I-04 and identify unresolved drawing questions' identifies a useful outcome. Write two or three questions that the visit can realistically address within your assigned role.

Agree on who needs the information and when. FHWA's preparation guidance supports setting an objective before gathering information; this lesson applies that idea to a small documentation task.

Build a small, traceable reference packet

Gather the relevant drawing sheets, prior observations, open questions, and records connected to your objective. List each document's identifier, revision, issue date, and storage location. Confirm the applicable version through the project's document process.

Open the files before the visit, including any approved offline copies. Label a missing reference as missing instead of substituting a similar document from another project. Preserve the original source location when making working copies.

Coordinate the people and the questions

Confirm the visit with the designated project contact, including the meeting location, expected timing, and people who can help locate the records. Share your documentation questions beforehand so the relevant recordkeeper can prepare. Separate the person providing information from the person authorized to interpret or approve it.

Ask the site contact about the site's access and orientation arrangements and follow the established process. This preparation exercise does not grant site access or provide safety instructions. If the intended activity or responsible contact changes, revise the documentation plan rather than silently expanding your assignment.

Set up the record before filling it

Prepare a blank note with the project identifier, author, visit purpose, date, locations, reference list, and space for follow-up. Leave observation fields blank until you have evidence. Use the team's existing record identifiers rather than creating a parallel naming system.

Plan how photos and document references will connect to the note. Check that the chosen recording method can save and reopen a sample file. A successful screen entry is not the same as a retrievable record. Keep preparation notes separate from observations made during the visit.

Reserve time for the handoff

Before the visit ends, compare your questions with the information collected. Mark each question answered, partly answered, or unresolved. Record why information is missing and who will obtain it.

Afterward, confirm that references open, captions identify their locations, and the intended recipient can find the record. Send a concise handoff through the approved project channel. Preserve the visit's actual scope: an unvisited area stays unvisited. Caltrans' records chapter offers an agency-specific example of organizing documents for later retrieval.

Fictional training example

Worked example: Willow Run inlet records

Fictional training scenario. Coordinator Maya is asked to visit project WR-08 before a materials meeting. She agrees that the outcome is a delivery-record summary for inlet I-04, not a material acceptance decision. Her packet index lists plan C-110 revision 3, receiving log RL-17, and open request RFI-009. The document controller confirms the drawing reference; the supplier's supporting record remains outstanding.

Maya prepares note SV-006 with those references and an empty observation section. At the visit, she obtains the available delivery identifiers and records the missing supplier document as an action for the materials coordinator. Her handoff states what was reviewed, links the records, and preserves the pending status. She does not describe the entire drainage system as inspected.

Try it yourself · Fictional scenario

Practice: turn a vague request into a visit plan

Fictional scenario. A manager writes: 'Please visit Birch Street tomorrow and sort out the pipe paperwork.' You have receiving log RL-12, two drawing versions, and an email mentioning a missing ticket. The intended report recipient and the applicable drawing version have not been confirmed.

Your task

Write a specific documentation objective without promising an acceptance decision.
Name three preparation gaps and the roles you would contact.
Draft one sentence describing the handoff you intend to produce.

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

Reveal a sample response

An appropriate objective is to identify the delivery records associated with the stated pipe delivery and list unresolved references. Ask the manager to confirm the recipient and timing, the document controller to confirm the drawing reference, and the materials recordkeeper to locate the ticket. Arrange the visit through the designated site contact.

The planned handoff is a referenced record summary showing documents reviewed, missing information, and assigned follow-up. It will describe the visit's actual scope and leave technical review with the authorized role.

Keep in mind: A useful visit begins with a question and ends with a traceable handoff.

Your practical checklist

The visit has specific questions and an intended recipient.
My role and the planned scope are clear.
References include versions, locations, and known gaps.
The project contact has confirmed visit arrangements.
The recording method can save and reopen a record.
Time is reserved for unresolved questions and handoff.