St. Louis County Recorder Announces Transition to New Land Records System

The St. Louis County Recorder’s Office has posted a public notice that it is transitioning to a new Land Records Management System (LRMS) and new recording software; the county’s recording pages direct users to a transition schedule and a web-based land records/login portal. The notice as supplied to this newsroom did not include vendor names, a posting date, or detailed instructions beyond the referenced schedule and portal.

Nearby counties provide examples of services St. Louis County could deploy during or after its conversion. Columbia County, Oregon announced a Property Recording Alert Service, PRAS, on February 09, 2026; Columbia County Clerk Debbie Klug said, “Maintaining accurate and transparent property records is a core responsibility of the Clerk’s Office,” and described the PRAS as a free alert that notifies property owners when new documents are recorded. Columbia County’s announcement included a county phone contact, (503) 397-3796, for the Clerk’s Office.

Douglas County, Nevada describes a comparable rollout with a vendor identified as Helion Software. Murray Giesbrecht, Helion owner, is quoted: “Helion Software is pleased to announce the release of their Property Recording Alert Service. This notification allows (registered) members of the public to review the document and to personally verify it was legitimate. Douglas County, NV will be the first county to offer this new service from Helion.” Douglas County says the PRAS is a free replacement for its previous recording-notification service and that automated emails include a direct link to view or download the recorded document.

Douglas County Recorder Shawnyne Garren framed the limits of what a recorder’s office can do even with new technology: “Our office has seen growing concern from property owners about the potential of property fraud,” said Shawnyne Garren. “While we empathize with this concern, the staff of the Recorder’s Office do not have the legal authority to determine the validity or authenticity of a document submitted for recording. Nevada law requires that a document meeting the statutory recording requirements be recorded by my office. Although we cannot guarantee prevention of fraud, I am proud to have worked closely with Helion to design and implement this improved technology and encourage all property owners to register.”

National LRMS best-practice guidance underscores the technical choices counties face during a conversion. PRIA guidance notes that “an effective LRMS should have the ability to adapt to the changing demands and requirements of the recorder’s office” and warns that “state legislative actions may change recording requirements; therefore, capability for these revisions should be considered.” The guidance also stresses that “if historical images and data are added to the LRMS at a future date, the indexing and verification should be easily accomplished” and raises specific operational questions: “When an eRecorded document is modified after recordation, does the LRMS notify the submitter?”; “If there are communication interruptions during delivery, does the LRMS recognize and respond to the error?”; “Does the LRMS have safeguards in place to prevent duplicate recordings when documents are electronically delivered?” The guidance further notes that “Redacting Personally Identifiable Information (PII) from public documents recorded in the LRMS should be done when required by state, county or city legislation, or office policy.”

What the St. Louis County notice makes explicit and what remains unknown are both clear. The county has announced the LRMS transition and pointed the public to a schedule and a web-based login portal, but the notice supplied here did not state an LRMS vendor, provide a posting date, specify whether historical records will be migrated immediately or in phases, or say whether the Recorder will offer an alert service similar to PRAS. The county recording pages are the only channel named in the public notice for transition details and the schedule for implementation.