Tax Strategy

    4 STR Hour Log Mistakes That Lose in Tax Court

    Last updated: April 2026 · 10 min read

    Jennifer Beadles

    April 20, 2026 · 10 min read

    Share:
    4 STR Hour Log Mistakes That Lose in Tax Court

    Most STR loophole content tells you what to do. This one is about what not to do.

    In 2020, the U.S. Tax Court decided a short-term rental case that has become a touchstone for how not to document material participation. The taxpayer had a real STR. Real guests. Average stays under seven days. Real operational involvement. He still lost his deduction for two years running, and the reasons why are a four-item checklist every STR investor should read before filing.

    Here are the four mistakes, why each one killed the deduction, and how to avoid them.

    • Reconstructing the log after the audit started opened every entry to credibility scrutiny.
    • Counting commute time signals the log does not understand which hours qualify.
    • Inflating task duration discredits the entire log, not just the padded entries.
    • Mixing personal and business errands inflates time and invites IRS cross-referencing against receipts.
    • Even a perfect log cannot win the 100-hour test without evidence of your property manager's hours.

    The Case Behind the Mistakes

    Ronald Lucero owned a short-term rental in The Sea Ranch, California. The property was legitimately short-term: 146 nights rented in 2014 and 152 nights in 2015, average guest stays under seven days. The 7-day rule was satisfied and the activity was eligible to be non-passive under Treas. Reg. §1.469-1T(e)(3)(ii)(A). The STR loophole was his to claim.

    The property was managed by Sea Ranch Escapes, LLC. The management company handled advertising, reservations, guest communication, cleaning, landscaping, and contractor coordination. Mr. Lucero retained control over rate-setting and approval of expenses over $100, and he drove from Sacramento to Sea Ranch six to nine times a year to handle upkeep personally.

    That is a real operational footprint. It is also exactly the setup most high-income STR investors run: a property too far to manage daily, a management company doing the bulk of the work, and the owner showing up for hands-on stretches.

    The Luceros reported a $17,631 loss in 2014 and a $24,490 loss in 2015. The IRS disallowed both. The Tax Court sided with the IRS (Lucero v. Commissioner, T.C. Memo. 2020-136). Here is why.

    Mistake 1: Reconstructing the Log After the Audit Started

    The Luceros did not maintain a time log during 2014 or 2015. When the IRS challenged their returns, Mr. Lucero built a log using credit card receipts, invoices from contractors, and his memory of what happened on each trip.

    The Tax Court did not flat-out reject reconstructed logs. The IRS allows documentation through "any reasonable means," and Treas. Reg. §1.469-5T(f)(4) explicitly permits appointment books, calendars, and narrative summaries. Reconstruction is not automatically fatal.

    What killed this log was not that it was reconstructed. It was that once the court looked at it closely, three different credibility problems appeared — each one documented in the opinion, each one avoidable with contemporaneous tracking.

    The fix: Log every activity when it happens, with the actual time spent. A log that existed before the audit letter arrived is fundamentally stronger than one built after.

    Mistake 2: Counting Commute Time

    The court excluded every hour Mr. Lucero spent driving between Sacramento and the Sea Ranch property. The court's words: commute time "is a personal expense unless an allocation for additional expenses can be made between personal and business expenses."

    This matters because STR investors often own properties far from home. If you buy a beach house in Destin and fly from Chicago to manage it, the flight time does not count toward your 100 hours. Neither does the drive from the airport to the house. Time at the property working counts. Time getting there does not.

    The problem is not just that commute hours get excluded. It is that including them signals the log was built without understanding which hours qualify — which calls the rest of the entries into question.

    The fix: Do not log drive time, flight time, or any commute from your home to the STR. If you stop at the property to handle a specific task en route to somewhere else, log only the time spent on the task itself.

    Mistake 3: Inflating Task Duration

    The log included entries where time spent was wildly out of proportion to the task — most famously, two hours shopping for coffee filters at Bed Bath & Beyond. That single line from the opinion did more damage than almost any other piece of evidence in the case.

    The reason is structural. Courts assess log credibility holistically. When one entry is obviously padded, every other entry becomes suspect, including the legitimate ones. A log with 100 real hours and 20 padded hours does not come out as 100 defensible hours. It often comes out as zero defensible hours, because the entire log has been discredited.

    Investors who try to round up their hours to hit 100 are doing themselves no favors. A log that makes the taxpayer look credible will have short entries for short tasks and longer entries for longer ones. Padding a 20-minute supply run into two hours makes every other entry look padded too.

    The fix: Log actual time, not rounded time. If a trip to Lowe's took 45 minutes, log 45 minutes. If a guest message took 10 minutes, log 10 minutes.

    Mistake 4: Mixing Personal and Business Errands on the Same Entry

    The same Gualala Supermarket trip that bought two items for the Sea Ranch property also included 20+ personal grocery items. The court noted that combined trips "further erode the log's reliability."

    Life is mixed. Most STR owners who run errands for their property also do personal errands on the same trip. That is not the problem.

    The problem is claiming the full trip as STR time when most of the trip was not STR work. If you spend 90 minutes at a grocery store and 15 of those minutes were grabbing supplies for the rental, the qualifying log entry is 15 minutes, not 90.

    This is where most reconstructed logs go wrong. The taxpayer sees a receipt from Home Depot and logs two hours for "property supplies," without remembering that half the cart was a light fixture for their own kitchen. The IRS cross-references receipts against the log, sees the mismatch, and the entry gets flagged.

    The fix: When a trip includes personal and property purchases, log only the portion of time attributable to the property. Note on the entry that the trip was combined. This honest tagging is stronger evidence than silence.

    The Bigger Trap: The 100-Hour Test Isn't Just About Your Hours

    This is the part of the case that deserves the most attention, because it is the one most STR investors do not realize applies to them.

    The 100-hour material participation test under Treas. Reg. §1.469-5T(a)(3) is actually two requirements in one: you must participate for more than 100 hours, AND your participation must not be less than the participation of any other individual, including non-owners and employees. Translation: you need to beat your property manager, your cleaner, your handyman — anyone who touched the property.

    The Tax Court said it plainly. Even assuming Mr. Lucero's 273 claimed hours in 2015 were valid, "petitioners failed to show that Mr. Lucero's participation in short-term-rental activities exceeded the participation of any other individuals."

    He did not document the management company's hours. He did not ask them for a report. He did not estimate their time with any backup. The 100-hour test was unwinnable before the court even got to his own log.

    Fixing the four log mistakes above is necessary but not sufficient. If you use a property manager, a cleaner, a landscaper, or any vendor who touches your STR, you also need a documented position on their hours. See our guide on tracking others' hours for the STR loophole for how to do this.

    What Would Have Saved This Case?

    Mr. Lucero was almost certainly at the property doing real work. He drove six to nine times a year. He oversaw maintenance. He paid contractors. He approved repairs. The work happened.

    What did not happen was the documentation.

    Every hour he actually worked on the property during 2014 and 2015 was invisible to the court because nothing was written down while it happened. By the time he tried to prove his hours, the log was a memory exercise with receipts as prompts — and the credibility problems buried the legitimate time along with the padded time.

    What would have changed the outcome:

    • A contemporaneous log maintained during 2014 and 2015
    • Task times that matched real work
    • Commute hours excluded from the outset
    • Personal errands separated from property errands
    • A documented count of Sea Ranch Escapes' hours

    Any one of those fixes would have been a meaningful improvement. All of them together would have likely won the case.

    For STR investors reading this case, the takeaway is not "log more hours." It is "log actual hours, log them when they happen, and know what your cleaner and manager are logging too."

    Preventing These Problems Going Forward

    The Lucero log had four structural problems, plus one bigger trap. Here is how a purpose-built STR tracking tool addresses each one:

    The MistakeWhat Purpose-Built Tracking Does
    Reconstructed months laterEvery log entry records when it was created, not just when the activity happened
    Commute time countedCategory tags help separate operational hours from non-qualifying time
    Excessive task timeLogging actual time spent creates a natural check against padding
    Mixed personal and property errandsPer-entry notes and tags let you log only the property-related portion
    No record of property manager hoursTrack hours from cleaners, co-hosts, and property managers to see your position against the "more than anyone else" test

    Calendar sync with Google Calendar and iCal pulls in guest bookings, cleaner turnover appointments, maintenance visits, and vendor calls that are already on your calendar — the difference between building a log from memory after an audit and having one that existed before the letter arrived.

    What to Do If Your Log Already Has These Problems

    A log that has credibility problems is worse than no log, because it invites sentence-by-sentence scrutiny like the kind the Tax Court applied to Lucero's log. If your current year's tracking is weak, inflated, or contradicted by your calendar or credit card statements, the safest move is often to start fresh with a clean, contemporaneous system and be conservative about what you claim from the pre-fix period.

    Talk to your CPA before filing. You may be better off treating the STR as passive this year and protecting next year than trying to defend a weak log.


    This article is for educational purposes only and does not constitute tax or legal advice. Every STR owner's situation is different, and Tax Court decisions turn on specific facts and records. Consult your CPA or tax attorney about your specific situation.

    The Bottom Line: A log that existed before the audit letter arrived is fundamentally stronger than one built after. Log actual hours when they happen, exclude commute time, separate personal errands, and know your property manager's hour count.

    Ready to see if you qualify? Try the free STR loophole calculator →

    Start Tracking Your Hours Today

    STR Loophole makes documentation effortless.

    Frequently Asked Questions

    Related Articles