Engineering Insights · Site Development

What Information Does a Civil Engineer Need to Start Site Design?

A civil engineer can often begin before every record is available, but the team should know which inputs are confirmed, which are preliminary and which assumptions could change the design. A clean starter package reduces rework and helps the engineer define scope, schedule and coordination needs.

Key Takeaways

Provide the property, program and current design concept first.
A useful survey should reflect the features and elevations that control the civil work.
Share agency comments, prior records and known constraints early—even if they are incomplete.
Document assumptions when design begins before all inputs are confirmed.
Identify the decision-makers and required deliverables, not only the drawing deadline.

Property Information

Start with the property address, assessor parcel number or parcel identification, and legal description if available. Identify whether the work covers the entire parcel, a tenant area, a lease boundary, an easement or a defined improvement zone. Provide title information and recorded documents that affect access, utilities, drainage or development rights.

Survey

The appropriate survey scope depends on the project, but civil design commonly needs boundary, topographic information, existing improvements, easements, utilities, right-of-way and relevant control. Surface features may include pavement, curbs, sidewalks, walls, drainage structures, buildings, trees and visible utility appurtenances. Coordinate the survey scope before field work so critical tie-in areas and offsite connections are included.

Record drawings or GIS are useful background but are not a substitute for survey where precise location or elevation controls design. Identify features that remain unverified and determine whether utility locating, potholing or supplemental survey will be needed.

Project Program

Describe what the site must support: use, building size and location, parking, loading, drive-through or truck movements, outdoor uses, refuse service, fire access, phasing and expansion. Include operational constraints such as delivery patterns, gate controls or hours that affect circulation. A concise written program helps civil and architectural teams resolve conflicts before the layout becomes fixed.

Architectural Information

Provide the current site plan, floor plan and building entrances where applicable. Civil design needs reliable building footprints, finished-floor assumptions, door locations, utility service points, accessible entrances, roof drainage concepts and loading interfaces. Mark whether information is conceptual, approved or still changing.

Geotechnical Information

Geotechnical recommendations may affect pavement, earthwork, subgrade preparation, infiltration assumptions, retaining structures and foundation coordination. If a report is not yet available, identify when it will be completed and which early decisions must remain provisional. Do not silently apply recommendations from a different property or project without confirming applicability.

Utility Information

Share utility maps, will-serve information, capacity correspondence, point-of-connection guidance, meter or service requirements and available as-builts. Identify known owners and coordination contacts. The team should distinguish a mapped utility from a verified utility and an available connection from an approved service.

Drainage and Flood Information

Provide existing drainage studies, flood mapping, watershed or master-plan information, prior calculations, outfall information and agency criteria where available. Identify visible washes, channels, low points, storm drains and offsite flow paths. Early drainage information helps reserve space and set grading strategy before the building and parking layout are locked.

Existing Records

Prior plans, permits, inspection records, reports, as-builts and comment letters can explain how the site or adjacent improvements were constructed. They may also reveal unresolved obligations. Records vary in reliability and should be checked against current conditions, survey and agency requirements.

Agency and Entitlement Information

Provide zoning information, conditions of approval, development standards, pre-application notes and review comments. Include required public improvements, dedication or frontage conditions if known. Civil design should align with the land-use approvals while recognizing that those approvals may not resolve detailed access, utility or drainage design.

Traffic and Access Information

Share approved access points, traffic studies, driveway criteria, roadway plans, sight-distance information and agency correspondence. Identify expected vehicle types and truck movements. Access changes can affect the entire layout, so unresolved driveway assumptions should be visible to the full team.

Known Constraints and Project History

Tell the engineer about prior denials, neighbor drainage issues, utility conflicts, unusual fill, access disputes, maintenance concerns or field conditions. A constraint does not become less important because it is difficult to document. Early disclosure lets the team define the right investigation instead of discovering the issue during review or construction.

Schedule, Deliverables and Team

Identify real milestones: concept decision, entitlement, permit submittal, pricing, bid, construction and occupancy. Define expected deliverables and software or CAD standards. List the owner, architect, surveyor, geotechnical engineer, landscape architect, utility coordinator, contractor and other disciplines, including who can approve design decisions.

When Information Is Incomplete

A project can sometimes start with partial information. The engineer should document assumptions, limitations and items that may require redesign. The team should agree which work can proceed, what is held, who will obtain missing data and when the design will be reconciled. Starting early is different from pretending uncertainty does not exist.

Minimum Useful Starter Package

Property address and parcel information.
Current survey or a plan for obtaining one.
Written project program and current site concept.
Architectural footprint and entrances if available.
Known access, utility, drainage and flood information.
Prior plans, permits, reports and agency comments.
Conditions of approval or development requirements.
Known constraints and unresolved decisions.
Project milestones, expected deliverables and team contacts.

When to Involve a Civil Engineer

Bring civil engineering into the project while the site layout can still respond to grading, drainage, access and utility constraints. The first task may be an input review and gap list rather than full design. That early definition helps the owner request the right survey and studies, coordinate the design team and avoid building a concept around unsupported assumptions.

Related Services

Related Insights

Professional Note

Requirements vary by jurisdiction and project. This article provides general engineering guidance and is not a substitute for project-specific review of applicable codes, standards, records, surveys, geotechnical information, utility information or agency requirements.

Sawan Dhaliwal, PE
Licensed Civil Engineer — AZ | CA | MO