Opening: Treat every visit as a controlled activity
Owners and principals set the conditions under which staff may go to a site. They establish who authorizes a visit, what must be checked before travel, how hazards are handled, and how observations reach the project team. A policy cannot predict every condition at every site. It can make the decision path clear when conditions are uncertain or change.
The firm’s safety rules and the direction of qualified personnel govern. Client requirements, contractor rules, site-specific plans, and applicable laws may add requirements. Staff should follow the most restrictive applicable direction when requirements differ, and raise conflicts before entering the site.
A good policy makes three things clear: what the visit is for, who is responsible for the decisions, and what staff must do when the plan no longer fits the conditions. The steps below can form the core of a firm-wide standard. Project teams can then add details for the site and scope, plus the people involved.
1. Define the purpose and authorize the visit
Start with a defined purpose. “Go see the site” does not tell staff what to inspect, what information to collect, or what they are authorized to say. The request should identify the project, the reason for the visit, the expected deliverable, and the person directing the technical work.
Common purposes include documenting existing conditions, observing work for a limited scope, collecting measurements, locating visible features, or meeting with an owner or contractor. These activities carry different responsibilities. A site visit should not quietly expand into inspection, acceptance, certification, or construction direction unless that work is within the agreed scope and assigned authority.
The project manager or designated technical lead should approve the visit. The authorization should cover:
- The objective and limits of the visit.
- Who is attending and who is leading it.
- The date or work window, planned activities, and expected duration.
- The client contact and site representative.
- Required qualifications, training, personal protective equipment, and access permissions.
- How observations and hazards will be reported, including changes.
For work involving technical judgment, identify the licensed PE responsible for that work and the qualified person who will make field decisions. A staff member should not infer authority from job title or client preference. If a client asks an employee to approve a change or direct construction, the employee should refer the request to the designated project lead.
The owner’s policy should state when authorization is required. It may allow a project manager to approve routine visits within an approved scope, while requiring higher review for unfamiliar sites, unusual hazards, after-hours work, or work outside the contract. The approval path should be short enough to use under normal project pressure. A policy that is easy to bypass will not control the work.
Before departure, attendees should understand what is in scope and what is not. If the purpose is observation, for example, staff can document visible conditions and relay concerns through the established channel. They should not imply that the work has been exhaustively inspected or accepted. The project’s contract and scope, along with direction from the responsible PE, govern what the firm is engaged to do.
2. Confirm site access and local requirements
Permission to enter a property does not always mean permission to enter every area or perform every activity. Confirm access with the owner, client, contractor, or site operator, as appropriate. Ask who will meet the team, where to check in, what identification is needed, and which areas are off limits.
For active construction, coordinate with the contractor’s site representative before arriving. Confirm orientation or induction requirements, sign-in procedures, escort rules, work-hour restrictions, and any required site-specific safety plan. Determine whether photography, measurements, equipment use, or contact with workers requires separate approval. Do not assume that an earlier visit or another consultant’s access arrangement applies to the current visit.
Access planning also covers practical conditions. Identify the approved entrance, parking location, pedestrian route, and any restrictions on vehicles or equipment. Consider whether the site is remote, gated, subject to weather closures, or difficult to reach. If mobile service may be limited, plan how the team will check in and contact support.
The visit lead should make sure each attendee knows how to leave the site and where to gather if separated. On larger sites, agree on meeting points and a method to keep track of the team. Visitors should remain within authorized areas and follow instructions from the site operator. If access is denied or the required escort is unavailable, staff should pause and contact the project lead instead of finding another way in.
A firm policy can use a pre-visit access checklist, but it should not become a substitute for direct coordination. The checklist helps prompt the right questions. The site representative provides current instructions, and the team must follow them.
3. Plan for hazards before arrival
Hazard planning begins with the specific activities and conditions expected at the site. A generic list of protective equipment is not enough. The project lead and visit lead should consider the site environment, the work underway, the route, the planned observations, and the experience of the attendees.
Potential hazards can include traffic, moving equipment, excavations, unstable ground, water, overhead work, electrical systems, confined spaces, hazardous substances, poor air quality, temperature extremes, wildlife, or surfaces that are uneven or obstructed. The relevant hazards depend on the location and task. Staff should not enter a confined space, approach a suspected hazardous atmosphere, or perform a task requiring special training unless they have authorization and are qualified. They must also have the equipment required under the applicable safety program.
Use the employer’s safety procedures and any site-specific plan to identify controls. These may include orientation, an escort, restricted zones, protective clothing, a spotter, a defined travel route, or a change in timing. The project team should identify who provides required equipment and verify that each attendee knows how to use it. Personal protective equipment does not make an otherwise unauthorized or unsafe activity acceptable.
The visit lead should check the forecast and site status close to the visit. Rain can affect slopes and access roads. It can also change conditions in trenches or streams. Wind, heat, cold, lightning, smoke, or flooding may change what is safe or possible. A policy should define who can postpone or cancel a visit and how the team communicates that decision.
Before entry, hold a brief hazard discussion. Cover the intended route, known hazards, controls, emergency contacts, exit plan, and stop-work authority. Invite attendees to raise concerns. The person leading the visit should not treat silence as confirmation that everyone understands.
Every attendee should have authority to stop or leave work when they see an immediate hazard, feel unwell, lose required protective equipment, or cannot follow the agreed controls. The team should move to a safe location and notify the site contact and firm lead. No schedule or client request overrides employer safety rules or qualified direction.
4. Set a communications plan
A communications plan helps the firm know where the team is, who is responsible, and how concerns reach someone able to act. Set it before travel, with more detail for remote sites, solo travel, or work outside normal hours.
Identify the visit lead, the firm contact, the client or site contact, and the emergency contact process. Give attendees the site address, check-in instructions, and a reliable way to reach the lead and firm contact. If service is uncertain, agree on check-in points or an alternate method approved by the employer’s procedures.
For a team visit, designate one person to coordinate the group and speak with the site representative. This reduces conflicting requests and helps keep the visit within scope. Other attendees should know who to approach with questions, hazards, or requests for action. A team member who sees an urgent concern should raise it promptly, even if the lead is speaking with someone else.
Set check-in and check-out expectations. The firm contact should know when the team expects to arrive and leave, and what to do if the team misses a check-in. The response should follow firm procedures, account for the site’s communications limits, and avoid relying on a single person who may be unavailable. For longer visits, decide whether check-ins occur at set times or when the team reaches agreed locations.
Clarify what may be said on site. Staff can describe the purpose of the visit, identify observations within their assigned role, and explain that technical questions will go to the designated lead. They should avoid commitments on cost, schedule, design, acceptance, or scope changes unless authorized. If someone requests an immediate decision outside the attendee’s authority, record the request and refer it to the responsible project contact.
5. Make field records useful and clear
Field records should allow another qualified person to understand what the team did, what it observed, when it happened, and what needs follow-up. The record should be prompt, factual, and tied to the project. It may include field notes, photographs, sketches, measurements, a checklist, or a formal report, depending on the scope.
At the start of the record, capture the project name or identifier, location, date, time, attendees, weather or relevant site conditions, and the visit purpose. Note who provided access or information. Record the area covered and any limits, such as an inaccessible zone, a blocked route, or a condition the team could not verify.
Describe observations in neutral, specific language. Distinguish what the attendee directly saw or measured from what another person reported. For example, record a visible crack and its location rather than labeling it structurally significant unless a qualified person has made that assessment. Use sketches, marked-up plans, or photographs to show location and orientation. Include a scale or reference where appropriate and safe to do so.
Photographs should support the record, not replace it. Give them a date, location, and direction where the system allows. Add a subject description as well. Preserve original files according to firm procedures. Do not edit an image in a way that changes the apparent condition. If an image is annotated, retain the original and identify the annotation.
Record interruptions or deviations, along with any uncertainty. If the team changed routes, could not inspect a requested area, or stopped an activity, document why and who was notified. If a measurement is approximate or a location is uncertain, say so. Do not fill gaps with assumptions after leaving the site.
The project lead should set deadlines and storage locations for field records. Notes should be uploaded to the approved project system and shared with the people responsible for technical review and follow-up. Retention, quality review, and records access should follow the firm’s document control policy and contract obligations.
6. Protect privacy and sensitive information
A civil site visit can expose personal information, security details, proprietary operations, or images of people who did not expect to be included in a project record. Firm policy should set clear limits on what staff may capture, store, and share.
Take photographs only when they serve the authorized purpose and site rules permit them. Avoid capturing faces, license plates, private areas, computer screens, security devices, or unrelated property when those details are not needed. If a person appears incidentally in a necessary photograph, follow the client’s and employer’s rules for handling that image. Do not post site images or visit details to personal social media, messaging groups, or public portfolio pages without written authorization.
Use firm-approved devices and storage systems when required by policy. Avoid saving project images to personal cloud accounts or leaving them in a camera roll that syncs beyond firm control. Share records only with authorized project participants, and use approved channels for sensitive material. If a client has a confidentiality agreement or site-specific photography rule, confirm that attendees know it before entry.
Field notes should contain information needed for the project, not personal commentary about workers, residents, or clients. If an incident or sensitive matter arises, record facts relevant to the work and report it through the firm’s designated process. Do not circulate rumors or speculate about causes.
Owners should align site visit procedures with the firm’s privacy and cybersecurity policies. They should also align them with records retention and client confidentiality policies. A field team should know how to report a lost device, misdirected file, or unauthorized image promptly.
7. Respond when conditions change
A plan is based on information available before the visit. Conditions may differ when the team arrives, or change while staff are on site. The policy should make clear that the team pauses and reassesses when the actual conditions fall outside the authorization, hazard controls, or qualifications established for the visit.
Examples include an excavation that is unprotected, an access route that has become unstable, unexpected equipment movement, a newly restricted area, severe weather, a suspected release, or a request to inspect work beyond the agreed scope. The person who sees the change should alert the visit lead. The team should move away from immediate hazards, follow site emergency procedures where applicable, and contact the firm’s designated lead.
The visit lead should determine whether the activity can continue under existing controls, needs new authorization or qualified support, or should stop. Staff should not improvise technical controls or enter a restricted area to complete a checklist. If conditions affect the project’s technical assumptions, the responsible PE should decide what additional evaluation is needed.
Document the change, the time it was observed, the action taken, and who was notified. Tell the client or site representative what the team can state within its authority. Do not make a verbal commitment that conflicts with contract scope or technical direction. If the issue may require immediate action by the site operator, communicate the observed condition promptly through the agreed channel.
A stop or pause is a proper outcome when conditions change. The firm should support staff who use that authority in good faith and review the circumstances after the visit. The purpose of review is to improve planning and controls, not to pressure staff to continue when the plan no longer applies.
8. Close out the visit and follow up
A visit is not complete when the team leaves the site. Close-out confirms that people are accounted for, records are preserved, and observations reach the people responsible for decisions.
On departure, check out with the site representative if required. Notify the firm contact that the team has left or reached its next agreed location. If a check-in was missed, follow the established response process. Report any injury, near miss, exposure, property damage, security concern, or other incident through the firm’s procedures without delay.
The visit lead should organize the records and send a concise summary to the project lead. Include the purpose, areas visited, key observations, limitations, requests made, changed conditions, and outstanding actions. Separate facts from interpretation. Identify who owns each follow-up and the expected response path. Urgent concerns should be escalated directly instead of left for a routine report.
The responsible PE or other qualified reviewer should decide whether observations affect design, construction, schedule, or client commitments. They may request clarification, additional photographs, a return visit, or further analysis. Staff should not close out technical questions by assumption. Follow-up instructions should be documented in the project record.
After unusual or challenging visits, the owner or safety lead can review whether authorization, access, the hazard discussion, communications, and records worked as intended. Update firm procedures when recurring gaps appear. Keep the policy stable enough for staff to learn, while allowing project-specific plans to address real differences among sites.
Build a policy people can use
Firm-wide site visit policy works when it connects planning to authority. Owners set minimum requirements and name responsible roles. Project leads define the visit scope and technical direction. Visit leads coordinate the team and respond to field conditions. Each attendee follows safety requirements, records what they observe, and speaks up when the plan no longer fits.
A short standard checklist can prompt authorization, access, hazards, communications, records, privacy, and follow-up. Keep the checklist tied to a clear decision path. Staff should know whom to contact, when to pause, and where the record belongs. Review the procedure with new employees and revisit it after significant changes to the firm’s work or safety program.
Related CivilEngineers.com resources
For related reference material, visit CivilEngineers.com calculators, the civil engineering glossary, and the CivilEngineers.com Q&A.
General education only, not engineering, legal, tax or investment advice. Licensed PE judgment and local codes govern.
