communitization agreement tract index: What the index must answer
A communitization agreement tract index is a document map. It should let a reviewer move from an agreement-level record to the exact exhibit row that describes a tract, then to the lease or serial number named on that row. That sounds simple until the file contains several versions of the same schedule, a map whose labels do not match the table, or an approval that incorporates only some attachments.
The first question is therefore not how much a tract participates. It is which approved document supplies the tract population. Start with the executed agreement, the approval record, and every exhibit that the agreement or approval expressly incorporates. Record the agreement number and name exactly as shown. Keep execution, submission, approval, and effective dates in separate fields because each date describes a different event. If the file does not establish one of those events, leave it unresolved rather than borrowing a date from a later database display.
This index does not decide title, working interest, allocation, or whether the agreement remains effective. It preserves the evidence needed by the person who owns those decisions.
Build one row from one tract claim
Each tract row should reproduce the source claim closely enough that another researcher can find it without guessing. The row needs the tract label, lease or serial number, land description, stated acreage, participation factor when supplied, exhibit name, page, and a stable source locator. Those values belong together because their meaning comes from the same exhibit context. Pulling the acreage from one version and the lease number from another creates a row that never existed in the record.
Do not normalize tract labels in place. "Tract 4," "Tr. 4," and a map label of "4A" may refer to related land, but the index should retain each form until the file explains the relationship. The same rule applies to lease and serial numbers. A corrected analyst value can sit beside the original as a proposed crosswalk, with the reason and reviewer status shown, but it should not replace the text that appeared on the exhibit.
Legal descriptions need the same care. Preserve section, township, range, survey, lot, aliquot, county, and state wording as the source presents it. A map can help a reviewer understand where the tract lies. It cannot repair a missing call or prove that two differently worded descriptions cover the same land.
Establish the approved version
Many index errors begin with a perfectly legible exhibit that was not the approved exhibit. Assemble the chronology before entering tract data. Identify the executed agreement, the version submitted for approval, the approval record, any corrected or replacement exhibit, and the version visible in the current system. Then ask what the approval actually incorporates.
File names and upload dates are clues, not answers. A later file may be a scan replacement rather than a substantive revision. Conversely, a document with the same title may contain a changed acreage table. Compare page count, tract labels, totals, signatures, revision notes, and any approval reference. If the approval points to an exhibit by date or letter, retain that reference in the index header.
The working index should state its cutoff date and source set. That statement prevents a later user from mistaking an incomplete research snapshot for a final agreement history. When an attachment cannot be retrieved, name it as missing and explain why it matters to the tract population.
Reconcile the table, map, and lease references
Three comparisons catch most documentary problems. First, recount the tract rows and compare the result with any stated tract total. Second, total the acreage exactly as listed, without changing a number to make the arithmetic work. Third, trace every lease or serial reference back to the exhibit page on which it appears.
Suppose the acreage schedule lists Tract 4 as 160 acres, while a later exhibit carries 120 acres under the same label. The index should not choose 160 because it appears earlier or 120 because it appears later. It should show both observations, their document dates, page locators, and approval context. The exception asks which version governs the working tract set. That is a bounded question a reviewer can answer.
A different problem arises when the map shows a tract label that has no table row. The map may depict context outside the participating area, or the table may be incomplete. Record the unmatched map label and inspect legends, continuation pages, and incorporated schedules. Do not invent a row from the map geometry. Likewise, if the table cites a lease that does not appear on the map, keep the table row and return the visual mismatch for review.
Participation factors require their own check
A participation factor is not self-validating because the column totals to one. Preserve the factor as stated and note the tract acreage or other basis shown by the same approved schedule. If the file contains more than one factor column, copy the column heading and any footnote. A decimal without its heading can be mistaken for an ownership interest, tract contribution, or another allocation.
Recalculation can expose a transcription error, but it remains an analyst test. Store the formula, inputs, rounding rule, and result separately from the source factor. A mismatch should identify the affected row and the source values used in the check. The reviewer then decides whether the problem is a transcription error, a stated adjustment, a superseded exhibit, or something the available record does not explain.
Search records without overstating absence
Official custodians provide the starting routes for agreement, lease, well, and regulatory records. Search by the agreement identifier first, then by exact lease or serial numbers and distinctive tract references. Save the query route, terms, filters, access time, and returned condition when the assignment permits it. If the query returns nothing, report that result as a documented unsuccessful search. It does not prove that an agreement or attachment never existed.
Older identifiers, incomplete indexing, and scanned files can require a second route or a direct record request. Keep secondary databases and internal spreadsheets in a supporting role. They can suggest another identifier or reveal a mismatch, but they do not replace an approved agreement or incorporated exhibit.
What belongs in the review packet
The handoff should include the agreement version used, the approval locator, a tract table tied to exhibit pages, unmatched map or table labels, conflicting acreage or lease references, missing attachments, and any recalculation sheet. Each exception should state the decision it blocks. "Tract 4 conflict" is not enough. "Confirm whether the approved schedule uses the 160-acre or 120-acre Tract 4 row before the participation table is released" gives the reviewer a usable question.
A second researcher should reopen the approval and every material exhibit, recount the tract population, sample the legal descriptions against the images, and verify that proposed crosswalks remain separate from source text. The file can close when every included tract has an approved-document locator and every unresolved discrepancy has an owner and disposition. A tidy spreadsheet is not the closing condition. A reproducible path through the agreement record is.
If your team needs support maintaining a traceable communitization agreement tract index, Book a free consultation.
Authoritative starting points
Use the official custodian relevant to the asset and jurisdiction. These sources help confirm terminology, record coverage, identifiers, and access routes:
Ready to Scale Your Landman Business?
Discuss a defined remote support scope for title research, lease administration, GIS coordination, or document work.
