Free Rental Property Maintenance Log Template for Landlords (Google Sheets)

Most "maintenance log" downloads are a single blank grid. This one is a small workbook — a rental property maintenance tracker spreadsheet with five tabs that work together:

• Start Here — setup notes, a safety and local-law note, and quick instructions. Read it once, then ignore it.
• Maintenance Log — the main tracker. One row per request, 30 columns from intake to closeout, with dropdowns for priority, status, source channel, issue category, vendor confirmation, owner approval, and tenant confirmation. Two example rows show how a real urgent plumbing request and a real emergency leak look when logged — delete them and start typing.
• Dashboard — summary counts for open requests, priorities, statuses, and recorded cost. Open it Monday morning and you know where things stand without scrolling the log.
• Lists — the dropdown values the log uses. Edit these to match your own statuses and vendors; don't delete the tab.
• Vendor Directory — an optional reference list so your plumber's number lives next to the log instead of in a five-year-old text thread.

Thirty columns sounds like a lot. In practice you fill most of them in under a minute, and each one exists because skipping it costs you later. Grouped by what they do:

The spreadsheet is the artifact. The workflow is what makes it work. Here is how to track tenant maintenance requests with this kit, from first text to closed file:

The expensive mistakes in maintenance are usually triage mistakes: treating a burst pipe as routine, or dispatching an after-hours plumber for a dripping faucet. The kit includes a one-page triage checklist that sorts any request in about a minute.

Response-time targets vary by lease, local law, and season, but common practice across the industry looks like this:

The checklist has a fourth tier the response-time charts skip: Needs more information. If you can't tell from the message whether that "water thing" is a drip or a flood, don't guess a priority — same day, ask for a photo, the exact location, when it started, and whether it's getting worse. Then triage properly.

One rule above the whole table: for fire, smoke, gas smell, a carbon monoxide alarm, or any active danger, the tenant calls emergency services first. Nobody waits on a spreadsheet.

The gap between "I texted my plumber" and an actual work order is where money leaks. A vague handoff produces phone tag, a failed first visit, and an invoice you didn't expect. The kit's vendor handoff template turns a log row into a message a vendor can act on in one read:

• Work order ID — the same Request ID as the log row, so the invoice that comes back matches the record you keep.
• Priority and issue — what's wrong, when it started, photos attached.
• Tenant availability and access notes — days and times that work, lockbox code, pets, parking, whether the tenant must be home. The single biggest cause of failed visits is missing access details.
• Tenant contact permission — whether the vendor may coordinate arrival with the tenant directly.
• Not-to-exceed amount — "up to $300; call or text before exceeding." One line, and the surprise-invoice conversation never happens.
• Confirmation ask — the message ends by asking the vendor to confirm they'll take the job and give an arrival window. No confirmation logged means the job isn't actually assigned.
• Closeout requirements — what you need back: diagnosis, completion photo, invoice with the work order ID on it.

Send it, then record the vendor's reply in the log: Vendor confirmed, Vendor arrival/window. The template ships with a filled example so you can see what a complete handoff reads like before you write your first one.

Here's the part where most pages like this pivot to selling you software. The honest version:

A spreadsheet is enough for a lot of self-managing landlords. If you run a handful of units, requests arrive at a pace one person can handle, and you have the discipline to log things when they happen, this workbook plus the checklist covers intake, triage, vendor handoff, tenant updates, and history. It's free, there's nothing to adopt, your tenants don't install anything, and you own the data.

Where it breaks is not unit count — it's discipline at volume. Every request still has to be retyped from a text or a voicemail into a row. The Next follow-up date column only works if you're the kind of person who checks it. Nothing reminds you a vendor never confirmed. Tenants still text "any update?" because the log is yours, not theirs. And after-hours triage still happens on your phone, from memory, at 11:47pm. Full property-management platforms solve this, but they bundle it with rent collection, accounting, and tenant portals — a lot of software when maintenance is the only part that hurts.

What I'm building. I'm Denis. I build software; I'm not a landlord. This template comes out of reading how landlords describe handling repair requests in forums and community threads, and the same pattern keeps coming up: the tools are either a manual spreadsheet or a full platform, with nothing in between. So I'm building a maintenance-only triage inbox — requests come in by the text and email channels tenants already use, get logged and triaged automatically, and the vendor handoff and tenant updates happen from one place. It doesn't exist yet; I'm validating whether it should. If the "where it breaks" list above sounds like your week, see what I'm building and join the waitlist — and if you tell me how you handle maintenance today, I read every reply.