Every survey crew has a story about a bad setup that went undetected too long. The instrument height that was estimated instead of measured. The benchmark that was misidentified in the field. The grade stake set off a control point that hadn't been checked since the last site visit. The job that had to be redone because nobody ran a check shot before moving on.
Check shots don't prevent every error. But they catch most blunders at the moment they're cheapest to fix — while the instrument is still set up and a re-observation takes seconds instead of a return trip.
What a Check Shot Is
A check shot is an independent observation to a known point — a benchmark, a control point, or a previously established elevation — taken to verify that the current setup is producing correct results before you continue working. It's not a new measurement of something unknown. It's a deliberate verification of something you already know, used to confirm that what you're about to record is trustworthy.
The key word is independent. An observation that simply repeats the measurement used to establish the setup isn't a check — it's a confirmation of the same potential error. A genuine check shot goes to a different known point and asks: does what I'm seeing agree with what I should see?
Check Shots as Blunder Detection
Most survey errors in the field aren't systematic — they're blunders. A misread rod graduation. A wrong instrument height. A setup on the wrong point. An elevation recorded from memory instead of direct observation. These don't accumulate gradually the way systematic errors do. They hit all at once, and they can shift every elevation in a run by a fixed amount that looks completely plausible until it doesn't close.
A check shot to a known point at the start of each setup catches a blunder immediately. The difference between what you observe and what you know is either within tolerance — in which case you proceed with confidence — or it isn't, in which case you have a problem to diagnose before you've propagated it through every subsequent observation. The time cost of that check is measured in seconds. The time cost of discovering the same blunder at closure, after the crew has moved on, is measured in hours or days.
Before Stakeout — the Most Important Check Shot
Before a single grade stake is set, a check shot to a nearby benchmark or TBM verifies that the instrument is on, the HI is correct, and the elevations the crew is about to work from are reliable. This is the setup that everything else depends on. An error here doesn't affect one stake — it affects all of them.
The check shot before stakeout is also the easiest to skip, especially on jobs the crew has worked before. They know where the control is. They've set up on this point before. It's always been fine. This familiarity is exactly when the check matters most, because it's also when attention to the setup details drops. The benchmark that was fine last month might have moved. The HI might have been estimated instead of carefully measured. Two minutes of verification before the first stake protects the entire day's work.
Along the Run — Midpoint Checks
On long level runs between control points, periodic check shots to intermediate TBMs or recoverable benchmarks serve as sanity checks along the way. If something went wrong in the first half of the run — a blunder, a disturbed turning point, an instrument that shifted — a midpoint check shot tells you before you've carried the error through the rest of the job.
This is particularly valuable on runs that span a full day or multiple setup locations. The longer the run, the more opportunities there are for something to go wrong, and the more expensive it is to discover the problem at the end. Breaking a long run with intermediate checks keeps the exposure to any single blunder contained.
When Conditions Change
A setup that was verified at 7 AM may not be reliable at 2 PM if conditions have changed significantly. Temperature swings affect instrument calibration. Soft ground allows tripods to settle between setups. Equipment gets bumped during moves. Any of these can introduce error into a setup that was fine an hour ago.
A check shot after a long break, after moving to a new area of the site, or after any event that might have disturbed the instrument or its control is cheap insurance. The cost is one observation to a known point. The benefit is knowing, rather than assuming, that the setup is still good.
When Your Control Can't Be Trusted
There's a more fundamental version of the check shot question that experienced surveyors learn to ask, especially in certain environments: not just “is my setup correct?” but “is my control still valid?”
In areas affected by land subsidence — coastal regions, areas with heavy groundwater extraction, mining subsidence zones, or anywhere with significant soil consolidation — benchmarks and control points can lose elevation over time. A control point that was established two years ago and used without issue on previous visits may have moved enough to affect deliverable accuracy today. The crew that blindly trusts a benchmark because it worked last year is building their entire job on an assumption they never verified.
Subsidence doesn't always announce itself. It can be gradual enough that a single check to one benchmark looks fine, while the benchmark itself has dropped along with the surrounding area. This is where the value of checking multiple control points becomes clear. Running observations through several benchmarks — comparing them against each other and against published elevations — gives a picture of whether the control network is internally consistent and whether any individual point appears to have moved.
The same logic applies on long-running projects where months or years pass between field visits. Even on stable ground, a lot can happen to physical monuments between site visits. Construction activity, repaving, frost heave, equipment strikes, and erosion can all compromise a control point that was reliable on the last visit. Returning to a project after a significant gap and immediately working off existing control without verification is a risk that check shots are specifically designed to catch.
The professional standard on return visits — particularly in subsidence-prone areas or after long gaps — is to verify the control network itself before beginning production work. That means running observations through multiple known points, closing the loop, and confirming that the network is consistent before relying on it. It adds time to the start of the job. It eliminates the far larger cost of completing a job on compromised control.
Check Shots Aren't Distrust — They're Professional Standard
New crew members sometimes treat check shots as an implicit criticism of their work — as if running a check implies that someone expects them to make mistakes. Experienced surveyors understand them differently. The Party Chief who runs check shots consistently isn't expressing doubt in their crew. They're applying the same standard to their own work that they'd want applied to anyone's work in the same situation.
The standard exists because blunders happen to experienced crews too. Not from carelessness — from the accumulated small pressures of field work. A misread when the sun is in your eyes. An HI estimation when the crew is moving fast. A distracted moment at a busy setup. These are human factors, not skill factors, and no amount of experience eliminates them. What experience provides is the judgment to know that a 30-second check shot is always worth the time.
Recording the Check Shot
A check shot that isn't in the notes didn't happen from a documentation standpoint. If a job is ever questioned, the ability to show that control was verified — what point was checked, what the observed elevation was, what the known elevation is, and what the difference was — is part of what makes the field record defensible.
Recording check shots in structured digital field notes also makes the verification visible to the office team processing the data. When someone on the office side can see that control was checked at setup, checked at midpoint, and checked before departure, the confidence in the deliverable is justified by the record — not just assumed from past experience with the crew.
The check shot is one of the simplest habits in field work. It's also one of the most valuable. The crews that run them consistently are the crews that deliver clean data, close their loops, and don't make return visits. That's not a coincidence.