%20(1).png?width=85&height=64&name=deckard-logo-only-white-ai%20(1)%20(1).png){kind=logo}
A rental registration ordinance that actually gets enforced needs three things working together: a data structure that captures the contact fields necessary for outreach and enforcement; design decisions that give landlords a real reason to comply; and a mechanism to find the landlords who never register voluntarily. Most ordinances get the first two partially right. Almost none solve the third without technology support. This guide walks through all three, written for the planning department staff member drafting a council recommendation or updating an existing program that has stalled.
Updated May 2026.
What a Well-Designed Ordinance Must Require
The National League of Cities is direct on this point: "The absolute minimum is information about the owners (and if an LLC, the real people behind it) and, if the owners live outside the city or county, a local agent or manager who will handle emergencies and accept legal services." That framing matters because the purpose of a registration requirement is not to generate paperwork. It is to give the city a verified contact for every landlord operating within its boundaries.
High-compliance programs collect a specific set of data fields at registration. Each one does a different job:
- Legal owner name and mailing address. The address on the tax assessor's record is often a PO box or out-of-state LLC address that no one monitors. The ordinance should require the physical mailing address of the person who makes decisions about the property.
- Out-of-state or absentee landlord designation. Jurisdictions with a large share of investment properties need to know which owners cannot receive a notice by local mail. Out-of-state investors are the hardest segment to reach and the most likely to be non-compliant. Flagging them at registration changes the outreach strategy.
- Local emergency contact. A landlord in another state cannot respond to a pipe burst or a tenant welfare check. PolicyLink recommends requiring a locally-based emergency contact who can be reached 24 hours a day and accept legal service, separate from the owner record.
- LLC beneficial owner disclosure. The majority of investment rental properties are owned through limited liability companies. In most states, an LLC is only required to list a registered agent, not the individual who financially benefits from the investment. Minneapolis addresses this directly: rental properties owned by LLCs must disclose "an associated natural person… and a copy of the Articles of Organization listing the shareholders of the LLC." Without this field, your ordinance creates a built-in evasion path for portfolio investors.
- Unit count and property type. A four-unit building with one absentee owner represents four households, not one property. Recording unit count makes fee calculations accurate and sets the scale of the compliance gap correctly.
"The absolute minimum is information about the owners (and if an LLC, the real people behind it) and, if the owners live outside the city or county, a local agent or manager who will handle emergencies and accept legal services."
National League of Cities, Rental Registry Guidance
Two additional fields that programs frequently omit but later wish they had: tenant emergency contact information (critical for emergency evacuations and public health notifications) and a current photograph or description of property entry points (valuable for code enforcement officers doing first contact visits). These are not required for a functional ordinance, but they meaningfully expand the city's ability to respond to incidents at properties where the landlord is unreachable.
Three Design Decisions That Determine Enforcement Outcomes
The data fields in your ordinance determine what you can do with it. The design choices below determine how many landlords will actually comply, which shapes whether those fields ever get populated.
1
Tie registration to a meaningful prerequisite
The cities with the highest compliance rates do not rely on good faith. They tie registration to something the landlord actually wants. PolicyLink identifies three proven triggers: the ability to raise rent (registration required before any rent increase takes effect), access to eviction court (Seattle implemented this; a landlord whose property is unregistered cannot proceed with eviction until registration is current), and the issuance of a certificate of compliance required for certain property transactions. Even a modest trigger changes the calculus for landlords who would otherwise ignore a registration notice. Programs without any meaningful prerequisite consistently stall in the 20–40% compliance range.
2
Set fees at the right level to fund program administration
Rental registration programs are generally designed to be revenue-neutral on administration costs: fees cover staff time, system maintenance, and outreach without generating surplus. In practice, a per-unit fee in the $5–$15 range funds program operations without being punitive enough to generate political opposition from landlord groups. Real-world data confirms this range: Concord, CA charges $5.25/unit; Cape Coral, FL charges $35/year for long-term rentals; Spokane, WA uses a $127 base plus $15/unit. Higher fees are feasible in larger cities but require a clear public justification. Per-property fees (flat rate regardless of unit count) systematically undercharge portfolio investors who own multi-unit buildings and overcharge single-property owners, a design flaw that creates equity problems. Per-unit structures are more defensible and more revenue-proportionate.
3
Choose proactive versus complaint-based inspection triggers deliberately
Complaint-based inspection is the default because it requires no staff capacity beyond responding to filed complaints. Proactive inspection, where the city initiates inspections on a schedule without waiting for a report, costs more but produces measurably better compliance rates and housing quality outcomes than complaint-based systems alone. Seattle's Rental Registration and Inspection Ordinance (RRIO), the most-studied model in the country, covers 14.5% of properties with inspections annually, with random selection for compliance verification. The practical middle path for smaller jurisdictions is risk-based inspection triggers: proactive inspection for properties with prior complaints or violations, complaint-based for first-time registrations in good standing. This concentrates staff resources where the risk is highest.
A 2019 report for the City and County of San Francisco found that "active enforcement involving regular communication between rent programs and landlords and tenants results in a higher rate of compliance with program requirements" than passive programs that charge lower fees and rely on voluntary participation. That finding generalizes: the design of the program predicts its compliance rate more reliably than the text of the ordinance.
The Outreach Strategy That Drives Initial Registration
Most programs launch with a single citywide notice and then spend the next three years wondering why compliance plateaued at 35%. The programs that achieve 70%+ compliance in their first year use a segmented, phased rollout that is worth replicating.
Three-Phase Rollout That Works
Phase 1: Large portfolio owners first. Property management companies and investors with three or more properties are responsible for a disproportionate share of the rental housing stock. They also have business relationships that make compliance administratively manageable for them. Start here. Direct outreach by phone or formal written notice to this segment, identified from property tax records, builds the initial registry quickly and generates fee revenue that funds the rest of the rollout.
Phase 2: Single-property owners with a grace period and amnesty window. Individual landlords with one property are often unaware an ordinance applies to them. An amnesty window (typically 60 to 90 days) during which late fees are waived for first-time registrations dramatically improves initial uptake. Frame the amnesty explicitly in outreach communications. "Register by [date] and no penalty applies" converts more landlords than any enforcement threat, and it is politically easier to administer than a citywide penalty campaign.
Phase 3: Targeted follow-up on non-responders. After the grace period closes, the non-responder list is the enforcement queue. This is where the compliance gap lives permanently: absentee owners who did not receive the notice, LLC-owned properties where the registered agent did not forward the communication, and landlords who deliberately avoid registration. Without a mechanism to identify and reach this segment, program compliance will never exceed what voluntary participation alone produces.
Seattle's program explicitly planned its rollout to start with known "bad actors," a targeted enforcement-first strategy that signals to the broader market that the city intends to enforce. The NLC cites this as one of the design elements that contributed to Seattle's long-term compliance success. Newark, NJ demonstrates what active outreach can achieve at scale: stepped-up enforcement of its rental registry ordinance helped increase registered landlords from 520 in 2018 to 2,885 in 2020, a 454% increase in two years. That did not happen through passive noticing.
The Technology Gap That Defeats Even Well-Designed Ordinances
Rentalscape LTR by Deckard Technologies exists to solve the one problem a well-written ordinance cannot: a jurisdiction cannot enforce registration against landlords it does not know exist. After the initial rollout, the non-compliant population is not the landlords who registered and then lapsed. It is the absentee owners, the recent property conversions to rental use, and the LLC-held properties where the registered agent absorbed the notice and did nothing. The city has no mechanism to find them unless a complaint gets filed, and complaints only arrive after a problem has already occurred.
Rentalscape LTR is an extension of Rentalscape STR, the AI-powered platform already trusted by more than 500 jurisdictions for rental compliance. It provides the discovery mechanism that ordinance-only programs lack: an automated system that surfaces unregistered long-term rental properties before any complaint is filed, by cross-referencing residential rental listing data with property ownership records and comparing that against the jurisdiction's existing license database. Properties actively advertised as rentals but not appearing in the registration system become visible, with verified owner contact data attached, so the city can initiate targeted outreach rather than waiting.
The difference between an ordinance-only program and one supported by active discovery is not marginal. Deckard's deployment data shows that jurisdictions using AI-powered discovery and active outreach typically move compliance rates from the 20–30% range to 70–95% over 12 to 18 months. The ordinance sets the legal framework. The technology solves the discovery problem the ordinance cannot.
| Program Element | Ordinance-Only Program | Ordinance + Rentalscape LTR |
|---|---|---|
| Property discovery | Only properties that self-register are known | Forensic AI cross-references listing data and property records to surface likely unregistered rentals automatically |
| Non-compliant landlord outreach | Depends on complaint or manual investigation | Targeted outreach campaigns with verified owner contact data, including absentee and out-of-state landlords |
| LLC-owned properties | Visible only if LLC voluntarily registers | Platform cross-references ownership records and listing data to identify LLC-held properties operating as rentals |
| Compliance rate over 18 months | Typically stalls at 20–40% without active follow-up mechanism | 70–95% with AI discovery and targeted outreach campaigns |
| Renewal tracking | Manual; staff draft and send individual reminders | Automated renewal alerts at configurable intervals; renewal queue visible in dashboard |
| Staff hours required | High; manual effort for data entry, reminders, and reporting each cycle | Low; automated workflows handle routine tasks; staff focus shifts to enforcement decisions |
| Council reporting | Manual data manipulation; hours per report cycle | Council-ready reports generated in minutes; interactive map filterable by status, neighborhood, or expiration date |
The key shift is that once Rentalscape LTR is deployed, staff stop asking "how do we find who isn't registered?" and start asking "which non-registrants should we prioritize for enforcement?" That is a materially different and more productive operational question.
For more on the technical side of how AI surfaces unregistered properties, see How AI Discovers Unregistered Long-Term Rentals.
What Implementation Actually Looks Like
Rentalscape LTR deploys in weeks, not months. Implementation starts with data ingestion: the platform is configured to match your jurisdiction's specific ordinance requirements and connected to your existing property data sources. Staff onboarding follows. The first outreach campaigns to non-compliant landlords typically launch within weeks of go-live, not the months or quarters that custom-built systems require. Deckard's dedicated customer experience team manages the process.
The operational shift is immediate. Before deployment, a typical housing department staffer spends a significant portion of their week on data entry: entering new registrations, tracking renewal dates, manually checking which properties have lapsed. After deployment, those tasks are automated. Renewal alerts go out on a configured schedule. The dashboard flags properties approaching expiration. The outreach queue for non-registrants is populated by the AI discovery engine, not by manual cross-checking. Staff involvement moves from data entry to enforcement decisions: reviewing flagged properties, approving outreach letters, following up on non-responses. The Mount Pleasant benchmark (one coordinator managing 400 annual STR permit renewals) demonstrates what this shift looks like at operational scale on the Rentalscape STR platform that LTR extends.
For the council recommendation, the financial argument is straightforward. For a mid-size city with a 30% compliance rate and 2,000 registered properties, closing that gap at a $100 annual license fee generates hundreds of thousands of dollars annually in previously uncollected revenue, from existing ordinance authority and without creating new taxes. Jurisdictions typically recover program implementation costs within the first renewal cycle. For a detailed framework on building that budget case for your finance director or city manager, see How to Build a Business Case for Long-Term Rental Compliance Software.
Frequently Asked Questions
Do we need to update our ordinance to use Rentalscape LTR?
No. Rentalscape LTR is configured to match your jurisdiction's existing ordinance requirements, not the other way around. The platform handles whatever your current ordinance specifies: annual or biennial registration cycles, per-unit or per-property fee structures, specific data fields, and inspection workflows. If your program is currently operating with a compliant ordinance but low registration rates, the platform can be deployed without any ordinance changes. If you are drafting a new ordinance or revising an existing one, Deckard's team can provide guidance on data field requirements and fee structures that maximize enforcement capability, but a policy update is not a prerequisite for going live.
How does Rentalscape LTR handle properties owned by LLCs?
Rentalscape LTR's discovery engine cross-references rental listing activity with property ownership records, including LLC-held properties, to identify non-compliant owners regardless of corporate structure. When a property actively advertised as a rental is traced to an LLC not in the registration database, the platform flags it for outreach with whatever ownership contact information is available. This does not replace an ordinance provision requiring beneficial owner disclosure at registration (that provision remains important for the reasons described above), but it means the city can identify and initiate contact with LLC-held non-compliant properties rather than waiting for them to appear voluntarily. For a broader look at why LLC ownership structures create specific data challenges for housing departments, see Institutional Landlords: What Cities Don't Know About Who Owns Their Rentals.
What data does Rentalscape LTR need from us to get started?
Rentalscape LTR accepts your existing registration data in whatever format it currently lives in: spreadsheets, a legacy licensing system, or a partial database. Bulk spreadsheet uploads seed the system with your current registered properties so the AI discovery engine immediately has a baseline to compare against. From there, the Deckard implementation team handles configuration: ordinance-specific fields, fee schedules, renewal cycles, and integration with your property assessor data. The onboarding process is designed for jurisdictions with limited IT staff. You do not need an enterprise data integration project to get started.
What compliance rate should we expect?
The range across Deckard deployments is 70–95% compliance over 12 to 18 months for jurisdictions starting from a typical 20–30% baseline. The higher end of that range requires active AI-powered discovery, targeted outreach campaigns, and a meaningful compliance trigger in the ordinance. Programs with weaker compliance triggers will reach a lower ceiling regardless of the technology supporting them. Deckard Technologies provides jurisdiction-specific revenue impact estimates as part of the evaluation process, using your current license count, fee structure, and estimated gap to model realistic outcomes.
What if our jurisdiction is starting from scratch with no ordinance yet?
A jurisdiction without a current ordinance has the design opportunity that existing programs rarely get: the chance to build in the right data fields, compliance triggers, and fee structure from the start. The NLC's rental registry guidance and the Local Housing Solutions case studies provide ordinance model language reviewed against real programs across dozens of cities. Deckard's team has worked with jurisdictions at every stage of program development, from pre-ordinance planning through post-launch enforcement. Starting with the right design (LLC beneficial owner disclosure, a meaningful compliance trigger, a phased rollout plan, and the right fee range) sets a compliance ceiling significantly higher than programs that layer technology onto a weak ordinance after the fact.
For a broader foundation on what a fully modern LTR compliance program looks like, see the Local Government Guide to Long-Term Rental Compliance. To understand the AI technology that powers property discovery, see What Is Forensic AI for Rental Compliance?
LinkedIn
Facebook
X
Related resources
