division order decimal change approval packet: A decimal change begins with a claim, not a keystroke
A request to change a division-order decimal usually arrives as a short instruction: update an owner from one number to another, make the change effective for a stated month, and release whatever work depends on it. The instruction is not the evidence. Before anyone edits an ownership deck, the analyst needs a packet that explains where the proposed number came from, what period it is meant to affect, and who is authorized to approve the result.
Start the packet with one sentence that can be tested: for a named payee on a named property, the current system decimal is one value and the proposed decimal is another. Identify the deck or ownership version in which the current value was observed. Include the date and time of that observation because the deck can change while the packet is under review. A screenshot can help a reviewer orient quickly, but the packet also needs an export, report, or other retrievable system reference whenever the procedure permits one.
Keep the identifiers literal. An owner number, payee number, property number, well number, and deck name may refer to related records, but they are not interchangeable. A name match alone is especially weak when trusts, estates, similarly named family members, or vendor records are involved. The packet should show how the proposed change was joined to the exact owner and property without implying that the join itself proves entitlement.
Reproduce the calculation at source precision
Place the inputs above the formula. Depending on the approved ownership method, those inputs may include a tract interest, net mineral acres, spacing or unit acres, royalty fraction, burden, allocation factor, or a value carried forward from an authorized ownership schedule. Each input needs a document name, page or row locator, and the precision displayed by that source. Do not round the components merely to make the working paper easier to read.
The calculation sheet should display the formula and every intermediate result. If the system stores eight decimal places, show at least that precision in the final comparison and document any rounding rule used at entry. Also show the unrounded result. A proposed value of 0.01000000 is not adequately supported by a note saying “one percent”; the reviewer needs to see whether the underlying arithmetic produced exactly that value or a nearby number that was rounded under a defined rule.
Reperformance should be possible without opening the analyst's private notes. A second person ought to be able to retrieve the listed sources, enter the preserved inputs, follow the same arithmetic, and reach the proposed decimal. If that exercise produces a different number, the packet remains an exception even when the variance appears small. The proper next step is to locate the different input or rule, not to choose whichever result matches the existing deck.
Ownership effective dates and payment periods answer different questions
The date attached to a source does not automatically state the first production month affected by a change. A conveyance may have an execution date, an effective date in its text, a recording date, and a date received by the company. An ownership schedule may have its own “as of” date. The system change will have an entry timestamp, while revenue statements use production and accounting periods. Record these events separately.
Suppose a new schedule changes an owner's decimal from 0.01250000 to 0.01000000 and labels March as the effective production month. The April statement was already paid using the old decimal. The packet should not silently convert that sequence into an adjustment instruction. It should show the source for March, list every potentially affected production and check period, note the statement on which the old value appears, and ask the authorized reviewer what implementation is approved.
This separation matters because a change can be correct prospectively while its retroactive treatment remains unresolved. Suspense, recoupment, prior payments, owner communication, and accounting entries may be controlled by different procedures and decision owners. The land or division-order analyst can assemble the facts without deciding those consequences.
Compare the proposal with the records already in use
Build a compact variance table with one row for the current system deck, one for the last approved ownership schedule, one for the new source, and one for the analyst's recomputation. For each row, identify the decimal, source date, relevant production period, document locator, and status. The table makes agreement visible, but its more important job is to keep disagreement from disappearing inside a narrative summary.
Review the last statement paid at the old value and the first statement expected to use the new value. Confirm that both belong to the same owner and property identifiers used in the calculation. If a statement combines multiple wells, products, or adjustment lines, preserve those distinctions. A total payment variance cannot by itself establish which decimal or period produced it.
Check whether the owner is in suspense and record the status as an observation. Suspense may affect the operational sequence, but it does not prove that the proposed decimal is correct. Likewise, a division order signed by an owner is relevant evidence under the company's procedure; the packet should not characterize the signature as an independent title determination.
Design approval so the decision cannot be mistaken
The approval page should put the proposed action next to the unresolved consequences. Name the owner, property, old decimal, proposed decimal, stated effective production month, and calculation version. Then list the affected periods identified by the comparison and any open question concerning prior payments or suspense. A reviewer should be able to approve the decimal calculation without accidentally approving a retroactive accounting treatment that was never evaluated.
Use separate fields when the organization assigns separate authorities. One reviewer may confirm that the ownership inputs and arithmetic comply with the approved record, while another authorizes the system effective period or resulting payment adjustment. Record the decision, reviewer identity, timestamp, and packet version. An email saying “looks good” is not enough if it does not establish which version and which action were reviewed.
After approval, retain the before-and-after system evidence rather than overwriting the old observation. Record who entered the change, when it was entered, the deck version created, and the approved effective period. If entry reveals a system constraint, return the packet for a decision. Do not change the approved decimal or period informally to fit a field limitation.
Verify the posted result and close with evidence
The first system check confirms that the approved value was entered on the intended owner and property. The first affected statement check answers a different question: whether the value was applied to the approved production period in the actual accounting output. Both checks belong in the packet. Capture a stable report or statement locator, the observed decimal, the production month, and the checker's name and date.
If the first statement differs from the approval, reopen the packet. Describe whether the variance comes from decimal precision, a different deck, a property mismatch, a product allocation, a production-period boundary, or an unidentified cause. Do not relabel the approved calculation to match the posted result. The discrepancy is the work item.
A complete handoff therefore contains the source index, calculation with preserved precision, current-versus-proposed comparison, effective-period timeline, approval record, system entry evidence, and first-statement check. It also states what remains outside the analyst's conclusion. The packet supports a controlled decimal change; it does not establish ownership, entitlement, recoupment rights, or the legal and accounting treatment of prior payments.
If your team needs support maintaining a traceable division order decimal change approval packet, 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.
