A fieldwork check-in plan for site visits and outdoor surveys
A fieldwork check-in plan should identify the approved activity, the people and sites involved, the contact schedule, the person receiving updates and the response to a missed message. Build it within your institution’s field safety process and have the responsible supervisor review it. A personal location app may supply extra context, but it does not approve solo work, assess site hazards or replace the institution’s communication requirements.
Place communication inside the approved field plan
Start with the institution’s own process for planning and approving field activity. A short ecology survey or a visit to retrieve equipment may still fall within that process. Ask the supervisor which plan covers the work, whether the proposed staffing is appropriate and what must be reviewed before departure. A phone-based return reminder does not answer those questions.
Stanford’s published guidance describes a field safety plan that includes hazards, communication, emergency procedures and training. It permits preparation to be delegated while retaining supervisory responsibility for review and implementation. That is an example of an institutional process, not a policy this page can impose on another university or employer. Use the current requirements that actually apply to your project.
Treat the worksheet below as discussion material for the communication section. It is not a complete risk assessment, permit or approval form. The outing-plan tool can help collect a personal route note, but a short general-purpose template should not displace the institution’s required document or omit specialist activity controls.
Turn research site codes into usable location information
A label such as “plot B” may be sufficient for a dataset and useless to the person receiving an overdue call. Give that person an authorized map or location reference, the access point and the intended sequence of sites. Explain how field labels match the map. If there are several similar names, use the exact form that appears in the approved itinerary.
Keep the location note useful without distributing sensitive research information unnecessarily. A contact may need to know the access route and the team’s current site, while public readers do not need the exact coordinates of a protected habitat or private property. Follow institutional data-handling and land-access arrangements when deciding who can receive which details.
The trip-plan guide explains how to make route information readable. For fieldwork, add the relevant project reference and the approved location key. Keep the current copy available to the designated contact before the team leaves. A map stored only on a researcher’s laptop in the field cannot help that contact if it becomes inaccessible.
Specify the message and how receipt is confirmed
Define what a routine update needs to say. For example, a message might identify the team, confirm the agreed people are accounted for, give the current approved site and state the next expected contact. Use your project’s chosen format. Avoid a bare “all good” if the recipient still cannot tell which team or stage it refers to.
Virginia Tech’s field-safety guidance calls for designated contacts, communication schedules, missed-contact procedures and alternate methods. It also addresses potential mobile-service interruptions. Those elements are useful prompts for discussion with your supervisor. The actual interval should be chosen through the project’s planning process; there is no single appropriate check-in frequency for all surveys or site visits.
Decide whether a reply, a documented system state or another agreed signal establishes receipt. A locally saved message or observation record is not proof that the outside contact has received a safety update. Rehearse the arrangement using the devices and authorized channels intended for the trip, including how a delayed or failed message will be recognized.
| Plan element | Question to settle before departure |
|---|---|
| Approved scope | Which activity, people and locations does the current plan cover? |
| Recipient | Who has accepted the role during each field period? |
| Message format | Which team, site, status and next-contact details must be included? |
| Receipt | What confirms that the message reached the responsible person? |
| Fallback | What approved method applies if the primary channel fails? |
| Missed check-in | Which named person begins the documented response? |
| Completion | Does the plan close at site exit, base or another defined endpoint? |
Keep changes under the same review process
An extra sampling location or a different pickup arrangement can change the communication assumptions even when the scientific task looks similar. Ask how to handle that change under the approved process. Tell the responsible people which version of the itinerary is current. Do not rely on an informal note in a research chat that the designated outside contact does not read.
Stanford’s published plan guidance explicitly addresses updates when locations or participants change. Your institution may specify its own review triggers. Identify those triggers before departure so a researcher is not left deciding, under time pressure, whether a changed team or route still fits the plan. Preserve a clear record of approved changes and when contacts received them.
If the person receiving updates becomes unavailable, transfer the current plan and any outstanding check-ins through an accepted handoff. The group contact handoff guide describes the communication problem. For institutional work, adapt it to the designated roles and emergency chain rather than bypassing them with a personal substitute.
Assess a personal app against the actual requirement
List the required function before evaluating an app: a shared position, scheduled contact, a two-way exchange or a documented institutional response. Those are different capabilities. The outdoor check-in app comparison can help you ask precise questions, but it is not an approved-products list for your employer or university.
Holler can give a Guardian a browser link without requiring an account. The link reports a phone’s position and update time; it does not maintain a field team roster or confirm that every member is with that phone. Obtain the necessary agreement before sharing participant or sensitive site information through any personal service.
Holler’s return setting is a single deadline up to 23 hours ahead, subject to share expiry, rather than a recurring fieldwork schedule. It must be saved and verified while connected. Fresh location updates need internet access and phone-browser tracking requires the page open with the screen on. Email and push delivery can fail or be delayed. These limits may leave a project requirement unmet, which the supervisor must resolve before relying on the arrangement.
Define the response and the final checkout
University of California, Santa Barbara’s field-plan guidance lists communication and check-in procedures alongside emergency contacts, response arrangements and travel information. Keep those parts connected in your own plan. The recipient should know where to find the current itinerary and which approved response follows a missed update. A timer alone does not supply that procedure.
When a check-in is missed, carry out the documented response and use known facts. Separate the last direct message from the latest map point, including timestamps. The dead-phone answer explains why an old shared location cannot establish someone’s present condition. If there is evidence of an emergency, seek emergency help promptly; do not wait for a routine app alert to authorize action.
Finish with a received checkout that accounts for the people and endpoint covered by the plan. Uploading survey data, submitting time records or returning a vehicle key may be useful administrative events, but they should not silently substitute for the agreed message. Record any communication problem through the institution’s review process so the next field period uses the corrected arrangement.
Questions people ask
How often should field researchers check in?
The frequency belongs in the approved plan and should reflect the activity, site, available communication and institutional requirements. Do not copy a universal interval from an app or general article. Also agree the missed-contact response and confirm that the recipient is available.
Does a check-in app make solo fieldwork acceptable?
No. Solo-work decisions belong to the responsible institution and supervisor through their planning process. A location link or return deadline does not remove the need for appropriate staffing, training, site assessment and communication equipment.
Can my family member be the only contact?
Ask the institution which contacts and roles are required. A personal contact may complement that structure, but should not replace an institutional role without approval. Everyone involved should know which plan they hold and which part of the response they have accepted.
Is this a complete fieldwork safety-plan template?
No. It focuses on the communication section and questions to resolve with the responsible supervisor. Use the institution’s full planning process for hazards, training, permissions, emergency procedures and other requirements that apply to the work.
Keep reading
Questions people ask about this
Sources: Stanford EH&S: assemble your field safety plan, Virginia Tech EH&S: field safety plan and communications, UC Santa Barbara EH&S: elements of a field safety plan.