The 4-Log System Every STR Host Needs: Participation, Mileage, Expenses, Stays

At a glance: four logs, four questions

Not tax advice; general framework only. See your CPA for how any of this applies to your specific facts.

Log	Question it answers	Statutory anchor
1. Participation	Did you materially participate?	§469; §1.469-5T
2. Mileage	Are those miles deductible?	§274(d)
3. Expenses	What goes on Schedule E, and what has to be capitalized?	Schedule E lines 5–19; §263; §1.263(a)-1(f); §168
4. Stays	Is it a short-term rental at all? Is it still a rental, not a residence?	§1.469-1T(e)(3)(ii)(A); §280A(d)

Four logs, four different sets of required fields, four different tests. When one log is missing or leaks into another, the year-end story falls apart at the seam you didn't notice.

Why four logs, not one big spreadsheet

The temptation is to open one "STR Operations" tab and dump everything into it. Hours here, miles there, receipts stapled to a page, guest names when you remember. It feels efficient in March. It falls apart at year-end because each of the four logs is proving a different thing under a different section of the tax code, and the required fields don't overlap cleanly.

Material participation under §469 and §1.469-5T cares about who did what work, when, and for how many hours; and for the "100 hours and more than anyone else" test, how that stacks against your co-host, cleaner, or spouse. Mileage under §274(d) needs date, place, and business purpose per trip, elements a participation log doesn't require. Schedule E cares about vendor, amount, and expense category. The stays log proves your rental qualifies as an STR under §1.469-1T (average stay of seven days or fewer) and hasn't tipped into personal-residence territory under §280A(d) (personal use over the greater of 14 days or 10% of days rented at fair rental).

When a single spreadsheet tries to be all four logs at once, at least one column ends up missing. Usually stated business purpose on mileage entries, or the personal-use days you spent at the property in November. The CPA can't fill those in from memory in April, and you can't either. Separate logs, or one system that keeps them separate internally and cross-references them, is the pattern that survives.

Log 1: Participation (material-participation hours)

What it captures. Date, activity type, hours worked, participant identity (owner, co-owner, vendor, or manager), and which property. Every entry ties a person to time spent on a specific activity on a specific date.

What it proves. Whether you satisfy one of the seven material-participation tests under §1.469-5T. The three most common paths for STR hosts are the 500-hour test (§1.469-5T(a)(1)), the "substantially all participation" test (§1.469-5T(a)(2)), and the 100-hour-and-more-than-anyone-else test (§1.469-5T(a)(3)). For that third one, the log needs to capture other participants' hours too, otherwise you can't show you did more than they did.

Traps. Two big ones. First, travel time to and from the property is not material-participation time. §1.469-5T(f)(1) treats work "in connection with" the activity as participation, but courts and IRS practice have consistently declined to count commute-style travel as substantive work in the activity. Second, investor-context work (reviewing bookkeeping totals, reconciled account statements, analyzing property finances, researching STR markets, reading an STR investing article, listening to a real-estate podcast) is excluded under §1.469-5T(f)(2)(ii). These are investor activities, not operator activities, and logging them as MP hours weakens the file if it's ever reviewed.

Field Ledger's approach. Every activity record carries a participant field in the schema (owner, co-owner, vendor, manager) that feeds the 100-hour-and-more-than-anyone-else comparison logic; a first-class UI for logging non-owner participants' hours is on the roadmap. Investor-context keywords trigger a structural veto rather than a soft warning. The hours are still recorded, but they won't inflate the qualifying total. This is one of Field Ledger's taxpayer-safe defaults: the product never machine-asserts a tax-favorable §469 fact you didn't state. Full detail in how to track Airbnb hosting activity for taxes.

Log 2: Mileage (business-purpose miles)

What it captures. Date, origin, destination, miles driven, and the field most mileage logs skip: the stated business purpose of the trip. Optionally hours, which the participation log doesn't want.

What it proves. That each business mile satisfies §274(d) substantiation, which requires four elements for every trip: amount (miles), time (date), place (origin and destination), and business purpose. All four have to be present or the trip is unsubstantiated, and unsubstantiated mileage doesn't count toward the standard mileage rate deduction on Schedule E.

Traps. The most common is logging miles without a stated purpose ("Drove to the cabin, 62 mi"). The IRS position on §274(d) is strict: no stated purpose means the trip fails substantiation, even if the drive really did happen and really was business-related. A destination alone proves place, not purpose. The other trap is treating mileage-log hours as participation-log hours. They're not. The mileage log's purpose is proving the deduction; participation hours are governed by the separate §469 tests above.

