The nine title defects that stall most closings

Curative backlogs are not random. Across files we work, the same nine defect families account for nearly everything that stalls a closing. This is the list we teach new reviewers, in the order of how often each one eats a week of somebody's time.

1. Unreleased mortgages

The loan was paid, the satisfaction was never recorded. The lien still encumbers title. Resolution: identify the current holder through the assignment chain or the servicer, request the satisfaction with payoff evidence, and chase on a dated schedule. The ALTA survey from March 2026 put this defect family at the top: 59 percent of respondents called it their number one problem.

2. Missing or broken assignment chains

The mortgage was assigned from A to C, but the assignment from A to B never got recorded, or references the wrong instrument. Resolution: reconstruct the chain from public records and servicer data, then request a corrective assignment or a assignment nunc pro tunc from the current holder. This defect hides inside defect number one more often than it appears alone.

3. Probate and heirship gaps

An owner died and title never formally transferred: no probate opened, heirs never deeded, or an estate was administered in another state. Resolution: establish the devolution of title under the applicable state law, open or reopen probate where required, obtain deeds from heirs or a court determination. These are the slowest files in the pile because they involve courts.

4. Name mismatches

Robert Nguyen took title, the lien names Robert Nguyn, the payoff statement says Bob Nguyen. Same person, three spellings, and every one of them is an underwriting question. Resolution: alias documentation that ties the identities together, from DBA filings and prior policies to affidavits, so the chain reads clean to an underwriter.

5. Judgment and lien indexing errors

A judgment against James A. Smith lands on the title of James R. Smith, or a released lien never got marked released in the index. Resolution: pull the underlying instrument and the release, document the mismatch, and request a corrective entry from the recorder where the index itself is wrong. Unglamorous work, and exactly the kind of cross-referencing machines finish in one pass.

6. Mechanic's liens

A contractor recorded a lien for work the owner says was paid or never completed. Resolution: obtain a release from the contractor, a bond off the lien where state law allows, or a court order after the statutory window. Timelines are jurisdiction specific and the deadlines are unforgiving.

7. Missing heirs and undisclosed spouses

A prior owner's spouse never joined a conveyance, or an heir was omitted from an estate distribution decades ago. Resolution: heirship affidavits, curative deeds, or quiet title depending on how deep the gap sits. These defects surface during refinance booms when old files get re-underwritten.

8. Boundary and easement defects

The legal description in the deed does not close, overlaps the neighbor, or an easement referenced in the survey was never recorded. Resolution: surveyor reconciliation, corrective deeds, and recorded easement documentation. The math of a bad metes and bounds description is a specialist of its own.

9. Forged or defective instruments in the chain

The rarest family and the most serious: a notarization defect, an unauthorized signature, or an outright forgery years back. Resolution: court action to remove the instrument, with the evidence package doing the heavy lifting. This is where a citation-grounded work product earns its keep, because every assertion needs to survive an adversary reading it.

The pattern across all nine

Every family resolves the same way: assemble the evidence, identify the party who can fix it, push the paper, record the cure. The work is investigation and chase, spread across more than 3,100 county systems with no shared format. That shape is why we built ClearFile as an agent harness with a citation layer instead of a chatbot: the machine searches, reads, cross-references, and drafts, and a licensed human approves the package.

A defect table your officer can verify link by link beats a summary your officer has to trust.

If your backlog holds a mix of these, the fastest evaluation is empirical: send the ugliest file on the desk and compare what comes back overnight against what the team has after a week.