
A 60-Day Cap Turns Your Rate Into a Capacity Price
A published night cap doesn't lower your rate. It changes what the rate is for: a small set of sellable nights has to carry a full year of costs. Price each one against the top of your market, and write down the floor below which a night isn't worth selling.

When the calendar can only sell sixty nights a year, the nightly rate stops being a price and becomes a target: what each sellable night has to earn to carry the other three hundred.
Last updated: October 29, 2026
A cap doesn't lower your rate. It changes what the rate is for. Once the calendar can only sell a fixed number of nights, the nightly rate stops answering what a room is worth tonight. It starts answering what each sellable night has to earn to keep the unit open all year. That second question prices differently, and it prices badly if you answer it with the first one.
Key Takeaways
- A cap is a denominator, not a ceiling. It sets how many nights you can sell, and the rate has to work across that number.
- The nights you can't sell still cost money. Carrying costs don't shrink because the calendar is closed.
- Every discounted night spends capacity. A cheap night in a capped year uses a slot you can't get back.
- Price the sellable nights against the top of your market. An average includes nights you're not allowed to sell.
- A floor is a decision, not a mood. Write down what a night must earn before you'd rather leave it empty.
The cap as a denominator
A published cap is a number in an ordinance, and it reads like a permission: you may sell this many nights, so sell this many. That reading is compliant, and it's also how capped hosts leave money on the table. The number isn't a permission. It's a divisor.
Greater Sydney's 180-night annual cap, as published by the NSW Government and logged in the regulatory radar of 25 October 2026, is one published example. Sixty is the working number in this article. It's an illustration rather than a quote from any jurisdiction, so substitute whatever your own authority publishes. The reasoning survives the substitution; only the divisor moves.
Here's the shift. With an open calendar, a rate is a price. The market clears at roughly what the room is worth on the night, and if a Tuesday is quiet you drop the rate and take what you can get. With a capped calendar, the rate becomes a collection target. A small set of sellable nights has to produce enough to carry a full year of costs, and when one of them underperforms there's no spare night to make it back on.
That's why a capped host who benchmarks against an uncapped neighbour on the same street ends up with a misleading number. The neighbour can sell a weak Saturday and recover on a Tuesday in February. You can't. Your Saturday is already carrying part of February, whether you price it that way or not.
Working back from the ceiling
The ceiling in a capped market isn't a guess. It's the best night your unit can sell, and it shows up in data you already have: which nights sold, at what rate, and how far ahead they went.
localsbnb.com puts occupancy, ADR and RevPAR for each unit on one dashboard, which is the quickest way to see whether your best nights are pricing at the top of your own market or drifting toward the middle of it.
Work backwards from there. The best nights tell you what the unit earns when demand is on your side. The number of those nights tells you whether the year closes. If the top nights can't carry the costs, discounting the quiet ones won't fix it. You'd be selling nights you were going to sell anyway at a lower rate, and in a capped year you'd also be spending capacity to do it.
Two moves follow. Protect the peak first: a minimum stay that stops a two-night booking from splitting a week that would have sold whole. Then stop releasing peak nights cheap at the last minute. In an open calendar, a last-minute discount fills a night that would otherwise sit empty. In a capped calendar, that night was never going to sit empty. You've paid to sell it.
Discounting isn't the only leak. The other is a rate card built for a calendar you no longer have: seven nights a week on a smooth curve, as though each one were equally available. Under a cap the curve has to go lumpy. Peak nights sit near the ceiling, shoulder nights sit near the floor, and a Tuesday in the middle of the season can go either way depending on what your own booking data says about demand at that distance.
What the empty nights still cost
Split your costs in two and the cap gets easier to price against. Carrying costs arrive whether or not a guest does: the mortgage or the rent, insurance, the licence, baseline maintenance, the standing charges on utilities. Per-stay costs appear only when a night sells: cleaning, laundry, consumables, the hour you spend answering messages.
A cap doesn't touch the first group. It squeezes the second into fewer nights, so every sold night has to clear its own per-stay cost and still contribute to the year. That's the whole mechanism, and it explains the case that puzzles hosts most: a rate that looks healthy next to a competitor and still leaves you short.
The empty night isn't free either, and it's the part that gets undercounted. An unsold night in a capped year costs you the carrying share it would have covered, and it can't be recovered later because the year has a hard stop. That's the difference between a soft month and a lost one.
Your own time sits in the second group too. Every sold night carries a fixed amount of admin, and a capped calendar concentrates that admin into fewer, longer stays. One guest booking fourteen nights generates fewer messages than two guests booking seven each, and one changeover instead of two. That isn't a reason to refuse short bookings, but it does mean the short ones have to earn their slot.
None of this argues for charging whatever the market will bear. It argues for knowing which of your nights are scarce and which aren't, because they no longer price the same way. A Tuesday in November and a Saturday in July are both nights on the same calendar. Only one of them is worth defending.
Setting a floor you can defend
A floor is the rate below which you'd rather the night stayed empty. Most hosts carry one in their head and never write it down, which means it moves with their mood and their bank balance.
Write it down in two parts. The first is the per-stay cost of selling at all: cleaning, laundry, consumables, your own time. The second is the contribution you've decided each sold night owes the year. Add them and you have a number you can defend in a conversation with yourself at eleven at night. Everything above it is margin. Everything below it is a night that costs you money to sell.
Then apply it to the whole calendar rather than the quiet end. A floor that only bites in February isn't a floor; it's a discount policy with a lower bound. In a capped year the floor has to bite on shoulder nights too, because those nights compete with your peak for the same scarce slot.
Review it on a schedule. Costs move, the market moves, and a floor set in spring is a guess by autumn. Quarterly is often enough, and the review takes minutes when occupancy, ADR and RevPAR sit on the same screen as the rates you're testing.



FAQ
Does a cap mean I should raise every rate?
No. It means the rate has to be set per sellable night rather than per calendar night. Some nights can move up, because they're the ones carrying the year. Others should stay where they are, or come out of the calendar entirely rather than sell below their per-stay cost.
Is a longer minimum stay the right answer?
Often, but not automatically. A longer minimum protects peak weeks from being split and cuts the number of changeovers, which is where per-stay costs pile up. It hurts when your market is mostly two-night weekend demand and the extra night stays empty. Test it on one peak month before you apply it everywhere.
My city's figure is different from sixty. Does the method still hold?
The method holds; the divisor doesn't. Replace sixty with the number your authority publishes, then check the current wording with the competent authority, because caps get amended. The details that decide the real number are usually which nights count and what exemptions apply, not the headline.
The figure in the ordinance isn't yours to choose. What each sellable night has to earn is. localsbnb.com keeps every unit's occupancy, ADR and RevPAR together, so the number you're pricing against is on screen while you set the rate.
This article is general guidance for hosts and isn't legal, tax or insurance advice. Caps are set, amended and enforced by local authorities, and how a night is counted differs between them. Confirm the current rule, and any exemption you intend to rely on, with the competent authority before you change a rate or a calendar.
Reviewed by
Localsbnb Editorial Team