Field Ledger's approach. Mileage lines require a stated business purpose to count toward the deductible-miles total; entries missing purpose are flagged and excluded from the "at standard mileage rate" figure until you fix them. Travel hours are logged separately from participation hours and never auto-roll into the MP total. Full detail in how to track Airbnb mileage for taxes.

Log 3: Expenses (Schedule E line-items)

What it captures. Date, vendor, amount, expense category (repairs, supplies, utilities, insurance, cleaning, management fees), which property the cost belongs to, and (for larger items) a repair-vs-improvement flag.

What it proves. The operating expenses that end up on Schedule E, Lines 5 through 19: the ordinary and necessary costs of running the rental that are deductible in the year incurred. Separately, it identifies the items that have to be capitalized under §263 and depreciated over their MACRS class life (5-year for appliances, carpeting, and furniture used in the rental; 7-year for office furniture and equipment; 15-year for land improvements; 27.5-year for the residential-rental building itself and for structural building components like HVAC, roofing, hard flooring, and water heaters).

Traps. The repair-vs-improvement line, which is where the de-minimis safe harbor under §1.263(a)-1(f) enters. Items at or under $2,500 per invoice can generally be expensed rather than capitalized, provided the taxpayer has a written accounting policy in place at the start of the year treating such items as expenses, expenses them on their books, and makes the annual safe-harbor election on the return. Above that threshold, or for items that materially improve or extend the useful life of the property, capitalization is usually required and MACRS depreciation applies. Getting this call wrong in either direction changes both the year's deduction and the property's basis when you eventually sell.

Field Ledger's approach. A transaction-to-asset heuristic suggests a MACRS class for items that look like capital purchases: 5, 7, or 15-year classes for personal property (appliances, furniture, land improvements), and 27.5-year for structural building components it can identify from the transaction description (HVAC, roofing, hard flooring, water heaters, treated as §1250 residential rental real property). Whether the building itself is 27.5-year residential or 39-year nonresidential is a facts-and-circumstances call left to your CPA. At year-end, export a Schedule E summary CSV: operating expenses subtotaled by line, capital items listed separately with the suggested MACRS class, items at or under $2,500 flagged for your CPA's §1.263(a)-1(f) safe-harbor decision. Your CPA still makes the classification calls; the file gives them clean facts to work from.

Log 4: Stays (guest stays and personal-use days)

What it captures. Check-in date, check-out date, number of days (nights, in Airbnb parlance), guest identifier (a booking reference is enough), gross rental amount. On the other side, any days the owner or a related party used the property personally.

What it proves. Two distinct tests, neither of which is the material-participation test. The first sits within §469; the second is a separate Code section that applies alongside §469.

Test one: §1.469-1T(e)(3)(ii)(A), the "average period of customer use" test. If your total rental days divided by the number of separate rental periods averages seven or fewer, the property is not a per-se rental activity under §469(c)(2), which is the gateway that lets a materially participated rental be non-passive at all.

Test two: IRC §280A(d), the residence-reclassification rule. If personal use of the dwelling by you or a related party exceeds the greater of 14 days or 10% of the days the property was rented at a fair rental, the property is treated as a residence and rental deductions are capped at rental income (no net loss).

Traps. The average-stay test is often mis-computed as "usually people stay a weekend" rather than the actual arithmetic: total days divided by total separate stays. A single 30-day booking can push a property that "feels" like a short-term rental over the 7-day threshold for that year. The §280A trap is that personal-use days are almost never tracked at all. Hosts remember to log guest stays but not the long weekend the family spent there in October, which is the day-count that actually determines whether losses stay deductible.

Field Ledger's approach. Two independent status pills, one for average stay, one for personal-use days, each showing your current computed value in plain language against its threshold ("under the 7-day threshold," "approaching the §280A(d) threshold," "residence reclassification risk") rather than a binary "PASS" or "FAIL" verdict. Stays log includes personal-use days as a first-class field, not an afterthought. Underlying framework in the Airbnb rental activity tracker guide.

Where the four logs cross-check each other

This is the three-axis §469 record: material-participation hours, average-stay days, and personal-use days, checking each other inside one tool. Single-purpose trackers (an hours app, a mileage app, a bookkeeping tool) can't do this because none of them hold all three axes. Each log's value is easy to see in isolation. What's less obvious, and what makes a record file actually hold up, is how the four are supposed to check each other.

