Landman Business | September 19, 2026 | 10 min read
pooled unit tract status board: What this workflow is for
A pooled unit tract status board gives a land team a controlled way to move unit administration work from intake to review. It records what the source actually says, where the evidence lives, what is still missing, and who owns the next action. It does not decide title, construe an agreement, calculate a legal deadline, determine regulatory compliance, approve payment, or replace advice from the responsible land, legal, regulatory, accounting, survey, or engineering professional.
The practical goal is continuity. Remote support should be able to open a row and understand the asset, question, source, present condition, and next step without relying on memory or an unexplained status color. A well-maintained record also prevents a later team member from turning an assumption into an apparent fact.
Begin with a narrow assignment
Write the assignment as one answerable question tied to one stable asset key. Identify the lease, tract, well, unit, owner, agreement, instrument, or submission before research begins. State the jurisdiction and the requested output. If the request asks support staff to decide legal effect or approve a business action, return it for a named professional owner.
An application exhibit and final order exhibit use different tract numbering for apparently similar descriptions. The safe response is not to reconcile the problem from context. Preserve each observation, identify its source and date, describe the difference at field level, and route the narrow question to the authorized reviewer.
The minimum working fields are docket, order number, exhibit version, tract label, acreage as stated, party string, evidence status, reviewer. Add a source locator and access date to every material observation. If a document has pages or exhibits, cite the exact page. If a system result can change, retain the query inputs and the date it was accessed.
Separate evidence from working interpretation
Use three distinct layers. The evidence layer contains exact identifiers, text, values, dates, and locators. The working layer contains normalization, candidate matches, calculations requested by the assignment, and exception flags. The decision layer records the authorized reviewer's disposition and date. Never overwrite evidence with a preferred working value.
Names are especially risky. Punctuation, suffixes, abbreviations, former operator names, estate references, and business designators may vary across sources. Store the original string and any normalized string in separate columns. A similar name is a research lead, not proof that two parties or records are identical.
Dates need event labels. Execution, acknowledgment, filing, recording, effective, approval, notice, receipt, production, sales, payment, rejection, and access dates describe different events. A generic “date” column invites false chronology. Preserve both the value and its meaning, and document any calculation rule supplied by the assignment owner.
Build a repeatable source trail
Start with official commission dockets, orders, and exhibits. Use official systems for discovery and verification when they apply, but record their coverage limits. Search results can omit images, use legacy identifiers, lag later filings, or display only a current status. An official interface is authoritative about what it displayed on the access date; it may not tell the whole history.
For every search, retain the jurisdiction, system, identifier or query text, filters, result condition, locator, and access date. A positive match should be tested by opening the record and comparing stable identifiers. A negative search supports only the statement that the documented query returned no match. It does not prove that no record exists.
Convenience copies should point back to the controlled source. Screenshots may help a reviewer see a transient display, but they should not replace downloadable documents or stable record links when those are available. Label every local copy with its source and retrieval date.
Use statuses that describe work, not conclusions
A compact status set is easier to govern: new, researching, waiting on source, ready for review, returned, and accepted. Define each status. “Waiting on source” means a request was sent and responsive evidence has not arrived. “Ready for review” means the packet meets the intake standard. Neither status says the underlying legal, regulatory, payment, or ownership question is resolved.
Each open row needs one next action, one responsible person, and one follow-up date. “Follow up” is not a useful action unless it names the recipient and the evidence requested. When a response arrives, record what arrived rather than automatically closing the item.
Priority should consider a documented project deadline, consequence of delay, evidence readiness, and reviewer availability. Do not let an old but inactive request hide a newer item tied to an approved operational milestone. At the same time, keep aging visible so unresolved requests do not disappear.
Reconcile differences without erasing history
Compare jurisdiction and stable identifiers first. Then compare document role, version, date meaning, party string, legal-description text, status, and amount or acreage as applicable. When sources conflict, retain both rows and write a concise exception: which fields differ, which sources show them, and what question needs review.
Do not silently replace an earlier value when a portal changes. Add a new dated observation. The change might reflect a new filing, a corrected index, processing lag, a system migration, or a prior transcription error. The history helps a reviewer distinguish those possibilities.
If the team chooses a working value, record who chose it, the rule supplied, the period or deliverable for which it applies, and its review state. This prevents a project-specific convention from becoming an unsupported enterprise rule.
Prepare the review packet
Lead with the single question requiring a decision. Follow with the asset key, assignment scope, chronological observations, direct locators, relevant pages, query history, comparison table, exception statement, known limitations, and proposed administrative next step. Keep the summary no broader than the underlying evidence.
Before delivery, open every important locator, spot-check identifiers and transcriptions, confirm that each date has an event label, and verify that the latest evidence is included. Record the packet version, recipient, delivery time, requested response, and returned or accepted state.
A response is not acceptance unless the designated reviewer says it resolves the assignment. If the packet is returned, preserve the comment, reopen the exact missing step, and create a new version when the evidence changes.
Quality-control checklist
- Does the row identify one asset and one question?
- Can another researcher repeat every material search?
- Are original values preserved separately from normalized values?
- Does each date state what event it represents?
- Are conflicts described at field level rather than silently resolved?
- Does every open item have an owner and follow-up date?
- Is the requested decision assigned to an authorized professional?
- Can the reviewer reach the underlying evidence from the packet?
Example handoff
Suppose a researcher finds two records that appear connected but differ in one identifier and one date label. The handoff should not say that one record supersedes the other. It should list both records, preserve the exact strings, identify the matching fields, identify the differences, state the search routes used, and ask whether the candidate link may be used for the named project purpose.
That phrasing makes the boundary visible. Support staff have completed collection, comparison, and exception documentation. The responsible professional retains the decision about legal effect, sufficiency, identity, compliance, or payment treatment.
Frequently asked questions
Can remote land support maintain this tracker?
Yes. Trained support staff can collect documents, transcribe values, maintain source links, apply documented normalization rules, track requests, compare observations, and assemble review packets. Reserved judgments remain with the designated professional.
How should missing records be reported?
State the systems, jurisdictions, queries, filters, date ranges, and access dates checked, followed by the exact returned condition. Avoid absolute statements unless the responsible authority provides a basis for them.
When is an item complete?
Completion requires the evidence and acceptance defined by the assignment. Sending a request, uploading a document, or changing a status does not by itself establish completion.
Sources and further research
These official entry points help teams confirm coverage, terminology, and record routes for applicable jurisdictions. Always use the source relevant to the asset and question.
Closing standard
A strong pooled unit tract status board lets the next person reproduce the work and see the unresolved judgment immediately. It preserves source truth, makes limitations explicit, and creates a clean path to professional review.
If your team needs help building a dependable unit administration process, Book a free consultation.
