Rental property maintenance log template.
A practical repair-log structure for landlords who want each tenant request, access attempt, vendor visit, invoice, photo set, and final status to live in one reviewable place.
A rental property maintenance log should be boring in the best way: easy to update, easy to scan, and complete enough that you do not need to search five apps to remember what happened. Most days, it is just an operating record. When a repair becomes expensive, delayed, contested, or hard to explain, it becomes the timeline everyone reaches for.
The mistake is treating the log as a thin spreadsheet with three columns: date, repair, cost. That is useful for bookkeeping, but it does not preserve the tenant report, access history, photos, vendor findings, invoices, status changes, or closeout note. A better log keeps the whole repair story attached to one issue, while the details are still fresh.
From repair list to usable record.
5/3 - sink leak - plumber - $218
Tenant report, photos, access window, landlord response, vendor finding, invoice, completion photo, cost, and final summary all attached to the same issue.
Issue identity
Give each repair a clear name, property, unit, category, and status. A title like Unit 2B kitchen sink leak is easier to review later than plumbing problem, especially if you manage more than one unit.
Example: Unit 2B - kitchen sink leak - active
Date reported and source
Record when the issue first reached you and where it came from: tenant link, text, email, phone call, walkthrough, owner note, or vendor follow-up.
Example: May 3, 2026 - tenant submission link
Tenant description and photos
Keep the tenant's plain-English description close to any submitted photos, videos, or access notes. The first report is often the cleanest starting point because nobody is reconstructing the story yet.
Example: Slow drain, water under cabinet, three photos attached
Landlord response and access attempts
Log your response, inspection notes, proposed access windows, access granted, access denied, missed appointments, and any emergency mitigation. This is where many repair records become fuzzy later.
Example: Offered May 4 morning or May 5 afternoon; tenant confirmed May 5
Vendor visits and findings
Track who was scheduled, who entered the unit, what they found, what they repaired, and whether there are follow-up parts, estimates, or owner approvals.
Example: ABC Plumbing cleared trap; recommended faucet supply-line replacement
Costs, invoices, and files
Attach estimates, invoices, receipts, completion photos, and cost notes to the same issue so repair history is not split between bookkeeping and maintenance records.
Example: $218 invoice attached; paid May 8
Final summary
Close each record with a short summary: what was fixed, what remains open, who confirmed completion, and which files support the conclusion. Your future self should not have to reread every note.
Example: Leak stopped, cabinet dried, tenant confirmed no water on May 10
Maintenance log fields to keep.
These columns work in a spreadsheet, a shared document, or an issue timeline. Start simple. The important part is that each repair has one home before photos, invoices, and messages spread across your tools.
| Field | What to enter | Example |
|---|---|---|
| Issue ID | A stable name or number for the repair | 2B-SINK-2026-05 |
| Property / unit | The exact rental and unit | 1639 Cornelia, Unit 2B |
| Date reported | When the issue first entered your record | May 3, 2026 |
| Reported by | Tenant, landlord, manager, owner, vendor | Tenant |
| Issue category | Plumbing, appliance, HVAC, pest, move-in condition | Plumbing |
| Status | New, scheduled, in progress, waiting, resolved | Waiting on vendor |
| Access notes | Access windows, no-shows, denials, lockbox notes | Tenant approved May 5, 1-4 PM |
| Photos / files | Photo count, invoice names, estimate names | 3 tenant photos, 1 invoice |
| Cost | Invoice, estimate, or running cost | $218.00 |
| Final summary | Plain-English closeout | Trap cleared; no leak after follow-up |
Unit 2B kitchen sink leak.
A good maintenance log does not need dramatic language. It needs sequence. Here is how an ordinary repair reads when the record is built as events instead of scattered notes.
Kitchen sink drains slowly and water is visible under the cabinet. Tenant attached three photos and asked for afternoon access.
Acknowledged report, asked tenant to stop using the sink if active leaking continues, and offered two access windows.
ABC Plumbing cleared trap and replaced a worn supply-line washer. Invoice and completion photo added to the issue.
Tenant confirmed cabinet remained dry. Issue marked resolved with invoice, before photos, and repair note attached.
When a spreadsheet stops being enough.
- The tenant submitted photos, but they live in a text thread.
- The vendor invoice is in email, not attached to the repair.
- There were multiple access attempts before the visit happened.
- The owner wants a clean explanation of a delayed repair.
- A repair turns into a habitability, deposit, insurance, or attorney question.
- You inherit old units and need to explain work you did not personally perform.
- You need to share a PDF record without forwarding months of messages.
Keep the original records too.
A maintenance log is an organizing layer, not your only archive. Keep independent copies of original photos, messages, notices, estimates, invoices, and exported PDFs. For urgent repairs, use your normal emergency process first and document after people and property are safe.
One repair log per issue.
IssueLedger helps landlords keep tenant reports, landlord notes, access attempts, photos, vendor visits, invoices, costs, and final summaries in a timestamped issue timeline that can be searched, shared, and exported as a PDF.