Why the IRS Rejects Most REPS Hour Logs (And What 'Contemporaneous' Actually Means)

TL;DR: The IRS standard for REPS hour logs is "contemporaneous" — created at or near the time of the activity, not reconstructed later. Tax Court consistently rejects after-the-fact spreadsheets. Defensible logs need three things: real-time timestamps, specific verifiable details, and corroborating evidence like emails or receipts.

You did the work. Eight hundred hours of it. Property inspections, contractor calls, lease negotiations, drive-bys after tenant complaints at 10 PM. Your spouse handled it all so you could keep your W-2 job and still claim Real Estate Professional Status.

Then the IRS audited you, and your CPA asked for your hour log.

You opened a spreadsheet. Typed in dates from memory. Estimated hours. Rounded to the nearest 30 minutes. Three months later, a Tax Court judge looked at that spreadsheet and said it wasn't worth the cells it was printed on.

This happens more than you'd think. Not because taxpayers are lying — most of them genuinely did the work. It happens because the IRS has a specific standard for what counts as proof, and a spreadsheet filled in after the fact doesn't meet it.

That standard has a name: contemporaneous.

What "contemporaneous" actually means under the tax code

Here's what trips people up. The Treasury Regulations technically don't require contemporaneous daily time logs to prove material participation.

Treas. Reg. §1.469-5T(f)(4) The regulation that governs how taxpayers prove material participation. It says participation can be established "by any reasonable means" and that "contemporaneous daily time reports, logs, or similar documents are not required." But it also says a "post-event ballpark guesstimate" is not sufficient.

Read that regulation and you might think you're in the clear. You're not.

In practice, Tax Court judges have drawn the line much closer to "contemporaneous or nothing" than the regulation's text suggests. Case after case follows the same pattern. Taxpayer claims REPS qualification with 750+ hours of real estate activity. Taxpayer presents a log that was clearly assembled weeks or months later. The court discounts it — not because the regulation technically demands real-time logs, but because reconstructed records are treated as self-serving testimony. And self-serving testimony, standing alone, rarely wins.

Courts have been consistent about this. When a log appears in the record for the first time during litigation, judges notice. When every entry is rounded to the hour, judges notice. When nothing corroborates the log — no contractor invoices matching the dates, no emails, no calendar entries — judges notice that too.

"Contemporaneous" in courtroom practice means: created at or near the time of the activity, not assembled later from memory.

Three things that make a REPS hour log defensible

Tax Court opinions in material participation cases reveal three consistent threads. Logs that survive IRS audits tend to share all three.

1. Created at or near the time

A log entry written the same day — or even the same week — as the activity carries fundamentally different evidentiary weight than one written months later. The closer the entry is to the activity, the more credible it is.

This is why daily logs win and annual reconstructions lose. It's not a technicality. It's basic evidentiary reasoning: a record made in the moment is less likely to be inflated, misremembered, or fabricated than one written from memory at tax time.

2. Specific enough to verify

"Property management — 2 hours" tells a judge nothing. It could mean anything. It could mean nothing.

Compare that with: "Called Mike Rivera at Greenfield Plumbing re: unit 4B water heater replacement. Discussed quote, scheduled install for Friday. 25 minutes."

The second entry can be checked. A judge can ask: does Greenfield Plumbing exist? Did they replace a water heater at that property? Does the timeline hold up? The first entry invites none of those questions — there's nothing to verify. That's exactly why courts give it little weight.

Specificity isn't about being verbose. It's about being verifiable.

3. Corroborated by independent evidence

The strongest hour logs don't stand alone. They're backed by evidence the taxpayer didn't create for tax purposes: emails with contractors, text messages about property issues, receipts from hardware stores, mileage records, calendar invitations with property managers.

None of these individually prove hours spent. But together, they create a pattern that's very hard to fabricate. If your log says you spent Tuesday morning dealing with a plumbing emergency at your rental, and your email shows a thread with the plumber that Tuesday morning, and your credit card shows a charge at the hardware store that afternoon — that's the kind of contemporaneous record a judge can trust.

The mistakes that get hour logs thrown out

If you're logging REPS hours the way most investors do, you're probably making at least one of these.