Mileage hours do not roll into participation hours. A trip logged in the mileage log has an hours field for travel time. Those hours never auto-roll into the participation total. §1.469-5T(f)(1)'s "in connection with" language has been narrowed by case law and IRS practice to exclude commute-style travel from qualifying work. If you also did qualifying work at the destination (cleaning, guest turnover, on-site repair), that work belongs in the participation log as its own entry with its own hours.
Personal-use days and MP hours on the same date. A day the user classifies as "personal use" (principal purpose personal enjoyment) is not the same as a day whose principal purpose was on-site work. §280A(d)(2) excludes days spent substantially full-time on repair or maintenance from personal-use counts. The two flow into different logs on purpose, and overlaps that occur should be resolved to one or the other before filing.
Investor-context entries in the participation log get flagged. Bookkeeping-review time, market research, and reading investing articles or newsletters are hours you may have really spent; they just don't count under §1.469-5T(f)(2)(ii) toward material participation. A good system records them and labels them, rather than pretending they didn't happen or laundering them as "management".
Mileage without stated purpose stays out of the deduction total. You can leave the entry in the log for your own recall, but the "$X at the standard mileage rate" figure a CPA works from should only sum lines that carry the §274(d) purpose element. Flagging is honest; auto-including is optimistic.
Capital-vs-repair decisions on the expense log affect basis in the property record. A $3,000 water heater expensed in error inflates this year's deduction and understates the property's basis when you sell. The cross-reference is subtle but real. Schedule E line 5 (Advertising) doesn't affect basis; MACRS depreciation does.

Why four separate tools tend to break

A common host stack looks something like: a Google Sheet for hours, MileIQ (or a similar app) for miles, QuickBooks or Wave (or a shoebox of receipts) for expenses, the Airbnb dashboard for guest stays. Four tools, four owners of four slices of the truth. Each one is fine at its job. The problem is the seams.

At year-end, someone (usually you, sometimes your CPA) has to line the four up. Do the mileage entries reconcile with the days you were on-property in the activity log? Do the personal-use days in your calendar match the Airbnb nights that weren't booked? Does the expense you logged in July have a matching activity entry that hour-audits the installation work? None of these questions has a "cross-tool sync" answer. The typical result is a compressed weekend of spreadsheet archaeology, from which the numbers on Schedule E get typed with more confidence than the underlying records actually justify.

MileIQ, QuickBooks, and Wave are real trademarks of their respective owners: Microsoft, Intuit, and H&R Block. The point isn't that any of them is bad. They just each know one slice, and the cross-checks between slices are where STR record-keeping actually lives.

How Field Ledger keeps the four logs coherent

Field Ledger is one tool that holds all four log types with the cross-references intact. A single day's capture, one paragraph or a batch of prefixed lines (Activity:, Trip:, Expense:), gets parsed into the right log types with the right fields filled in. Guest stays and personal-use days live in a separate form (or property-side records) that the stays log pulls from.

Nothing writes to your records without your review. The staged entries are shown to you before they save, so the system is capturing your intent, not replacing it. The rules that matter for the four cross-checks above (travel hours stay separate from participation hours, investor-context keywords trigger a structural veto, mileage without stated purpose is flagged and excluded from the deduction total, capital items get suggested MACRS classes) are enforced by the parser, not asked of you as configuration. Personal-use overlap with MP hours on the same date is not auto-flagged today; it surfaces at year-end as an inconsistency for you and your CPA to reconcile.

One honest caveat: guest-stay and revenue data is currently manual entry in Field Ledger. The stays log for hosts on Airbnb, VRBO, and Booking.com platforms requires periodic manual reconciliation from the platform's own transaction export. Airbnb, VRBO, and Booking.com are trademarks of their respective owners; Field Ledger is not affiliated with any of them.

One tool. Four logs. Cross-references intact.

Start a free trial and log a day's worth of work in a single entry. You'll see the participation, mileage, and expense lines separate into their own logs, with the cross-checks the four-log framework depends on already enforced.

Four log types, one entry surface
Travel hours never auto-count toward material-participation totals
Mileage without stated purpose flagged, not silently deducted
Status pills for the average-stay and personal-use tests, in plain language (not PASS/FAIL)
Schedule E summary CSV your CPA can work from, with MACRS + de-minimis flags included
You review every parsed entry before it saves

