Module 13: Site Development and Civil Drawings
Learning Objectives
- Organize verified survey, property, regulatory, architectural, and utility inputs into a controlled civil/site drawing set.
- Translate the approved building position into coordinated access, grading, drainage, external-utility, and site-structure information.
- Establish and communicate horizontal coordinate control, vertical datum control, finished-floor relationships, spot elevations, contours, and slopes without inventing missing survey or design values.
- Draft civil sections, utility interfaces, site details, general notes, and cross-references that remain traceable to the governing design basis.
- Coordinate drainage, sewer, water, utility crossings, retaining/site structures, and building penetrations across civil, architectural, structural, and plumbing documents.
- Audit a site drawing package for dimensional closure, elevation continuity, drainage logic, constructability, and revision consistency before issue.
Civil/Site Drawing Set
A coordinated group of drawings that communicates the verified property and survey basis, building position, external works, grades, drainage, utilities, access, site structures, control information, and interfaces needed to construct the project outside and at the boundary of the building.
Professional and Project-Control Boundary
This module teaches production and coordination of civil/site drawings from an authorized project design basis. The drafter or coordinator must not invent property boundaries, survey monuments, drainage criteria, utility capacities, road geometry, retaining-wall design, structural details, or other professional design values. Missing or conflicting information is recorded and returned to the responsible professional for resolution. A civil/site drawing is therefore not an independent design source; it is the controlled communication of verified survey information and authorized civil/site design.
1. Start With Controlled Site Information
Minimum Input Package
A civil/site drawing should begin from controlled source information rather than from an architectural sketch alone. Typical inputs include:
- current property survey, lot bearings/distances, monuments, easements, road right-of-way information, and coordinate/datum references;
- topographic survey with existing contours, spot levels, surface features, drainage paths, utilities, trees, walls, adjoining roads, and other relevant improvements;
- approved architectural site layout and building footprint;
- structural requirements affecting foundations, retaining elements, ramps, equipment pads, and below-grade structures;
- plumbing and utility requirements for water, sanitary, storm, fire-service, and other external connections where applicable;
- geotechnical and site-development criteria when they control earthworks, slopes, retaining systems, infiltration, or subgrade preparation;
- permit, zoning, access, utility-provider, and owner requirements applicable to the project;
- the current revision register identifying which source documents are authorized for coordination.
Site Information Hierarchy
Trace every civil drawing decision back to a controlled source. Survey facts establish the site frame; authorized design inputs define what is to be placed inside it.
Do Not Redraw the Survey as an Uncontrolled Approximation
A copied or manually reconstructed property outline can introduce closure, bearing, coordinate, or monument errors. Preserve the controlled survey geometry and clearly identify the source survey, datum, coordinate system, benchmark, and revision used for the civil base. In the Philippines, property, boundary, horizontal/vertical control, topographic, engineering, and construction-survey activities fall within regulated Geodetic Engineering practice under Republic Act No. 8560, as amended by Republic Act No. 9200; civil/site documentation should consume the authorized survey rather than recreate or alter professional survey determinations.
2. Vicinity, Location, Property, and Building Position
Vicinity and Location Information
A vicinity or location view helps the reader find the project in its broader context. Depending on the project and authority requirements, it may show named roads, recognizable junctions, barangay/city context, north direction, access approach, nearby landmarks, and the project parcel. It is orientational information, not a substitute for the controlled property survey.
Property and Lot Geometry
The site plan should preserve the verified lot lines, corner identifiers, bearings/distances or coordinates, adjoining parcels or road boundaries where relevant, easements, setback/control lines supplied by the authorized design basis, and survey monuments. The building position should be tied to these controlled references by dimensions, coordinates, grid relationships, or approved offsets that can be set out in the field.
Building Position and Site Interfaces
Show the building footprint and the external features that affect construction and use: entrances, ramps, steps, accessible approaches, driveways, loading areas, parking interfaces, walkways, curbs, retaining/site walls, platforms, equipment areas, gates, fences, and other approved site elements. Distinguish existing, proposed, demolished, and retained work using the project's graphic convention.
Iterative Site-to-Building Coordination Loop
Use this as a coordination loop, not a one-way design algorithm. Survey control establishes the common spatial basis; architectural layout, grading, drainage, utilities, and the building finished-floor elevation must be repeatedly reconciled until the authorized interfaces agree.
3. Coordinate and Elevation Control
Horizontal Control
The coordinate, monument, grid, baseline, station, or other approved reference framework used to locate points and features in plan.
Vertical Datum
The defined elevation reference from which project levels are measured, normally connected to a verified benchmark or project benchmark.
Control Information to Show
Where applicable, identify the coordinate system or project grid, benchmark designation and elevation, project datum, north reference, control points, grid intersections, stationing, and critical set-out coordinates. A coordinate must be associated with the correct system and units; an elevation must be associated with the correct datum. Never combine levels from different datums without a documented transformation.
Finished-Floor Elevation as an Interface
The building finished-floor elevation (FFL) is a critical interface among architecture, civil grading, structural foundation/entry conditions, plumbing drainage, accessible approaches, and flood or surface-water considerations. Civil drawings must reconcile the approved architectural finished-floor elevation with the structural level convention and the project datum. Finished floor, top of structural slab, finished grade, invert, and other level types can be different physical elevations; the drawings should show or reference the intended offsets/relationships clearly rather than treating those labels as interchangeable.
One Datum, Many Elevation Uses
Different disciplines may label different physical surfaces, but all levels must resolve to one controlled vertical reference or to explicitly documented transformations.
4. Grading, Spot Elevations, Slopes, and Contours
Finished Grade
The intended final ground or paved-surface elevation after earthworks, subgrade preparation, pavement/landscape build-up, and other specified site work.
Surface Slope
A basic drawing check relates the elevation difference between two points to the horizontal run. Use the project-specified sign and percentage convention.
Variables
| Symbol | Description | Unit |
|---|---|---|
| Surface slope expressed as a ratio; multiply by 100 for percent when that convention is used | - | |
| Elevation difference between the two controlled points | m | |
| Horizontal plan distance between the points | m |
Grading Plan Content
A grading plan may show existing and proposed contours, spot elevations, high and low points, ridges and swales, pavement and landscape grades, top/bottom of slope, curb/gutter grades, ramp transitions, retaining-wall top/bottom levels, building thresholds, and drainage structures. Use enough information to make the intended surface reconstructible without covering the sheet with redundant spot levels.
Interactive Topographic Plan Reader
Use the repository's technical topographic viewer to inspect contour spacing, spot elevations, terrain form, survey features, and plan interpretation. Treat its values as a teaching dataset; project grading must use the current verified survey and authorized design surfaces.
- Spot elevation
- 176.5 m
- Local slope
- 23.8%
- Downslope azimuth
- 298°
- Profile average grade
- 1.93%
- Profile relief
- 94.6 m
- Contours drawn
- 17
Contour segments reuse one precomputed terrain grid, avoiding repeated terrain sampling when only the contour interval changes.
Local slope uses deterministic finite differences over 25 m east and north.
The section samples the same terrain function, preserving map-profile consistency.
Classroom terrain only. Survey datum, breaklines, TIN construction, interpolation, contour smoothing, hydrology, and grading decisions require controlled project data.
Grading Logic
Grading should express where water is expected to move and how surfaces connect. Check that local low points are intentional, ramps and walkways tie into building entries, surface changes do not create unexplained steps, proposed contours agree with spot levels, and grade breaks connect to the drainage system. Any design criterion such as minimum/maximum slope remains project- and code-specific and must come from the authorized design basis.
Grade-to-Drainage Relationship
A grading drawing is readable when each surface has a controlled elevation logic and each low point has an intended drainage destination.
- FFL and threshold levels agree with the building drawings
- Spot elevations create a continuous surface
- Low points align with approved drainage inlets
- Contours, arrows, and sections tell the same story
- Civil and architectural levels use different references
- A grade break creates an unintended ponding pocket
- An inlet is above the surrounding low point
- Plan grades and section grades contradict each other
5. Site Drainage and Stormwater Drawings
Drainage and Civil-Utility Design-Source Hierarchy
Drainage and civil-utility geometry should be traceable to a controlled technical source rather than inferred from drafting convenience. Use the hierarchy applicable to the project:
- the responsible civil professional's authorized design and calculations;
- the verified survey, benchmark, coordinate system, and vertical datum;
- the project hydrologic/hydraulic design and approved drainage catchments or contributing areas;
- receiving-system, discharge, tailwater, flood-level, or outfall constraints supplied by the responsible design/authority;
- utility-owner or service-provider requirements for connection, separation, access, protection, and maintenance; and
- the applicable current DPWH, LGU, project, and authority standards adopted for the work.
For DPWH-governed work, verify the project-adopted DPWH Design Guidelines, Criteria and Standards (DGCS), current Department Orders, Standard Specifications, and project-specific criteria. DPWH Department Order No. 97, s. 2024 continues to cite the 2015 DGCS, including Volume 3: Water Engineering Projects, within current water-management guidance. This does not make DPWH criteria universal for every private/LGU project, and it does not authorize the drafter to select return periods, pipe sizes, velocities, slopes, freeboards, or other hydraulic criteria.
Surface and Subsurface Drainage Information
Depending on the authorized design, drawings may show catch basins, area drains, trench/channel drains, manholes, swales, gutters, channels, culverts, storm pipes, detention or treatment interfaces, discharge points, and connections to approved receiving systems. Show identifying marks, relevant rim/grate and invert levels, flow direction, pipe or channel information supplied by the design, and references to profiles/sections/details where required.
Drainage Continuity Check
A stormwater path should be traceable from the contributing surface to the approved discharge or storage interface. Verify that the plan, longitudinal information, structure schedule, and civil sections agree on structure IDs, flow direction, inverts, crossings, and outlet conditions. Do not assume an existing drain has adequate capacity or permission for connection without the required design/authority confirmation.
6. External Water, Sewer, and Utility Corridors
Utility Plan Information
External utility drawings may include potable/service water, sanitary sewer, storm drainage, fire-service, electrical/communications ducts, fuel or other services as applicable. Show route, service point, structures, valves or chambers, crossings, offsets, levels/inverts where controlled, sleeves/casings where specified, and building entry/interface points. Where several services occupy an approved utility corridor, show its controlling limits or offsets and preserve enough coordinated space for crossings, structures, installation, access, and maintenance rather than treating each line independently. The discipline responsible for each system remains defined by the project and applicable professional laws.
Utility Crossings
A crossing is a three-dimensional coordination problem. Plan separation alone is insufficient: check invert/elevation, pipe or duct outside dimension, required clearance from the authorized criteria, structure depth, excavation/installation sequence, sleeves or protection, and accessibility for maintenance. If the required separation cannot be achieved, the drawing should identify the conflict for professional resolution rather than conceal it with a graphical offset.
7. Roads, Driveways, Parking Interfaces, and Access
Access Geometry
Show the approved site access and its relationship to the public road or property boundary, including driveway edges, curb returns, ramps, walkways, loading/parking interfaces, gates, and transition points. Where profiles or cross-sections are needed, coordinate horizontal geometry with vertical grades and building entry levels.
Parking and Pedestrian Coordination
Civil drawings should align pavement limits, curb lines, islands, drainage paths, wheel stops or barriers where specified, pedestrian crossings, accessible routes, landscape zones, and building entrances with the architectural site plan. Dimensions and accessibility criteria must come from the applicable approved design and governing requirements; do not infer them from a generic template.
8. Retaining/Site Structures, Civil Sections, and Details
Retaining and Site Structures
Where retaining walls, headwalls, channels, culverts, tanks, pits, equipment pads, or similar structures form part of the site works, civil drawings should identify their location, extents, controlling levels, interfaces, drainage provisions, and structural references. Structural sizes and reinforcement belong to the responsible structural design unless the civil engineer is also the responsible professional for that work under the project scope.
Civil Sections and Details
Use sections where plan information cannot adequately communicate vertical relationships. Typical sections include building-to-site transitions, road/driveway profiles, retaining-wall interfaces, drainage channels, utility crossings, pavement build-ups, curb/gutter relationships, and property-boundary conditions. Every section/detail callout must resolve to a valid current reference, use the same applicable datum/control basis as the plan, and belong to a coordinated issue/revision state. Different sheets do not need identical revision numbers or dates if each is the current authorized revision and their interfaces agree.
9. General Notes, Legends, and Drawing Organization
Civil Sheet Organization
A practical set may include:
- cover/general civil notes and legend;
- vicinity/location and survey-control information;
- site development plan;
- grading and drainage plan;
- utility plan;
- road/driveway profiles or grading sections;
- drainage/utility profiles or schedules where applicable;
- civil sections and details;
- demolition/existing-condition information when required.
The exact arrangement should follow project complexity, permit requirements, office standards, and readability rather than a rigid sheet count.
General Notes
General notes should identify the governing project documents, units, datum/control basis, existing-condition verification requirements, coordination obligations, and discipline-specific construction requirements supplied by the responsible professional. Avoid notes that contradict details or duplicate a value in several places. A single controlled source for a requirement is safer than repeated inconsistent instructions.
10. Multidisciplinary Coordination and Release Review
Civil/Site Drawing Coordination Review
Trace the controlled survey and building basis through grading, drainage, utilities, interfaces, and release readiness.
Use one controlled coordinate/elevation basis. A failed check is documented and held for authorized professional resolution; the reviewer does not invent a property, grading, drainage, utility, or structural solution.
Start civil/site drawing review → Current survey, architectural, civil, structural, plumbing, and utility inputs; Current survey, architectural, civil, structural, plumbing, and utility inputs → Verify property, coordinates, benchmark, datum, building location, and FFL; Verify property, coordinates, benchmark, datum, building location, and FFL → Check access, grading, contours, spot elevations, and drainage paths; Check access, grading, contours, spot elevations, and drainage paths → Check storm, sewer, water, utility routes, crossings, and building entries; Check storm, sewer, water, utility routes, crossings, and building entries → Trace civil sections, site structures, ramps, thresholds, and external interfaces; Trace civil sections, site structures, ramps, thresholds, and external interfaces → Are geometry, levels, references, and revisions compatible?; Are geometry, levels, references, and revisions compatible? — Yes → Record coordinated civil/site package for responsible review; Are geometry, levels, references, and revisions compatible? — No → Record conflict, missing value, source, and affected drawings; Record conflict, missing value, source, and affected drawings → Has an authorized professional response been issued?; Has an authorized professional response been issued? — Yes → Update only the controlled affected drawings and references; Has an authorized professional response been issued? — No → Hold affected issue until resolution; Update only the controlled affected drawings and references → Do updated plans, sections, levels, and interfaces now agree?; Do updated plans, sections, levels, and interfaces now agree? — Yes → Ready for issue under project authorization; Do updated plans, sections, levels, and interfaces now agree? — No → Hold affected issue until resolution; Record coordinated civil/site package for responsible review → Ready for issue under project authorization
- Start civil/site drawing review: terminator
- Current survey, architectural, civil, structural, plumbing, and utility inputs: data
- Verify property, coordinates, benchmark, datum, building location, and FFL: process
- Check access, grading, contours, spot elevations, and drainage paths: process
- Check storm, sewer, water, utility routes, crossings, and building entries: process
- Trace civil sections, site structures, ramps, thresholds, and external interfaces: process
- Are geometry, levels, references, and revisions compatible?: decision
- Record coordinated civil/site package for responsible review: document
- Record conflict, missing value, source, and affected drawings: document
- Has an authorized professional response been issued?: decision
- Update only the controlled affected drawings and references: process
- Hold affected issue until resolution: terminator
- Do updated plans, sections, levels, and interfaces now agree?: decision
- Ready for issue under project authorization: terminator
Civil Review Case: A Route Reaches the Site Boundary
A drainage line is continuous within the site plan but stops at the boundary. That does not establish a usable discharge connection.
Identify the receiving point, connection authority, controlling levels/datum, available receiving-system information, and the responsible designer's discharge basis. Compare plan, profile, details, and utility information for the same connection identifier. Keep missing external information as an assigned interface issue rather than drawing an assumed outlet. Closure requires an authorized, technically coordinated connection across the boundary; internal line continuity alone cannot demonstrate that the receiving system is available or suitable.
- Control Comes First: Property geometry, survey coordinates, benchmarks, datums, and revisions are the reference frame for every site drawing.
- FFL Is a Multidisciplinary Interface: Building floor levels must align with grading, entries, foundations, drainage, and utilities.
- Grading and Drainage Are One System: Surface geometry should make the intended water path legible from high points to approved collection/discharge points.
- Utilities Are Three-Dimensional: Crossings require plan position, elevation/invert, clearance criteria, structure depth, access, and sequencing checks.
- Do Not Invent Missing Design: Record discrepancies and obtain authorized resolution before issuing construction information.
References
- Republic Act No. 544, as amended by Republic Act No. 1582 — Civil Engineering Law (Professional Regulation Commission PDF)
- Republic Act No. 8560 — Philippine Geodetic Engineering Act of 1998 (Lawphil)
- Republic Act No. 9200 — Amendment to Republic Act No. 8560 (Lawphil)
- Presidential Decree No. 1096 — National Building Code of the Philippines (Senate Legislative Reference Bureau)
- DPWH Department Order No. 97, s. 2024 — Guidelines for the Integration of Comprehensive Water Management in Flood Control Projects
- DPWH 2025 public project plans — current example citing DGCS Volume 3 (2015) and DPWH Standard Specifications Volume III (2019)
- ISO 128-1:2020 — Technical product documentation: General principles of representation
- ISO 7200:2004 — Data fields in title blocks and document headers
These references support professional-scope awareness, building/site documentation, technical-drawing representation, document control, and the current DPWH water-management context. DPWH Department Order No. 97, s. 2024 cites the 2015 DGCS, including Volume 3: Water Engineering Projects, and current 2025 DPWH project plans continue to cite DGCS Volume 3 (2015) together with the applicable DPWH Standard Specifications. These citations establish current DPWH usage, not universal criteria for every LGU/private project; use the edition and requirements actually adopted by the project/authority. Project-specific survey data, hydrologic/hydraulic design, utility-owner requirements, receiving-system constraints, adopted codes, and approved professional documents govern the actual work.