Per-MW pricing, regional variance, and cost drivers for owners scoping hyperscale & AI builds.
Salary benchmarks across the 14 mission-critical disciplines.
A land development engineer owns the civil work assigned by the contract - not every site decision. Before hiring, I’d define the deliverables, sealing duties, permit scope, and authority to review field changes.
For an industrial campus, I’d check four areas:
My rule: <u>separate technical review from cost and schedule approval</u>. The engineer designs the contracted civil systems. Other parties handle subsurface findings, building design, construction, funding, and agency decisions. I’d put those boundaries in writing and assess performance against work the engineer controls.
Buildable acreage is not the same as total acreage. The engineer’s first test of ownership is whether the site can support the campus program. That means checking topography, floodplain and floodway status, wetlands, zoning, setbacks, easements, drainage patterns, soil data, utility availability, road and fire access, and likely stormwater outfalls. FEMA flood maps provide an initial screen, but site surveys and jurisdictional studies may still be needed. Mapped risk does not replace design or agency review.[5]
The due-diligence memo, constraint map, and concept plan should separate verified conditions from assumptions and identify needed survey, geotechnical, environmental, and traffic studies. These constraints shape the grading, drainage, and utility layout.
The preliminary utility assessment should confirm connection points, capacity, and required extensions - not just show nearby lines. Compare grading concepts by cut-and-fill volumes, retaining-wall needs, stormwater facility requirements, and off-site improvements. These findings inform civil costs and schedules. Reserve drainage and utility corridors early for future phases.
Construction documents must work as one package. The deliverable is a civil system that can be built, not a stack of separate plan sheets. Existing-conditions and demolition plans show what stays and what goes. Site layouts, grading plans, drainage calculations, details, and specifications connect building pads, finished floors, roads, dock aprons, utility cover, and outfalls.
Use survey data and geotechnical recommendations to check earthwork assumptions and pavement needs. Mark unresolved elevations and interface points before issuing the documents.
Permanent stormwater plans document runoff assumptions, storage, treatment, discharge controls, maintenance access, and emergency overflow. Erosion-control plans address the construction phase. Earth disturbance of 1 acre or more, including smaller sites within a qualifying common development plan, generally requires construction-stormwater permit coverage.[3] Preparing these plans does not make the engineer responsible for installing, inspecting, or maintaining field controls.
The civil sheets then serve as the basis for permit submittals and agency review.
Utility plans and profiles should show sizes, materials, slopes, elevations, cover, required separations, crossings, easements, connection points, and service limits. Civil scope commonly covers site water, fire service, sanitary sewer, and storm sewer. Site utility coordination does not automatically include building MEP, high-voltage, process-utility, or utility-provider system design.
Plan campus access for phased industrial growth. Pair pavement and grading plans with swept-path checks for delivery trucks and fire apparatus. Document phased extensions, loading areas, truck courts, fire lanes, public-road tie-ins, and temporary access so later work does not block occupied buildings or require moving phase-one infrastructure. These utility and access layouts establish the basis for the permit package and field support scope.
Industrial Campus Responsibilities: Who Owns What?
Once the civil package is coordinated, the engineer prepares the permit submittal and manages agency comments. The land development engineer typically assembles the site plan, survey, grading, drainage, stormwater, erosion-control, utility, and access documents. Optional items include floodplain documentation, traffic studies, fire-access exhibits, and easement documents.
The engineer owns the permit package within the contracted scope - not the approval decision. Agencies and utilities approve their respective submissions. Applicant status, fees, signatures, and permit-holder duties depend on jurisdictional rules and the contract.
Maintain a comment log linking each agency comment to its discipline, required fix, revised sheet or calculation, and resubmittal date. Organized responses help avoid delayed resubmittals and permit drift, making schedules more predictable. Track permit conditions separately, with responsible parties, deadlines, inspections, and closeout evidence.
Before issuing construction documents, check them against the approved set and resolve any differences. Review phased work and later changes for effects on permitted drainage, utility connections, access, and required agency approvals.
After permit approval and during construction, the engineer’s work shifts to RFIs, submittals, and closeout support. Civil construction support includes written RFI responses, submittal reviews for conformance to design intent, and technical reviews of substitutions and differing site conditions.
Each response should name the governing document, explain the required clarification or revision, and identify any permit or scope impact. RFI and submittal responses address technical conformance only. They do not authorize change orders.
Closeout may include contracted site observations, punch-list comments, record drawings, stormwater documentation, and required certifications. Record drawings should identify where each change came from - contractor redlines, survey, or field verification - without suggesting that every installed elevation was checked.
Certifications require proper authority and professional responsibility. Agency acceptance and permit termination are separate actions. Under EPA’s 2022 Construction General Permit, operators must retain corrective-action logs for at least 3 years after coverage expires or terminates. Applicable state permits may differ.[6]
These boundaries are typical, not universal. In design-bid-build, the owner usually contracts separately with the designer and contractor. In design-build, one design-builder is responsible for both design and construction. This gives the owner a single contractual point of responsibility, though separate civil or specialty designers may still perform delegated work. Owner-led arrangements need explicit coordination authority.
Document this project’s engineer-of-record duties, delegated design, and change authority. Geotechnical recommendations inform civil earthwork design. Finished-floor elevations need architectural and civil coordination. Field changes need technical review, commercial authorization, and agency approval where required.
The matrix below separates technical ownership from commercial and construction responsibility. Check each assignment against the project’s contract and delivery model.
Use the ownership boundaries above to distinguish industrial-campus leadership from general civil drafting experience. Look for experience with phased industrial sites - not just plan production. Ask candidates for the acreage, building count, utility demands, jurisdiction, delivery model, and phase they handled. Have them identify the deliverables they led, checked, or sealed, and explain how early civil decisions shaped later expansion.
Verify authority to take responsible charge or seal documents: check state PE licensure, comity eligibility, and licensing board rules for the project state.[7][8] Assess their experience with local drainage criteria, permit coordination, utility integration, and resolving issues during construction.
Work samples should show that candidates can turn site constraints into permit-ready, buildable documents. Request redacted civil plans, drainage calculations, agency-comment responses, and field design responses. Ask them to identify what they owned, led, checked, or sealed.
Trace a drainage calculation to its plan sheet. Then check utility crossings and permit conditions for consistency. Look at how candidates handled missing information and conflicts between disciplines - not just how polished the documents look.
Measure performance against work within the engineer’s control. Track permit milestones met, civil RFI response times, unresolved conflicts before construction, and avoidable redesign. Compare earthwork estimates with later quantities using consistent assumptions. Record delay causes separately; don't automatically count owner revisions, agency actions, unforeseen conditions, or contractor execution against the engineer. Reference checks should confirm the candidate’s actual authority and scope of contribution.
Match the job title to the actual civil scope before sourcing candidates. Specify the campus type, acreage, project phase, jurisdiction, delivery model, reporting line, and expected site presence.
Separate coordination support from engineer-of-record responsibility: an in-house coordination position is not a consultant engineer-of-record role. Before accepting, candidates should know which decisions they own and which require approval. Clear responsibilities help you match candidate experience to the work.
The land development engineer turns site constraints and program requirements into coordinated civil documents, especially for phased industrial campuses. These include feasibility findings, site plans, grading and drainage calculations, stormwater designs, utility layouts, access-road plans, permit packages, and field design responses. The contract and delivery model determine which outputs the engineer prepares, reviews, coordinates, and seals.
That scope does not cover every site responsibility. The documents depend on clear lines of responsibility. Geotechnical engineers handle subsurface work and foundation and pavement recommendations. Architects handle building design and code coordination. Contractors control means, methods, sequencing, temporary works, and execution. Project managers oversee their assigned scope, budget, schedule, and risk. The agreement still governs owner approvals and other reserved decisions.
Use these boundaries to write the job description and screen candidates. Before recruiting, define deliverables, discipline interfaces, credentials, and decision authority in the scope of work. Specify who supplies survey and geotechnical data, who prepares or signs stormwater documents, who reviews contractor submittals, and who approves field changes that affect cost or schedule.
Recruit for the civil responsibilities the industrial campus project actually assigns. Coordinated civil work can improve buildability, cost control, and schedule predictability - but it cannot guarantee them. Clearly exclude risks the engineer cannot control.
Bring in a land development engineer early, ideally during initial planning or site selection. They can flag zoning issues, utility limits, and geotechnical risks before those problems lead to costly delays [1].
Keep the engineer involved through design and construction to handle site plans, grading and drainage calculations, utility layouts, permitting, and design questions that come up in the field [1][2]. As a rule of thumb, bring key technical staff on board 6 to 12 months before fieldwork begins [3][4].
Set up a formal change control process before design moves beyond the schematic phase. Have the owner’s representative, civil engineer, and land-use attorney review any changes to entitlements, civil plans, or agency filings. They should check whether those changes affect permits, could reset approvals, or could delay the schedule [1].
Review drawings at schematic design, design development, and construction documents to catch scope drift before it leads to costly rework or permit resubmissions [1].
Ask for evidence that they led early site feasibility and sequencing decisions - including facility type, phasing, budgets, and permit dependencies - and followed those decisions through to buildable outcomes. Review feasibility by phase, grading and drainage scope, utility tie-in and access road layouts, permit-ready civil packages, and monthly approval tracking.
Request RFI and field question responses, plus action logs that show who owned each task across the civil, geotechnical, and general contractor teams. These records should also show how they prevented late redesign or schedule delays. [1][2][3]
