As-Built Surveying: What to Measure and How to Verify Results

Surveyor in a blue vest holding a GNSS rover pole with a data collector on a grass field

A stamped set of construction drawings tells you what a project was supposed to become. It rarely tells you what actually happened once crews were in the ground. Utility lines get shifted around an unexpected rock outcrop, a foundation gets nudged to clear a property line, a mechanical run gets rerouted to dodge a structural beam that showed up late in the design. None of that gets caught by the original plan set, and all of it matters the moment someone needs to renovate, maintain, or sell that property.

An as-built survey exists to close that gap between what was drawn and what was actually constructed, giving owners, engineers, and municipalities a record they can trust rather than a set of assumptions they have to verify by digging.

For land surveyors and civil engineers working across Canada, as-built work has become one of the more consistent revenue streams on any given project, precisely because deviations from plan are the rule rather than the exception. Getting it right depends less on effort and more on knowing exactly what to measure, which method fits the site, and how to confirm the results before they go out the door.

Key Takeaways
What an As-Built Survey Actually Captures
Choosing the Right Measurement Method
Verifying the Results Before They Go Out
Common Pitfalls That Undermine Accuracy
The Real Value Shows Up Later, Not on Delivery Day

Key Takeaways

  • An as-built survey is an independent field record, not a redraw of the original plan with a new date on it
  • Core measurement targets include utilities, grading and finished surfaces, structural elements, and site features tied to easements
  • RTK GNSS handles most open-site work, total stations cover obstructed areas, and scanning adds value on larger or more complex sites
  • Verification (redundant checks, control comparison, fix-quality review, and reconciling field notes) is what protects accuracy before delivery
  • Municipal submissions across Canada often require specific coordinate systems and datums, so confirming those early avoids rework

What an As-Built Survey Actually Captures

An as-built survey documents the physical, verified location of everything that was constructed, compared against the design. That includes horizontal and vertical positioning, materials used where they differ from spec, and any field changes that never made it back onto the drawings. It is not a redraw of the original plan with a new date stamp. It is an independent record built from field observations.

Most as-built surveys focus on a similar core set of features, though the exact scope depends on the project type:

  • Utilities and underground infrastructure: water, sewer, storm, gas, electrical, and telecom lines, including depth, material, and connection points
  • Grading and finished surfaces: pavement elevations, curb lines, drainage swales, and site grading compared to design contours
  • Structural elements: foundation footprints, building corners, column locations, and any dimensional deviations from the architectural set
  • Site features: retaining walls, fencing, signage, landscaping tied to easements, and access points that affect future permitting

On larger civil or subdivision projects, this list expands to include road geometry, stormwater management facilities, and utility easements that municipalities will want verified before accepting the infrastructure.

Choosing the Right Measurement Method

The method you choose shapes both the accuracy and the turnaround time of the final deliverable, and it needs to match the site rather than default to habit.

RTK GNSS remains the workhorse for open sites with reasonable sky visibility, since it gets a surveyor centimeter-level horizontal and vertical positions in real time, without the post-processing delay of static methods. It handles utility staking, grading verification, and building corner ties efficiently, and it scales well across sites of any size, from a single infill lot to a full subdivision.

For crews weighing which system fits their as-built workload, Bench-Mark’s page on land survey and RTK equipment breaks down the receivers and total stations best suited to different field conditions.

Total stations still earn their place where GNSS struggles, particularly under dense canopy, inside structures, or in urban canyons where satellite visibility drops off. Many crews run a hybrid workflow, using RTK for open areas and switching to a total station for tight or obstructed zones on the same site.

For larger or more complex projects, laser scanning and photogrammetry add a layer that point-by-point measurement cannot match on its own: a dense, navigable dataset of the entire structure or site. This matters most on renovations, industrial facilities, or any project where the client needs to revisit the data later without sending a crew back out.

Verifying the Results Before They Go Out

An as-built survey is only as useful as its accuracy, and verification is where a lot of otherwise solid fieldwork falls apart. A few checks should happen before any deliverable leaves the office:

  1. Cross-check redundant observations. Any point tied from more than one setup or control station should agree within tolerance. A mismatch usually points to a control error rather than a field mistake, and it needs to be resolved before drafting starts.
  2. Compare against known control. Tie the survey back to established benchmarks or geodetic control monuments, ideally ones already on record with the relevant provincial or municipal authority, so the dataset holds up against future surveys on the same site.
  3. Review fix quality in the field, not just the office. RTK data collected with a poor fix or excessive PDOP can look reasonable on a screen and still be off by centimeters. Flagging low-quality shots at the point of collection saves a return trip later.
  4. Reconcile field notes with drawings. Every deviation noted verbally by a foreman or crew lead needs a corresponding measured point. A written note with no matching coordinate is a gap that shows up during a later dispute.

Municipalities across Canada increasingly expect as-built submissions tied to specific coordinate systems and datums, and getting that wrong is one of the more common reasons a package gets sent back for revision. Confirming the required datum, projection, and vertical reference before fieldwork begins avoids a rework cycle that costs more time than the original survey.

Surveyor checking a handheld data collector beside a GNSS rover pole in a parking lot

Common Pitfalls That Undermine Accuracy

A handful of issues show up repeatedly on as-built projects, and most are avoidable with a bit of planning:

  • Relying on a single control point instead of a redundant network, which leaves no way to catch an error after the fact
  • Measuring finished surfaces before construction is fully settled, particularly with fresh grading or newly poured concrete that can shift
  • Skipping subsurface utility locates and measuring only what is visible, which leaves the most disputed part of the record incomplete
  • Failing to document the as-installed material or size when it differs from spec, since that detail often matters more than position alone during future maintenance

Bench-Mark works with surveyors across Canada who run into these exact issues on a weekly basis, and the pattern is almost always the same: the fieldwork itself was competent, but the verification step got compressed under deadline pressure.

The Real Value Shows Up Later, Not on Delivery Day

An as-built survey rarely gets appreciated the day it is submitted. Its value shows up eighteen months later, when a contractor needs to know exactly where a buried line sits before excavating, or when an owner is trying to close a sale and needs documentation that matches reality rather than intent.

Treating the measurement and verification steps with the same rigor as the original design survey is what separates a record people can actually rely on from one that just gets filed away. Bench-Mark continues to see that the projects with the fewest callbacks are the ones where accuracy was checked twice before anyone signed off on it once.

About the Author

Portrait of Nolan Betzner, Bench Mark team member
Nolan has been working in the surveying field since 2017, starting as a part-time student at Bench-Mark while attending the University of Calgary. He now works in technical support and sales helping customers find the right product for them.

In this article