10 public references
Three reconciliation layers
One obligation-level unit
Right-of-way files often contain two parallel truths. The payment ledger says an obligation is paid. The easement folder says the agreement is signed but not recorded. A third system says the payee address changed. Reconciliation is the work of making those statements agree, or documenting why they cannot.
This study design describes how to measure reconciliation quality for right-of-way payment obligations. It is an administrative research protocol. It does not interpret an easement, determine ownership, approve a payment, or replace review by counsel or a qualified right-of-way professional.
Right-of-Way Payment Reconciliation Study: Research question and boundary
The primary question is: for a defined population of right-of-way payment obligations, what proportion is reconciled across the easement record, the payee record, the payment record, and the recording record, and what is the age and reason mix of the items that are not?
The unit is one payment obligation tied to one easement or option, one tract, and one payee. A single project can produce many units. A single easement can produce an option payment, a damage payment, an installment, and a final payment, each with its own trigger and evidence.
The study measures administrative reconciliation, not the legal sufficiency of an easement or the correctness of a damage amount. Those are reviewer questions outside the measurement boundary.
Three reconciliation layers
The first layer is the land right. The file should show the grantor, grantee, tract, rights granted, term, and the executed easement or option. The second layer is the payment. The file should show the obligation, amount, trigger, approval, release, delivery, and clearing. The third layer is the recording. Where the agreement or the client's procedure requires recording, the file should link the accepted recorded copy.
A unit can reconcile at one layer and fail at another. A payment may clear while the easement remains unrecorded. An easement may be recorded while a damage payment remains open. The study should report the layers separately before reporting a combined reconciliation rate.
The right-of-way payment status ledger describes the operating record. This study design tests whether the record reconciles across a cohort.
Why reconciliation fails
Common failure modes are structural rather than mysterious. The payment system uses a payee ID that does not match the easement grantee. The recording office returns a document for a description defect, and the payment is not updated. A damage claim is paid from a project cost code that is not linked to the tract. A final payment is released before the recording condition is met. A returned check is reissued without preserving the original event.
Each failure has a different control. A payee crosswalk addresses the first. A recording rejection packet addresses the second. A tract-level cost code addresses the third. A trigger checklist addresses the fourth. A payment event history addresses the fifth.
Data sources and methodology
Build the cohort from the payment obligation register, not from a folder inventory. Record the extraction date, the project, the workflow version, and the number of obligations. Exclude duplicate obligations only under a written rule. Keep amended or reissued obligations linked to the original.
| Layer |
Evidence required |
Failure state |
Reported measure |
| Land right |
Executed easement or option, tract, parties |
Missing or unsigned |
Right-layer complete rate |
| Payment |
Approval, release, delivery, clearing |
Any gate missing |
Payment-layer complete rate |
| Recording |
Accepted recorded copy and reference |
Pending or rejected |
Recording-layer complete rate |
| Crosswalk |
Same tract and payee identifiers |
Mismatch |
Crosswalk exception count |
| Open items |
Reason, owner, next date |
No owner or date |
Aging by reason |
The evidence base provides general context on right-of-way practice, infrastructure records, public land, privacy, and data quality. It does not establish a legal standard for a particular easement or jurisdiction.
- FHWA Uniform Act resources
- FHWA real estate programs
- PHMSA pipeline safety
- EIA natural gas data
- BLM land records
- NARA Records Management
- NIST Privacy Framework
- GAO Data Reliability Assessment
- Federal Register
- DOI Natural Resources Revenue Data
Cohort and stratification
Stratify by payment type, project, payee type, and recording status. Payment types behave differently: an option payment may precede the easement, while a final payment may follow recording. Mixing them in one rate obscures the trigger logic.
If the population is large, draw a reproducible sample before inspecting outcomes. If the question is about a specific failure, such as unrecorded easements, a targeted cohort is more useful than a representative sample. State which design is being used and avoid generalizing a targeted review to the whole portfolio.
Measures and denominators
Report the number of obligations in the frame, the number eligible, the number reviewed, and the number open at the cutoff. Then report each layer and the combined reconciliation rate. A combined rate should require all applicable layers, including recording where the agreement makes it a condition.
Report median age for open items and bands at 30, 60, 90, and 180 days. Separate items waiting on the owner, the recorder, the payment processor, and the internal reviewer. A single aging number hides the dependency.
Reliability review
Two reviewers should classify a planned subset. The codebook should define what counts as an accepted recorded copy, what counts as delivery evidence, and how a reissued payment is treated. Preserve the initial ratings before adjudication.
Disagreement often appears at the boundary between "recording pending" and "recording not required." The reviewer should apply the agreement and the client's procedure, not a default assumption. If the agreement is ambiguous, record the ambiguity rather than forcing a yes or no.
Analysis and sensitivity
Begin with a flow table and a layer table. Then compare projects or periods only after confirming that the payment type mix and the recording rule are similar. A project with more option payments may look better on the recording layer simply because recording occurs later.
Run sensitivity checks with and without obligations that are not yet due, with strict and operational definitions of delivery, and with open items assigned to the oldest age band. If the ranking changes, report the sensitivity rather than a single ranking.
Bias and alternate explanations
Reconciliation can be affected by project mix, county recorder turnaround, payee turnover, system migration, and the timing of the analysis. A file that looks unreconciled may be waiting on a recorder who has not returned the document. A file that looks reconciled may link a recorded copy for the wrong tract.
The study should distinguish a missing record from a record that exists but is not linked. The first is an evidence gap; the second is an indexing or crosswalk problem. They require different fixes.
Keep payee names, addresses, banking details, and executed easements in the approved source system. Use study identifiers in the analytic table. Suppress small cells where an owner could be identified. Follow the client's retention and access rules.
Interpretation limits
The study describes administrative reconciliation under a declared workflow. It cannot determine whether an easement is enforceable, whether a payment amount is correct, or whether a recording is legally sufficient. It cannot prove that an unrecorded payment was improper. It can show where the file does not support a review.
Decision threshold
Define in advance what result triggers a project review, a recorder follow-up, a payee crosswalk cleanup, or a larger sample. A cluster of unrecorded easements may trigger a recording review. A cluster of payee mismatches may trigger a data cleanup. The threshold should not authorize an automatic payment or legal action.
Worked analytic scenario
A team extracts all right-of-way obligations for one quarter and stratifies by payment type. It reviews the land right, payment gates, and recording link for each unit. Two reviewers classify a subset and clarify the treatment of an option payment that precedes recording.
The analyst reports the layer rates, the open-age bands, and the top three failure reasons. The project owner uses the list to assign recorder follow-up, payee crosswalk cleanup, and payment evidence requests. The list is a review aid, not a finding that any payment was improper.
Limitations
The design depends on the completeness of the obligation register. If a payment was made outside the register, the study will not see it. If a recorded copy is stored in a personal folder, the study may classify it as missing. The report should describe these limits and the steps taken to search for off-register records.
Frequently asked questions
Is reconciliation the same as audit?
No. Reconciliation tests whether records agree and whether required evidence is linked. An audit may test substantive compliance, authorization, and accuracy.
Should an unrecorded easement always block payment?
That depends on the agreement and the client's procedure. The study records the condition; the authorized reviewer decides the payment consequence.
Can the study be used for a single pipeline project?
Yes. A project-level census is often the most useful first step because it exposes the crosswalk and recording gaps that a portfolio average would hide.
Conclusion
Right-of-way payment reconciliation is a layered test. A payment can clear while the land right or the recording link is incomplete. The useful measure is the proportion of obligations that reconcile at each applicable layer, with open items and dependencies visible. That result gives project teams a concrete follow-up list and gives reviewers a defensible description of what the file does and does not prove.
To review a right-of-way file against this model, Book a free consultation. The lease bonus payment evidence completeness study provides a comparable gate-level method for lease payments.
