You just pulled your year-end booking report and something looks off. Most of your guests stayed two or three nights. But in March you had a couple who stayed 28 days, and in September a traveling nurse booked six weeks. Now your CPA is frowning at your spreadsheet. One big question sits in the middle of the room: does your property still qualify for the 7-day rule?
TL;DR: The IRS calculates average period of customer use by dividing total rental days by total number of rentals for the tax year (Treas. Reg. §1.469-1T(e)(3)(ii)(A)). Every rental — short or long — goes into that formula. One 30-day stay mixed with ten 3-day stays produces an average of 5.5 days, which still qualifies. But two 30-day stays mixed with ten 3-day stays produces an average of 7.5 days, which does not. The math is simple. The consequences are not.
Jennifer Beadles is a real estate investor and short-term rental owner who uses the STR loophole on her own properties. She writes from hands-on operating experience plus current IRS guidance (IRC §469 and Treas. Reg. §1.469-1T(e)(3)(ii)(A)).
How the IRS Calculates Average Period of Customer Use
The formula lives in Treas. Reg. §1.469-1T(e)(3)(ii)(A), and it is not complicated. The IRS defines average period of customer use as:
Total rental days ÷ Total number of rentals = Average period of customer use
That is it. No weighting by revenue. No adjustment for gap nights between guests. No special treatment for off-season stays. You count every day a guest occupied the property, total those days across all rentals, and divide by the number of separate rental agreements (or stays) for the year.
If that number lands at 7.0 or below, your property is not a "rental activity" under IRC §469 for that tax year. That single fact is what makes the STR loophole work. Because the property is not a rental activity, the passive activity loss rules do not automatically apply, and if you materially participate, your losses become non-passive and can offset your W-2 or other ordinary income.
If the average lands at 7.1, the loophole is gone for the year.
What Counts as One "Rental"
Each separate booking is one rental. A guest who books Sunday through Friday under one reservation is one rental of six days. If that same guest re-books the following week under a new reservation, that is a second rental of seven days. The IRS looks at the rental agreement, not the guest.
Back-to-back bookings by the same guest under separate reservations are two rentals. A single extended booking by a traveling nurse is one rental, no matter how many weeks it covers.
This matters a lot when you have a property management software that auto-splits long stays into shorter blocks for platform reasons. Make sure your records reflect the actual number of binding rental agreements, not the number of check-in events.
The Worked Example: Short and Long Stays on the Same Calendar
Say you own a lakehouse. Here is what your booking calendar looked like last year:
| Stay # | Rental Days | Notes |
|---|---|---|
| 1 | 2 | Weekend stay |
| 2 | 3 | Long weekend |
| 3 | 2 | Weekend stay |
| 4 | 3 | Long weekend |
| 5 | 2 | Weekend stay |
| 6 | 5 | Holiday week |
| 7 | 3 | Long weekend |
| 8 | 28 | March monthly rental |
| 9 | 2 | Weekend stay |
| 10 | 3 | Long weekend |
| 11 | 2 | Weekend stay |
| 12 | 4 | Four-night stay |
Step 1: Add up total rental days. 2 + 3 + 2 + 3 + 2 + 5 + 3 + 28 + 2 + 3 + 2 + 4 = 59 total rental days
Step 2: Count total number of rentals. 12 separate bookings.
Step 3: Divide. 59 ÷ 12 = 4.92 days average
You are well under 7. Even with that 28-day stay in March, the volume of short bookings pulls the average down comfortably. The property qualifies.
Now, change the scenario slightly. Same calendar, but instead of one 28-day stay, you have two: one in March and one in October.
New total rental days: 59 + 28 = 87 days (still 12 rentals, now 13 with the added stay). Wait, let us be precise. You had 12 stays before. Add one more 28-day stay and you have 13 stays.
87 days ÷ 13 stays = 6.69 days average. Still qualifies.
But what if the second long stay is 42 days (six weeks)?
New total: 59 + 42 = 101 days, 13 stays. 101 ÷ 13 = 7.77 days average. The loophole is gone.
At a 35% marginal rate and a $50,000 paper loss from depreciation, that difference costs you $17,500 in taxes you could have avoided. One booking decision. Real money.
Why Long Stays Are a Hidden Risk Most Hosts Miss
Short stays feel risky. Long stays feel safe. Hosts often worry about noise complaints and party guests with two-night bookings, so they occasionally open the calendar to a month-long corporate traveler or a contractor who needs a base. It feels like easy, low-maintenance income.
And it might be. But it can also quietly wreck your average.
The math is asymmetric. A 2-night stay pulls your average down by a lot. A 45-night stay pulls it up by a lot more. Because the formula weights every rental by its duration, a single outlier long stay can overwhelm dozens of short ones.
Here is a quick way to think about it: if you have N short stays averaging S days, and you add one long stay of L days, your new average is:
(N × S + L) ÷ (N + 1)
To stay at or below 7.0 days, you need:
(N × S + L) ÷ (N + 1) ≤ 7
Solve for L: L ≤ 7(N + 1) − (N × S)
So if you have 20 stays averaging 3 days each, and you want to add one long stay while keeping the average at or below 7:
L ≤ 7(21) − (20 × 3) = 147 − 60 = 87 days maximum
With 20 short stays already in the books, you can actually absorb a pretty long rental. The danger zone is when you have fewer bookings overall, which means each individual stay carries more weight in the average.
A slow shoulder season with only four short bookings on the books? One 30-day stay could push you over the edge.
What to Do If Your Average Is Creeping Toward 7 Days
For a deeper look at mid-year warning signs and tactical fixes, see what happens if your STR average stay creeps above 7 days mid-year. But here are the core moves:
1. Cap your maximum booking length. Most platforms let you set a maximum stay length. If you set it at 6 nights, you structurally prevent any single booking from dragging your average above 6, no matter how few other bookings you have.
2. Watch your rolling average, not just your annual total. Calculate your average stay every month, not once at tax time. By December, you may not have enough bookings left in the year to pull a bad average back down.
3. Treat monthly rentals as a separate decision. If you want to offer monthly rentals at all, run the math first. How many short stays do you currently have? What is your average now? How far does adding one long stay move the needle? The formula above tells you.
4. Keep long stays off your primary STR property. Some hosts run a mixed portfolio: one property dedicated to short stays (the STR loophole property) and another they are fine treating as a passive long-term rental. If you do this, do not group them together for material participation purposes. Long-term rentals cannot be grouped with STRs under Treas. Reg. §1.469-9(g). For more on how the STR and medium-term rental mix works from a tax standpoint, see STR loophole with a mix of STR and MTR properties.
How to Document the Calculation for an Audit
The IRS does not ask you to file a worksheet showing your average period of customer use with your return. But if you are audited, you will need to produce it.
What you need:
- A record of every rental agreement (or booking confirmation) for the year
- The check-in and check-out date for each booking
- The total days for each stay
- A simple tally showing total days divided by total stays
Your platform's booking history report is a good starting point, but it is not sufficient on its own. Bookings can be cancelled, modified, or overlap with personal-use days. Export the data, clean it, and reconcile it against your own calendar.
Personal-use days do not count as rental days. If you or your family stayed at the property, those days are excluded from both the numerator and denominator of the average-stay calculation. This actually helps your average if your personal stays would otherwise be counted as long occupancy events, but you cannot count them as rentals for purposes of the formula. For the full rules on what counts as personal use versus rental use, see understanding personal use days for the STR loophole.
The 7-Day Rule Is Just the First Gate
Qualifying on the average-stay calculation means your property is not a rental activity. That is necessary but not sufficient to get the tax benefit. You also need to materially participate.
Material participation is most commonly met through what practitioners call Test 3: you logged more than 100 hours of participation AND more hours than any other individual, including your cleaner, co-host, or property manager. Test 1 (500 or more hours total) also works. The full breakdown of both tests and when each one fits is in the 100-hours vs. 500-hours comparison for the STR loophole.
You do not need to qualify as a real estate professional. You do not need 750 hours. The STR loophole specifically exists so that STR owners can make their losses non-passive without meeting the REPS standard.
If you are tracking your hours and want a reliable system for logging them, the STR Loophole app is built specifically for this: date, task, start and end time, and a running total you can produce if the IRS asks.
Once you clear both gates, a cost segregation study accelerates the paper losses that offset your W-2 income. You can run the numbers in our cost segregation calculator to see how much of your property's depreciable basis might be reclassified into 5-, 7-, and 15-year components eligible for 100% first-year bonus depreciation under IRC §168(k) as restored by the One Big Beautiful Bill Act.
Key Takeaways
- The formula is: total rental days ÷ total number of rentals = average period of customer use (Treas. Reg. §1.469-1T(e)(3)(ii)(A)).
- Every booking, short or long, goes into the calculation. No weighting by revenue or season.
- One long stay can be absorbed if you have enough short stays. Two or three long stays with a thin calendar can push you over 7.0.
- Personal-use days are excluded from both the numerator and denominator.
- Track your rolling average monthly. By December it may be too late to fix a bad number.
- Cap maximum booking lengths on your platform as a structural safeguard.
- Passing the 7-day test is necessary but not sufficient. You must also materially participate.
Sources
- Treas. Reg. §1.469-1T(e)(3)(ii)(A) — eCFR
- Treas. Reg. §1.469-5T — Material Participation — eCFR
- Treas. Reg. §1.469-9(g) — Rental Real Estate Grouping Rules — eCFR
- IRC §469 — Passive Activity Losses and Credits — Cornell LII
- IRC §168(k) — Bonus Depreciation — Cornell LII
- IRS Publication 527 — Residential Rental Property
This article is for educational purposes only and is not tax or legal advice. Talk to a CPA who knows short-term rentals before you act on it.
The Bottom Line: Run the average-stay math on your actual booking calendar before year-end, not after. If one or two long stays are pushing your average toward 8 or 9 days, you still have time to take action. Cap long bookings at 6 nights, add more short stays to pull the average back down, or split your calendar intentionally. Get that number to 7.0 or below, document it cleanly, and then make sure your participation hours beat the cleaner and co-host. Those two moves together are what make the STR loophole work.
Ready to see if you qualify? Try the free STR loophole calculator →
Start Tracking Your Hours Today
STR Loophole makes documentation effortless. Sign up free on the web, then log from your desk or the mobile app — everything syncs.

