The operational handbook for record indexing projects
Written for county clerks, recorders, and records managers navigating backfile conversion, AI-assisted indexing, and the practical work of getting legacy records into modern systems.
Why these projects are harder than they look
The gap between “we have scanned records” and “our records are searchable” is where most of the real work lives.
Scanned doesn't mean indexed
Many offices digitized records years ago but never added metadata. The result is image files that can't be searched — only browsed manually.
OCR quality varies widely
Older documents, poor scan quality, and handwritten text all reduce OCR accuracy. Without a validation step, extracted data is unreliable.
Legacy index data is inconsistent
Offices that have been through multiple systems often have index data in different formats, with different field names, and different levels of completeness.
Import is more than an upload
Getting validated index data into a land records system or DMS requires precise formatting, field mapping, and error handling. It's rarely straightforward.
Two audiences, one project
Backfile and indexing projects sit at the intersection of budget decisions and daily operations. This handbook addresses both sides.
What leadership needs to know
Scoping and budgeting
Project cost depends on document volume, scan quality, the number of index fields per document type, and expected exception review volume. Get a realistic count and sample set before requesting quotes.
Evaluating timelines
Backfile projects are rarely fast. Build in time for piloting, QC iteration, and import testing — not just extraction.
Defining success
Success means records are searchable in the target system, staff can retrieve them reliably, and accuracy standards are met — not just that extraction ran.
What operators need to know
Exception review efficiency
How fast can staff review and correct low-confidence extractions? The review interface matters as much as the extraction accuracy.
Day-forward alongside backfile
Most offices can't pause daily recording to run a backfile project. The workflow needs to support both without doubling staff workload.
Import reliability
Getting clean data into the target system — with correct field mapping, validation, and error handling — is where many projects stall. Test imports early.
Stages of an indexing workflow
Whether you're running a backfile project or indexing day-forward, these are the stages that determine quality and throughput.
Scanning and image prep
Clean, consistent scans at appropriate resolution. Deskew, despeckle, and crop before OCR — image quality drives everything downstream.
OCR and text extraction
Convert scanned images to machine-readable text. Accuracy depends on scan quality, document age, and whether text is typed or handwritten.
Metadata extraction
Pull structured fields — document type, dates, party names, legal descriptions — from OCR output. High-confidence cases can be auto-accepted; edge cases need human review.
Exception review and QC
Staff review documents where extraction confidence is low, fields are missing, or data looks inconsistent. This is where accuracy is built into the process.
Normalization and cleanup
Standardize field formats, reconcile against existing data, and correct legacy inconsistencies — especially important for system migrations.
Import and validation
Map fields to the target system schema, validate against business rules, and load. Error handling and rollback procedures matter here.
Handbook chapters
Deep dives into the core topics, written for the people who plan and execute these projects.
What Is Backfile Conversion?
A plain-language guide to backfile conversion — what it involves, why public offices undertake it, and how to plan a project from scanning through indexing and import.
Read chapterAI Document Indexing for County Records
How AI-assisted indexing works for county clerk and recorder offices — OCR, metadata extraction, exception review, and what to realistically expect.
Read chapterReindexing, Quality Control, and Imports
Practical guidance on reindexing legacy data, QC workflows, exception handling, and importing index data into downstream systems.
Read chapterAbout This Handbook
Who produces this resource, why it exists, and our editorial standards.
Read moreState-specific guides
Recording office structures, governing statutes, and indexing requirements vary significantly by state. These guides cover the practical details for specific jurisdictions.
Connecticut
169 independent town clerks — not county recorders. The most fragmented land records system in the US, with no statewide portal.
View guideIowa
99 county recorders with a free statewide portal covering all counties, universal e-recording adoption, and companion document requirements.
View guideIllinois
102 counties, Cook County's 2020 recorder merger, and race-notice recording that makes grantor/grantee indexing accuracy legally material.
View guideLouisiana
The only US civil law state. Parishes, authentic acts, two-witness execution, and separate mortgage and conveyance record books.
View guideOhio
88 county recorders with a unique two-step Auditor-to-Recorder deed process and document formatting standards codified in statute.
View guideGeorgia
159 Superior Court Clerk offices with a statewide GSCCCA portal and the Deed to Secure Debt instrument used in place of mortgages.
View guidePennsylvania
67 county Recorders of Deeds with a mandatory UPI on all instruments, Realty Transfer Tax, and a strict 5-day Right-to-Know Law response window.
View guideVirginia
Circuit Court Clerks in the judicial branch, covering 95 counties and 38 independent cities — a structure unique to Virginia.
View guideNorth Carolina
100 Register of Deeds offices using Deed of Trust instruments exclusively, with Excise Tax stamps on older documents and NCAOR-coordinated standards.
View guideNew York
62 County Clerk offices upstate, NYC ACRIS for four boroughs, the RP-5217 companion document requirement, and LGRMIF grant funding.
View guideMichigan
83 county registers, dual transfer tax (SRETT + CRETT), and MCL 565.841 e-recording adoption across independent register offices.
View guideTexas
254 counties (most in the US), no state transfer tax, Deed of Trust standard, and the Texas Public Information Act's 10-business-day response window.
View guideFlorida
67 Clerks of the Circuit Court, Florida Sunshine Law immediate access standard, Documentary Stamp Tax, and the MyFloridaCounty.com statewide portal.
View guideTennessee
95 county registers, Realty Transfer Tax ($0.37/$100), Deed of Trust standard, and TSLA's Local Records Management program for digitization support.
View guideMaryland
23 counties plus independent Baltimore City, ground rent instruments unique to Maryland, and mdlandrec.net — one of the best free statewide land records portals in the US.
View guide