SB 255: from legislation to action for county recorders

SB 255 is a short bill with a long operational tail. It added Section 27297.7 to the California Government Code, and in a handful of subsections it asks each covered county to do something most recorder offices have never done at scale: tell the people who signed a deed, quitclaim deed, mortgage or deed of trust that the document was recorded, by mail, within 30 days.

This article walks through what the section says, the decisions it leaves to each county, and a practical sequence for moving from "we read the bill" to "a print-ready batch is waiting every morning."

What the statute asks for

Paraphrasing the section's main parts:

• A program and a resolution. Each county establishes a recorder notification program, and the board of supervisors adopts an authorizing resolution. The statute sets January 1, 2027 as the date to have this in place.
• A mailed notice within 30 days. After the resolution, the recorder notifies the party or parties who executed a covered document, by mail, within 30 days of recording.
• The right address. The notice goes to the address for mailing tax bills that was established before the document was recorded.
• APNs on page one. The recorder may require the assessor's parcel number on the first page of covered documents, and may rely on it.
• Optional email alerts. The recorder may also run an electronic notification program in addition to the mailed notice.
• Exemptions and limits. Documents where a government entity is the grantee are excluded; the county is not liable for a failed notice; returned notices need not be kept; contracts for processing or mailing follow competitive bidding rules; and a board may authorize a fee capped at the program's reasonable cost.

Counties that already operate a notification program under Section 27297.6 are outside this section.

The decisions the statute leaves to you

The text is short, so much of the program design is local. Before choosing tools, most offices settle a few questions:

• Which of your document types are "covered." Your system probably has dozens of codes: grant deeds, trust transfer deeds, interspousal transfer deeds, corrective deeds, several flavors of deed of trust. Each needs to map to one of the four statutory categories or be excluded.
• Who counts as a government grantee. A list of agency names and patterns, and a rule for the uncertain ones.
• Whether to require APNs on page one. If you do, you can rely on them; if you don't, you need another way to find the parcel.
• Where the tax-bill address comes from. The Assessor's roll, but as of which date? The statute's "established prior to the recording" wording means you need history, not just today's snapshot.
• Who prints and mails. In-house staff, a county print shop or a mail house, and how the handoff is documented.
• Whether to offer email alerts, and in which languages.

From text to a daily routine

Once those choices are made, the program is mostly a daily loop. In SentraDeed it looks like this:

1. Files arrive. The Recorder's daily index and the Assessor's ownership extract land by SFTP or upload. A mapping profile translates each county's column names and codes into one standard format.
2. Every document is decided. Each recorded deed, deed of trust and mortgage is classified as a notice, a notice flagged for signer review, an exception, or excluded, with the reason stored. On a synthetic reference test set, the matching engine agrees with the answer key 100% of the time.
3. The parcel is found, from the index or, when the index has no APN, from the document image itself. Uncertain readings go to staff instead of producing a notice.
4. The right address is chosen from Assessor history as of the day before recording.
5. Staff work the exceptions, sorted by days left on the 30-day clock.
6. SentraDeed produces a print-ready batch, one accessible PDF with a mail-house manifest. County staff or the county's mail house print and mail it, then mark it mailed so the record shows when each notice left the building.

A realistic timeline

Counties that are further along tend to work in this order: confirm the program design with county counsel, collect a week of sample exports from both offices, build and dry-run the file mappings, approve a notice template in English and Spanish, run in parallel with real data for a few weeks, then go live and take the resolution to the board with real numbers in hand. The last two steps are where operating cost and staff time become visible, which also informs any fee the board considers under subsection (f).

What "done" looks like

A working program is not just a stack of mailed letters. It is being able to answer, on any given day: how many covered documents were recorded, how many notices went out and when, which cases are still open and how many days they have left, and who decided each exception. That record is what protects the office when a resident calls to ask why they did, or did not, receive a notice.