How to Measure Land Survey Field Crew Readiness: Practical Metrics

Metrics for land survey field crew readiness should help small land-surveying firms coordinating field crews and office deliverables decide what to change next. Avoid universal benchmarks: volume, service model, and exception mix differ. Establish a baseline from your own records and compare the process against itself.

Three useful measures

| Metric | Simple calculation | Decision it supports | |---|---|---| | Ready-by-dispatch rate | assignments released by dispatch / assignments scheduled | staff research | | Field-stop rate | assignments stopped for missing office input / assignments started | improve packet | | Wrong-version rate | assignments using superseded scope or file / assignments released | strengthen change handoff |

Capture the minimum viable data

The calculations only work if the operating record consistently includes Client project parcel and task, Scope deliverable and due date, Deeds plats control and prior survey files, Coordinate system data files and version, Access permission contact and timing, Hazards utility traffic and site conditions, Crew roles equipment and calibration, Office reviewer release and crew acknowledgment. Define when the clock starts and stops. Decide whether paused or waiting time remains inside cycle time, and keep that rule stable across the comparison period.

Segment before interpreting

Separate normal work from exception-heavy work. At minimum, segment by owner, workflow stage, and closed reason. Averages can hide a small blocked queue that creates most of the follow-up burden.

Review decisions, not dashboard colors

For each metric, write an action threshold in plain language. Examples:

• If Ready-by-dispatch rate changes materially, use it to staff research.
• If Field-stop rate changes materially, use it to improve packet.
• If Wrong-version rate changes materially, use it to strengthen change handoff.

Do not automate a response until a person has reviewed several examples. A high number can indicate a broken process, difficult work, or a data-definition change.

Validate each calculation manually

Choose one closed record and calculate every metric by hand from its timestamps and statuses. Save the numerator, denominator, exclusions, and timezone rule beside the definition. Then test an abandoned record, a reopened record, and a record that spent time waiting. If two people produce different answers, the metric is not ready for a dashboard. Fix the event definitions before collecting more data.

Repeat that spot check whenever a workflow status, integration, or reporting period changes.

A four-week measurement loop

Week one defines fields and baselines. Week two fixes missing data. Week three tests one workflow change. Week four compares the same metric definitions and reviews exceptions. Keep the change only if it improves the intended outcome without shifting work somewhere invisible.

Next step

Explore the Survey Field Readiness workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Survey Deliverable Release.