Skip to content
Editorial title card for Lease Depth Severance Obligation Register
Lease Administration9 min readReviewed October 6, 2026

Lease Depth Severance Obligation Register

A practical lease depth severance obligation register for evidence-led land operations, exception control, and review-ready handoffs.

Table of Contents▾
  1. lease depth severance obligation register: Start with the clause {/* pda6bc0d00032 */} vocabulary
  2. Depth {/* pda6bc0d00044 /} is meaningless without a {/ pda6bc0d00045 */} datum
  3. Connect {/* pda6bc0d00051 /} the well evidence carefully {/ pda6bc0d00052 */}
  4. Construct the {/* pda6bc0d00075 */} retained-interval question
  5. Formation {/* pda6bc0d00093 /} names versus measured footage {/ pda6bc0d00094 */}
  6. Reviewer {/* pda6bc0d00113 */} worksheet
  7. What the register cannot {/* pda6bc0d00127 */} decide
  8. Field {/* pda6bc0d00130 */} notes for depth
  9. Reference {/* pda6bc0d00198 */} desks
  10. A useful finish {/* pda6bc0d00206 */} line

Landman Business | October {/ pda6bc0d00002 /} 6, 2026 | 10 min {/ pda6bc0d00003 /} read

Lease Depth Severance {/* pda6bc0d00004 /} Obligation Register is most {/ pda6bc0d00005 /} useful when it answers {/ pda6bc0d00006 /} a narrow operational question {/ pda6bc0d00007 /} about depth, formation, datum {/ pda6bc0d00008 /}, perforation, and lease. This {/ pda6bc0d00009 /} guide treats the subject {/ pda6bc0d00010 /} as a vertical rights {/ pda6bc0d00011 /} decision ladder: a working {/ pda6bc0d00012 /} record that preserves disagreement {/ pda6bc0d00013 /}, identifies the next decision {/ pda6bc0d00014 /} owner, and keeps administrative {/ pda6bc0d00015 /} progress from masquerading as {/ pda6bc0d00016 /} a legal, technical, or {/ pda6bc0d00017 */} accounting conclusion.

The design {/* pda6bc0d00018 /} below is deliberately specific {/ pda6bc0d00019 /}. Its columns, review sequence {/ pda6bc0d00020 /}, and examples follow the {/ pda6bc0d00021 /} failure points peculiar to {/ pda6bc0d00022 /} datum, perforation, lease, interval {/ pda6bc0d00023 /}, severance. A generic “documents {/ pda6bc0d00024 /} received” checklist cannot show {/ pda6bc0d00025 /} whether the team has {/ pda6bc0d00026 /} the right version, whether {/ pda6bc0d00027 /} two identifiers describe the {/ pda6bc0d00028 /} same thing, or whether {/ pda6bc0d00029 /} an unresolved professional judgment {/ pda6bc0d00030 /} still controls the outcome {/ pda6bc0d00031 */}.

lease depth severance obligation register: Start with the clause {/* pda6bc0d00032 */} vocabulary

Put the source {/* pda6bc0d00033 /} wording next to every {/ pda6bc0d00034 /} translated, standardized, or computed {/ pda6bc0d00035 /} entry. Keep blanks as {/ pda6bc0d00036 /} blanks. A nearby row {/ pda6bc0d00037 /}, familiar naming pattern, or {/ pda6bc0d00038 /} value from another system {/ pda6bc0d00039 /} cannot silently fill a {/ pda6bc0d00040 /} source gap. If the {/ pda6bc0d00041 /} project authorizes a transformation {/ pda6bc0d00042 /}, name the rule, version {/ pda6bc0d00043 */}, analyst, and date.

Depth {/* pda6bc0d00044 /} is meaningless without a {/ pda6bc0d00045 */} datum

A date earns {/* pda6bc0d00046 /} a place on the {/ pda6bc0d00047 /} timeline only when its {/ pda6bc0d00048 /} event meaning is named {/ pda6bc0d00049 /}. This workflow should track {/ pda6bc0d00050 */} the following sequence:

Connect {/* pda6bc0d00051 /} the well evidence carefully {/ pda6bc0d00052 */}

The useful unit is {/* pda6bc0d00053 /} a vertical-rights decision {/ pda6bc0d00054 /} record, not a folder {/ pda6bc0d00055 /} of well papers for {/ pda6bc0d00056 /} one lease, retained interval {/ pda6bc0d00057 /}, and depth-severance event {/ pda6bc0d00058 /}. It connects executed leases {/ pda6bc0d00059 /}, depth clauses, amendments, pooling {/ pda6bc0d00060 /} instruments, completion reports, well {/ pda6bc0d00061 /} logs, release instruments, and {/ pda6bc0d00062 /} approved tract formation records {/ pda6bc0d00063 /}. The aim is not {/ pda6bc0d00064 /} to make a legal {/ pda6bc0d00065 /}, title, accounting, regulatory, engineering {/ pda6bc0d00066 /}, or commercial judgment by {/ pda6bc0d00067 /} implication. The aim is {/ pda6bc0d00068 /} to show exactly what {/ pda6bc0d00069 /} the formation records say {/ pda6bc0d00070 /}, where they say it {/ pda6bc0d00071 /}, how the observations relate {/ pda6bc0d00072 /}, and which decision still {/ pda6bc0d00073 /} belongs to an authorized {/ pda6bc0d00074 */} severance reviewer.

