How to document tenant repair requests.
A practical maintenance documentation workflow for small landlords: tenant reports, photos, access attempts, vendor visits, invoices, repair notes, and PDF-ready rental property records.
Most landlord maintenance documentation breaks down because the record is scattered before anyone realizes it matters. The tenant repair request is in one text thread. Photos are in a camera roll. The vendor quote is in email. The access attempt was discussed on the phone. The repair invoice lives in accounting software. Months later, everyone is trying to rebuild a timeline from fragments.
A useful rental property maintenance record does not need fancy language. It needs sequence, timestamps, files, and plain-English context. The goal is to make the issue easy to review later: what was reported, what happened next, what was attached, and what the final status was.
Start with the tenant repair request
Capture the date received, the unit, the issue category, the tenant's description, and any photos or videos the tenant provides. If the request arrived by text, email, phone, or portal, record where it came from so the maintenance timeline has a clear starting point.
Add photos before the repair changes the scene
Photos help show the condition at the time the issue was reported. Keep the original files elsewhere too, then attach the useful photos to the issue record with captions such as ceiling leak, damaged floor, broken appliance, mold concern, or access path.
Record your response and access attempts
A landlord maintenance record should show the follow-up: inspection notes, messages to the tenant, requested access windows, access granted, access denied, no-show appointments, and any emergency steps taken to prevent further damage.
Log vendors, repair decisions, and invoices
Vendor visits, estimates, repair findings, invoices, and completion photos should stay attached to the same issue. This keeps the repair history connected instead of split across email attachments, camera rolls, and bookkeeping notes.
Close the issue with a plain-English summary
When the issue is resolved or paused, summarize the final status: what was repaired, what remains open, who confirmed completion, and which records support that status. The summary should help someone else understand the record without reading every message.
Export and check the PDF before relying on it
A PDF maintenance record is only useful if it contains the correct events and attachments. Before sending it to an owner, insurer, mediator, attorney, or tenant, review the export and keep an independent copy outside any single software tool.
What to keep in a maintenance record.
- Property, unit, issue title, and issue category
- Tenant repair request text and submission date
- Photos, files, captions, and original filenames
- Landlord response notes and inspection results
- Access requests, access granted, access denied, and missed appointments
- Vendor scheduled dates, visit notes, estimates, and invoices
- Repair completed notes, status changes, and follow-up reminders
- Exported PDF record packets reviewed before use
Keep independent backups.
No online tool should be your only archive. Keep independent copies of original photos, text messages, emails, notices, invoices, and exported PDFs outside IssueLedger. If a repair becomes urgent, use your normal emergency process first and document after people and property are safe.
One timeline per maintenance issue.
IssueLedger helps small landlords turn tenant reports, landlord notes, photos, repair logs, and vendor files into a timestamped issue record that can be searched, shared, and exported as a PDF.