lease schedule legal description audit: Freeze the schedule before reviewing it
A lease schedule can change while a transaction is moving. Save the version under review, record its filename or document identifier, date received, page count, and a hash when policy allows. If the schedule came from a spreadsheet, keep the native file as well as any rendered copy used for review. Filters, hidden rows, merged cells, and print settings can change what appears on a PDF.
Number the source rows without altering their order. Include continuation pages and blank lines that carry a lease number or legal description from the row above. A review copy may add analyst columns, but it should not replace the original text. The source row is the evidence against which every correction is measured.
Establish the population before testing legal calls. Count schedule rows, unique lease locators, blank locators, duplicate locators, and rows marked as continuations. Reconcile those totals to the source pages. This catches omitted sheets and extraction errors that a row-by-row description review will miss.
Tie each row to an actual lease
The recording reference is usually the fastest route to the source, but it still needs verification. Record the jurisdiction, book and page or instrument number, image page, and retrieval date. If the reference returns no image, document the exact search and try the approved alternate routes. Do not attach a different lease simply because its parties and date look close.
Compare the lease date, lessor and lessee strings, county, recording data, and any property or internal identifier stated on the schedule. Names are search clues. Spelling variants, initials, trust capacities, and assignments can make a correct match look imperfect, while common names can make the wrong match look convincing.
When a schedule row lacks a direct locator, keep it open. A neighboring row's instrument number cannot be carried down unless the source formatting clearly does so and the reviewer can reproduce that reading. Record why the row appears related and what evidence is still needed. The audit should expose weak joins rather than turn them into permanent identifiers.
Compare legal descriptions as documentary text
Transcribe the schedule call and the lease call into separate fields. Preserve abbreviations, punctuation, directional letters, lot numbers, survey names, section-township-range values, metes-and-bounds references, and exception language. A normalized comparison field may sit beside the transcription, but it must never overwrite either source string.
Break a long description into review units only when the split is traceable. For a public-land survey description, units might include section, township direction, range direction, aliquot part, lot, and meridian. For a survey or abstract system, the useful units will differ. Metes-and-bounds descriptions may require a specialist and should not be forced into a section-township-range grid.
Character-level comparison is especially useful for digits and directional calls. Section 14, Township 3 North, Range 8 West is not the same text as Section 14, Township 3 North, Range 9 West. Even if surrounding calls suggest a typographical error, the analyst should preserve both values and route the conflict. Choosing the "likely" range would erase the very evidence the audit was meant to surface.
Read the full description and its exceptions
A schedule often shortens a description to its headline call. The lease may continue onto another page, incorporate an exhibit, or exclude specific depths, tracts, roads, or prior conveyances. Confirm where the legal description begins and ends. Retrieve every incorporated page before marking a row matched.
Track exception language separately from the base land call. Two rows may share the same section and acreage while differing because one excludes a tract or limits a depth interval. Conversely, a lease and schedule can describe the same documentary tract with different acreage labels. Neither situation can be resolved by the headline call alone.
Image quality matters. If a range number, lot number, or directional letter is unclear, save the page locator and mark the character unreadable. Check another official image or related recorded reference where the procedure permits, but do not silently substitute the clearer value. The reviewer needs to know which source was illegible and which later source supplied the alternate observation.
Use acreage as a diagnostic, not a match key
Record the acreage exactly as labeled. Gross acres, net acres, described acres, and transaction acres are different fields. A schedule may list a rounded total while the lease states acreage for several component tracts. Add the components only in a separate calculation with the formula and source pages shown.
Matching acreage does not prove matching land. Two descriptions can total the same number while differing in a quarter section, lot, survey, or excluded parcel. A variance also does not prove that one source is wrong. It may reflect gross-versus-net treatment, a partial assignment, or a schedule that covers only certain tracts. The exception should state the observed labels before asking anyone to explain the difference.
For a multi-county lease, partition the review by recording jurisdiction. The same lease may have separate instrument numbers and different image sets in each county. Confirm that the schedule includes every county named in the lease and that each recording reference leads to the corresponding local record. A complete row in one jurisdiction does not cure a missing continuation elsewhere.
Find omissions and duplicates before correcting text
Sort a working copy by the stable lease locator and source row number. Repeated locators may represent legitimate tract lines, duplicate schedule entries, or one lease recorded in several counties. Review the surrounding columns and source pages before classifying them. Keep all source rows even when the final decision removes a duplicate from the transaction schedule.
Look for leases that appear in the transaction file but not the schedule, and schedule rows without a retrieved lease. Reconcile page headers, subtotals, and continuation markers. After every accepted correction, recalculate row counts and exception totals. A corrected description is not useful if the correction process dropped another row.
Version corrections as events. Preserve the submitted schedule, the proposed correction, the reviewer disposition, and the accepted replacement. State who approved the change and which version it affects. An analyst note can recommend a correction, but it should not be presented as an amendment to the executed lease.
Return the exact conflict
The handoff should include the frozen schedule row, direct lease page, recording reference, exact differing characters or calls, related instruments checked, search history, and one requested decision. If the source chain is incomplete, name the missing page or instrument. If a specialist must evaluate a boundary or acreage question, say which documentary observations produced that need.
A second reviewer should reopen a sample from each description format, all material conflicts, and enough clean rows to test the extraction process. The reviewer should also recount the schedule population and duplicates. Close a row only after the source match, legal-call comparison, and correction disposition are documented.
This audit detects differences between a transaction schedule and its cited records. It does not locate a boundary, calculate net acreage, repair an instrument, or decide which description controls. Keeping those decisions outside the audit makes the result more useful to the people authorized to make them.
If your team needs support maintaining a traceable lease schedule legal description audit, 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.
