Curative Exception Data 2026: 6 Tracking Fields

A curative exception register should answer one question at a glance: what evidence created the exception, who can decide the response, and what recorded evidence would allow the reviewer to close it? Six fields cover that trail. An "ordered" or "received" document is not automatically a resolved exception.

The examples below come from Texas and Oklahoma statutes concerning correction instruments, heirship evidence, powers of attorney, and mortgage records. They show why the tracker needs jurisdiction and instrument fields. They are not legal advice, form instructions, or a decision that any instrument cures a particular defect.

Curative Exception Data 2026: What belongs in a curative exception register?

Each row should contain these six fields:

Keep the cited evidence separate from the requested response. If an opinion calls for a release, the tracker should preserve the exact requirement and its source. An administrator should not quietly translate it into a different instrument type.

This register can sit beside the broader land administration control fields. For ownership work, the mineral ownership research controls explain how to preserve source observations without turning them into conclusions.

Use document-specific examples, not a generic label

The word "curative" does not identify the document, signer, filing office, or legal basis. A useful row states what the reviewer requested and where the related requirement came from.

Texas correction instruments

Texas Property Code Sections 5.028 through 5.031 distinguish correction instruments used to correct recorded conveyances and set out different treatment for nonmaterial and material corrections. A tracking row should cite the original recording reference, the exact item identified for correction, the section or reviewer instruction being followed, the proposed signer path, and the recording reference for any completed correction instrument.

Do not reduce the row to "corrective deed pending." The distinction between an administrative typo and a substantive change is a reviewer decision.

Texas heirship evidence

Texas Estates Code Chapter 203 addresses recorded evidence concerning heirship. If a reviewer requests an affidavit or other heirship evidence, the register should name the decedent, affected tract, source of the requirement, requested evidence, county, and review state. Receipt of an affidavit does not settle whether it is sufficient for the project.

Oklahoma authority and mortgage records

Oklahoma Statutes Title 16, Section 20 addresses the execution and recording of a power of attorney used for a conveyance or the execution or release of a mortgage. A tracker concerning an instrument signed by an attorney-in-fact should identify both the affected instrument and the power-of-attorney recording reference requested by the reviewer.

Oklahoma Statutes Title 46 addresses mortgages and recorded assignments. For a missing release or assignment issue, preserve the mortgage reference, the last recorded assignment found, the evidence requested, and the county search date. Do not mark the row closed merely because payoff correspondence or an unrecorded copy entered the file.

These examples are deliberately different. The evidence needed to review a correction instrument is not the same as the evidence needed to trace signer authority or a mortgage assignment.

Status should describe evidence

Use a controlled status set that tells the next person what happened:

1. Open: the exception has been entered and needs reviewer direction or research.
2. Researching: assigned searches are underway.
3. Requested: a specific item was requested from a named party on a recorded date.
4. Received, unverified: the item is in the file but has not passed review.
5. Recorded, pending review: a recording reference is available for comparison.
6. Closed by reviewer: the authorized reviewer accepted the cited resolution evidence.

Avoid "done," "handled," and "looks good." Those labels hide whether the document was signed, recorded, compared with the request, or approved.

The lease administration data controls use a similar distinction between source values and workflow decisions.

Build the evidence chain before changing status

For every exception, preserve three separate layers.

The first layer is the trigger. Save the title requirement, instrument reference, missing link in the record, or reviewer note exactly enough that another person can locate it.

The second layer is activity. Log requests, follow-ups, responses, rejected drafts, and county searches with dates and responsible parties. Activity may show progress, but it does not prove resolution.

The third layer is closure evidence. Record the returned instrument, county filing reference, court order, or other item the reviewer required. Add the verification date and the reviewer who approved closure.

This separation prevents a common reporting error: measuring closed tasks instead of closed exceptions.

A sample row without a legal conclusion

Consider a reviewer who flags a Texas deed because a recorded name needs correction. The administrative row could say:

• Cited evidence: original county recording reference and the reviewer's written exception.
• Jurisdiction and tract: named Texas county and the project's tract identifier.
• Requested evidence: correction instrument as specified by the reviewer.
• Owner and status: assigned coordinator; requested on a stated date.
• Resolution evidence: blank until a recording reference is received and checked.
• Review: blank until the authorized reviewer accepts the evidence.

The coordinator can maintain that row without deciding whether the correction is material, who must sign, or whether the final instrument is legally sufficient.

Quality checks before delivery

Review the register for false closure and missing attribution:

• Every exception points to the evidence that created it.
• The jurisdiction and affected tract are explicit.
• Requested evidence uses the reviewer's wording.
• Each status has a dated event behind it.
• Recorded documents include the clerk reference and verification date.
• Closure names the approving reviewer.
• Unresolved scope, signer, and sufficiency questions remain visible.

Also check for duplicate rows. Two reviewers may describe the same record problem differently, while one exception may affect several tracts. Keep a stable exception ID and document the relationship instead of merging rows by guesswork.

Data sources and methodology

This review checked ten official Texas and Oklahoma statutory sources on July 30, 2026. Sources were selected because they name a document, record, acknowledgment, succession issue, or recording step that can appear in an exception register. The comparison extracts administrative fields for tracking. It does not recommend a form, determine who must sign, or decide whether evidence cures a defect.

Frequently asked questions

Who decides what document is required?

The client's authorized legal or title reviewer does. Administrative staff can organize the cited evidence, route requests, and track responses.

Does receiving a signed document close the exception?

Not by itself. The register should reflect whether recording, comparison, or reviewer approval is still required.

Can one status workflow cover every jurisdiction?

The high-level statuses can be shared, but document requirements and recording rules remain jurisdiction specific. Store the state, county, source authority, and reviewer instruction on each row.

What should a weekly curative report show?

Show open exceptions by age and owner, the last documented action, the next required evidence, and items awaiting reviewer approval. Keep activity counts separate from reviewer-approved closures.

Conclusion

A curative register earns trust when it preserves the defect, the requested response, and the closing evidence as separate facts. That structure lets administrative staff move work forward while keeping legal and title decisions with the authorized reviewer.

If curative tracking is consuming senior staff time, Book a free consultation.

Sources

1. Texas Property Code, Chapter 5, Sections 5.028 through 5.031 on correction instruments
2. Texas Estates Code, Chapter 203, nonjudicial evidence of heirship
3. Texas Property Code, Chapter 52, judgment liens and statutory release-of-record procedures
4. Oklahoma Statutes, Title 16, conveyances and recording requirements
5. Oklahoma Statutes, Title 46, mortgages and recorded assignments
6. Texas Civil Practice and Remedies Code, Chapter 121, acknowledgments and proofs of written instruments
7. Texas Estates Code, Chapter 201, intestate succession
8. Texas Estates Code, Chapter 252, safekeeping and custody of wills
9. Oklahoma Statutes, Title 58, probate procedure
10. Oklahoma Statutes, Title 84, wills and succession