Construction Survey Stakeout Documentation Best Practices

Survey stakes are ephemeral — they get hit by equipment, buried under fill, or pulled by other trades. The stakeout documentation, on the other hand, is permanent. When a grade dispute arises weeks or months after staking, the record of what was staked, where, and when is the evidence that determines who is responsible.

Published May 28, 2026·8 min read

Start Free Trial

Quick Answer

What should be documented at a construction survey stakeout?

Construction survey stakeout documentation should include: date and time of staking; instrument type and calibration date; control point or benchmark used for the survey; for each stake set — point ID, station and offset, northing and easting coordinates, design elevation, existing ground elevation if shot, cut or fill amount, and lath marking description; photographs of each stake set in context; and the surveyor's name and license number. The stakeout record should be created contemporaneously — at the time of staking — not reconstructed from memory afterward. Contemporaneous records carry more weight in dispute resolution than records that appear to have been assembled after the fact.

Digital (preferred) or field book — must be contemporaneous

Stakeout record format

At least one photo per stake set, geo-tagged if possible

Photograph requirement

Record the specific benchmark or control point used for each stakeout session

Control source

What the Stakeout Record Must Contain

A complete stakeout record includes the following data for each stake or control point set:

Data Element	Why It Matters
Date and time	Establishes the timeline — when the stake was set relative to when grading occurred
Control source (benchmark/monument)	Proves the stakeout was referenced to the correct datum
Instrument type and calibration	Validates measurement accuracy; required by some specifications
Point ID / station / offset	Ties the stake to the design drawings and plan sheets
Design elevation	The grade the grading crew should achieve — the target
Cut or fill amount on lath	What was written on the stake — if the crew misread it, the record shows the correct value
Surveyor name and license	Required on public works; establishes professional accountability
Lath color and marking description	Helps identify which stakes belong to which stakeout event if multiple crews work the same area

Handling Restaking Requests

Stakes are removed or damaged constantly on active job sites — by equipment, by other trades, by weather. Restaking is a normal part of construction, but it creates a documentation risk: if a stake was set incorrectly and the error was not caught until the second stakeout event, the record must clearly show which stakes were original and which were restaked, and why.

Best practices for restaking documentation:

Require a written restaking request from the contractor or superintendent before performing the restake. The request should identify the stakes affected and the reason for restaking (equipment hit, flood, other trade removed stakes, etc.).
Record the restaking event with a new date, time, and point list in the stakeout record. Note the original stakeout date and the reason for restaking.
If the original stake is still in place and the request is because the crew cannot find it, verify the original stake location before restaking. Do not assume the original stake is wrong simply because the crew cannot find it.
If the original stake is found to be incorrect (data entry error, software error, or wrong design version used), document the error, correct the stake, and notify the contractor in writing. File the error notification with the project record.

Stakeout Documentation for Machine Control Projects

Machine control projects reduce the number of physical stakes required but do not eliminate the need for stakeout documentation. The machine control system uses a digital design surface — documenting the source, version, and date of that surface is the machine control equivalent of the stakeout record.

Required documentation for machine control stakeout:

Design surface file. Record the filename, version number, and date of the design surface loaded into the machine control system. If the design is revised during construction, document when the revised surface was loaded and which machines received the update.
Calibration check shots. Before each shift and after any instrument repositioning, verify the machine control position against a known control point. Record the check shot results — position error in X, Y, Z — in the daily machine control log.
Spot check survey. Periodically (at least once per day on active grading), shoot a GPS spot check on recently machine-graded areas to confirm the surface matches the design. Document the check shot results and compare to the design surface.

Build a Complete Stakeout Record as You Work

Sitemark links grade verification shots to the original stakeout data — giving you a continuous record from stakeout through finish grade that resolves disputes before they escalate. Start free.