Construct the {/* pda6bc0d00075 */} retained-interval question

First {/* pda6bc0d00076 /} inventory the controlling papers {/ pda6bc0d00077 /} and the observations each {/ pda6bc0d00078 /} one can actually support {/ pda6bc0d00079 /}. For every item, capture {/ pda6bc0d00080 /} the custodian, document role {/ pda6bc0d00081 /}, identifier, stable locator, page {/ pda6bc0d00082 /} or row, access time {/ pda6bc0d00083 /}, and whether the file {/ pda6bc0d00084 /} is native, scanned, exported {/ pda6bc0d00085 /}, or transcribed. A county {/ pda6bc0d00086 /} index, regulator portal, operator {/ pda6bc0d00087 /} statement, executed instrument, and {/ pda6bc0d00088 /} internal spreadsheet can each {/ pda6bc0d00089 /} be useful, but they {/ pda6bc0d00090 /} do not carry the {/ pda6bc0d00091 /} same authority or prove {/ pda6bc0d00092 */} the same fact.

Formation {/* pda6bc0d00093 /} names versus measured footage {/ pda6bc0d00094 */}

The material conflict for {/* pda6bc0d00095 /} this packet is that {/ pda6bc0d00096 /} the lease defines the {/ pda6bc0d00097 /} severance point by a {/ pda6bc0d00098 /} named formation while the {/ pda6bc0d00099 /} completion report gives measured {/ pda6bc0d00100 /} depths without an approved {/ pda6bc0d00101 /} formation cross-reference. Reduce {/ pda6bc0d00102 /} the conflict to the {/ pda6bc0d00103 /} exact values, labels, and {/ pda6bc0d00104 /} locators that disagree. Place {/ pda6bc0d00105 /} both observations, their roles {/ pda6bc0d00106 /}, dates, and locators side {/ pda6bc0d00107 /} by side. Do not {/ pda6bc0d00108 /} choose the newest, cleanest {/ pda6bc0d00109 /}, or most convenient value {/ pda6bc0d00110 /} unless the approved procedure {/ pda6bc0d00111 /} and severance reviewer decision {/ pda6bc0d00112 */} support that choice.

Reviewer {/* pda6bc0d00113 */} worksheet

Have another reader {/* pda6bc0d00114 /} independently retrace the few {/ pda6bc0d00115 /} facts on which the {/ pda6bc0d00116 /} next action depends. Reopen {/ pda6bc0d00117 /} direct locators, compare identifiers {/ pda6bc0d00118 /} character by character, verify {/ pda6bc0d00119 /} page references, inspect incorporated {/ pda6bc0d00120 /} exhibits, and reproduce permitted {/ pda6bc0d00121 /} calculations from saved inputs {/ pda6bc0d00122 /}. Test apparently clean rows {/ pda6bc0d00123 /} as well as known {/ pda6bc0d00124 /} exceptions; false matches often {/ pda6bc0d00125 /} hide inside tidy tables {/ pda6bc0d00126 */}.

What the register cannot {/* pda6bc0d00127 */} decide

  1. Name one {/* pda6bc0d00128 /} depth, jurisdiction, period, deliverable {/ pda6bc0d00129 */}, and acceptance owner.

Field {/* pda6bc0d00130 */} notes for depth

At {/* pda6bc0d00131 /} intake, label formation with {/ pda6bc0d00132 /} the name printed on {/ pda6bc0d00133 /} its own source. Next {/ pda6bc0d00134 /} capture the locator for {/ pda6bc0d00135 /} datum, the vintage attached {/ pda6bc0d00136 /} to perforation, and the {/ pda6bc0d00137 /} person responsible for lease {/ pda6bc0d00138 /}. Keep the observed value {/ pda6bc0d00139 /} for interval apart from {/ pda6bc0d00140 /} internal shorthand. If severance {/ pda6bc0d00141 /} changes, append the new {/ pda6bc0d00142 /} state and retain the {/ pda6bc0d00143 /} old one. When release {/ pda6bc0d00144 /} cannot be verified, mark {/ pda6bc0d00145 /} the exact search attempted {/ pda6bc0d00146 /} and leave the cell {/ pda6bc0d00147 */} unresolved.

