What Does Your Real Estate Professional Hour Log Actually Need to Prove?

Real estate professional status under IRC §469(c)(7) unlocks the ability to deduct rental losses against ordinary income - but the 750-hour threshold is only as strong as the records behind it. The IRS does not accept self-serving testimony alone, and Tax Court has repeatedly rejected REP claims where the log was the only evidence offered. The burden of proof sits entirely with the taxpayer, and that burden is heavier than most people expect. This article covers what a defensible hour log actually needs to contain, the specific patterns that trigger examiner skepticism, and what good documentation looks like in practice.

The log is not a formality - it is the whole case

IRC §469(c)(7) provides that a taxpayer qualifies as a real estate professional if more than half of their personal services during the year are performed in real property trades or businesses in which they materially participate, and those services total at least 750 hours. Clear the threshold and rental losses become nonpassive. Miss it - or fail to prove it - and the losses stay suspended.

That second part is where most REP claims actually fail. The 750-hour requirement is not self-executing. A taxpayer who genuinely worked 800 hours in their rental activities but kept no contemporaneous records is in a worse position at audit than one who worked 760 hours and documented every one of them. The IRS will not take your word for it, and Tax Court will not either. A long line of decisions makes clear that oral testimony alone, without corroborating records, is insufficient to establish REP status. The log is not supporting evidence - in most cases, it is the case.

What "contemporaneous" actually means

Temp. Reg. §1.469-9T does not define contemporaneous with a hard rule, but courts interpret it consistently: entries should be made close in time to the activity, not reconstructed from memory at year-end. A log assembled in December to cover the prior twelve months is not contemporaneous. Neither is one finalized in January "based on notes" that no longer exist.

The practical test courts apply is whether the log can be independently corroborated. Entries that align with calendar records, tenant emails, contractor invoices, bank transactions, and timestamped photos carry weight. Entries that cannot be cross-referenced to any external record are vulnerable - not because the activity did not happen, but because there is no way to verify it did.

Why corroborating records matter as much as the log itself

An examiner reviewing a log with no corroborating trail will treat that log as a reconstruction, and the burden to prove otherwise falls on the taxpayer. A well-maintained hour log paired with a calendar full of property-related entries, a text thread with a contractor, and dated repair invoices is a defensible package. A polished log with nothing behind it is not.

The boilerplate problem

One of the most common and most damaging patterns in REP audits: a log that shows the same activity label, the same hour count, and the same description week after week for the entire year.

"Operations review - budget and record keeping - 4.5 hours." Week 1. Week 2. Week 3. All the way to Week 52, with no variation in language, hours, or the nature of the work described.

This pattern does not reflect how real property management works. Genuine rental activity varies - leases turn over, repairs get scheduled and completed, tenant issues arise and resolve, seasonal maintenance happens on a cycle. A log that shows perfectly uniform activity across every week of the year does not describe a real rental portfolio. It describes a number that someone needed to reach.

How Tax Court has treated this pattern

In Pohoski v. Commissioner, T.C. Memo. 1998-137, the court noted that repetitive, identical entries undermine the credibility of the entire log - not just the entries themselves. When a court finds that a log was assembled to justify a predetermined hour total rather than to record actual activity, it will typically reject the log in its entirety, even if some of the underlying activity may have occurred. The evidentiary standard is not whether you worked - it is whether your records prove you worked the hours you claim.

The plausibility test

Examiners and courts apply a common-sense reasonableness check that goes beyond the total hour count. Hours must be plausible relative to the number of properties, the type of properties, and the documented events of the year.

Credible profile: hours that spike during documented repair projects, leasing activity, or tenant transitions; lower-activity periods that reflect the actual rhythm of the portfolio; administrative time proportionate to the scale of the operation
Profile that raises flags: uniform weekly totals regardless of what was happening with the properties; large single-week hour claims with no corroborating records; administrative hours that are high relative to portfolio size

The question an examiner is asking - even if they do not say it out loud - is whether this log describes a real year of activity or a number engineered to clear 750. Variation, specificity, and corroboration answer that question. Uniformity and vague labels do not.

Hours must reflect real activity, not just a number

