Timedora

Reliable Field Records

A practical guide to documenting, checking, correcting, and organizing field measurements so they remain interpretable and verifiable.

Documenting Measurements in the Field

Documenting Measurements in the Field

A measurement is useful only when someone can tell what it describes and how it was obtained. Record notes at the site using the project’s standard form, and connect each value to its identity, time, place, reference, method, units, and quality status. This helps a later reader check the observation and interpret it without guessing.

Include the project and site identifiers, date, time and time zone, observers, and visit number as applicable. Describe the measurement location with coordinates and their coordinate system and , and identify the measurement point or benchmark. For elevations, specify the vertical or local reference and any offset used. Record the quantity measured, value, units, method, instrument or equipment ID, and relevant setup or environmental conditions.

Keep quality information with the individual measurement: note calibration or check results, repeat readings, uncertainty or estimated status, equipment problems, and departures from the planned procedure. Record site conditions—such as weather, obstacles, or ground conditions—that may help explain an unusual value. Mark an estimated, qualified, or unusual value alongside the value and explain its status. Use consistent units and enough detail to distinguish an elevation from a height relative to a local benchmark.

Add spatial context and make readings checkable

A labeled field sketch shows key site features and relationships among measurement points. Include a title, date, orientation or north arrow, labels, reference points, and dimensions. Say whether it is to scale; if not, label it not to scale. Use identifiers that match the notes and measurement log. A sketch complements written notes; it does not replace the recorded measurements.

A structured log makes repeated readings easier to compare. For example, the source’s entry for point P1 records a reading of 102.438 m at 09:15, using level instrument L2, with project benchmark BM1 as the reference and a repeat reading of 102.439 m. The details alongside the number let a reader identify the method and reference and see the repeat value. Follow the project’s required precision and recording conventions; do not imply more precision than the instrument or method supports.

Example measurement log entry
Point and timeMeasurementMethod or instrumentReference and check
P1, 09:15102.438 mLevel, instrument L2Project benchmark BM1; repeat: 102.439 m
Source example: a measurement log entry keeps the method, reference, time, units, and repeat reading alongside the result.

Checking and Correcting Records

Checking and Correcting Records

(QA) establishes procedures for obtaining reliable data. (QC) consists of checks that help detect problems in particular observations or records. In practice, follow the project’s procedures and check records in the field when practical, then review them promptly afterward while conditions and decisions are still easy to recall.

Use a systematic review:

  1. Check completeness. Confirm that required fields, units, identifiers, dates, and references are present.

  2. Check equipment and method. Verify that the equipment was suitable and checked or calibrated as required. Make sure the instrument ID and method are recorded.

  3. Compare independent or repeat checks. Compare repeated readings, closures, or other checks with the project’s acceptance criteria. If values differ, investigate the difference rather than silently selecting one.

  4. Recheck calculations and transcription. Review arithmetic, sign conventions, unit conversions, and transfers from field sheets to electronic records.

  5. Check plausibility and traceability. Consider whether values make sense in the site and measurement context. Confirm that each final value can be traced to its original observation and any correction or adjustment.

If an error is found, preserve the original record and make the correction traceable under project procedures. For electronic records, use an or revision history where available. Record failed checks, corrective actions, and unresolved limitations. An unexpected value should not be concealed just because it looks unusual; retain it and document the issue so it can be assessed in context.

Organizing Records for Later Use

Organizing Records for Later Use

Records are easier to locate and verify when projects, sites, visits, and measurements have consistent identifiers. Use those identifiers to link field notes, sketches, measurement logs, calibration records, photographs, and related files. A predictable folder structure, clear filenames containing dates and site IDs, and a short index describing file contents and versions help later users find the relevant material.

Keep original field records separate from processed or corrected datasets. Use access and backup practices appropriate to the project so that records remain available without confusing original observations with later work.

After fieldwork, review and enter data promptly. Compare digital entries against the original notes, retaining units, references, and any qualifiers or comments needed to interpret questionable values. A second-person review can help catch omissions and transcription errors that the person who collected the data may overlook.

  • : A contemporaneous record of observations and the context needed to interpret them.

  • : A consistent label used to distinguish and link a project, site, visit, measurement, or file.