If your project involves grading, drainage, utilities, access, or land division, bring surveying and civil engineering into the conversation before fieldwork begins.
Terrane provides surveying and engineering, so we can define what the survey needs to capture with the civil design in mind. If you already have an engineer, we’ll coordinate with them directly.
Either way, the next design stage starts with information your team can use.
Start with the decisions your permit set must support
A building addition may change drainage or utility demand. An infill project may depend on a shared drive, retaining wall, or narrow service corridor. A short plat may need access and infrastructure work before its lot layout makes sense.
Commercial parking, loading, accessible routes, fire access, steep slopes, and critical areas can also make an early joint scope useful. A simple interior renovation may need little or no site work.
Tell us what you're designing and permitting. That is more useful than asking for a generic topographic survey and hoping it contains everything the engineer needs.
Define the fieldwork around the design
Drainage design often requires flow paths, rim and invert elevations, culverts, and outfall information beyond the apparent work area. Access design can depend on roadway grades, curbs, sidewalks, and grade breaks. Utility design may need connection points and selected off-site features.
If those needs emerge after fieldwork, the project may require another visit. More seriously, the design may already rely on an assumption that the additional measurements change.
We’ll shape the boundary and topographic survey around the known analyses and submissions. The scope should identify what is included, what others supply, and what remains to be investigated.
Bring six things to the kickoff
A short conversation with you, your architect, and the survey and engineering teams can establish the scope before separate work begins.
- Approvals: jurisdiction, anticipated permits, checklists, and known reviewer requirements.
- Design work: grading, drainage, utilities, access, frontage, retaining conditions, or land division to evaluate.
- Survey limits: the on-site and off-site area needed for those decisions.
- Control: coordinate system, vertical datum, benchmark, units, and file formats.
- Information sources: field observations, record data, specialist reports, and unverified conditions.
- Schedule: fieldwork, base-map delivery, design review, and permit milestones.
Off-site observations depend on access rights and safe working conditions. If you need a partial base early, agree on its contents and intended use before release.
Check the features the engineer will use
The final feature list depends on the project. Review these categories together:
- Boundary and title: property lines, monuments, applicable easements, rights-of-way, and adjoining context.
- Terrain: contours, spot elevations, grade breaks, slopes, walls, and surface materials.
- Drainage: swales, ditches, catch basins, culverts, discharge points, and relevant building elevations.
- Access and frontage: streets, curbs, sidewalks, ramps, drives, parking, and visible conflicts.
- Utilities: surface structures, accessible rim and invert information, record lines, and connection context.
- Improvements: buildings, eaves, decks, stairs, fences, and other design constraints.
- Specialist information: environmental, tree, or geotechnical features identified for incorporation.
The survey locates the agreed features and documents their sources. The appropriate specialist establishes any environmental or other professional determination that falls outside that scope.
Keep utility certainty visible
Surface structures, utility records, locator markings, and subsurface investigations provide different information. The base map should say where each came from and what remains unverified.
If a buried connection or conflict controls the design, identify the additional locating or investigation needed. Do not let a record line become an assumed field measurement as the drawing moves between teams.
Agency requirements can add another layer to the scope. In Seattle, Seattle Public Utilities’ survey requirements apply to City work and certain private projects involving City infrastructure. You should review the applicable requirements with the engineer before fieldwork, so the survey captures what the design and permit submission will need.
Deliver a base the whole team can use
A usable survey base starts with shared standards for CAD format, layers, units, scale, coordinate system, datum, and benchmark. The handoff should also identify survey and fieldwork dates, feature coding, record sources, exclusions, inaccessible areas, and revision status.
Keep all information attached to the linework. An unexplained elevation shift or an outdated background can undo careful coordination.
Architecture and engineering teams need a clear way to receive updates. If one discipline changes the concept, the others need to know whether it creates a new survey requirement.
Move from the field to the permit set
We begin with the project’s approval path, concept, and important constraints. Survey and engineering then agree on the field limits, features, control, and deliverables.
After research and fieldwork, the engineer reviews the base against the planned analyses. The team resolves boundary, grading, access, and utility conflicts before moving into detailed design. The team adds supplemental survey work deliberately when the project requires it.
The engineer develops the civil permit documents from that base. Seattle’s site-plan guidance can help frame the submittal discussion, but the reviewing agency’s current requirements govern the project.
Construction is another handoff. Define staking and construction survey needs separately, including the design files, control, and later as-built requirements. A design survey does not automatically include every construction service.
Send us what you have
Share the address and parcel numbers, title material, prior surveys, current architectural concept, anticipated civil scope, permit path, and milestone schedule. Include utility correspondence, specialist reports, access conditions, and CAD standards.
A preliminary concept is enough to start a useful discussion. We can identify the decisions that need early information and agree on a phased release where appropriate.
Early coordination helps us reduce avoidable return visits and design rework. It also makes the remaining assumptions visible before the team relies on them.
Common questions
Can coordinating surveying and civil engineering save time? It can. When Terrane’s surveyors and civil engineers scope the work together, the engineer’s design questions can shape what the field team captures. That can reduce avoidable return visits, missing information, and rework. Agency review and approval still follow their own timelines.
Does starting together mean all work happens at once? No. It means we coordinate survey and civil requirements before fieldwork. Tasks still follow the project's required sequence.
Can Terrane work with our existing engineer? Yes. Connect us early so we can confirm the engineer’s feature list, survey limits, control, and digital requirements.
Will this guarantee a faster permit? No. Agency review, project changes, and other conditions still affect timing. Early coordination can reduce missing information and avoidable rework within the team’s control.
Can we use an early survey release for final design? Only for the uses it is ready to support. Agree on what each release contains, its limits, and how later information will be incorporated.
Ready for a scope?
Just punch the pulsing green button, fill out a few questions, and we’ll get right to work on your estimate. Because time is the measure.
