Most field note problems don't surface in the field. They surface days or weeks later, in the office, when someone tries to use the data and discovers that a critical piece is missing. By then the crew has moved on, the site conditions have changed, and reconstructing what actually happened is somewhere between difficult and impossible.
The mistakes below aren't random — they follow predictable patterns. They happen most often when crews are moving fast, when the job feels routine, and when the documentation step gets treated as less important than getting to the next shot. Understanding where the gaps typically appear is the first step toward closing them.
Missing or Wrong Instrument Height
The single most common source of elevation errors that don't get caught until it's too late. The height of instrument gets estimated, read incorrectly, or simply not recorded when the crew is moving fast through setups. In the field, the party chief knows the HI because they just set it. Three hours later, back at the office, all that remains is a column of rod readings with no instrument height attached to any of them.
What makes this mistake particularly costly is that it's often undetectable until someone tries to compute elevations. A missing or wrong HI doesn't produce an obvious error in the field — it produces elevations that look plausible but are consistently off by a fixed amount. By the time the error is found, returning to the setup location to re-observe may not be practical.
The fix is simple in principle: instrument height gets recorded the moment the instrument is set up, not after the first shot is taken. Making it the first entry for every setup — before any rod readings — removes the opportunity to forget it.
No Pre-Job Setup Recorded
Date, crew names, equipment, control used, benchmark — skipped entirely or filled in later from memory. On a normal day when nothing goes wrong, this information never gets needed. On the day a job gets disputed, questioned, or audited, it's the first thing anyone asks for.
“We think we used BM-14” is not a defensible answer. “We used BM-14, elevation 498.32, verified against BM-11 before starting” — with a timestamp and crew names — is. The difference between those two answers is five minutes of documentation at the beginning of the job.
Pre-job setup also tends to be the section most often filled in after the fact. A crew that plans to record it “in a minute” frequently ends up recording it at the end of the day from memory, with details that are approximate at best. Recording setup information before the first shot ensures it's accurate and in the notes where it belongs.
Skipping the Level Loop Closure
The loop gets run but never closed before the crew leaves. Nobody checks the closure error. The data goes back to the office, someone computes elevations, and the misclosure shows up then — when the crew is already 45 minutes away and the window for a quick re-observation has closed.
Closing the loop before leaving is not a formality. It's the only quality check that happens while something can still be done about it. A closure of 0.003 feet on a one-mile loop is acceptable. A closure of 0.14 feet means something went wrong, and “something went wrong” is much cheaper to diagnose at the site than at the office.
The habit that prevents this is simple: the loop closure is the last entry on every leveling job, recorded at the instrument before the crew packs up. Not at the truck. Not the next morning. Before anything gets loaded.
Illegible or Missing Sketches
A column of rod readings means nothing without a sketch showing what was shot and where. Point descriptions alone — “TP1,” “TP2,” “MH rim” — don't communicate layout, relationships between shots, or the physical context of the job. Sketches do.
Crews skip sketches when they're in a hurry. The justification is usually that the job is simple enough that a sketch isn't needed. That judgment tends to hold up fine on simple jobs and fail badly on complicated ones — which are exactly the jobs where a missing sketch causes the most trouble. The office then spends time calling the field to ask questions a two-minute sketch at the truck would have answered.
A sketch doesn't have to be a work of art. It needs to show point locations relative to each other, the approximate layout of the site, and enough context that someone reading the notes a month later can orient themselves. That takes two minutes and prevents a phone call.
Undocumented Deviations from Plan
A stake couldn't be set as specified — an obstruction, a grade conflict, a missing reference — so the crew made a judgment call and moved on. The judgment call might have been completely reasonable. The problem is that it wasn't written down, so six months later when a contractor disputes a grade, nobody can explain why the stake was offset from the plan.
Deviations from plan are one of the most consistently under-documented aspects of field work. When everything goes according to plan, notes are complete. When something unexpected requires an adjustment, the adjustment gets made and the notes move on as if nothing happened.
Any time the crew does something different from what the plan specified — different location, different elevation, different offset — that decision and the reason for it need to be in the notes. It doesn't require a paragraph. A single line explaining what was done and why is enough to make the record defensible.
Observations Without Context
Raw numbers with no description of what was shot. “4.82” with no rod point, no description, no station reference. Readable in the field when everything is fresh. Meaningless three weeks later when the office is trying to figure out which 4.82 that was and what it refers to.
This mistake is especially common on jobs with repetitive shots — control runs, topographic work, stakeout jobs with many similar points. After the tenth shot of the same type, recording the description can start to feel unnecessary. It almost never is. The one shot that matters is usually the one without a description.
Weather and Conditions Left Blank
Skipped because it feels like an administrative checkbox rather than a real field observation. It is relevant, though — not every day, but on the days it matters, it matters significantly. Instrument performance questions, return visit disputes, and legal challenges all benefit from a record of site conditions on a specific date. “Clear, 58°F, light wind” takes five seconds to write and provides context that can't be reconstructed later.
Notes Finished After the Fact
The most insidious mistake on this list, because it looks like complete notes. A crew that fills in field notes at the truck at the end of the day — or worse, back at the office — is producing a record of what they remember happening, not what actually happened. Details get consolidated. The sequence gets smoothed out. Observations that happened in a specific order get recorded in a tidier order that doesn't reflect reality.
Notes filled in after the fact are legally weaker than contemporaneous notes — recorded at the time of observation. In a dispute where the timing of documentation matters, notes that were clearly produced after the field work is done carry less weight than notes recorded in real time.
The standard that prevents this is straightforward: field notes get recorded at the instrument, at the time of each observation. Not summarized at the end of the setup. Not reconstructed at the truck. At the instrument, as the work happens.
The Common Thread
Every mistake on this list shares the same root cause: documentation that gets treated as secondary to the field work itself. The measurement is the job; the notes are the paperwork. That framing leads directly to notes that are incomplete, filled in late, or skipped under pressure.
The practical fix is a change in framing: the field note is not a record of the survey. It is the survey. The measurements exist only in memory until they're recorded. A level run that was never closed exists only in the party chief's head. An instrument height that wasn't written down is gone the moment the crew drives away.
Crews that internalize that framing produce better notes — not because they work harder, but because they understand what they're actually producing. The measurement and the documentation are the same task. You're not done with the setup until both are complete.