Module 5: Occupation, Encroachments, Plans, and Government Processing

Module 5: Occupation, Encroachments, Plans, and Government Processing

$Learning Objectives$

Locate fences, walls, buildings, roads, easements, and other visible occupation or improvement features relative to the surveyed parcel.
Describe apparent encroachments, overlaps, gaps, and record conflicts using neutral technical language.
Prepare internally consistent plans, coordinate tables, technical descriptions, corner records, and survey reports.
Distinguish a relocation/boundary deliverable from subdivision, consolidation, or other work requiring formal approval and registration steps.
Identify the competent plan-approval path for the transaction, including DENR-approved plans where applicable, and the current LRA/Registry of Deeds requirements for registration and electronic technical descriptions.

$Occupation Line$

An occupation line is a visible line or feature by which land is physically used, enclosed, or treated on the ground, such as a fence or wall. It is survey evidence to be measured and evaluated; it is not automatically identical to the registered or retraced parcel boundary.

$Apparent Encroachment$

For this training, an apparent encroachment is a measured condition in which a visible improvement or occupation feature crosses or lies beyond the surveyed boundary under the stated survey basis. The survey report should describe the geometry without making unsupported legal conclusions about rights or liability.

$Station$

Station is the measured distance along a stated alignment from a specified origin, with an explicitly identified increasing direction. On a property boundary, the course, starting corner, and station direction must be stated.

$Signed Offset$

A signed offset is a perpendicular distance from a stated alignment to a measured feature, with its positive and negative sides defined in the project record. The sign has no parcel meaning unless the subject-parcel side and convention are explicitly identified.

Linear Interpolation of a Signed Offset

Estimates where a feature's signed perpendicular offset reaches zero between two measured stations, assuming the offset changes linearly over that interval.

\begin{aligned} d(s)&=d_1+\frac{d_2-d_1}{s_2-s_1}(s-s_1) \\ s_0&=s_1-\frac{d_1(s_2-s_1)}{d_2-d_1} \end{aligned}

Variables

Symbol	Description	Unit
$s$	Station along the identified boundary course	m
$s_1$	First observed station	m
$s_2$	Second observed station, with s_2 not equal to s_1	m
$d(s)$	Linearly interpolated signed offset at station s	m
$d_1$	Signed offset measured at station s_1	m
$d_2$	Signed offset measured at station s_2	m
$s_0$	Interpolated station where d(s) equals zero	m

$Limits of Offset Interpolation$

Use only measurements tied to the same verified boundary course, origin, increasing station direction, and perpendicular-offset convention. A zero crossing is an interpolated geometric indication between the observations. It is not a boundary determination or legal conclusion. The zero-crossing formula requires the offset difference d₂ − d₁ to be nonzero: a pair of same-sign nonzero offsets has no crossing under linear interpolation, while two zero offsets do not define a unique crossing station.

Do not interpolate across a parcel corner, curve, kink, unverified coordinate change, or a long interval that hides a turn in the feature. Add observations where the wall, fence, or other feature changes direction, and report interpolation assumptions and field-measurement precision.

$Survey the Boundary and the Occupation Separately$

When the client's purpose includes fencing, design, acquisition, due diligence, or dispute investigation, measure relevant physical features such as:

fences and walls;
building corners, eaves, canopies, and other projections when material;
roads, curbs, drainage, and access routes;
easements or right-of-way features shown by the record;
utilities or structures affecting corner access;
waterways or other natural features when they form or influence the surveyed description;
adjoining occupation features needed to explain the field condition.

Plot them as distinct features rather than moving the boundary line to match occupation.

Survey Deliverable and Processing Decision

Separate documentation of an existing parcel from work that changes parcel configuration, then confirm the competent current approval and registration path. Verify the applicable path against current requirements before filing.

$Neutral Encroachment Reporting$

Prefer measured statements:

“The existing concrete wall is observed 0.42 m inside the retraced parcel boundary at the stated location.”
“The roof projection extends approximately 0.18 m beyond the surveyed boundary based on the observations shown.”
“The fence alignment does not coincide with the retraced boundary; offsets range from the values tabulated on the plan.”

Avoid unsupported statements:

“The neighbor stole 0.42 m of land.”
“The wall is illegal.”
“The fence proves ownership.”

If the boundary itself remains disputed or technically unresolved, state that limitation before describing the offset.

Boundary Versus Occupation

Both should be measured, but they represent different kinds of information.

The comparison prevents a common category error: treating physical occupation as if it automatically defines the surveyed parcel.

Surveyed Boundary

Derived from reconciled survey evidence
Shown with bearings/distances or coordinates
Subject to the applicable approved records
Supports parcel geometry

Occupation / Improvement

Fence, wall, building, road, use line
Measured as field feature
May coincide or differ
Does not by itself decide legal ownership

$Plan and Report Consistency$

A property-survey package may include, as appropriate:

plan showing parcel lines, bearings, distances, corner IDs, monuments, adjoining information, north/reference information, and relevant improvements;
coordinate table with stated reference system;
technical description;
corner/monument record;
field notes and computation archive;
photographs or sketches;
discrepancy/encroachment table;
concise survey report explaining purpose, records used, method, findings, limitations, and unresolved issues.

Every repeated value should agree across the plan, technical description, coordinate table, and report.

$Survey Deliverable Production and Cross-Check Procedure$

STEP-BY-STEP

