Construction stake-out report: stakes, photos, tolerances and MapLab Survey records
Stake-out value is not only the stake in the ground. It is the record that explains what was set, when, by whom and against which control.
Field takeaways
- A stake-out report should include point name, design coordinate, residual, tolerance, date, crew and photo.
- CRS and control point information are the technical backbone.
- RTK records should include fixed status, antenna height and control checks.
- State whether GNSS or total station was used.
- MapLab Survey keeps points, photos, notes and exports together.
Why the report matters as much as the peg
On site, a stake is driven, paint is sprayed, a nail is set, the operator starts work. If the record is weak, a few days later the argument begins about what the mark was set against. The report exists to prevent that argument: it has to prove that a specific point was set on a specific date, by a stated method, within a stated tolerance. Anything less is a note, not a record.
The minimum content
- Project name, date, crew and instrument used.
- Point name, design E/N/Z and the target tolerance.
- The remaining difference after setting, or the control note.
- Coordinate system, EPSG, height reference and units.
- Control point name, measured difference, fixed/float status.
- A photo of the stake, paint, nail or mark.
RTK and total station, stated explicitly
RTK works fast under open sky; the total station is often safer around buildings, on column axes, indoors and in precise detail. The report must say which was used — with GNSS, note the antenna height and fix status; with a total station, the setup point, orientation and reflector. And state which control point the work was based on and what it read when checked: if the control was wrong, everything downstream is wrong in the same direction, and only that line will show it.
Tolerance language
"It came out close" is not report language. Write the tolerance horizontally and vertically — 2 cm horizontal, 1 cm vertical — so acceptance or re-measurement is a fast decision. Record the measured deviation, not a tick: a column of numbers reveals a drift, a column of ticks hides one. An out-of-tolerance point is never hidden; it opens a re-stake or a design check note.
Recording it in MapLab Survey
Keep the stake-out points in the project, add a photo and short note to every critical point — framed wide enough to show where it sits, because close-ups of a peg identify nothing weeks later — and keep control points on their own layer. At the end of the day, share the DXF, CSV or report together with the coordinate system note. A good stake-out report puts both the setting crew and the receiving crew at ease.
See it in action
MapLab Survey | Professional Mobile GIS, GPS Surveying & Land Measurement App
Visit the YouTube channel ->Try these steps on your own phone.
MapLab Survey handles RTK/GNSS point capture, drawing, area and volume calculations and coordinate conversion, then exports to DXF, KML/KMZ, GeoJSON, Shapefile, GeoPackage, NCZ or CSV. Capture, calculation and export work offline. Live NTRIP corrections and online basemaps need a connection.
Frequently asked questions
Should photos be included?
Yes, especially for critical points.
How to state tolerance?
State horizontal and vertical tolerances separately.
Is RTK fixed enough?
No. Add control checks, antenna height and CRS.
Technical references
The field guidance in this article is aligned with the technical and official references below.
Related: Stake-out · iPhone Android RTK GNSS · Field survey checklist · MapLab Survey