Phase 0 Resource · civil
How to Review a Grading Plan: Design Inputs
A grading-plan review traces existing and proposed elevations through drainage, access, utilities, and adjacent-property constraints. This design perspective focuses on contours, spot elevations, drainage arrows, ADA routes, utilities, and erosion controls.
By Apex Grid Engineering · Updated 2026-09-15
Start with the design decision
A grading-plan review traces existing and proposed elevations through drainage, access, utilities, and adjacent-property constraints. This design perspective focuses on contours, spot elevations, drainage arrows, ADA routes, utilities, and erosion controls. Before selecting a detail, calculation method, assembly, or system, write the decision in one sentence: what must be designed, for which project condition, and what document will prove it. For this civil topic, the design team should identify contours, spot elevations, drainage arrows, ADA routes, utilities, and erosion controls; the governing code or AHJ checklist; current architectural and engineering backgrounds; assumptions that need confirmation; and a record of unresolved decisions.. That short brief prevents a preliminary idea from being mistaken for a permit-ready conclusion.
Build an input register, not a wish list
The design register should name the source and status of each input: current, assumed, pending, or rejected. For civil, this normally means checking contours, spot elevations, drainage arrows, ADA routes, utilities, and erosion controls; the governing code or AHJ checklist; current architectural and engineering backgrounds; assumptions that need confirmation; and a record of unresolved decisions. against the current architectural background, project address, code edition, owner criteria, and known field constraints. Note who can confirm each open item. A missing measurement or unselected product is a design dependency, not an invitation to invent a value.
- Design question and acceptance criterion
- Source, date, and confidence for each input
- Code provisions or engineering method to be used
- Interfaces with architecture, MEP, civil, contractor, and owner scope
- Open decisions that must be resolved before issue
Example design deliverable
A useful civil design record connects the selected approach to a drawing, schedule, calculation, or narrative. It should show the governing assumptions, the condition the design addresses, the limits of applicability, and the coordination detail a reviewer or builder will need. For how to review a grading plan: design inputs, the output is not just a checklist: it is a controlled design decision that can be checked against later revisions.
Design gate before handoff
Before the design moves to review, compare it with the latest background and ask whether changed geometry, occupancy, equipment, loads, utilities, or site evidence affects the conclusion. The responsible engineer decides whether further analysis, a site observation, survey, geotechnical input, testing, or product data is required. Record unresolved items visibly rather than hiding them in a general note.
Related Engineering Resources
Frequently Asked Questions
What must be decided before how to review a grading plan: design inputs begins?
What makes a design input reliable?
Can a preliminary design value be used as the final permit basis?
Discuss your engineering scope
Share the project address, current records, requested deliverable, authority information, and schedule. Apex Grid confirms professional responsibility, availability, and scope before work begins.
Start an Engineering Estimate