Module 4: Site, Property, and Existing-Condition Information
Learning Objectives
- Identify the property, survey, topographic, access, utility, hazard, geotechnical, and existing-condition information needed before dependable design development.
- Distinguish client-supplied records, field observations, official records, verified survey information, and assumptions requiring confirmation.
- Interpret the purpose of technical descriptions, bearings and distances, lot limits, control points, benchmarks, contours, and elevation information without inventing missing survey data.
- Establish a controlled Project Base File that provides one traceable multidisciplinary reference for location and existing conditions.
- Apply hold points when parcel identity, site geometry, levels, access, utilities, hazards, or other critical information remains unresolved.
Project Base File
A Project Base File is the controlled multidisciplinary reference containing the current verified property, survey, topographic, existing-condition, access, utility, and related site information used as the common spatial basis for project design.
Technical Description
A technical description is a formal description of a parcel or surveyed lot using prescribed survey information such as point references, bearings, distances, and related identifiers. Its legal and surveying significance depends on the authoritative record and applicable land-survey procedures.
Control Point
A control point is a surveyed reference point with established position used to control the location of subsequent survey or construction measurements.
Benchmark
A benchmark is a reference point with an established elevation used to transfer and check vertical control. The datum and source of the elevation must be known before it is used as a project basis.
Topographic Survey
A topographic survey records the horizontal and vertical position of relevant natural and constructed features so that terrain, levels, drainage paths, access, structures, and other site conditions can be represented for planning and design.
Information Provenance
Information provenance is the traceable record of where project information came from, who produced or supplied it, when it was created or verified, what revision it represents, and what limitations apply to its use.
Why Site Information Must Precede Reliable Geometry
For the progressive two-storey community/institutional building, architectural and structural drafting cannot be treated as reliable until the team knows what property is being designed on and what site geometry controls the work.
A drawing can look precise while being based on poor evidence. Examples include:
- tracing lot lines from an online basemap;
- using a fence as the legal boundary without survey confirmation;
- assuming that the road elevation is the project benchmark;
- copying utility lines from an old plan that has not been verified;
- assuming that a nearby drain establishes the permitted discharge point;
- using photographs to estimate floor elevations;
- reproducing an old renovation drawing without confirming that the building was constructed as shown.
The professional objective is not to collect the largest number of documents. It is to establish which evidence is current, authoritative, technically appropriate, and fit for the specific design decision.
Site Information Evidence Stack
Different evidence types can support different decisions; they should not be treated as interchangeable.
Property and Title Information
Property records help establish the legal and documentary context of the site.
Useful records may include:
- current certified copy of title where applicable;
- lot, block, plan, and survey references;
- registered annotations affecting the property;
- technical description;
- approved survey plans or cadastral records where available;
- records concerning rights-of-way, easements, restrictions, or encumbrances;
- tax and local property records where relevant to project administration.
A title record and a field survey answer different questions. A title identifies the registered property and the matters stated in the registration record, while a competent geodetic survey locates or reconstructs the parcel geometry from the controlling technical description, approved survey information, monuments, control, and field evidence appropriate to the task. A survey plan is not, by itself, a conveyance or conclusive proof of ownership. Designers should not convert documentary references into field coordinates by assumption, and they should not treat a relocation or verification survey as an adjudication of a disputed ownership or boundary right.
Use Government-Issued Property Records for Formal Due Diligence
The Land Registration Authority provides a current eSerbisyo channel for requesting Certified True Copies of titles. Project teams should use appropriate official records and competent professional advice for actual property due diligence rather than relying on screenshots, broker summaries, or unofficial reproductions.
Survey Plans and Technical Descriptions
Survey information may include:
- lot corner identifiers;
- bearings and distances;
- tie lines or reference information;
- survey plan number;
- surveyor or geodetic engineer information;
- approved-plan references;
- coordinate or control information;
- technical descriptions;
- lot area;
- adjoining parcels or roads;
- monuments and boundary evidence.
Under DENR Administrative Order No. 2007-29, isolated survey plans are prepared in prescribed formats and the original plans are signed and sealed by the Geodetic Engineer; a technical description for each lot is prepared upon approval of the survey plan and signed by the concerned Geodetic Engineer. The design team should preserve the plan identity, approval/status information, and source rather than redrawing the parcel and losing its provenance.
If different survey records disagree, the correct response is not to average the values. Open a discrepancy, identify the controlling source or obtain competent verification.
Boundary Record Versus Field Condition
Legal or survey boundary evidence and visible occupation are related but not identical datasets.
- Title and plan references
- Technical description
- Surveyed lot corners
- Bearings and distances
- Approved survey records
- Fences and walls
- Existing buildings
- Road edges
- Trees and improvements
- Apparent access paths
A Fence Is Not Automatically the Property Boundary
Fences, walls, hedges, paths, and other occupation features can be important evidence of existing conditions, but their visible location should not be substituted for a verified parcel boundary when boundary location controls design, setbacks, access, or construction.
Bearings, Distances, Lot Limits, and Control
Bearings and distances describe survey geometry. Their correct use depends on the source survey, reference system, and professional interpretation.
Before using them in a design base, establish:
- which survey or technical description they came from;
- whether the information is approved or otherwise authoritative for the intended purpose;
- whether the lot corners have been verified or recovered in the field;
- what coordinate or reference system is being used;
- whether transformations or legacy datums are involved;
- whether the plotted parcel agrees with the current field survey;
- how project control will be related to the parcel.
Do not infer a coordinate system from the appearance of a drawing.
Do Not Mix Coordinate Reference Frames or Epochs
Coordinate labels that look numerically similar are not automatically compatible. As of 2026-10-05, NAMRIA PAGeNet offers real-time corrections in multiple reference frames, including PGD2020, WGS84 (2010 adjustment), and the original WGS84 realization used with older control. The Project Base File should record the actual reference frame, datum realization, epoch where relevant, and transformation method. Coordinates from different frames or realizations should not be combined until a competent geodetic professional has established a valid relationship between them.
Benchmarks, Elevations, and Vertical Datum
Elevation data requires the same discipline as horizontal location.
The Project Base File should identify:
- the benchmark used;
- benchmark description and physical location;
- source of the benchmark elevation;
- vertical datum or reference basis;
- survey date;
- relationship between survey levels and architectural project levels;
- any local temporary benchmark established for construction;
- checks performed before the benchmark is reused.
A project level such as “Ground Floor = 0.000” is a design convention. It becomes meaningful in the real world only when its relationship to the verified site elevation datum is defined.
Vertical Control Chain
Design levels become buildable only when their relationship to a verified elevation reference is explicit.
Topographic Survey and Contours
A topographic survey should capture the features needed for the actual project, which may include:
- ground elevations;
- contours or spot levels;
- road and curb levels;
- drainage channels and inlets;
- existing buildings and structures;
- walls, fences, and major improvements;
- trees and significant vegetation;
- poles, manholes, hydrants, visible utility features, or service entries;
- watercourses and drainage paths;
- slope breaks;
- adjacent features that materially affect access, drainage, retaining, or construction.
Contour interval and survey extent should be appropriate to the site and design need. A small urban parcel, steep hillside, flood-sensitive site, or large campus may require different field detail and survey extent.
Adjoining Properties, Roads, and Access
Design does not stop at the lot line when external conditions control the project.
Investigate:
- legal and physical access;
- public or private road relationship;
- road width and edge condition;
- curb, gutter, sidewalk, and drainage;
- adjoining building proximity;
- retaining walls or slope conditions;
- gates and delivery access;
- emergency and service access requirements;
- construction access and staging constraints;
- potential rights-of-way or easements.
The existence of a visible path or driveway does not establish a legal access right. Likewise, a mapped right-of-way must be related to actual field conditions before it is used for design.
Existing Buildings and Renovation Projects
For renovation, alteration, addition, or adaptive reuse, existing drawings are evidence—not proof that the built structure matches the documents.
A controlled existing-condition investigation may include:
- original and revised drawings;
- as-built or record drawings;
- permits and prior alteration records;
- field measurements;
- structural framing observations;
- material and condition observations;
- equipment and service locations;
- photographs with location and date;
- intrusive investigation where justified and properly authorized;
- survey control for the existing building;
- discrepancy records between drawings and field conditions.
Concealed conditions should remain identified as unknown until exposed, tested, surveyed, or otherwise competently verified.
Existing Utilities
Utility information can come from client records, visible site features, utility providers, prior surveys, scanning or detection work, field investigation, and other sources.
Record, where relevant:
- water service;
- sanitary sewer or septic systems;
- storm drainage;
- electrical supply;
- communications;
- gas or fuel systems where applicable;
- site lighting;
- underground and overhead lines;
- manholes, vaults, meters, poles, transformers, and service entries.
Utility plans may be incomplete or schematic. Before excavation, relocation, connection, or detailed coordination, the team should obtain the level of verification appropriate to the consequence of error.
Underground Utility Evidence and Verification
Subsurface utility information has a reliability problem that must remain visible in the design basis.
- As-built or record drawings may be incomplete, schematic, superseded, or different from the actual installed condition.
- Utility-provider records can identify expected systems, service information, or approximate routes, but they do not necessarily prove the current horizontal position, depth, condition, or presence of every underground line.
- Visible appurtenances such as manholes, poles, meters, valves, boxes, and service entries provide useful clues but do not by themselves establish the full underground alignment or depth between visible points.
- Detection or utility-locating methods may improve the evidence where appropriate, but their suitability and limitations depend on the utility type, site conditions, equipment, operator competence, and project risk.
- Surveyed locations provide controlled position for features that have actually been located or exposed; a surveyed symbol should not imply that an unseen utility was physically verified when it was only inferred.
- Physical exposure or verification, such as an authorized test pit, pothole, or other controlled investigation, may be justified where consequence of error is high, but the method must be selected and performed under the project's safety, utility-owner, excavation, permit, and professional requirements.
A useful evidence progression is:
Evidence hierarchy: provider/record information → site reconnaissance → utility locating where appropriate → surveyed location evidence → authorized physical verification where justified → controlled Project Base File update.
Do Not Design or Excavate from an Assumed Underground Utility Position
Foundation, excavation, trench, retaining, and other high-consequence work should not rely on an underground alignment or depth that is merely inferred from an old drawing or visible endpoint. Keep uncertainty explicitly marked until the project has obtained verification appropriate to the risk. This lesson does not prescribe excavation, potholing, or a specific locating method; intrusive verification must be separately authorized, planned, and performed safely by competent parties under applicable requirements.
Drainage and Water Movement
Site drainage understanding may require more than identifying existing pipes.
Review:
- high and low points;
- apparent overland flow paths;
- roof discharge locations;
- road and gutter levels;
- existing channels and inlets;
- receiving drainage system;
- adjacent runoff;
- erosion evidence;
- ponding evidence;
- historical flooding information;
- topographic controls;
- proposed grading implications.
A photograph taken on a dry day cannot establish flood behavior. Historical evidence, official hazard information, survey data, drainage analysis, and local observations can each contribute different evidence.
Trees and Major Site Features
Major trees, rock outcrops, retaining walls, waterways, monuments, utility structures, neighboring improvements, and other physical features can affect layout, excavation, access, drainage, safety, or permitting.
The base file should distinguish:
- feature observed in the field;
- feature surveyed;
- feature shown on an old plan;
- feature whose legal or regulatory significance still requires confirmation.
Do not assign protected status, ownership, or removal permission solely from visual observation.
Known Hazards, Flooding, and Slope Concerns
Early site screening should identify evidence of hazards that may require specialist investigation or design response.
Examples include:
- mapped flood susceptibility;
- landslide susceptibility;
- steep or unstable slopes;
- erosion;
- seismic and fault-related hazards;
- volcanic hazards where relevant;
- coastal or river hazards;
- fill, made ground, or uncertain ground conditions;
- adjacent retaining or excavation risks.
Official hazard maps and government hazard platforms are screening inputs, not project-specific design investigations. A mapped susceptibility class does not, by itself, establish foundation parameters, slope stability, flood elevations, design discharges, drainage capacity, groundwater conditions, or a site-specific structural response. Where those matters control the project, the responsible team must obtain the appropriate geotechnical, hydrologic/hydraulic, survey, structural, or other specialist investigation.
HazardHunterPH provides multi-agency government hazard information and can support preliminary screening. HazardHunterPH itself describes its generated assessments as indicative; official hazard-assessment documents should be requested from the concerned mandated agency when the project or approving authority requires them. Whether or not an official hazard record is obtained, the project team must still assess the source, scale, date, limitations, and whether project-specific investigation is needed for the actual design decision.
Geotechnical Information
Geotechnical information may include:
- borehole or test-pit logs;
- laboratory test results;
- subsurface profiles;
- groundwater observations;
- engineering parameters;
- foundation recommendations;
- excavation and retaining considerations;
- slope-stability information;
- liquefaction or seismic-site considerations where relevant;
- limitations and recommended further investigation.
The structural or civil designer should not invent soil parameters because the architectural layout is already progressing. When a design decision depends materially on ground behavior, obtain appropriate geotechnical evidence and professional interpretation.
Photographs as Controlled Evidence
Site photographs are useful when they preserve context.
A good photographic record identifies:
- date;
- location or viewpoint;
- direction of view;
- subject;
- relevant scale or dimension where needed;
- relationship to survey or drawing references;
- photographer or source;
- whether the condition was directly observed or supplied by another party.
Photographs should supplement measurement and professional investigation, not substitute for them.
Five Information Classes
Every important site datum should be classified.
- Client-supplied information: received from the client or owner. It may be useful but is not automatically verified.
- Field-observed information: directly observed on site. It describes visible conditions but may not establish concealed, legal, or surveyed facts.
- Officially sourced records: issued or certified by an authority or official custodian for a defined purpose.
- Verified survey information: produced or verified through competent geodetic surveying appropriate to the required decision.
- Assumptions requiring confirmation: provisional information explicitly marked for later verification.
The class should remain visible in the project record until the information is superseded by a more authoritative source.
Information Reliability Is Decision-Specific
Source class matters, but fitness also depends on what decision the information is being used to support.
Creating the Project Base File
- Inventory all property, survey, topographic, utility, geotechnical, hazard, photograph, and existing-building information received.
- Record source, date, author, document identity, revision, coordinate or elevation reference, and stated limitations.
- Separate official records, verified survey information, observations, client records, and assumptions.
- Compare parcel identity, geometry, levels, access, and major existing features across sources.
- Open a discrepancy for contradictions instead of silently selecting the most convenient value.
- Obtain competent verification for information that materially controls design, including underground utilities where their location or depth affects high-consequence work.
- Establish the approved horizontal and vertical project reference.
- Compile the current base geometry and associated source references.
- Issue the Project Base File with a revision identifier and effective date.
- Require affected disciplines to use the same current base and reissue it when verified site information changes.
Project Base File Evidence Gate
Shows how site and property information is classified by source and fitness for use before it becomes part of the controlled Project Base File.
Critical unverified information is held for competent verification; noncritical contextual information remains explicitly provisional and cannot silently become controlling design data.
Site or property information received → Identify source, date, author, revision, datum, and stated reliability; Identify source, date, author, revision, datum, and stated reliability → Classify as official record, verified survey, field observation, client record, or assumption; Classify as official record, verified survey, field observation, client record, or assumption → Source and verification adequate for the intended design use?; Source and verification adequate for the intended design use? — Yes → Evidence consistent with the current Project Base File?; Source and verification adequate for the intended design use? — No → Would unverified use affect parcel identity, geometry, levels, access, utilities, or hazard decisions?; Would unverified use affect parcel identity, geometry, levels, access, utilities, or hazard decisions? — Yes → Obtain competent verification or authoritative record; Would unverified use affect parcel identity, geometry, levels, access, utilities, or hazard decisions? — No → Record as contextual or provisional; do not use as controlling design data; Obtain competent verification or authoritative record → Source and verification adequate for the intended design use?; Record as contextual or provisional; do not use as controlling design data → Issue controlled Project Base File reference; Evidence consistent with the current Project Base File? — No → Open discrepancy and hold affected downstream drafting; Open discrepancy and hold affected downstream drafting → Obtain competent verification or authoritative record; Evidence consistent with the current Project Base File? — Yes → Incorporate fit-for-use information with revision, status, and provenance; Incorporate fit-for-use information with revision, status, and provenance → Issue controlled Project Base File reference; Issue controlled Project Base File reference → Use verified controlling data as coordinated design basis
- Site or property information received: terminator
- Identify source, date, author, revision, datum, and stated reliability: process
- Classify as official record, verified survey, field observation, client record, or assumption: process
- Source and verification adequate for the intended design use?: decision
- Would unverified use affect parcel identity, geometry, levels, access, utilities, or hazard decisions?: decision
- Obtain competent verification or authoritative record: process
- Record as contextual or provisional; do not use as controlling design data: data
- Evidence consistent with the current Project Base File?: decision
- Open discrepancy and hold affected downstream drafting: process
- Incorporate fit-for-use information with revision, status, and provenance: data
- Issue controlled Project Base File reference: document
- Use verified controlling data as coordinated design basis: terminator
Hold Points Protect Downstream Design
Place a documented hold on affected downstream drafting when unresolved information can materially change parcel location, site geometry, levels, access, drainage, utility interfaces, structural support conditions, hazard response, or another critical design basis. A hold is not project paralysis; it identifies exactly what cannot be finalized until evidence is obtained.
Typical Project Base File Hold Points
Examples include:
- title or parcel identity not reconciled with the survey;
- boundary geometry unresolved;
- benchmark or vertical datum unknown;
- topographic survey does not cover the required design extent;
- road or access relationship uncertain;
- utility location or connection point unverified where it controls design;
- existing building dimensions conflict with record drawings;
- concealed structural condition required for alteration remains unknown;
- geotechnical information is absent where foundation or slope decisions depend on it;
- official hazard information identifies a concern requiring specialist evaluation;
- contradictory source documents have not been resolved.
A team may continue non-dependent work, but the drawings should not conceal the unresolved basis.
Philippine Survey and Land-Record Context
Republic Act No. 8560, as amended by Republic Act No. 9200, regulates geodetic-engineering practice in the Philippines. DENR land-survey regulations govern survey-plan and technical-description processes within their scope, while LRA and NAMRIA provide official land-record and geodetic-reference services. Project teams should verify the current agency procedure and the appropriate source for the specific property, survey, coordinate, elevation, or land-record need.
Base-File Review Case: Conflicting Levels
A utility record and a recent site survey show different levels for the same connection. Do not average the values or select the more convenient one.
First compare point identity, datum, units, observation date, source authority, and whether each value is measured, designed, or recalled. Assign a verification task to the appropriate party and identify every drawing that depends on the unresolved level. Keep preliminary studies explicitly provisional; hold the affected gravity connection and construction issue until the controlling value is resolved. Preserve both source records and the resolution so the selected level remains traceable after the base file is updated.
- Reliable design geometry depends on controlled property, survey, level, access, utility, hazard, geotechnical, and existing-condition information.
- Client records, observations, official records, verified surveys, and assumptions are different evidence classes and should remain distinguishable.
- A title, survey plan, field observation, and topographic survey answer different questions; none should be silently substituted for another.
- The Project Base File gives all disciplines one traceable spatial reference with known provenance, revision, and limitations.
- Critical uncertainty creates a hold point; downstream drafting should not invent the missing property, level, access, utility, or ground information.
References
- Republic Act No. 8560 — Philippine Geodetic Engineering Act of 1998 — Lawphil; statutory scope of geodetic engineering and surveying activities.
- Republic Act No. 9200 — Amendment to the Philippine Geodetic Engineering Act of 1998 — Lawphil; amends R.A. No. 8560, including geodetic-engineering consultancy and requirements for survey-plan submission using government-prescribed numbering and projection.
- Heirs of Aurio T. Casiño, Sr. v. Development Bank of the Philippines and Green River Gold, Inc., G.R. Nos. 204052-53, March 11, 2020 — Supreme Court; reiterates that a survey plan is not a conveyance, a mode of acquiring ownership, or conclusive evidence of ownership.
- DENR Administrative Order No. 2007-29 — Revised Regulations on Land Surveys — Department of Environment and Natural Resources; regulations addressing survey plans, survey returns, technical descriptions, and land-survey administration.
- DENR NCR IVAS Corner — Department of Environment and Natural Resources; current land-survey administration resources including survey-return, LAMS/e-survey, and DAO 2007-29 materials.
- LRA eSerbisyo — Land Registration Authority; official online service for requesting Certified True Copies of land titles.
- NAMRIA Geodetic Services — National Mapping and Resource Information Authority; official surveying, mapping, geodetic, and benchmark-related services.
- NAMRIA Products and Geodetic Control Services — National Mapping and Resource Information Authority; official products and services including geodetic control points and topographic mapping.
- NAMRIA PAGeNet Services and Reference Frames — National Mapping and Resource Information Authority; current GNSS reference-frame and correction-service information.
- HazardHunterPH — About and limitations — GeoRisk Philippines / DOST-PHIVOLCS; identifies the platform as an indicative multi-agency hazard-assessment tool and directs users to mandated agencies for official hazard reports.