Even hours that are logged and technically plausible do not automatically translate to deductible activity. The underlying tasks must be ordinary and necessary for that type of rental operation - the same standard that applies under §162 and §212 to business and investment expenses generally.

Consider administrative tasks on a small residential portfolio. A landlord with two rental properties logging 50 to 60 hours annually on budgeting, record organization, and financial review has a problem. There is no credible industry comparator for that volume of administrative time on a two-property portfolio. Fifty hours of annual administrative work on two properties is not ordinary by any reasonable measure, and an examiner will treat those entries as inflated - which calls the entire log into question.

How the comparator test applies across activity categories

Travel time, tenant communication, maintenance oversight - each of these has a plausible range relative to the number and type of properties. Hours that exceed that range without specific documentation explaining why are a liability, not an asset. The question is what a typical landlord with a similar portfolio would reasonably spend on a given activity, and every category in the log is subject to that question.

What each entry actually needs to contain

At minimum, a defensible log entry includes:

Date or date range - specific enough to be cross-referenced to other records
Property - which property or properties the activity related to
Activity type - the category of work (maintenance, leasing, tenant communication, financial review, etc.)
Description - what was actually done, not a generic label
Hours spent - the time claimed for that entry
Supporting record reference - ideally a tie to an invoice, email, calendar entry, or other corroborating document

The difference between a weak entry and a defensible one is specificity. "Tenant communications - 4 hours" tells an examiner nothing. "Tenant communications - 2.5 hours - responded to HVAC complaint at [address], coordinated with HVAC contractor, confirmed appointment for following week - see email thread 3/14" is an entry that can be verified. Generic labels are not just weak - they are a signal that the log was assembled after the fact.

The small portfolio problem

The math creates a specific challenge for taxpayers with one or two properties. Seven hundred fifty hours on two properties is roughly 375 hours per property per year - more than 7 hours per week per property, every week of the year. That is not impossible, but it requires records that account for that time in specific, documented activities.

A two-property portfolio cannot absorb 750 hours through routine administrative entries. The hours have to come from somewhere - active repair projects, significant leasing activity, renovation work, hands-on management that goes well beyond what a typical landlord delegates. If those events happened, there should be records: contractor invoices, permit applications, leasing correspondence, vendor communications. If the records do not exist, the hours are not defensible regardless of what the log says.

Why small portfolios face more scrutiny, not less

An examiner reviewing a two-property REP claim will apply more scrutiny because the math demands an explanation. This is not a rule that small portfolios cannot qualify - it is a recognition that the substantiation burden is proportionally higher when the implied time-per-property is high.

Reconstruction red flags

Certain patterns signal assembly after the fact. Examiners are trained to look for them:

Uniform round-number or consistent fractional hour entries - every entry is 3.0 hours, or every entry is 4.5 hours, with no variation across different types of activity
Identical descriptions copied across weeks - the same language, word for word, appearing in the same time slot throughout the year
Month-end management blocks - a recurring entry at the end of each month with the same hours and language, suggesting the log was updated monthly rather than in real time
Language that reads as reporting rather than recording - entries written to describe what the taxpayer does generally, rather than what they did on a specific date
Hour entries that conflict with other records - high-hour entries during periods when other records suggest the taxpayer was traveling, ill, or otherwise unavailable

Any one of these patterns creates a credibility problem. Multiple patterns in the same log are very difficult to overcome at audit or in Tax Court.

What good looks like

A defensible REP log has a few consistent characteristics: entries vary naturally in content and duration because real activity varies; descriptions are specific enough to identify the event, the property, and what was done; the hours profile across the year reflects the actual rhythm of the portfolio; and the log can be cross-referenced to external records that independently confirm the activity.

The practical standard is this: could an auditor who has never met you, reviewing your log alongside your supporting records, reconstruct a plausible picture of how you spent your time across the year? If yes, the log is defensible. If the log requires the auditor to take your word for it, it is not.

Maintaining that kind of log is not complicated, but it requires consistency throughout the year. The taxpayer who updates their log weekly, ties entries to calendar records and communications as they go, and keeps supporting documents organized by property is in a fundamentally different position than the one who assembles a log in December. The underlying activity may be identical. The tax outcome often is not.