In a busy stretch, log once a day rather than once a task: at the end of the day, write each thing you actually did, with its own real duration, before you go to bed. That keeps the entries contemporaneous without asking you to stop mid-turnover, and it avoids the reconstruction that makes a peak-season block of the log the easiest part to doubt. The reason to be careful here is arithmetic, not anxiety — the weeks when you have the least time to write anything down are the weeks that put the most hours on the board.
Why peak weeks carry most of the year's hours
Hours follow occupancy. A property that turns over twice a week in the shoulder season and six times a week at the top of the season is generating roughly three times the turnover work, laundry, restocking, guest messaging and small repairs in those weeks. For a seasonal property — a beach rental in July, a ski condo in February, a rental near a stadium or a festival — a large share of the year's total participation can sit inside a handful of months.
That concentration cuts both ways. It means a short, dense period can carry you to the 100-hour threshold under Treas. Reg. §1.469-5T(a)(3) or meaningfully toward 500 hours under §1.469-5T(a)(1). It also means that if the log for those months is thin, generic or written later, the weakest-documented part of your year is also the largest part of your claim. Examiners and the Tax Court read the busiest block closely for exactly that reason.
The same-day rule, under pressure
The regulations do not require a particular format. Treas. Reg. §1.469-5T(f)(4) says participation may be established by any reasonable means, and that contemporaneous daily time reports are not required. IRS Publication 925 describes the same flexibility. But the cases where logs are accepted and the cases where they are rejected tend to split on whether the record looks recorded or looks assigned, and a record written the day it happened is the version that reads as recorded.
In a slow month, "log it as you finish it" works. In a peak week it does not, because stopping to write an entry between a checkout and a 4 p.m. check-in is the first thing to go. So change the unit, not the standard. Logging everything from one day, at the end of that day, is still same-day. Logging everything from one week, on Sunday night, is already reconstruction — better than nothing, and much weaker.
Batch at the end of the day, not the end of the month
An evening batch works because the day is still in your head and the traces are still in front of you: today's messages, today's receipts, today's photos, today's cleaner texts. You are reading the day back, not remembering a season.
A workable batch looks like this:
- Open the log and set the date to today.
- Walk the day in order: morning checkout, laundry, restock run, the repair you squeezed in, the three message threads, the evening check-in.
- Give each its own line and its own duration.
- Attach anything you already have — the hardware-store receipt, the before photo of the broken blind.
Entering them the same day also means the timestamp STR Tracker records on each entry sits next to the date you are claiming, which is the small, boring difference between a record and a summary.
Keeping per-turnover times realistic when the days blur
The characteristic peak-season failure is not forgetting hours. It is rounding every turnover to the same figure because the days have merged. Forty lines reading "turnover — 4.0 hours" is a pattern, and a pattern invites the question of whether anyone measured anything.
Real turnovers vary, and the variation is your friend:
| Situation | What the entry should reflect |
|---|---|
| Back-to-back, same-day checkout and check-in | Often shorter and more frantic, not longer |
| Guest left the place tidy | Less time, and it is fine to say so |
| Long stay just ended | Usually more laundry and more deep cleaning |
| You supervised rather than cleaned | Log the supervision, not the cleaner's hours |
If you genuinely cannot recall whether a turnover took two hours or three, write the lower figure and keep a note that it is an estimate. A log that occasionally reads "approximately" is more credible than one that never does. Our post on how to log turnover hours breaks a single turnover into the component tasks worth separating, and the guide on whether cleaning counts covers how that work is characterised in the first place.
Cleaners and helpers during the rush
Peak season is also when other people's hours climb fastest, and that matters for the 100-hour test specifically, because §1.469-5T(a)(3) asks both whether you participated more than 100 hours and whether any other individual participated more than you did. A cleaner doing six turnovers a week in August is accumulating hours quickly.
So log them in the same evening pass. One line per helper per day, with a realistic duration, is enough, and the invoices you receive at the end of the month give you something to check it against. The shortcut owners regret is tracking their own hours all season and estimating the cleaner's in April, when the comparison is the half of the test they cannot reconstruct. There is more on this in tracking your cleaner's hours.
The mid-season check against your target
Halfway through the busy stretch, stop for ten minutes and add up what you have. You are looking for three things: your running total against whichever test you are working toward, your total against the largest other participant's, and any week with suspiciously few entries.
A gap found in mid-season is a gap you can still close with real work — taking a turnover back from the cleaner, handling a repair yourself, doing the guest communication personally. The same gap found in January is a gap you can only write around, which is not a thing to do. Whether the numbers are on track is a question for your CPA or EA, who will also tell you which test is the realistic one for each property.
A two-minute evening routine
- Date set to today, before anything else.
- One line per task, each with its own duration and a specific description ("replaced shower head, unit B" beats "maintenance").
- Other participants' time for the day, on their own lines.
- Receipts and photos attached to the entry they belong to, not dropped in a folder.
- A quick glance at yesterday: if it is empty and it should not be, fix it now while you still know.
Common mistakes in a busy season
- Identical durations across dozens of entries. The single clearest sign of a log written after the fact.
- One line for a whole day. "Property work, 9 hours" discards everything that made it credible.
- Leaving guest messaging out. Short exchanges are real participation and they add up across a full house.
- Logging the cleaner's work as your own. Supervision is yours; the cleaning is theirs.
- Promising yourself the September catch-up. It arrives as a reconstruction, and it will read like one.
If you are setting this up for the first time, the free log template shows the fields worth having before the season starts, so the evening pass takes two minutes rather than twenty.