Quick answer
Use your employer’s required record system, then make every observation traceable: identify the project, recorder, time and location; distinguish facts from interpretation; and connect each photograph to a unique ID and log entry. Preserve corrections and deliver the notes, photos and unresolved questions together. These principles align with EPA field-record guidance and USGS data-management guidance. (epa.gov)
This guide is for beginning field technicians and crew leaders working with surveying, mapping or environmental records. The examples below are organizational aids—not substitutes for approved forms, sampling records, survey procedures or chain-of-custody documentation.
1. Confirm the required system before creating your own
Before departure, ask your supervisor:
- Which notebook, form or application is the official record?
- Which project, station and equipment identifiers must we use?
- Who records observations, reviews them and receives the handoff?
- Are photography and location recording permitted?
- Where must records be stored, and who may access them?
- What is the approved process for correcting or adding information?
Write down the answers or reference the applicable procedure. USGS data-management planning guidance emphasizes defining responsibilities and planning for collection, preservation, sharing and sensitive information before acquisition begins. (usgs.gov)
Practical check: Ask to see an accepted example from a comparable task. Compare its required fields with your planned page and photo log.
Do not assume that a paper notebook is always required—or that a personal note-taking app is acceptable. EPA’s published logbook procedure allows electronic original observations within its own system, while explicitly warning that the procedure may not apply directly to other organizations. Your project’s rules determine the permitted format. (epa.gov)
2. Make time and location understandable without guesswork
Use the project’s approved date and time convention consistently. If you are helping establish one, an unambiguous date such as 2026-09-14 is preferable to an unexplained 09/14/26. USGS identifies ISO 8601 as a date/time standard and provides examples that include a UTC offset. (usgs.gov)
For a simple daily page, a header such as “All times local, UTC−04:00” can explain subsequent entries—if that format is approved. Record the observation time separately from a later entry time when necessary; do not make a delayed entry look contemporaneous.
For location, use the authorized station or feature ID plus a useful reference. “Near the gate” is weak. “Station S03, east side of the access gate shown on site sketch SK01” tells a colleague which reference to consult.
When coordinates are required, include or reference their coordinate system, datum and units. USGS guidance explains the importance of documenting datum information for horizontal and vertical coordinates. Do not guess a missing datum or treat unexplained coordinates as ready for mapping. (usgs.gov)
Practical check: Can someone identify the correct place and interpret the timestamp using only the record and its referenced documents?
3. Separate observations from explanations
Write what you observed before writing what you think caused it. EPA field-documentation guidance calls for factual, detailed and objective notebook entries. (nepis.epa.gov)
Compare these fictional entries:
| Unclear entry | Clearer entry |
|---|---|
| “Drain blocked.” | “Leaves and twigs visible across part of the inlet opening. No flow assessment performed.” |
| “Bad GPS.” | “Location capture not completed. Application displayed an error; error text recorded in equipment log.” |
| “Same as yesterday.” | “Today’s condition photographed as P001; previous visit not compared in the field.” |
If your procedure permits interpretation, label it separately: “Possible explanation—requires review.” If it does not, keep the record to observations and raise the question through the approved review process.
Use deliberate status terms instead of unexplained blanks. “Not measured,” “not observed” and “not applicable” mean different things; agree on their use with the project lead. USGS data standards guidance includes documenting conventions for missing or unavailable values. (usgs.gov)
Common mistake: Reporting an estimate as a measurement. If estimating is permitted, label the estimate and its basis. Otherwise, record that the quantity was not measured.
4. Connect photographs to notes with unique IDs
Give each photograph an identifier that is unique within the agreed project scope. A proposed pattern is:
DEMO01_20260914_CAM01_P001
Here, DEMO01 identifies the fictional project, 20260914 the date, CAM01 the device and P001 the sequence. The device component helps distinguish photographs from different crew cameras. This is an example, not an agency-mandated naming scheme.
For each image, log:
- Photo ID and original filename.
- Capture date, time and time basis.
- Photographer.
- Station or feature reference.
- Subject and direction faced.
- Related notebook page or electronic record ID.
EPA inspector-training material specifically includes date, time, photo number, direction and comments in photographic documentation. (archive.epa.gov)
Write the photo ID beside the relevant observation. In the photo log, point back to that observation. This creates a two-way connection rather than leaving the reader to infer which image belongs to which note.
For an unfamiliar feature, consider an overview followed by a detail image, where photography is permitted. Describe their relationship explicitly.
Practical check: Match the actual image to its log description. EPA photographic guidance includes checking that photographs and logs correspond. A descriptive filename alone does not complete that check. (nepis.epa.gov)
5. Worked example: one note page and its matching photo log
The following example is entirely fictional. Names, project identifiers, times and observations are invented solely to demonstrate the format. No real location, measurement or field result is represented.
Fictional field-note page
Project: DEMO01 — training observation visit
Date: 2026-09-14
Recorder: Alex Example (AE)
Record: Notebook NB01, page 12
Time basis: Local time, UTC−04:00
Location reference: Approved training sketch SK01
09:10 — S03, east side of access gate on SK01.
Leaves and twigs visible across part of inlet opening.
Photographs: DEMO01_20260914_CAM01_P001 and P002.
No flow assessment or dimensions recorded.
Question for supervisor: Is a follow-up inspection required?
09:18 — S04, marked path junction on SK01.
Overview photograph:
DEMO01_20260914_CAM01_P003.
No condition assessment performed.
16:05 — Daily review.
Photo IDs checked against log and image contents.
S03 follow-up question remains open.
Prepared by AE for supervisor review.
Matching fictional photo log
All photographs below were taken by Alex Example on September 14, 2026, using local time, UTC−04:00. All refer to NB01, page 12.
| Photo ID | Original file | Time | Reference | Subject and direction |
|---|---|---|---|---|
DEMO01_20260914_CAM01_P001 |
IMG_4101.JPG |
09:11 | S03; SK01 | Overview of inlet beside gate; facing west |
DEMO01_20260914_CAM01_P002 |
IMG_4102.JPG |
09:12 | S03; SK01 | Detail of leaves and twigs at inlet; facing west |
DEMO01_20260914_CAM01_P003 |
IMG_4103.JPG |
09:19 | S04; SK01 | Overview of marked path junction; facing north |
The example deliberately records limits: no dimensions, no flow assessment and no condition assessment at S04. It also leaves the follow-up question unresolved rather than inventing a conclusion.
Try the system yourself: start with P002, find its original file, then locate the associated note and sketch reference. If any connection depends on memory, add the missing reference.
6. Correct mistakes without hiding the original entry
Follow the approved correction procedure. In EPA’s published logbook procedure, a handwritten correction uses a single strike-through that leaves the original readable, with the correction dated and initialed. Electronic corrections are documented with the change, date and person’s initials. (epa.gov)
For an approved paper format, a fictional correction might look like:
Station: ~~S02~~ S03 — corrected AE, 2026-09-14
Do not erase the old entry, obscure it with correction fluid or rewrite the page merely to make it cleaner.
For a digital record, use the application’s approved audit trail or correction mechanism. If a controlled spreadsheet uses correction comments, follow that process rather than silently overwriting values.
A late addition should identify when it was added and what it concerns. Ask how your system labels late entries; never backdate one to suggest it was written at the observation time.
7. Use consistent filenames and protect sensitive information
If the project permits you to propose a folder structure, keep it small and explain it:
DEMO01/
2026-09-14/
notes/
photos-original/
photo-log/
handoff/
This is an organizational example, not a required layout. USGS recommends logical organization, consistent names and formats, clear abbreviations and version control. A short README can define identifiers, time conventions and the relationship between notes and photographs. (usgs.gov)
If files are renamed, retain the original-to-project-name relationship in the log or approved system. Keep report versions distinguishable—for example, handoff_v01—rather than accumulating ambiguous files named “final.”
Use only employer-approved devices, accounts and storage locations. Before collecting or sharing images, ask about people, identifying details, private property, confidential infrastructure and sensitive species locations.
USGS guidance recognizes that disclosure of sensitive data can cause harm. It also recommends making restrictions or generalizations in a distribution copy, documenting them and preserving the stored record. Do not delete an original coordinate or crop an original image to create a public-safe version; request the approved derivative workflow. (usgs.gov)
8. Close the day with a checked handoff
Make the handoff a defined package, not a message saying “photos uploaded.”
A proposed closing checklist is:
- Notes have project, recorder and page or record identifiers.
- Every referenced photo exists and has a matching log entry.
- Location references and abbreviations are explained.
- Missing work, equipment issues and open questions are identified.
- Files are in the approved location.
- Required backup and transfer checks are complete.
- The recipient knows what needs review and where to find it.
For transfer checks, follow your organization’s process. USGS recommends backing up metadata with data, checking copied files for opening errors and using checksums to verify identical copies where appropriate. Do not delete source files merely because an upload appears finished. (usgs.gov)
A useful fictional handoff message is:
“DEMO01 records for September 14 are in the approved project folder: NB01 page 12, three original photos and the matching photo log. S03 follow-up remains unresolved. Please review that question before the next visit.”
Finally, ask a colleague to retrieve one observation and its photo without your explanation. Treat any missing connection as a review issue to resolve through the approved process. USGS identifies documented quality checks and supporting field notes as part of sound data management. (usgs.gov)