The 180-day cap, in practice

How the cap actually behaves across a portfolio, and the planning it forces on a serious operator.

The 180 day cap on non-hosted short-term letting in Greater Sydney is usually read as a single number. Spend 180 nights, then stop. Run a portfolio and the number stops being one number. It becomes as many caps as you have properties, each counted across its own twelve month registration period dated from that property's registration anniversary rather than the calendar year. There is no shared budget and no single reset date.

That changes the work. The cap is not a ceiling to bump against late in the year, it is a budget to be spent on the right 180 nights. The right nights are the high tariff ones: summer, long weekends, events, the weeks where the difference between an open and a closed calendar is largest. A property that burns its allowance on quiet midweek nights in winter has spent the same budget for a fraction of the return.

The twenty-one night exclusion is the lever that makes this tractable. Bookings of twenty-one consecutive nights or more sit outside the count, so a property can stay occupied well beyond 180 effective nights if the calendar is built deliberately, with the capped nights reserved for peak short stays and the rest carried by longer bookings. Across a portfolio, the further refinement is to stagger registration dates so the properties are not all resetting in the same month, which smooths both the compliance load and the revenue.

The cost of getting it wrong is not a fine in the ordinary sense. Exceed the limit and the dwelling falls out of the exempt development pathway altogether, which is a different and worse problem than a quiet quarter. Planning the cap is therefore not housekeeping. It is one of the few decisions that sets the revenue ceiling for the entire year before a single guest arrives.