A division order that was mailed is not a division order that was signed. Land and revenue teams often know how many orders went out, but not how many reached the right person, how many came back with a defective signature, or how many are waiting on an estate document that nobody requested. The gap shows up later as a held payment, an owner complaint, or an acquisition file that cannot explain its own decimals.
This guide describes a division order signature follow-up queue for administrators and analysts who manage owner-facing paperwork. It is an administrative control, not an ownership decision, division order interpretation, decimal approval, or substitute for legal, land, revenue accounting, or compliance review.
Division Order Signature Follow-Up Queue: the unit of work
Track one row per owner, property, and division order version. A batch view hides the fact that one owner has three properties, two addresses, and a name that does not match the lease. A per-owner view makes those exceptions visible.
Each row needs a stable division order identifier, owner identifier, property or well reference, decimal or interest basis, document version, mailing date, delivery method, signer name, signer capacity, return date, defect reason, correction date, and current status. Keep the event history so the team can tell whether an order was never delivered or delivered and returned for a missing notary.
Statuses that work in practice are: prepared, validated, sent, delivered, returned complete, returned defective, corrected and resent, owner question open, escalated, and closed. Each status should name the next action and the role that owns it. A status such as "pending" without a dependency is a place where work goes to disappear.
Validate before the envelope
Most signature defects are predictable. Before mailing, compare the owner name on the division order to the lease, payee record, tax form, and address of record. Check whether the decimal is supported by the ownership schedule and whether the property description matches the intended well or unit. Confirm that the signature block matches the owner type: individual, joint owners, entity, trust, estate, or attorney-in-fact.
For an entity, confirm the legal name and signer capacity. For a trust, confirm the trustee and trust name. For an estate, confirm the personal representative and appointment document. For joint owners, confirm whether all signatures are required. The administrator can collect and index these documents, but the authorized reviewer decides whether capacity is sufficient. The IRS W-9 instructions describe the taxpayer identification and certification fields a payer normally requests; they do not establish signer authority.
Set a follow-up cadence that people can keep
A follow-up cadence only works if it is short enough to act on and long enough to be fair. A common pattern is a delivery check at 7 days, first owner contact at 14 days, second contact at 30 days, and escalation at 45 days. Adjust the intervals to the client's owner base, mail reliability, and payment calendar.
Each contact attempt needs a channel, date, outcome, and next step. "Left voicemail" is an outcome. "No answer" is not, unless the queue records how many attempts were made and when the next is due. If the owner asks a question, move the row to owner question open and route it to the role that can answer it.
Route defects with reason codes
Returns are not all the same. A missing signature, a signature by the wrong capacity, a missing notary, an altered decimal, a name mismatch, a wrong property, and a refused signature each require a different response. Use a controlled reason list and a short factual note.
For a missing signature, resend with the correct signature block and clear instructions. For a capacity problem, request the authority document before resending. For a decimal dispute, stop the correction and route the question to the reviewer who can compare the ownership schedule and the division order basis. For a name mismatch, request the connecting document rather than editing the name to match the lease.
Corrections should create a new version, not erase the old one. Record the version number, reason, reviewer, and date. If the owner already signed a prior version, preserve that signed copy even when it is superseded.
Keep owner questions inside the right lane
Owners often call with questions that sound administrative but are substantive. Why is my decimal lower than my sibling's? Why is this well on my statement? Why is the payment held? The administrator can explain the document, confirm receipt, request missing information, and route the question. The administrator should not interpret the lease, decide heirship, recalculate an interest without an approved basis, or promise a payment date that revenue accounting has not confirmed.
Create a small question log with the owner, property, question summary, date received, assigned reviewer, response date, and outcome. Link it to the division order row. If the same question appears across many owners, fix the form or add an explanatory insert rather than asking the queue to absorb the volume.
Measure the queue, not the mailing
Track the percentage of orders validated before mailing, median days from sent to returned complete, the defect rate by reason, the number of orders with no contact attempt after 14 days, and the age of owner questions. Report the denominator with each rate. A defect rate of 12 percent means something different when based on 25 orders than on 400.
Review a sample of closed rows each month. Confirm that the signed document is stored, the decimal matches the approved basis, the signer capacity is documented, and the status history is intact. Check a few rows that closed quickly as well as rows that took a long time. Fast closure can hide a missing document.
A practical launch sequence
Start with one property or owner group. Build the queue with the fields above, then run the next ten mailings through it. If entity authority documents are the bottleneck, create a separate document request queue rather than letting division order rows sit in limbo.
Publish the status definitions and follow-up intervals. Train the people who prepare documents and the people who answer the phone. Give one person authority to escalate rows that pass the final interval. Review the queue weekly for the first month, then monthly once the reason mix stabilizes.
Teams that need help with owner contact and document chase can use a defined administrative support service. The client keeps approval authority for decimals, ownership, and payment decisions. For the payment side of the same relationship, the lease bonus payment proof packet shows how to connect a signed lease to release, delivery, and clearing evidence.
Frequently asked questions
How many follow-up attempts are enough?
There is no universal number. Set an interval that fits the owner base and payment calendar, document each attempt, and escalate when the final interval passes.
Should a division order be resent after a name change?
Yes, when the name on the document no longer matches the evidence. Create a new version, document the connecting document, and keep the prior signed copy.
Can an administrator correct a decimal to clear a queue?
No. A decimal correction needs the approved ownership basis and the authorized reviewer. The administrator can prepare the comparison and route it, but should not change the number to close the row.
Ready to Scale Your Landman Business?
Discuss a defined remote support scope for title research, lease administration, GIS coordination, or document work.
