We Compared What REPS Tracking Apps Actually Capture on Manual Entries — Most Log Nothing

TL;DR: We compared what the top REPS tracking tools capture when you log a manual activity. Every tool except RE:Writeoff stores only what you type — no server timestamp, no device info, no location data. RE:Writeoff automatically captures city-level geolocation, device/browser info, IP address, and an independent server timestamp on every manual entry.

If you're claiming Real Estate Professional Status, roughly a third of your qualifying hours probably come from activities you log manually. Property visits, phone calls with contractors, drive-bys, in-person meetings. Things that don't leave an email trail.

These manual entries are also the weakest point in your audit defense. An email-sourced activity has built-in provenance — timestamps, sender headers, message IDs. A manual entry? It has whatever you typed and nothing else.

We looked at how the major REPS tracking tools handle this problem. The short answer: most of them don't.

What we compared

We examined the five most-used tools for tracking REPS and STR material participation hours, focusing on a single question: when a user logs a manual activity entry, what metadata does the tool capture automatically?

Not what the user types in. Not the activity description or duration. The metadata the system records on its own — the kind of data that could corroborate the entry during an IRS audit.

Tool	Server timestamp	Device info	Location data	IP address	Independent "logged at" time
RE:Writeoff	Yes	Browser, OS, device type	City, state, zip (server-side)	Yes	Yes (separate from activity date)
REPStracker	No	No	No	No	No
REPSLog	No	No	No	No	No
REPS Time	No	No	No	No	No
STR Hours	No	No	No	No	No

Every other tool in this space stores exactly what the user enters: a date, a description, and a duration. Nothing else. No independent record of when the entry was created, where the user was, or what device they used.

Why this matters for IRS audits

The IRS doesn't just care what you logged. They care when you logged it.

Tax Court has consistently distinguished between contemporaneous records — created at or near the time of the activity — and reconstructed records assembled after the fact. The former are treated as credible evidence. The latter are treated as self-serving testimony, often given little or no weight.

For email-sourced activities, this distinction barely matters. The email exists independently. Google's servers timestamped it. The headers prove it was sent and received. Nobody disputes an email's provenance.

For manual entries, the distinction is everything. If your tracking app stores "April 15 — property inspection — 45 minutes" and nothing else, there's no way to prove you didn't type that entry on December 30th while filling in the whole year from memory. Which is precisely the behavior Tax Court flags.

What RE:Writeoff captures (and why)

Every manual activity logged in RE:Writeoff automatically records:

• Server-side submission timestamp — when the entry was actually created, independent of the activity date the user assigns. If you log a property visit on April 15th, the server records that the entry was submitted on April 15th at 3:12 PM CDT. That's your contemporaneous proof — the system independently confirms you logged it that day, not six months later.

• City-level geolocation — derived from server-side infrastructure (Cloudflare request headers), not browser GPS. This means the location data comes from trusted infrastructure the user can't tamper with. If your rental property is in Austin and you logged the visit from Austin, the metadata corroborates your claim without you doing anything.

• Device and browser information — iPhone Safari, Chrome on a MacBook, Android Firefox. This is parsed from the request, not self-reported. It creates one more independent data point an auditor can cross-reference.

• IP address — recorded server-side as part of the request.

A manual entry in RE:Writeoff reads like this in your audit report:

April 15, 2026 — Property inspection at 123 Main St Duration: 45 minutes Source: Manual entry Logged: April 15, 2026 at 3:12 PM CDT Location: Austin, TX 78701 Device: iPhone Safari (iOS 18.1) Server timestamp: 2026-04-15T19:32:04Z

Compare that with what every other REPS tracker produces:

Apr 15 — Property inspection, 123 Main St — 45 min

Same activity. Same user effort. Completely different audit value.

Why server-side, not GPS

A reasonable question: why use IP-based city-level location instead of precise GPS from the browser?

Three reasons.

Trust. Browser geolocation is client-side. The user's device reports its own location. For tax documentation that might be scrutinized in court, you want the location data to come from infrastructure the user doesn't control. Cloudflare's geo headers are derived from the IP address on the server side — the user never touches this data.

Zero friction. Browser geolocation triggers a permission prompt. The user has to tap "Allow." This adds a step, and any added step means some percentage of entries won't capture the data. Server-side capture is invisible — it happens on every request, every time, with no user action.

Sufficient precision. You don't need GPS coordinates to prove you were in Austin when your property is in Austin. City-level accuracy is enough to corroborate a claim. An auditor isn't checking whether you were at 123 Main St versus 125 Main St — they're checking whether you were in Austin versus Cancun.

The full picture: email + manual, one audit trail

The provenance gap matters most because manual entries sit alongside email-sourced entries in the same audit report.

Email-sourced activities in RE:Writeoff carry Gmail message IDs, server timestamps, thread metadata, and sender/recipient headers. This is rich, third-party-verified provenance that the IRS can't reasonably dispute.

If your manual entries next to those emails show nothing but a date and a description, the contrast is stark. One type of evidence is verifiable. The other is just your word.

With provenance metadata on manual entries, both types of activity carry independent corroborating data. The audit trail reads consistently — every line item, whether it came from an email or was logged by hand, has a timestamp, a source, and metadata that supports the claim.

What this means if you're choosing a tracker

If you're evaluating REPS tracking tools, ask this question: what does the tool record when I log something manually?

If the answer is "whatever you type" — and for every tool except RE:Writeoff, that is the answer — then your manual entries have no more audit credibility than a spreadsheet. You're paying for an app that's functionally equivalent to Google Sheets for the activities that need the most defensibility.

The 750-hour threshold for REPS qualification isn't just about counting hours. It's about proving them. And proving means evidence that holds up under scrutiny — not a self-reported log that could have been written at any time.

Related guides

• Why the IRS Rejects Most REPS Hour Logs — what "contemporaneous" actually means in Tax Court
• What Is Real Estate Professional Status? — the full REPS qualification breakdown
• How to Track Property Management Hours — tracking methods compared

RE:Writeoff builds the evidence trail automatically. Every entry, every time, no extra steps.