A finished-floor elevation and a full topographic survey are not the same thing. They answer different questions. Mixing them up on a project can mean a second site visit. It can also mean extra cost. This article shows how the two survey types differ. It also shows when each one applies. And it shows how to ask for the right scope before a crew shows up.
One Height or the Whole Surface: The Core Difference
An elevation survey looks at one point, or a small set of points. Think finished floor, foundation top, road connection, or a single site benchmark. The surveyor measures those points. Then the surveyor reports the elevation values, tied to a stated reference. That’s the whole job.
A topographic survey covers more ground. It records the shape of the land. It also records visible features across the site, such as trees, utility structures, pavement edges, and drainage paths. Instead of a few numbers, you get a picture of how the whole surface rises and falls.
The difference is about scope, not accuracy. Both survey types give reliable numbers when done right. What changes is how much ground gets measured. It also changes how many points get recorded, and how the data gets used later by a designer.
Why the Number and Location of Survey Points Matter
The use of the data decides how many points a surveyor needs. It also decides where those points sit. A single question, like whether a proposed floor sits high enough above a flood line, might only need one or two points tied to a known reference. A full site design needs more. It needs enough ground data to show slope changes, low spots, and high spots across the whole lot.
Clients often ask for “elevations” without saying which points matter to them. That leaves the surveyor guessing at scope. A survey built on guesswork can miss what the project needs. Or it can cover far more ground than the project called for. A better approach is to name the actual spots. Name the northeast corner of a proposed addition. Name the centerline of a new driveway. Name the top of an existing retaining wall.
Naming the spots up front keeps the survey focused. It also keeps the cost tied to what the project truly needs, not to extra coverage that never gets used in the design.
Benchmarks, Vertical Datums, and Compatible Elevation Data
Every elevation number needs a starting point. That starting point is a benchmark, a fixed spot with a known height. Or it is a vertical datum, a system such as NAVD88. A datum ties elevations together across a wide area. Without one of these tied to the data, a number like “812.4 feet” means nothing on its own.
Before fieldwork starts, it helps to check the datum. Ask the architect, engineer, or local government which one they want. Some cities and towns ask for a set benchmark or datum for permit review. Others accept a benchmark set by the surveyor. It just has to be marked clearly on the drawing and the report.
No single rule covers every project in the state. A city, township, or county may set its own rule. That rule can differ from the one next door. Check the datum early, before the crew leaves the site. This keeps the elevation data in line with what the reviewer expects.
Matching the Survey to the Actual Michigan Project Question
Some project questions are narrow. Checking that a proposed finished floor sits above a required flood line is one example. That kind of question usually needs a few elevation points tied to a known datum. It does not need a full topographic survey. Paying for one adds cost without adding useful data.
Other questions are broader. Designing a driveway across a sloped lot is one example. Planning grading around a new addition is another. So is laying out drainage on an uneven site. All of these need topographic coverage. The design team needs to see how the ground moves across the whole area, not just at one or two points.
Michigan townships, cities, and counties do not all use the same rules. A civil engineer’s drainage plan might need contour lines every two feet across the site. A local building department might only need one floor elevation letter tied to a set datum. Check with the local authority or design pro before fieldwork starts. That is the best way to match the survey scope to the real question, instead of guessing.
When a Combined Scope Prevents a Second Field Visit
Some projects need both survey types. A builder might need a confirmed finished-floor elevation and topographic data for grading around the new structure, at the same time. In that case, covering both in one visit saves time. It also avoids a repeat trip to the site later in the project.
The way to avoid gaps is simple. Talk through the details before the crew shows up. Ask these questions first:
- Which points need measuring, and where exactly are they?
- Which features need to be mapped?
- How far past the building footprint should coverage extend?
- What format does the deliverable need to be, a PDF drawing, a CAD file, or both?
- Which benchmark or datum ties all of it together?
Getting these answers set ahead of time lets the crew collect everything in one trip. Missing a point or a feature after the crew has left usually means another visit. That extra trip costs more than the short talk that would have stopped it.
Elevation surveys and topographic surveys each have a place on a project. Know which one fits your question. Be clear about points, datum, and coverage before the survey starts. This keeps the project on schedule. It also gets the design team the numbers they need.
