Rebuilding an hours log for a year that is already filed does not, by itself, change anything on that return. An amended return is the only thing that changes a filed position, and whether to file one is a decision for the preparer who signs it, not for a tracking app and not for an article. What a rebuilt log does is supply the evidence the question turns on. This post describes what that evidence has to look like, what an amendment exposes, and what to assemble before the conversation.
Why owners reach this point
The pattern is familiar. An owner buys a short-term rental, hears that losses may offset other income if the activity is not a rental activity under Treas. Reg. §1.469-1T(e)(3) and the owner materially participates, and files the first year conservatively because nobody kept a log. A year later, with a log running properly, they look back and conclude they probably did the work in that first year too. The hours existed. The record did not.
Other versions: a preparer treated the activity as passive and suspended the losses on Form 8582, a new preparer reads the facts differently, or a sale makes the earlier years' reporting matter for how the suspended amounts come out. In each case the hours are historical fact and the only live question is whether they can be shown.
A reconstruction is evidence, not a fix
A rebuilt log is a piece of evidence about what happened. It is not a correction, and it does not travel back and make the year look documented. That distinction matters because of how the two are read. A log kept at the time is evidence created before anyone had a reason to want a particular number. A log built afterwards is evidence created by someone who knows what number would help.
That does not make it worthless. It does mean a reconstruction is judged by what sits underneath it. If each entry traces to something outside memory — a dated platform message, a checkout on the booking calendar, a timed receipt, a photograph — the log is a summary of those documents. If the entries trace to nothing, it is an assertion. Our walkthrough on rebuilding STR hours from real evidence covers the sources and how to label each entry with its basis.
What §1.469-5T(f)(4) does and does not allow
Treas. Reg. §1.469-5T(f)(4) is the provision every one of these conversations runs through. It says participation may be established "by any reasonable means," that contemporaneous daily time reports are not required, and that reasonable means may include appointment books, calendars or narrative summaries identifying the services performed and the approximate number of hours spent.
Read carefully, it grants less than owners hope and more than they fear:
- It does not require a contemporaneous log. An owner without one is not automatically out.
- It does require identification of the services performed. "Managed the property, 15 hours" identifies nothing.
- It does require approximate hours, which implies a basis for the approximation. An approximation derived from documents is an approximation. A figure chosen because it clears a threshold is not.
- It is a standard of proof, not a safe harbor. Meeting its description does not settle whether the hours happened; it only makes the record admissible as a reasonable means.
The Tax Court's reading has been consistent in shape: revisions that begin from a detailed day-by-day record and add a single clearly defined category have been accepted, while logs revised upward in rounds whose underlying documents were never produced have been rejected as uncorroborated. IRS Publication 925 describes the participation tests and the proof standard in plainer language, and is worth reading alongside the regulation. The reconstructed versus contemporaneous log guide sets out the standard in more detail.
The weaknesses an amendment puts on display
An amended return is a document that says the original was wrong and explains why. The explanation is read, and so is the record behind it. Three things tend to draw attention, and they are better known before the decision than after.
The first is the direction of the change. A rebuild that happens to land just above a threshold invites the question of whether the threshold shaped the numbers. Totals of 103 hours or 758 hours are not wrong, but they carry a burden that 140 or 900 does not.
The second is the gap between the years. If the documented year and the rebuilt year describe the same property, the same guests and roughly the same bookings, the hours should be broadly comparable. A rebuilt year that substantially exceeds a tracked year needs a reason in the facts — a renovation, a change of cleaner, a first season of setup work — and the reason should be visible in the entries.
The third is the state of the source documents. A rebuild is only as good as what it cites, and the citation has to survive being asked for. Platform message archives get purged. Card statements go back a limited number of years. Photo libraries get cleaned out. A log that cites a receipt nobody can produce is in a worse position than a log that says plainly which entries are estimates from a usual routine.
Statute-of-limitations basics, described generally
There are time limits on both sides, and they are the first thing a preparer will check. In general terms, IRC §6511 sets the period for a refund claim: broadly, within three years of filing the return or two years from the date the tax was paid, whichever is later. IRC §6501 sets the period during which the IRS may generally assess additional tax, ordinarily three years from filing, with longer periods in defined circumstances.
The exceptions and interactions are genuinely complicated — extensions, carryforwards, net operating losses and amounts suspended under §469 all have their own mechanics. Nothing here tells you which period applies to a specific year of a specific return. That determination belongs to a CPA or EA looking at the actual filings.
Consistency across years and the grouping question
A single amended year does not sit on its own. The participation tests in Treas. Reg. §1.469-5T apply per activity per year, so one year can differ from another on the facts. But a position taken in one year sets up expectations for the years around it, and an amendment that makes one year non-passive while the years on either side were filed as passive raises an obvious question about what was different.
Grouping adds another layer. How activities were grouped in the original filings, whether any election was made, and what the suspended amounts on Form 8582 reflect all bear on what an amendment actually accomplishes. Changing a prior year's characterisation can move suspended losses rather than release them. That is a large part of why the decision is not a self-service one. Our notes for CPAs and EAs describe the log format practitioners ask for here.
What to assemble before the conversation
Bring the record, not the conclusion. A preparer can work with evidence and a clear account of where it came from; they cannot work with a total.
- The rebuilt log itself, one line per task, with date, property, description, duration and the source each entry rests on.
- The source documents, attached to the entries they support rather than in a separate folder. STR Tracker lets you attach photos, receipts and invoices to the individual entry they belong to, so the log and its evidence stay together when you export it.
- An honest marking of which entries are documented and which are estimates from a usual routine.
- The other participants' hours for the same year, if a comparison test is in play, and the basis for those figures.
- The returns as filed for the year in question and the years on either side.
- A short written note of what prompted the rebuild and when you did it.
If the question is whether a test was met at all, the free STR loophole checker will show where the numbers stand before the meeting. Then take the whole file to a CPA or EA and let them decide whether an amendment is appropriate. That is their call to make, and it should be made on the strength of the record rather than on the size of the number.