Fidlar Technologies Alternatives for County Recorders and Land Records Offices

Why county recorders start looking for an alternative

Recording offices do not change software on a whim. The system runs the counter, takes money, and creates the permanent public record of who owns what, and every one of those functions is defined by state statute. When a recorder starts looking for a Fidlar alternative, it is usually one of four triggers. The fee schedule changed at the state level and the update did not arrive fast enough. The search product that title companies pay to use is generating complaints and the county is losing subscription revenue. A new commissioner asked why remote search is a paid subscription for professionals while the general public gets something worse. Or a contract renewal arrived and someone finally read the terms around data ownership.

There is a fifth trigger, and it is the one worth taking seriously: a redaction or public access requirement changed. States keep tightening rules on personal identifiers in publicly available documents, and the ability to redact at scale, retroactively, across decades of scanned images is not something every system handles gracefully. If that is your problem, it is a genuine reason to look, and it is also the problem most likely to be solved with a layer rather than a replacement.

What Fidlar genuinely does well

Fidlar builds for the actual counter, which sounds trivial until you watch a recording clerk work. Documents arrive in person, by mail, and electronically. Fees vary by page count, document type, and statutory add ons. Money has to balance to the penny at the end of the day, receipts have to print, and the index entry has to be created correctly the first time because it becomes the legal reference forever. Software that handles that ritual smoothly, in a small office with two clerks and no IT department, is doing something valuable and unglamorous.

The remote search side is the other genuine strength, and it is also a revenue line for many counties. Title companies, abstractors, and attorneys need reliable searchable access to the index and images, and offering both a subscription product for professionals and a pay per use option for occasional users is a sensible model that keeps county costs covered. Counties that switch away sometimes discover they have accidentally cancelled a revenue stream.

Where recording software actually strains

Fee statutes are the first strain, and they are not the vendor's fault. State legislatures change recording fees, add surcharges, and create exemptions on their own calendar, and every product in this category has to translate that into configuration under time pressure. When your county has a local variation on top of the state rule, you feel the ceiling.

Integration burden is the second. A recording system wants to exchange data with the treasurer and general ledger, the assessor and parcel data, GIS, the tax system, and multiple e-recording submission networks. Those interfaces are usually fine when they exist and painful when they do not, and county offices rarely have the technical staff to bridge a gap themselves. Third is reporting rigidity. Recorders get asked for transfer volumes, revenue by document type, turnaround times, and trend data for budget hearings, and the standard reports usually cover the first two well and the last two poorly.

The fourth strain is the one to negotiate hardest on: data portability. Your index and your images are the county's permanent record, sometimes stretching back a century and a half. Before you sign or renew anything, establish in writing that you can obtain the full index in a documented, machine readable format, the images in a standard file format, and the linkage between them. If that clause is vague, everything else in the contract matters less than it looks.

Your realistic options, competitors included

The county land records market has a handful of established names. Tyler Technologies sells recording products into county government, Cott Systems has a long history with recorders and clerks, Kofile combines records software with preservation and digitisation services, and providers such as US Imaging and Business Information Systems serve counties with imaging and records management. On the submission side, e-recording networks including Simplifile, CSC, and the eRecording Partners Network connect settlement agents to your office regardless of which back office you run.

That last point matters. E-recording connectivity is largely independent of your recording software, so a complaint about submitters is often a network configuration issue rather than a reason to replace your system. Check which layer your problem actually lives in before you go to procurement.

When staying is the right call

Stay if the daily balance is clean, the index is accurate, and e-recording flows without manual intervention. Those three things are the job, and a system that does them reliably is worth more than a nicer interface. Stay if you are a small county without technical staff, because every custom system needs an owner and yours would be the vendor you just left. Stay if your complaints are about the public search experience or reporting, since both can be improved without disturbing the record. And stay if you are mid-way through a back file conversion, because splitting a conversion project across two systems creates reconciliation problems that outlive everyone involved.

When a custom layer pays back

The public search portal is the best custom investment a recorder can make. It is the part the public and the press interact with, it is where redaction obligations are visible, and it is completely separable from the recording engine. Build a modern search over a nightly copy of the index and images, with proper redaction handling, plain language help for members of the public who have never used a grantor grantee index, and an API for the title companies who currently scrape or re-key. You improve service, you protect the record, and you touch nothing statutory.

The second case is the data layer. A queryable copy of the index unlocks the reporting nobody currently gets: transfer volume trends for budget hearings, turnaround time by submission channel, revenue by document type, and the analysis a county board actually asks for. The third is workflow around the edges, such as tracking back file conversion progress, managing redaction requests from the public, and handling records requests with an auditable trail.

Migration reality for a permanent public record

Two rules govern land records migrations. First, the index and the images must be reconciled against each other before and after the move, document by document for a statistically meaningful sample and by totals for everything. An index entry that points at the wrong image is worse than a missing one, because nobody notices until a title search fails years later. Second, never migrate during a high volume period, and never split a recording day across two systems.

Plan for dual entry or heavy verification for a period after cutover, keep the previous system available in read only form until the new index has been verified in production, and keep your e-recording partners informed well in advance so submissions do not bounce. Counter staff retraining is short but critical, since the counter is where errors enter the permanent record. Budget for a slower recording day during the first week and staff accordingly.

Set aside time for the title community as well. Abstractors and searchers build habits around a specific search interface over many years, and a change to how the index is presented generates more feedback than almost any internal change you will make. Brief them early, keep the previous search reachable during the transition, and treat their complaints as usability data rather than resistance.

What each path costs

County recording systems are quoted, often with a mix of licence, conversion services, and revenue sharing on remote search subscriptions. Read the revenue share terms closely, because they are frequently the largest number over a ten year term. On the custom side, from Digital Heroes delivery experience: a public search portal with redaction handling, an API, and a reporting data layer over your existing index runs roughly $45k to $110k in 8 to 14 weeks. A full recording platform covering intake, fee calculation, cashiering, indexing, imaging, and e-recording interfaces runs roughly $150k to $350k over six to twelve months, and only makes sense for larger counties with technical staff.

The honest recommendation

Keep the recording engine and buy your conversion services from people who do that for a living. Build the public search, the API, and the reporting layer, because those serve constituents and county leadership and are where a shared product will always be a compromise. Switch back office vendors only when the daily balance is genuinely unreliable, when statutory updates are chronically late, or when your data ownership terms are unacceptable and cannot be renegotiated. And regardless of what you decide, get the export clause fixed at your next renewal, because the county's permanent record should never be difficult to retrieve.