Start free trial

714-day free trial, no credit card required. Renews monthly or annually at the plan price you select until canceled. Cancel anytime in Manage Billing. Plus applicable US sales tax.

Frequently asked questions

What counts as a “log” for IRS purposes?

A log is a contemporaneous record, made at or near the time the activity happened, that captures the elements the applicable statute requires. For §469 material participation, the record needs date, description, hours, and (for the 100-hour-and-more-than-anyone test) participant identity. For §274(d) mileage, it needs date, place, business purpose, and miles. A spreadsheet, a notebook, and a purpose-built app all qualify as a “log” if the required elements are present and the entries were made contemporaneously. Reconstructed-from-memory records at year-end are what tends to fail.

Can I use one spreadsheet for all four logs?

Technically yes, but the four logs answer four different tax questions with four different sets of required fields, so a single mashed-together spreadsheet tends to be missing something for at least one of them. A more common failure mode: mixing mileage hours into the participation total (double-counting) or forgetting to log personal-use days at all (which blows up the §280A test at year-end). Separate logs, or a single tool that keeps them separate internally and cross-references them, is the safer pattern.

What if I've been mixing my mileage log into my activity log?

You'll want to separate them before filing. Travel hours (driving time to and from the property) generally do not count as material-participation hours. §1.469-5T(f)(1) treats work “in connection with” the activity as participation, but courts and IRS practice have consistently declined to count commute-style travel as substantive work in the activity. Meanwhile the miles themselves need §274(d) substantiation (date, place, purpose) that a bare hours entry doesn't provide. If your existing records mix them, a CPA can usually help you split them; going forward, keep them in separate log types.

Do the four logs need to be electronic?

No. A paper appointment book with dated entries qualifies. What matters is contemporaneity (entries made at or near the time the event happened, not reconstructed months later) and completeness of the required fields for each log type. Electronic records are easier to search, cross-reference, and hand to a CPA at year-end, but the statute does not require them.

How far back do I need to keep these records?

The general federal rule is three years from the date you filed the return (IRC §6501(a)). It stretches to six years if income is understated by more than 25%, and there is no time limit for fraudulent or unfiled returns. Property-related records tied to depreciation (asset purchase invoices, capital improvement receipts) should be kept for as long as you own the property plus the applicable limitations period after you sell, because gain calculations reach back to original basis.

Does this replace my CPA?

No. The four logs give your CPA the underlying facts they need to prepare Schedule E correctly and to answer questions about §469 material participation, §280A personal-use limits, and §274(d) mileage substantiation. The classification calls (which expenses go on which line, whether an item is a repair or a capital improvement, whether you meet a particular material-participation test in a given year) are your CPA's job, informed by records you kept during the year.

Related guides

Statutory sources

IRC §469 — passive activity loss rules
IRC §469(c)(2) — per-se rental characterization
Treas. Reg. §1.469-1T(e)(3)(ii)(A) — average-stay exception (≤7 days)
Treas. Reg. §1.469-5T — the seven material-participation tests
Treas. Reg. §1.469-5T(a)(1) — 500-hour test
Treas. Reg. §1.469-5T(a)(2) — "substantially all" test
Treas. Reg. §1.469-5T(a)(3) — 100-hour-and-more-than-anyone test
Treas. Reg. §1.469-5T(f)(1) — work "in connection with" the activity
Treas. Reg. §1.469-5T(f)(2)(ii) — investor-context exclusion
IRC §280A(d) — personal-use / residence reclassification
IRC §280A(d)(2) — days on repair or maintenance excluded from personal-use count
IRC §274(d) — substantiation requirements (travel, entertainment, gifts, listed property)
IRC §263; Treas. Reg. §1.263(a)-1(f) — capitalization; de-minimis safe harbor
IRC §168 — MACRS recovery periods
IRC §6501(a) — general statute of limitations for assessment

General information only. Tax outcomes depend on your specific facts; talk to a qualified tax professional before relying on any of this in filing.

The key takeaway

An STR record file that survives is four logs, not one. Participation proves material participation under §469. Mileage proves §274(d) substantiation. Expenses populate Schedule E and separate the operating from the capitalized. Stays prove the property is still a short-term rental and still a rental. The four cross-check each other, a fact any single-tool approach can't quite give you, and any single-spreadsheet approach reliably loses at the seam.