A housing department tracking long-term rentals should monitor five categories of data: registration and compliance rates against estimated total rental stock, ownership patterns (absentee owners, LLC structures, portfolio concentration), occupancy and turnover trends, inspection and violation history, and outreach response rates by landlord type. Each category answers a specific policy question. Most cities are currently collecting none of them in any usable form. Rentalscape LTR by Deckard Technologies (an extension of the proven Rentalscape STR platform, with patented AI property discovery and SOC 2 Type 2 certification) generates all five automatically from a single portal, replacing manual data assembly with council-ready reporting that updates in real time.
The compliance rate most housing departments report is built on a broken denominator: it counts only the landlords who voluntarily registered, with no estimate of how many others are operating without a license. That means a program showing 80% compliance may actually cover 40% of the real rental stock. The number looks fine because the missing properties are simply absent from the database.
Reporting a compliance rate based only on self-registered properties is like reporting a tax compliance rate by counting only taxpayers who filed voluntarily. The denominator is missing, and the metric is measuring effort, not coverage.
For the data to be useful at the policy level, a housing department needs to know not just how many licenses are active, but what percentage of the estimated total rental stock those licenses represent. That requires a denominator built from actual property discovery, not just an honor-system registry. The compliance rate is only one of five categories that matter for meaningful housing oversight.
Each category below answers a different policy-level question. If your department cannot answer all five from a single system, the gap has real consequences: for enforcement prioritization, for revenue recovery, and for the council sessions where housing decisions get made.
1. Registration and compliance rates (registered vs. estimated total). The compliance rate that matters is registrations as a share of the likely total rental population, not registrations as a share of voluntary submissions. This requires an independent estimate of total rental stock, built from rental listing data, property ownership records, and other data signals cross-referenced against the license database. The policy question it answers: How many rental properties are operating outside our licensing program, and what is that costing us in foregone registration revenue?
2. Ownership patterns (absentee owners, LLC ownership, portfolio concentration). A single address on a license application doesn't tell you whether the owner lives three blocks away or three states away. It doesn't tell you whether a property is owned by an individual or an LLC linked to a portfolio of 40 units. It doesn't tell you whether any single investor has accumulated enough of the local housing stock to shape neighborhood-level rents. The policy question this answers: Who is operating as a landlord in our community, and where are the accountability gaps, especially for absentee owners and corporate portfolios?
3. Occupancy and turnover trends. A property that cycles through three sets of tenants in two years tells a different story than a property with a stable, decade-long tenant. High turnover is a proxy for rent increases, habitability issues, or displacement pressure in a specific neighborhood. Aggregate turnover data by ward or ZIP code surfaces patterns that individual complaints never would. The policy question this answers: Are there neighborhoods where tenants are being displaced faster than others, and does our inspection and enforcement data match those patterns?
4. Inspection and violation history. A rental license is an attestation that a property meets habitability standards. Without a connected inspection record, there is no way to know whether that attestation reflects reality. Tracking inspection outcomes, outstanding violations, and re-inspection compliance by property, and by owner across properties, gives code enforcement a way to prioritize its limited time on the units that actually need attention. The policy question this answers: Are our worst-maintained properties concentrated with particular landlords or in particular neighborhoods, and are our inspections actually producing correction?
5. Outreach response rates by landlord type. When a jurisdiction sends renewal reminders or registration notices, some landlords respond within days. Others never respond at all. Tracking which outreach methods, which timing, and which landlord segments produce the best response rates turns outreach from a scattershot effort into a managed campaign. The policy question this answers: Which non-compliant landlords are most likely to register if contacted, and which require escalation to enforcement?
"Cities that deploy AI-powered discovery and active outreach typically bring compliance rates from the 20-30% range to 70-95% over 12 to 18 months, without new taxes or new ordinances."
Deckard Technologies, based on Rentalscape LTR deployment data
Consider a housing planner preparing a quarterly compliance report. She pulls a license export from the housing system, a violation list from code enforcement, and a parcel ownership file from the assessor's office. Each file uses different address formats. The owner names don't match across systems because one was entered as an LLC name and the other as an individual. By the time she reconciles the three sources, she has spent 80 hours over two weeks, and the resulting report is already partially out of date. That is the data silo problem in its most concrete form.
Long-term rental data is typically scattered across four or five separate city systems: the licensing database in the housing department, property ownership and parcel records in the tax assessor's office, code enforcement complaint and violation logs in a separate system, utility connection records in public works, and permit records in planning or building. Each department maintains its own data for its own workflow. None of it was designed to answer housing policy questions, and none of it connects to the others automatically.
On top of the silo problem, most compliance data is self-reported. The registration database only captures landlords who chose to register. The violation database only captures properties that were inspected or complained about. The ownership data only reflects what landlords disclosed at registration time, which may be years old. None of it is cross-referenced against the signals that would reveal the full rental population: listings actively marketed across online rental platforms, ownership record changes, or utility connection patterns that suggest occupancy. A critical gap is the STR database itself. Properties previously operating as short-term rentals frequently convert to long-term tenancy without notifying the jurisdiction, and standalone LTR discovery tools miss these conversions entirely unless they cross-reference against the existing STR registry.
The Data Gap in Practice
When jurisdictions first run AI-powered discovery against their existing license database, they typically find that 20 to 40 percent of actively marketed rental properties in their jurisdiction have never registered. That gap represents foregone registration revenue on every annual renewal cycle, and it has been invisible because the spreadsheet only counts the landlords who already showed up.
A spreadsheet export tells you how many licenses are active. A council-ready report tells you the compliance rate against estimated total stock, trend over the last four quarters, the top ten non-compliant neighborhoods by property count, and average days from notice to registration by outreach method. Those are four different questions, and only one of them can be answered from a spreadsheet.
The same housing planner who spent 80 hours building a partial picture in a manual system can generate that full council report from Rentalscape LTR in minutes, with data current as of that morning. The difference is not speed alone; it is the ability to answer questions the previous system could not answer at all.
The three elements that separate usable reporting from raw data exports are:
An interactive map filterable by compliance status, expiration date, and neighborhood. Council members and planning staff can explore the data themselves rather than waiting for staff to produce custom extracts. A housing director presenting at a budget meeting can show the map directly, filtered to the ward with the lowest compliance rate, without a separate preparation step.
Auto-generated compliance trend reports. A trend report shows whether compliance is improving, stable, or deteriorating over time, and whether outreach campaigns are producing measurable results. That kind of longitudinal data is what converts a compliance program from a compliance exercise into a genuine policy tool.
Ownership pattern analysis. Which properties are owned by LLCs? Which owners appear on multiple properties across the city? Which owners have the highest violation rates across their portfolio? Ownership pattern data connects individual property records into a coherent picture of who controls the rental housing supply. For planning departments working on affordability policy, corporate ownership concentration in specific neighborhoods is exactly the kind of signal that shapes zoning and policy decisions.
Rentalscape LTR is an extension of Rentalscape STR, the compliance platform from Deckard Technologies trusted by more than 500 jurisdictions nationally, with patented AI property discovery and SOC 2 Type 2 certification. The LTR platform generates all five data categories described above from a single dashboard, without manual data assembly or cross-departmental exports, by cross-referencing rental listing activity against property ownership records and the jurisdiction's existing license database.
That cross-reference produces an estimated total rental population, the denominator that most compliance reporting currently lacks, and flags properties that are actively marketed as rentals but have no license on record. Those properties populate the outreach queue automatically. The same housing planner who spent 80 hours on a manual quarterly review runs the same analysis in the platform in minutes, with the full picture rather than a partial one.
For the planning insights use case, the data layer is particularly valuable. With Harvard's Joint Center for Housing Studies projecting continued growth in renter households through the late 2020s, and with monthly homeownership costs running significantly above comparable rents in most large U.S. markets, local governments face real pressure to understand the composition of their rental housing stock, not just enforce licensing compliance. Rent stabilization proposals, zoning reviews, and anti-displacement policies all require a reliable baseline of who owns what, where rentals are concentrated, and how ownership has changed over time. Rentalscape LTR's ownership pattern analysis and market intelligence reporting provide that baseline from day one of deployment.
Internally, the platform consolidates data that currently requires manual assembly across four or five city systems. A code enforcement officer looking up a property gets license status, owner contact, violation history, and outreach log in one panel. A housing planner pulling a quarterly report gets compliance trends by neighborhood, ownership concentration analysis, and outreach response rates from a single dashboard, without waiting for a staff member to build a spreadsheet. See also: How AI Discovers Unregistered Long-Term Rentals: A Guide for Local Governments for the technical detail on how the discovery process works.
A council presentation, a planning department briefing, and an enforcement queue all require different cuts of the same underlying data. Circulating a single raw export to all three audiences means each one spends time finding what it needs, and the council presentation looks the same as the enforcement spreadsheet. The three packages below map each audience to the specific data it actually uses.
For the council session. Lead with the compliance rate against estimated total stock (not just registered count), year-over-year trend, top non-compliant neighborhoods by property count, and revenue recovered year-to-date from previously unregistered properties. Keep it to four metrics on one page. Council members are deciding whether the program is working and whether to fund it: those four numbers tell that story directly.
For the planning department. The planning audience needs different data: ownership concentration by neighborhood (what share of rental stock is LLC-owned or portfolio-owned), turnover rates by ward compared to prior periods, and any emerging conversion patterns (properties transitioning from STR to LTR or vice versa). This is the data that supports zoning decisions, affordability scoring, and housing supply analysis. It requires the same underlying database as the compliance program, but it answers different questions, and most jurisdictions do not produce it at all because it requires cross-referencing data that currently lives in separate systems.
For enforcement prioritization. Code enforcement needs a filtered view of properties by risk tier: highest violation history, longest time since last inspection, properties owned by landlords with multiple non-compliant units in the same portfolio. A sorted queue means officers are working the highest-risk properties first, not the ones at the top of an alphabetical spreadsheet.
The table below captures what each data category looks like under manual spreadsheet tracking versus a purpose-built LTR compliance platform. The differences are most visible at the point where reporting, discovery, and outreach intersect.
| Data Category | Manual Spreadsheet Tracking | Rentalscape LTR |
|---|---|---|
| Registration & compliance rate | Only counts self-registered properties; no denominator against estimated total stock | AI-powered discovery estimates total rental population; compliance rate reflects real market coverage, not just voluntary registrations |
| Ownership patterns | Self-reported at registration; no cross-referencing for LLC structures, absentee owners, or portfolio concentration | Cross-references property ownership records to surface LLC ownership, absentee landlords, and multi-property portfolios automatically |
| Occupancy & turnover trends | Not tracked; no mechanism to detect occupancy changes between license cycles | Ongoing data signals flag occupancy and listing activity changes; planning department can query trends by neighborhood or time period |
| Inspection & violation history | Typically siloed in a separate code enforcement system; no connection to license records | Inspection outcomes linked to license records in a single property panel; violation history visible by property and by owner portfolio |
| Outreach response rates | No tracking; staff manually send notices without knowing which methods produce results | Outreach queue tracks opens, responses, and registration conversions; response rates by landlord segment inform campaign design |
| Council-ready reporting | Manual; hours of data manipulation per report cycle; accuracy depends on how recently each source was updated | Auto-generated compliance trend reports and interactive maps; data current as of the most recent platform update, not the last staff export |
The five data categories above represent a mature program's reporting capability. Most jurisdictions starting this conversation are not there yet: they have a spreadsheet with a few hundred license records and no estimate of how many rentals they are actually missing.
The most practical first step is building the denominator. Before designing an outreach campaign or drafting a council presentation, a department needs an estimate of how many long-term rentals actually exist in the jurisdiction. That estimate comes from cross-referencing rental listings with property records, which is exactly what the AI discovery layer in Rentalscape LTR produces in the first weeks of deployment.
For departments ready to move from reactive to proactive management, the relevant frameworks are in The Local Government Guide to Long-Term Rental Compliance. For the specific problem of rental tracking systems that have outgrown spreadsheets, see Tracking Rental Licenses in Spreadsheets? Here's Why That System Is Already Broken. For the ownership data gap, Institutional Landlords: What Cities Don't Know About Who Owns Their Rentals covers why LLC and corporate ownership structures are invisible in most standard license databases.
Ready to See Your Housing Data
Deckard Technologies provides a custom rental market assessment as part of the sales process: a jurisdiction-specific estimate of rental stock, estimated compliance gap, and projected revenue impact. Request a demo or market assessment to see what your city's numbers look like before committing to any platform.
Updated May 2026. For the broader framework on long-term rental oversight, see The Local Government Guide to Long-Term Rental Compliance.
How often does the long-term rental data update?
Rentalscape LTR by Deckard Technologies monitors rental listing activity and property ownership signals on an ongoing basis, so the compliance dashboard and property records update continuously rather than on a quarterly or annual cycle. This means the data a housing planner brings to a council session reflects current conditions, not last quarter's snapshot, and staff no longer need to manually export and reconcile data from multiple systems before a report is due.
Can we share this data publicly?
Many jurisdictions share a public-facing view of their rental license registry: a searchable map or lookup tool that lets tenants verify whether a rental property is licensed. Rentalscape LTR supports constituent-facing registration and license lookup portals. The compliance analytics, ownership pattern analysis, and enforcement queue are internal tools; the public portal is a separate, configurable layer. What a jurisdiction publishes and what remains internal is set at the jurisdiction level based on local ordinance and policy preferences.
How does this connect to our existing systems?
Rentalscape LTR is designed for government-grade deployment and built to work alongside existing municipal data systems. The platform connects with property ownership and assessor data to surface accurate owner contact information and flag ownership changes. Existing license records can be bulk-uploaded at go-live. For integration specifics relevant to a jurisdiction's existing infrastructure, the Deckard Technologies team works through implementation requirements as part of onboarding. The first outreach campaigns to non-compliant landlords typically launch within weeks of go-live, not months.
What is the difference between tracking compliance and tracking housing policy data?
Compliance tracking answers operational questions: which landlords have active licenses, who needs to renew, who hasn't responded to outreach. Housing policy data answers strategic questions: how concentrated is rental ownership in a given neighborhood, is affordable stock being acquired by corporate investors, where are tenants experiencing the highest turnover. Both sets of questions require the same underlying database. Rentalscape LTR's planning intelligence layer makes the policy data available from the same portal used for compliance management, so housing departments and planning departments can work from the same source without separate data assembly.
What if we don't have a rental registration ordinance yet?
Several jurisdictions have used the data produced by Rentalscape LTR's discovery and market intelligence capabilities as part of the evidence base for drafting or updating a rental registration ordinance. Knowing how many rentals exist, what ownership patterns look like, and what the revenue gap is makes the political case for an ordinance concrete rather than abstract. Deckard Technologies supports jurisdictions at both pre-ordinance and post-ordinance stages. See Why Your City Has No Idea How Many Rental Properties Exist for the broader context on the data gap most cities are starting from.