A useful exception {/* pda6bc0d00148 /} note here has four {/ pda6bc0d00149 /} parts: the conflicting depth {/ pda6bc0d00150 /} observation; the source supplying {/ pda6bc0d00151 /} each version; the action {/ pda6bc0d00152 /} currently prevented; and the {/ pda6bc0d00153 /} role allowed to resolve {/ pda6bc0d00154 /} it. Avoid declaring that {/ pda6bc0d00155 /} datum controls merely because {/ pda6bc0d00156 /} it is newer. Do {/ pda6bc0d00157 /} not treat missing lease {/ pda6bc0d00158 /} as negative proof. Ask {/ pda6bc0d00159 /} whether another identifier, exhibit {/ pda6bc0d00160 /}, period, or custodian could {/ pda6bc0d00161 /} explain the gap. A {/ pda6bc0d00162 /} concise question travels farther {/ pda6bc0d00163 /} than a narrative without {/ pda6bc0d00164 */} a decision owner.

Before {/* pda6bc0d00165 /} release, sample one clean {/ pda6bc0d00166 /} formation row and every {/ pda6bc0d00167 /} exceptional perforation row. Reopen {/ pda6bc0d00168 /} the cited page, reproduce {/ pda6bc0d00169 /} any conversion involving interval {/ pda6bc0d00170 /}, and confirm that severance {/ pda6bc0d00171 /} describes workflow position rather {/ pda6bc0d00172 /} than substantive acceptance. Test {/ pda6bc0d00173 /} the handoff from the {/ pda6bc0d00174 /} recipient's point of view {/ pda6bc0d00175 /}: can that person locate {/ pda6bc0d00176 /} release without asking where {/ pda6bc0d00177 /} the spreadsheet came from {/ pda6bc0d00178 /}? Can the reader distinguish {/ pda6bc0d00179 /} a copied fact from {/ pda6bc0d00180 /} a candidate match? Can {/ pda6bc0d00181 /} the authorized specialist see {/ pda6bc0d00182 /} precisely which judgment is {/ pda6bc0d00183 */} requested?

This discipline improves {/* pda6bc0d00184 /} maintenance. A future analyst {/ pda6bc0d00185 /} can add a later {/ pda6bc0d00186 /} lease event without erasing {/ pda6bc0d00187 /} the history of depth {/ pda6bc0d00188 /}. Supervisors can count unresolved {/ pda6bc0d00189 /} datum questions without pretending {/ pda6bc0d00190 /} all exceptions carry equal {/ pda6bc0d00191 /} consequence. The file remains {/ pda6bc0d00192 /} useful when personnel change {/ pda6bc0d00193 /} because its logic lives {/ pda6bc0d00194 /} in cited observations, labeled {/ pda6bc0d00195 /} transformations, and recorded decisions {/ pda6bc0d00196 /} rather than in somebody's {/ pda6bc0d00197 */} inbox or memory.

Reference {/* pda6bc0d00198 */} desks

The correct custodian {/* pda6bc0d00199 /} depends on the jurisdiction {/ pda6bc0d00200 /} and asset. These official {/ pda6bc0d00201 /} resources provide starting points {/ pda6bc0d00202 /} for federal land records {/ pda6bc0d00203 /}, royalty reporting terminology, and {/ pda6bc0d00204 /} state well or regulatory {/ pda6bc0d00205 */} records:

A useful finish {/* pda6bc0d00206 */} line

The vertical rights {/* pda6bc0d00207 /} decision ladder is ready {/ pda6bc0d00208 /} to hand off when {/ pda6bc0d00209 /} another person can trace {/ pda6bc0d00210 /} depth, datum, and interval {/ pda6bc0d00211 /} to their exact sources {/ pda6bc0d00212 /}; understand why any competing {/ pda6bc0d00213 /} observation remains open; and {/ pda6bc0d00214 /} see who owns the {/ pda6bc0d00215 /} next decision. Completion does {/ pda6bc0d00216 /} not mean that every {/ pda6bc0d00217 /} uncertainty disappeared. It means {/ pda6bc0d00218 /} the evidence population is {/ pda6bc0d00219 /} defined, transformations are visible {/ pda6bc0d00220 /}, exceptions have not been {/ pda6bc0d00221 /} silently flattened, and the {/ pda6bc0d00222 /} requested administrative product can {/ pda6bc0d00223 /} be reviewed without reconstructing {/ pda6bc0d00224 /} the research from memory {/ pda6bc0d00225 */}.

For help designing a {/* pda6bc0d00226 /} repeatable vertical rights decision {/ pda6bc0d00227 /} ladder around your acreage {/ pda6bc0d00228 /}, owner, regulatory, or revenue {/ pda6bc0d00229 */} files, Book a free consultation.

Ready to Scale Your Landman Business?

Discuss a defined remote support scope for title research, lease administration, GIS coordination, or document work.

Quick Answers

How quickly can a remote landman professional start?▾
Timing depends on access, workflow definition, task complexity, and your review process. Confirm a written start plan during the free consultation.
How do I request a scoped quote?▾
Book a free consultation to review your task volume, access, review time, and required tools. Any quote is tied to that defined scope.
Are remote professionals a good fit for sensitive land data?▾
Sensitive work needs least privilege access, documented procedures, appropriate agreements, and client review. The required controls should be confirmed before access is granted.
What if I need to scale up or down?▾
Capacity changes depend on the written service agreement. Discuss expected workload changes before work begins so scope and review coverage remain clear.