The annual reconstruction. You sit down in March, open a fresh spreadsheet, and try to remember what you did last year. Maybe you scroll through your calendar for clues. This is the single most common reason REPS claims fail in Tax Court. By the time you're writing, you're guessing — and the IRS knows it.

Vague descriptions. "Property management," "research," "admin work." These tell the auditor you either don't remember what you actually did, or you're padding the log. Neither interpretation helps your case.

Round numbers everywhere. Every entry in your log is exactly 1 hour, 2 hours, or 30 minutes. This signals estimation, not tracking. Real work doesn't happen in neat increments. A 47-minute phone call logged as "1 hour" is a small thing, but twelve months of round numbers is a pattern — and it's the kind of pattern auditors are trained to spot.

No corroboration. Your log exists in a vacuum. No emails supporting it, no receipts, no calendar entries, no text messages. It's your word — and in Tax Court, your word alone usually isn't enough.

Activities that don't qualify. Travel time to properties generally counts toward REPS hours. "Thinking about real estate strategy" doesn't. "Reading real estate blogs" is a stretch. Padding with questionable activities undermines the legitimate entries around them.

What a defensible entry actually looks like

Here's the difference between an entry that survives an audit and one that doesn't.

Weak entry (the typical spreadsheet):

Apr 15 — Property inspection, 123 Main St — 1 hr

No timestamp for when it was logged. No detail about what was actually inspected. No corroboration. Created who-knows-when.

Strong entry:

April 15, 2026 — Drove to 123 Main St to inspect unit 2 after tenant reported water stain on ceiling. Found soft drywall near bathroom vent, took photos. Called ABC Restoration (512-555-0147), scheduled moisture assessment for Thursday. Duration: 1 hr 15 min (including 20 min drive each way) Logged: April 15, 2026 at 3:12 PM CDT Location: Austin, TX 78701 Device: iPhone Safari

The second entry is specific, timestamped at the time it was created, and references verifiable facts — the contractor, the phone number, the tenant complaint. An auditor can cross-reference it. A Tax Court judge can trust it.

The difference isn't effort. Both entries took roughly the same time to create. The difference is when they were created and how much context they captured.

How technology closes the gap

The traditional CPA advice is "keep a daily log." Solid advice. Most investors don't follow it — not because they're careless, but because pulling out a spreadsheet after every phone call or property visit is tedious enough that the habit dies within a week.

Technology can close this gap two ways.

Automated capture from existing workflows. If you're already emailing contractors, responding to tenant messages, and scheduling maintenance through your inbox, those emails are contemporaneous records with built-in provenance. Timestamps, sender/recipient headers, message IDs — all immutable, all created by a third party. An email thread with your property manager about a lease renewal is better audit documentation than any spreadsheet entry you could write after the fact. Pulling these into your activity log automatically means your best evidence requires zero extra effort.

Provenance metadata on manual entries. When you do need to log something by hand — a property visit, a phone call, a contractor meeting — the entry can capture more than just what you type. A server-side timestamp proves when you created the entry, independent of what date you assign the activity. IP-based geolocation records where you were when you logged it. Device metadata records how you submitted it. Together, these transform a self-reported entry into something with a real evidence trail.

This is what RE:Writeoff builds automatically. Email-sourced activities inherit the email's own metadata — message IDs, server timestamps, thread context. Manual entries capture device type, city-level location from server infrastructure, and an independent server timestamp separate from the activity date.

The result: an audit trail where every line item traces back to either a third-party email record or a timestamped, geolocated manual entry. Not "the user said so." Not a spreadsheet with round numbers. A structured, verifiable log that reads the way Tax Court expects contemporaneous records to read.

What this means for your REPS claim

REPS qualification and STR material participation both come down to proving hours. The legal standard is technically flexible — "any reasonable means." But courtroom reality demands contemporaneous, specific, corroborated records.

If your current system is a spreadsheet you fill in quarterly, you're building your tax position on exactly the kind of evidence Tax Court throws out.

Related guides

• What Is Real Estate Professional Status? — the 750-hour rule and material participation tests
• How to Track Property Management Hours — what the IRS expects in your records
• IRS Activity Categories for Rental Properties — 10 qualifying categories with examples
• What REPS Tracking Apps Actually Capture on Manual Entries — our companion comparison piece

Your CPA will thank you for fixing that before the audit letter arrives. Start with RE:Writeoff — the documentation builds itself.