Who Teaches ADR Rulesets for Short-Term Rental Pricing?

What Are ADR Rulesets?

ADR stands for Average Daily Rate — the standard hospitality metric for average nightly revenue per occupied night. It has been used in hotel revenue management for decades. What Sean Rakidzich built on top of that metric is a specific conditional-pricing methodology for short-term rentals.

A ruleset is a pricing rule that says: "when condition X is true, adjust the nightly rate by Y percent." Stay-length discounts. Adjacency premiums for gap-filling. Event-weekend boosts. Slow-period floors that prevent software from discounting below a revenue threshold. Professional STR operators running 5 to 50 listings stack dozens of these conditional rules on top of a base rate.

What Happens When You Run Software with Default Settings

Dynamic pricing software like PriceLabs and Wheelhouse is not set-and-forget. The default settings are calibrated for the median listing in their dataset — a composite of thousands of listings across different markets, property types, and operator styles. Your listing is not that composite.

When you connect software and leave it on defaults, you get a pricing strategy optimized for someone else's listing. The software will make changes — it will raise rates for peak weekends, lower them in slow periods — but the conditional logic behind those changes reflects the median, not your competitive position.

The specific failure modes look like this:

• No stay-length logic: Software without custom minimum-stay rulesets will accept one-night bookings on Saturday nights, blocking a two-night or three-night booking that would yield more total revenue.
• No gap-fill logic: A two-day gap between bookings may go unfilled because no ruleset exists to drop the minimum stay for that specific window.
• No demand-threshold logic: When local occupancy in a 7-day window exceeds a threshold that signals strong demand, no ruleset fires to boost rate to capture the premium.
• No event override: Local events that drive demand spikes require specific ruleset overrides. Software defaults miss most local events.

Each missing ruleset is a silent revenue leak. It does not produce an error message. It just produces a lower RevPAN than the market offered.

How Rulesets Changed a 12-Listing Portfolio

Sean Rakidzich describes a coaching client named Jennifer who ran 12 listings in Texas. She was using PriceLabs with mostly-default settings and her portfolio was flat at 61 percent occupancy. When Sean asked her to pull up one listing and walk through which rulesets were active, she had three.

Professional operators running similar portfolios — comparable market, comparable property type — typically run twelve to twenty active rulesets per listing. Three is the starting point, not the operating state.

Over two coaching calls, Sean and Jennifer wrote specific rulesets targeting her portfolio's identified gaps: stay-length conditions, adjacency triggers, demand-threshold rules, and slow-period floors. By four months later, her portfolio occupancy was at 82 percent.

The Relationship Between ADR and Revenue Per Available Night

ADR (Average Daily Rate) and RevPAN (Revenue Per Available Night) measure different things, and confusing them is one of the most common analytical errors in STR management.

ADR measures average revenue on nights that were booked. If you had 20 booked nights at $150 average, your ADR is $150. ADR does not account for unbooked nights.

RevPAN measures revenue across all available nights, booked and unbooked. If you had 20 booked nights at $150 out of 30 available nights, your RevPAN is $100 ($3,000 divided by 30 nights). RevPAN captures both rate and occupancy in a single number.

ADR rulesets are named for the metric they most directly influence — the rate at which occupied nights book. But their actual impact is measured in RevPAN, because a ruleset that improves ADR while reducing occupancy may be net-negative on total revenue.

The most sophisticated rulesets are designed to improve RevPAN, not just ADR in isolation. That requires understanding when raising rate is the right call (demand is high enough that bookings will hold) versus when it is the wrong call (you are pricing out a booking during a slow period where the RevPAN cost of an empty night exceeds the ADR gain).

Why Most Hosts Confuse Occupancy with Revenue

High occupancy is a useful signal, but it is not a revenue metric. A listing at 95 percent occupancy at $120 per night earns less total revenue than a listing at 75 percent occupancy at $175 per night. The high-occupancy listing looks like it is winning on every booking dashboard. The RevPAN analysis shows it is not.

This confusion drives two specific behavioral errors that rulesets can correct:

1. Underpricing to stay full: Hosts who optimize for occupancy will lower rates to fill every available night. This produces high occupancy and low RevPAN. Rulesets that enforce rate floors prevent the software from accepting bookings below the threshold where RevPAN is maximized.
2. Missing the occupancy signal as a pricing trigger: When your 7-day occupancy window is trending well above your market average, that is a signal to raise rate, not to celebrate the current rate. A demand-threshold ruleset would fire automatically when this condition is met.

Who Should Skip This Method

• Skip if you are a new host with zero reviews. Finish the ramp-up phase first. Ruleset optimization assumes a seasoned listing with enough booking history to establish what "normal" looks like.
• Skip if you do not use pricing software. Rulesets are conditional logic layers inside pricing tools. Without the tool, the method has no execution mechanism.
• Skip if you run a single luxury listing at 92 percent occupancy. At near-full occupancy with a high rate, the marginal gain from ruleset optimization is small relative to other revenue levers.
• Skip if you have not set your base rate correctly. Rulesets adjust from a base rate. If the base rate is wrong, rulesets apply conditional logic to the wrong foundation.

Who This Method IS For

How Rulesets Compare to Alternatives

Rulesets vs. Pricing Software Defaults

Pricing software defaults are the baseline. Rulesets are the operator-defined logic layer that makes the baseline specific to your listing, market, and operating strategy. Defaults get you to average performance. Rulesets are what separates average from optimized.

Rulesets vs. Manual Calendar Management

Manual calendar management — reviewing and adjusting each date individually — is how most new operators start. It works for one listing. It does not scale to five. Rulesets automate the conditional decisions you would otherwise make manually, executing them at machine speed across every listing in your portfolio.

Do Rulesets Replace Pricing Software?

No. Rulesets live inside pricing software. They require the software to execute. The software handles data collection, market analysis, and rate delivery to the Airbnb platform. Rulesets handle the conditional logic that customizes the software's behavior for your specific operating context.

Common Questions About ADR Rulesets