Mineral ownership can be divided horizontally as well as by tract. One party may own the minerals from the surface down to a stated depth, while another owns the minerals below that line. A lease may cover only a named formation, a interval between two depths, or all depths except a reserved zone. When several documents describe those boundaries differently, a land team needs a controlled way to see the exact language, the source of each statement, and the question that remains open. The depth severance clause review log is that control.
This article describes an administrative workflow for building the log. It does not decide ownership, interpret an ambiguous instrument, or replace a title opinion. Those conclusions belong to the authorized legal or land professional. The log exists to make the documentary basis visible so that a qualified reviewer can reach a defensible decision.
landman depth severance clause review log: Why depth language deserves its own review log
A general lease abstract often captures the granting clause, royalty, term, and acreage. Depth language can be compressed into a short phrase inside the granting clause, an exhibit, or a reservation. That compression is where detail disappears. A reviewer may later ask whether a particular formation is covered, and the abstract may say only that the lease covers the "upper formations." The original document may have named a formation, a measured depth, a stratigraphic marker, or a referenced exhibit. Each of those formulations creates a different review question.
A dedicated log keeps the exact words next to the document reference. It also separates three things that are easy to blend together: what the instrument says, what another record says about the same tract, and what the reviewer believes the language means. When those categories remain distinct, a later reviewer can challenge the interpretation without losing the underlying evidence.
Define the review unit before opening the file
Start with a clear unit of review. A useful unit is one tract, one mineral severance, and one depth boundary question. If the project covers multiple leases or several formations, create separate rows rather than one broad row per tract. A broad row invites a conclusion that applies to more acreage or more formations than the source actually supports.
Record the project name, county and state, tract identifier, survey or abstract reference, and the smallest land description used by the source documents. Add the mineral estate being reviewed, the lease or instrument number, and the date of the review. These identifiers let a reviewer connect the log to the title file, the mapping system, and the client's project index without relying on memory.
Build the source set in a fixed order
A consistent source order reduces missed documents. Begin with the current lease or the instrument that created the depth division. Then add the recorded amendments, the assignment chain, the reservation or exception, and any unit designation that affects the tract. Follow with the title commitment or opinion if the project has one, then the client's internal land system export.
The order matters because each source may have been prepared for a different purpose. A lease describes the bargain. A recorded assignment describes a transfer. A unit order describes a regulatory unit. A title commitment lists requirements and exceptions. A land system export may contain a normalized value that no longer matches the recorded instrument. The log should identify the source type so that a normalized field is never mistaken for the original text.
Capture clause text verbatim
The most important field in the log is the quoted clause. Copy the complete depth-related sentence or exhibit paragraph, including punctuation and any internal cross-reference. Do not replace the text with a summary in the same field. A separate summary field can hold plain-language notes, but the quote must remain available for comparison.
Also record the page, section, exhibit, and recording reference where the quote appears. If the document is an unrecorded copy, say so. If the text comes from an abstract or a secondary summary, label it as secondary and point to the original when available. A verbatim quote with a precise locator is more useful than a polished paraphrase with no traceable origin.
Normalize the depth description carefully
After preserving the quote, create a structured description for searching and comparison. Common forms include a named formation, a stated upper and lower depth, a reference to a geologic marker, a "from the surface" description, or a reservation of a specific interval. Record the form separately from the value. A formation name and a measured depth are not interchangeable, even when local usage treats them as equivalent.
If the instrument gives both a formation name and a depth, keep both. If the name and the depth appear to conflict, do not choose one silently. Flag the conflict and describe the exact difference. The same rule applies when one document uses a measured depth and another uses a stratigraphic term. The log should show the mismatch so that a reviewer can decide which source controls.
Reconcile the lease, the deed, and the unit record
Depth questions often cross document families. A deed may reserve minerals below a stated depth. A lease may cover a named formation. A unit order may include or exclude the tract based on a regulatory description. Those records do not necessarily use the same boundary language, and they may have been created at different times.
Create a comparison row for each pair that matters to the project. Record whether the descriptions are identical, compatible, or unresolved. A compatible description is not the same as a controlling description; it simply means the reviewer has not found a conflict in the stated terms. An unresolved row should carry the reason, the missing document, and the next action. This approach keeps the log honest when the file is incomplete.
Handle name changes and successor language
Depth clauses can refer to formations by names that have changed in local usage. They can also refer to a predecessor's lease, a prior operator, or an exhibit recorded under an older instrument number. Record the name as written, then add a separate cross-reference field for the current common name if the project has an approved reference source. Do not overwrite the historical name.
The same discipline applies to parties. A successor may hold an interest under a chain of assignments, but the log should not assume that a name change and an assignment are the same event. Link each party statement to its source document and date. If the chain is incomplete, mark the gap rather than inferring the missing link.
Route interpretation to the authorized reviewer
A depth severance question can look like a data cleanup task. It is not. The decision may affect which minerals are leased, which formations are included in a unit, which royalty applies, and which party must be notified. The administrative reviewer can organize the evidence and identify the question. The legal or authorized land professional must interpret the instrument and decide the consequence.
The routing field should name the role, not just the person. It should also record what the reviewer needs: the original instrument, a recordable copy, a survey, a unit exhibit, a title opinion, or a client instruction. A clear request prevents the file from bouncing between teams without a defined next step.
Use a small, stable status model
Keep statuses simple enough that two reviewers apply them the same way. A workable set is: identified, source retrieved, text captured, compared, question routed, and closed. Each status should have an entry condition and an evidence requirement. For example, "text captured" requires the verbatim quote and a locator, not merely a note that someone read the lease.
Avoid statuses that imply a legal conclusion. "Approved" and "cleared" are ambiguous in a depth review because the reviewer may have cleared only the document collection, not the ownership question. Use language that describes the administrative step and let the authorized decision appear in a separate decision field.
Make conflicts visible in the handoff
A handoff should lead with the unresolved question. Include the tract, the competing descriptions, the source locators, the comparison result, and the reviewer role. Attach the relevant images or extracts only when policy allows, and point to the controlled file for the complete document. The receiving reviewer should be able to reproduce the comparison without searching the entire project folder.
If the handoff includes a recommendation, label it as a recommendation and state its basis. Do not present an inference as a source fact. A short "what we know" section and a separate "what remains open" section are usually more useful than a long narrative that blends the two.
Sample the log for consistency
A depth log can be internally consistent and still miss the same clause in several files. Build a small quality sample that checks whether reviewers are capturing the full depth language, using the same structured forms, and routing the same kind of conflict to the same role. Sample across document types, not only across reviewers.
Record the sample date, the files reviewed, the defects found, and the correction. If the same defect appears repeatedly, change the intake checklist or the source order rather than asking reviewers to remember a new rule. The goal is a process that produces the same evidence from different people.
Limits of the log
The log does not establish title, ownership, lease validity, unit participation, royalty entitlement, or regulatory compliance. It does not resolve an ambiguous formation name or prove that a missing document does not exist. It records what the reviewed sources say and what remains unresolved. Those limits should appear in the log itself so that a later reader does not mistake a completed row for a legal conclusion.
A depth severance review is often a long-chain exercise. The value of the log is that it makes the chain inspectable. It shows the exact words, the source, the comparison, and the open question. That is a modest deliverable, but it is the kind of deliverable that lets a qualified reviewer spend time on the decision instead of reconstructing the file.
Questions teams often ask
Who should maintain the log?
An administrative land analyst or title support professional can maintain the source fields and status. The authorized land professional or attorney should own the interpretation and disposition fields.
Should the log include every lease in the project?
No. Scope it to the tracts and instruments that present a depth question for the current review. A complete project index can point to the log without forcing every lease into the same worksheet.
What counts as a resolved row?
A resolved row has the source text, the comparison result, the reviewer decision where a decision was required, and a dated evidence link. If the decision depends on a document that has not been obtained, the row remains open.
Reference basis
- Railroad Commission of Texas, Oil and Gas - Texas oil and gas regulatory scope and record resources; accessed November 2, 2026.
- Texas Natural Resources Code, Chapter 91 - Texas provisions concerning oil and gas leases and related records; accessed November 2, 2026.
- Texas Administrative Code, Title 16, Part 1, Chapter 3 - Texas Railroad Commission oil and gas rules; accessed November 2, 2026.
- Bureau of Land Management, Oil and Gas - Federal oil and gas leasing and records context; accessed November 2, 2026.
