Nothing in the passive activity rules prescribes a rounding increment for a participation log. Treas. Reg. §1.469-5T(f)(4) asks that the extent of participation be established by any reasonable means, which leaves the choice of precision to the taxpayer. What that trade produces is a different kind of scrutiny: because no increment is required, the pattern your numbers make is what gets read.
What §1.469-5T(f)(4) actually requires
The paragraph is short and it is worth knowing in outline. It says participation may be established by any reasonable means, that contemporaneous daily time reports and logs are not required where other reasonable means exist, and that reasonable means may include identifying the services performed over a period and the approximate number of hours spent on them, based on appointment books, calendars or narrative summaries. IRS Publication 925 describes the same standard for owners reading it in plain English.
Two words in that sentence matter here. "Approximate" is the regulation's own term, so an approximation is not a defect. "Reasonable" is the limit, and opinions applying this paragraph have repeatedly declined to accept figures assembled long after the fact with nothing behind them. The standard is credibility, not granularity.
Why no increment is prescribed
Appointment books and narrative summaries are named in the regulation as acceptable sources, and neither one produces minute-level precision. A diary that reads "Tuesday — met the plumber, mid-morning" was contemplated by the drafters. So a log kept in 15-minute blocks is not, as a matter of the regulation, better or worse than one kept to the minute.
The difference is in how each reads to someone testing it. Precision earns nothing on its own, but it tends to come with the things that do count: that the entry was made close to the event, and that there is a receipt, message or photo sitting behind it at the same time of day.
The problem with uniform figures
Rounded, repeating durations are the most common reason an otherwise plausible log reads as constructed. Compare two weeks of the same work:
| Rounded and vague | Measured as it happened |
|---|---|
| Mon — guest messages, 1.0 | Mon — answered 3 inquiries, confirmed late check-in, 25m |
| Tue — turnover, 3.0 | Tue — post-checkout turnover, linens and both baths, 2h 40m |
| Wed — maintenance, 2.0 | Wed — reset tripped GFCI, replaced porch bulb, 15m |
| Thu — admin, 1.0 | Thu — reconciled October platform payout, 35m |
| Fri — supplies, 2.0 | Fri — restock order placed, 20m; delivery received, 10m |
The left column totals nine hours and the right totals a little over four and a half, and the right column is the one that holds. The problem with the left is not the total. It is that real work is not shaped in whole and half hours, and once one line reads as invented, every other line in the log becomes negotiable. That is the mechanism behind cases where a large logged total was set aside anyway: the 932 hours rejected in Hairston failed on how the entries read, not on how many hours they came to.
Small entries are still entries
The instinct to drop anything under fifteen minutes is the quiet reason many logs end up reconstructed. A ten-minute entry is a real entry, and in a short-term rental the ten-minute items are most of the work: a message answered from a parking lot, a cleaner rescheduled, a smoke alarm chirping on the camera feed, a review replied to.
Across a season those are the entries that carry the 100-hour comparison, and they are also the ones you cannot rebuild in December with any honesty. Logging them small and logging them immediately solves the same problem twice. The anatomy of a credible entry applies in full to a twelve-minute line.
Marking an estimate as an estimate
Some entries will be estimates. A trip you remember clearly but did not time, a Saturday of yard work, an evening of listing edits. The regulation permits approximation, so the honest move is to record the approximation as one rather than dress it as a measurement.
In practice that means a note in the entry itself: "duration estimated from message timestamps, 7:05 to 7:40 pm", or "approximate, corroborated by hardware receipt 6/14". An estimate labelled and sourced is doing what the regulation describes. An estimate presented as a stopwatch figure is a problem only when the underlying record contradicts it — and platform timestamps, card settlements and photo metadata frequently do. The distinction between a log kept as you went and one assembled afterward is covered in the guide on contemporaneous versus reconstructed logs.
Totals that end in round numbers
A year total that lands on exactly 100.0 or 750.0 hours draws attention to the entries closest to the line, because the figure reads as a target rather than a sum. The same is true of a total that clears a threshold by a few tenths after a late batch of identical entries.
The response to that is not to adjust the total in either direction. Rounding up to reach a threshold is the specific thing that turns a record-keeping question into a credibility question, and it puts every other entry at risk. The total is an output. If an honest log lands under a threshold for the 2026 tax year, it lands under, and that is a conversation to have with a CPA or EA about the year's position — not something to fix in the log.
A convention to apply all year
Pick the rules once in January and apply them without thinking after that:
- Record start and end times, not durations. The duration then comes from the clock rather than from memory. In STR Tracker an entry is saved as a start time and an end time, with the hours derived from them, so the precision is a by-product of how the entry is made rather than a decision each time.
- Round to the nearest five minutes, and down when you are unsure. Downward rounding costs a few hours a year and removes the argument.
- One task and one property per entry. Combined lines are where uniform figures creep in.
- Note the source whenever the duration is an estimate. One short phrase in the notes field.
- Never edit a past entry to move a total. Add the entries you missed, dated the day the work happened, with a note saying when you added them.
If you are starting from paper or a spreadsheet, the free log template has the same fields in the same order, which makes the convention easier to keep than to remember.
A log does not need to be precise to be credible. It needs to read as measured rather than assembled, and those are different properties. Where the two come apart, the measurement is what matters.
