.png)
Key Takeaways
- Short-term rental requirements vary by jurisdiction and may include licensing, tax collection, listing disclosures, night caps, minimum stays, and operating standards.
- Cities typically use multiple sources, including registration records, listings, tax data, complaints, and reservation records, because no single source provides a complete picture of compliance.
- DMOs aren’t typically responsible for enforcing individual-property regulations, but destination-level lodging data can help them understand how supply and visitor activity change after new rules take effect.
Short-term rental compliance means meeting the local requirements for advertising and operating a rental. Those requirements vary widely by jurisdiction and may address everything from licensing and taxes to minimum stays and annual rental limits.
Passing an ordinance, however, is only the first step. Cities also need a way to determine whether properties are following it. That can be difficult when public listings don’t include exact addresses, operator information is incomplete, or the same property appears on multiple booking platforms.
DMOs have a different role. While they generally aren’t responsible for determining whether an individual property is compliant, they may need to understand how regulatory changes affect lodging supply, visitor activity, and tax revenue across the destination.
In this article, we’ll look at how cities track short-term rental compliance, which metrics can show whether compliance is changing, and how destination market data can complement enforcement records.
Disclaimer: This guide provides educational information, not legal or tax advice. Short-term rental requirements vary by jurisdiction and change frequently. Consult qualified legal or tax counsel for guidance on specific requirements.
What Does Short-Term Rental Compliance Mean?
Short-term rental compliance means meeting the requirements established by the jurisdiction where a property operates. Depending on the location, those requirements may include:
- Obtaining and renewing a registration or business license.
- Displaying a valid license or registration number in rental listings.
- Collecting and remitting applicable lodging taxes.
- Staying within annual limits on rental nights or licensed units.
- Following minimum-stay requirements.
- Meeting safety standards or maintaining a designated local contact.
The requirements a city establishes also determine what it needs to measure.
For example, Salt Lake City’s short-term rental ordinance, effective July 1, 2026, includes a two-night minimum stay and a 200-night annual cap. Operators must also hold a city business license. Those requirements create several distinct compliance questions: Is the property licensed? Are stays meeting the minimum length? Has the property exceeded its annual rental limit?
Different city departments may be responsible for answering those questions. Licensing, finance, planning, and code enforcement teams can each play a role depending on the jurisdiction.
DMOs typically approach regulation from another angle. Rather than determining whether individual properties are compliant, destination teams may monitor changes in lodging supply, visitor activity, and tax revenue to understand the broader effects of regulatory changes.
How Do Cities Track Short-Term Rental Compliance?
A valid license doesn’t necessarily mean a property complies with every operating requirement. That’s why cities may need to compare several types of records.
Registration and licensing records show which properties are authorized to operate. They provide a starting point but don’t capture unregistered rentals or prove continued compliance with other rules.
Listing monitoring can help identify active advertisements and compare them with registration records. Matching isn’t always straightforward, particularly when listings omit exact addresses or operator information.
Registration number verification can connect advertised properties with official records. A displayed number still needs to be checked for validity, and a valid registration doesn’t establish compliance with unrelated operating requirements.
Platform data may provide listing identifiers, addresses, registration information, or rental activity, depending on local requirements and the platform. The information available and reporting frequency vary by jurisdiction.
Tax reconciliation compares lodging tax collections with reported or estimated taxable activity. Differences can flag records that need further review, although exemptions and remittance timing need to be considered.
Complaints and inspections can identify nuisance, safety, and other property-level issues that aren’t visible through listing or tax records. Complaint counts should be kept separate from confirmed violations.
Reservation records can help assess rules involving minimum stays or annual night caps. Public calendar availability alone isn’t enough because blocked dates can represent reservations, owner stays, maintenance, or other unavailable periods.
Platform responsibilities also differ by jurisdiction. New York City’s Local Law 18, for example, requires booking platforms to verify registration before processing certain transactions. Other jurisdictions have established requirements around displaying registration numbers, sharing listing information, or reporting rental activity.
The broader point is that compliance systems vary with the ordinance. A city needs data that corresponds to the specific rules it has adopted rather than relying on a single source to determine whether a property is compliant.
Which Metrics Show Whether Compliance Is Improving?
Once the requirements and data sources are clear, cities can establish consistent measures for tracking changes over time.
Registration coverage: The percentage of active, nonexempt listings associated with a valid registration.
Unresolved listings: The number of potentially unlicensed listings still requiring review. Tracking both new and carried-forward cases can show whether the backlog is growing or shrinking.
Notice outcomes: The number of listings removed or brought into compliance after a notice. Delistings and corrected registrations should be reported separately.
Potential night-cap violations: Properties whose recorded booked nights exceed the applicable limit. These should be treated as cases for review rather than confirmed violations until the records are validated against the ordinance’s counting rules.
Tax reconciliation: The difference between expected and reported lodging tax activity after accounting for tax rates, exemptions, and reporting timing.
Complaints per 100 active listings: This puts complaint volume in the context of the destination’s short-term rental supply. Complaints should remain separate from confirmed violations.
Consistency matters as much as the individual metrics. Define what counts as an active listing and apply that definition from one reporting period to the next. A change in the denominator can make compliance appear to improve or worsen even when underlying behavior hasn’t changed.
Listings and unique rental units should also be reported separately because one property may be advertised on multiple platforms. Changes in exemptions, geographic boundaries, platform coverage, or reporting requirements should be documented so stakeholders understand whether periods remain comparable.
For longer-term evaluation, compare equivalent seasons and look across several months or quarters rather than relying on a single reporting period.
How Can DMOs Use Market Data Alongside Compliance Reporting?
Cities and DMOs need different types of information.
Compliance records help government agencies identify and investigate potential violations at individual properties. Destination-level market data answers broader questions: Is short-term rental supply changing? Are booked nights shifting between neighborhoods or seasons? Has visitor demand changed since a new policy took effect?
That distinction is particularly important when evaluating the effects of an ordinance. A decline in active listings after a new registration requirement, for example, doesn’t automatically tell you whether visitor demand also declined. Similarly, changes in lodging tax revenue could reflect demand, rates, supply, seasonality, or changes in tax policy.
DMOs can use market data alongside official tax and regulatory records to provide that broader context in board reports, stakeholder updates, and destination planning.
KeyData’s DestinationData provides aggregated lodging market data for destinations. It isn’t a property-level enforcement tool and doesn’t determine whether an individual rental complies with an ordinance. Instead, it can help destination teams understand how supply, occupancy, booked nights, rates, and other market indicators change over time.
For example, if a jurisdiction introduces an annual night cap, property-level reservation records may help officials determine whether an individual rental has exceeded that limit. Destination-level data can answer a different question: How have booked nights and lodging performance changed across the market since the policy took effect?
Pairing those trends with official lodging tax receipts and regulatory records can provide a more complete view of what’s happening across the destination.
Build a Baseline Before Regulations Change
Measuring the effects of short-term rental regulation starts before a new rule takes effect.
Cities should define the compliance measures tied to the ordinance, establish consistent reporting periods, and document the data sources they’ll use to track them. A baseline makes it easier to distinguish real changes from differences in definitions or reporting coverage later.
For DMOs, the baseline should focus on the broader destination: lodging supply, booked nights, occupancy, seasonality, and other measures relevant to visitor activity. Tracking the same measures after a policy change can help destination teams understand how the market is evolving alongside the new regulatory environment.
Book a demo to see how DestinationData can add lodging market context to your destination’s reporting.
Frequently Asked Questions
What is short-term rental compliance?
Short-term rental compliance means following the licensing, tax, advertising, safety, and operating requirements established by the jurisdiction where a rental is located. The specific requirements vary by city, county, state, and country.
How do cities identify unlicensed short-term rentals?
Cities may compare registration records with active rental listings, platform-provided data, tax records, complaints, and other available information. Because listing information can be incomplete, identifying a potential mismatch doesn’t necessarily establish a violation and may require further investigation.
What data can cities use to track short-term rental compliance?
Depending on the ordinance and available data, cities may use licensing records, registration numbers, listing information, lodging tax records, complaints, inspections, and reservation records. The appropriate sources depend on the specific requirement being measured.
Are DMOs responsible for short-term rental compliance?
Typically, DMOs aren’t responsible for licensing properties or enforcing short-term rental ordinances. Those responsibilities generally sit with local government departments. DMOs can use destination-level lodging data to understand how supply, visitor activity, and lodging performance change alongside new regulations.
How can a city measure the impact of new short-term rental regulations?
Establish a baseline before the regulation takes effect and track the same measures afterward. Compliance metrics can show changes in registration or potential violations, while market indicators such as supply and booked nights can provide context on broader changes across the destination. Comparisons should account for seasonality, demand, tax changes, and differences in data coverage.