Freeze one checked boundary model. Complete the evidence review and identify the coordinate/bearing-distance geometry from which released documents will be generated.
Generate each deliverable from that model. Use consistent corner IDs, sequence, bearings, distances, coordinates, area, and reference-system information.
Add occupation as separate geometry. Show fences, walls, projections, roads, and other material improvements without replacing the surveyed boundary.
State discrepancies neutrally. Report measured offsets, source conflicts, and unresolved evidence with the certainty actually supported by the survey.
Cross-check every repeated value. Compare plan, technical description, coordinate table, corner records, encoded data, and narrative report before signature or submission.
Verify the current processing path. For subdivision, consolidation, or covered registration work, confirm current official agency requirements instead of relying on an old checklist.
Release only a mutually consistent package. Any conflicting course, point of beginning, parcel identifier, or material limitation is a release blocker until reconciled.

Survey Deliverable Traceability

Checked boundary geometry should drive all downstream survey documents consistently.

The deliverable sequence emphasizes one source of checked geometry feeding every published document.

Verified records and field observations

Checked computation model

Plan and coordinate table

Technical description / corner records

Survey report and submission package

$Subdivision and Consolidation Are Not Just Drafting Tasks$

When the requested work changes parcel configuration for registration, the survey includes more than drawing proposed lot lines. The Geodetic Engineer must address the applicable survey authority, field survey, computations, monuments, survey returns, plan approval, technical descriptions, and registration requirements.

Do not hard-code one approving agency for every subdivision or consolidation. The current LRA Citizen's Charter includes an LRA central-office service for approval of subdivision/consolidation plans, while LRA registration guidance also recognizes plans approved by LRA or the Land Management Bureau and the eTD program specifically addresses DENR-approved plans submitted for registration. The correct path therefore depends on the survey class, source records, transaction, and current agency rules.

Confirm the current competent approving authority and the current LRA/Registry of Deeds registration requirements before submission rather than relying on an old office checklist.

Subdivision / Consolidation Processing Stack

A registered parcel change passes through survey production and the applicable approval and registration layers.

The processing stack shows the relationship between technical survey production, plan approval, and land-registration documents.

Survey authority / records basis

Field survey and computations

Survey returns / plan preparation

Current competent plan-approval path

LRA / Registry of Deeds registration documents

$Electronic Technical Descriptions$

LRA Circular No. 04-2020 introduced mandatory encoded technical descriptions (eTD) for covered registration transactions involving plans and resulting titles, and LRA Circular No. 20-2020 later clarified the submission requirement. Treat eTD as a controlled data-transfer step: the encoded description must agree with the applicable approved survey documents and the surveyor's checked geometry.

Do not generalize a 2020 transaction list into a permanent rule for every future filing. Verify the currently applicable LRA/Registry of Deeds instructions, covered transaction, format, and submission channel at the time of filing.

$Apparent Overlaps and Gaps$

If plotted records or field retracement suggest an overlap or gap:

verify parcel and adjoining identifiers;
verify the reference system and control;
confirm the correct approved plans and technical descriptions;
independently recompute the common line;
inspect recovered monuments and occupation;
research adjoining or parent survey records;
distinguish a drafting/record inconsistency from a true field conflict;
report the technical finding and limitation without adjudicating ownership.

Do not “split the difference” merely to produce a neat plan.

Objective Boundary-Condition Reporting

A defensible report separates what was observed, what was computed, and what remains unresolved.

The grid focuses report language on measured facts, sources, and uncertainty.

Observed feature and measurement

Record source

Survey computation

Boundary interpretation

Uncertainty / limitation

Recommended next technical step

$Client Communication$

Before release, explain:

what survey was performed;
what records controlled the analysis;
which corners were found, recovered, set, or not resolved;
whether occupation differs from the surveyed boundary;
what the plan can and cannot establish;
whether further agency processing is required;
whether unresolved conflict should be referred for additional records research, agency action, or legal advice.

The client should leave with a realistic understanding of the survey, not just a set of stakes.

Finding-to-Client Communication Loop

Technical results should be explained with their evidence and limitations before the survey is treated as complete.

The communication loop is complete only when the client understands findings, limitations, and required next actions.

Understandable survey conclusion

Measure

Analyze

Document

Explain

Clarify next action

↺ repeat when checks fail

Key Takeaways

Measure occupation and improvements separately from the surveyed boundary.
Report apparent encroachments as objective geometry, not accusations or legal conclusions.
Plans, coordinate tables, technical descriptions, and reports must agree with one checked survey model.
Subdivision and consolidation involve formal survey approval and registration processes beyond ordinary relocation work.
Verify the current competent approval authority plus LRA/Registry of Deeds requirements at the time of filing, including electronic technical-description procedures where applicable.

$References$

Land Registration Authority Frequently Asked Questions — Land Registration Authority.
LRA Citizen's Charter 2025, 1st Edition — Approval of Subdivision / Consolidation Plans — Land Registration Authority.
LRA Circular No. 04-2020 — Mandatory Requirement for the Submission of Encoded Technical Descriptions for Registration of Plans and Issuance of Resulting Titles — Land Registration Authority.
LRA Circular No. 20-2020 — Clarification on the Requirement for the Submission of Encoded Technical Descriptions in Relation to Circular No. 04-2020 — Land Registration Authority.
DENR Administrative Order No. 2007-29 — Revised Regulations on Land Surveys — Department of Environment and Natural Resources.
Republic Act No. 8560 — Philippine Geodetic Engineering Act of 1998 — Lawphil / Congress of the Philippines.

Previous TopicModule 4: Boundary Retracement, Computation, and Monumentation - Worked Examples

Quiz Me

Next TopicModule 5: Occupation, Encroachments, Plans, and Government Processing - Worked Examples

Prev Next

Quiz Me