curative requirement evidence matrix: Keep the requirement and response apart
A curative matrix should show three things without blending them: the original requirement, the material submitted in response, and the decision made by the person authorized to accept or reject that material. The distinction matters because a document can arrive on time and still fail to answer the request. Likewise, an email saying that a problem has been handled is evidence of a communication, not evidence that the reviewing attorney or title examiner has waived the requirement.
Begin a row by copying the requirement as issued. Retain the requirement number, affected party or tract, date, source document, and exact requested evidence. If the request contains alternatives, conditions, or a deadline, keep those terms with the row. A shorthand summary can help the team sort work, but it belongs beside the quoted requirement rather than in its place. That preserves the instruction a reviewer actually gave and prevents later responses from quietly changing the question.
Set the matrix scope before loading rows. Identify the project, jurisdiction, title opinion or examination, record cutoff, and decision owner. If one opinion covers several tracts or parties, decide whether a requirement will have a parent row with separate response items or one row for each affected interest. The structure should make partial completion visible. A single green status for a requirement that covers five tracts can hide the fact that one release or affidavit is still missing.
Describe evidence at document level
Describe each response item so another person can retrieve it. For a recorded instrument, capture the document title, grantor and grantee or other named parties, execution date, recording date, county, book and page or instrument number, and the image location. For a court document, retain the court, case number, filing title, date, and docket entry. An affidavit, death certificate, corporate record, tax document, or regulator filing needs an equivalent source-specific locator. “Affidavit received” is not enough when several affidavits concern the same family or tract.
One response may address only part of a requirement. Suppose a title opinion requests proof of identity and a recorded conveyance. An affidavit may answer the identity question while leaving the conveyance open. Enter it as a response item, link it to the identity component, and leave the other component unresolved. Do not force the whole requirement into a single complete or incomplete choice when the evidence supports a more precise account.
Record provenance for copies as well. Note whether an image came from an official county system, a court portal, the client, opposing counsel, or an internal archive. Save the access date and, where permitted, a checksum for the retained file. A source label helps the reviewer judge whether a legible but unofficial copy is enough for the immediate purpose or whether a certified or recorded version is still needed.
Normalized names and dates can support sorting, but they should not overwrite the source text. Keep “Jno. A. Smith,” “John A Smith,” and “John A. Smith, Jr.” as observed values, then explain any proposed identity link. Keep an instrument's execution and recording dates in separate fields. These controls expose the very differences that curative work is supposed to resolve.
Make disposition authority visible
Use event dates instead of one mutable “last updated” date. A practical history may include requirement issued, request sent, evidence received, review assigned, returned for more support, and accepted. Each event needs an actor, timestamp, and supporting message or document. This history explains why an item is still open after evidence arrived and shows whether delay sits with research, a third party, or the decision owner.
Only the designated reviewer should enter the substantive disposition. Staff may mark a delivery complete, assemble a comparison, or flag that every requested file appears to be present. Those are workflow observations. Acceptance, waiver, or a finding that alternative evidence satisfies the requirement is a different act. Make the distinction visible through separate fields for delivery status and reviewer disposition, with the reviewer name and decision date locked into the audit history.
Search failures also belong in the record. Document the official system or custodian, the names and identifiers searched, date range, filters, access time, and result. A no-result screen means that query returned no match; it does not prove that an instrument never existed. Spelling variants, historical names, unindexed images, another county, or a record outside the searchable period may require a different route. The next action should follow from the documented limit rather than from an unsupported conclusion.
Test a closed row from the beginning
Before closing a row, reconstruct it from the beginning. Open the cited opinion page and confirm the requirement number and exact language. Reopen every response item from its locator. Check that the party, tract, legal description, interest, and relevant dates match the requested scope. Then open the review note and confirm that the decision came from the authorized person and applies to this requirement rather than a similar item elsewhere in the project.
Consider a requirement for a recorded release of a lien affecting a named tract. The team receives a release, but its legal description covers only part of the tract and the instrument references a different recording number. The response is real and relevant, yet it does not establish that the cited lien was released across the required property. The matrix should record the instrument, identify both mismatches, and ask the reviewer whether another release, a correction, or additional evidence is required. Marking the row complete because the document title says “Release” would conceal the central issue.
A second example involves capacity. An affidavit may state that a signer acted as personal representative, while the requirement asks for the court appointment establishing that authority. The affidavit belongs in the response history, but the appointment or probate order remains a separate missing item. This is why evidence descriptions need document roles. A statement about authority and the judicial record conferring authority are not interchangeable merely because they concern the same person.
Return and review rules
Return a row when its status rests only on receipt, when the evidence lacks a retrievable locator, or when the reviewer decision is missing. The return note should name the requirement, affected party or tract, exact gap, sources checked, deadline, owner, and requested next step. “Needs more research” does not tell another person where the work stopped. “No recorded release found under these two names in the county index through the stated cutoff; request the lender's release information” does.
Quality review should sample both open and closed work. Open rows reveal whether next actions are specific and useful. Closed rows test whether the team preserved the original requirement and obtained a valid disposition. Recheck native identifiers, recording references, legal descriptions, and incorporated exhibits. If a spreadsheet formula or name normalization influenced the comparison, the reviewer should be able to see that rule without reverse-engineering the file.
Decision packet and operating rhythm
The reviewer packet should be short enough to decide but complete enough to verify. Include the original requirement, a list of response items with locators, the specific comparison performed, unresolved facts, earlier review notes, and one bounded question. If ten requirements are ready, group them without hiding their separate decisions. A cover summary can list the rows, but each acceptance should still point back to its own evidence.
Manage the queue by real deadlines and decision dependencies. New evidence should trigger a comparison, not an automatic status change. Returned items should show what was added since the prior review. Long-running third-party requests need a last-contact date and next follow-up date, while internal review waits need the assigned reviewer. Close a requirement only when its requested support and reviewer disposition are both present, then retain the event history so later users can see how the conclusion was reached.
If your team needs support maintaining a traceable curative requirement evidence matrix, 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.
