Across landlord forums, renter forums, property-management reviews, and public complaint records, the same pattern repeats: repair requests get scattered across texts, portals, emails, photos, invoices, and memory. IssueLedger gives each issue a timeline before it turns into a fight.
The people who need this are not thinking about legal files. A landlord is thinking: “My tenant says I ignored this leak.” A tenant is thinking: “My landlord keeps forgetting what I sent.” A property manager is thinking: “The owner wants a repair history and it's scattered across three apps.” Nobody wakes up saying they need a legal record system. They wake up saying they need a clear record — that they handled it, that they reported it, that it happened when they said it did.
Maintenance documentation rarely fails in one dramatic moment. It fails slowly: the first request is a text, the photo stays in a camera roll, the vendor note is verbal, the invoice lands in email, and nobody knows which version of the story is complete.
IssueLedger is built around the boring parts that matter later: who reported what, when it was logged, what photos or files were attached, what follow-up happened, and what can be exported when a third party needs the facts.
It is built for small landlords managing a handful of units without a full property management system. For property managers who need a clean record to hand owners or attorneys when something goes sideways. For tenants who want their move-in condition documented and repair requests on record — not buried in an email thread they cannot find two years later.
Each card is a public-source example of a documentation failure mode. The source did not use, review, or endorse IssueLedger.
Pattern
Audience
“tenant info, leases, notices, repairs, logs of maintenance and tenant damage”
A landlord managing multiple rentals had too many categories of property records spread across folders and systems.
Property, unit, tenant, issue, photos, repair log, notices, and maintenance history in one structured record.
“Maintenance records and costs (what was fixed when, how much)”
A landlord wanted a better way to track repairs, inventory, dates, and costs across multiple rentals.
Repair date, issue type, vendor, cost, invoice, photos, and property/unit association.
“how do you keep routine maintenance from slipping?”
A landlord asked how other owners stay ahead of routine maintenance across multiple units.
Recurring maintenance records, due dates, vendor follow-ups, and unit-level completion history.
“Tenant submits a maintenance request like...”
A property manager described the problem of tenants submitting vague maintenance requests that lack enough context to dispatch the right vendor.
Structured intake: issue type, urgency, room/location, photos, notes, permission-to-enter, and follow-up status.
“how do you guys keep track of yearly maintenance tasks”
A landlord wanted a simple system for tracking recurring maintenance and repairs on a rental.
Yearly maintenance timeline, completed tasks, photos, service notes, and annual property summary.
“How do you track maintenance & capex for multiple rentals?”
A rental investor needed a clearer way to track maintenance and capital improvements across properties.
Issue history, cost category, property-level totals, vendor notes, and year-by-year maintenance export.
“they don't yet have maintenance and issue tracking”
A landlord using a property finance app still lacked maintenance and issue tracking.
A purpose-built maintenance records layer that can exist alongside accounting tools.
“Utilize Google forms as a landlord”
A landlord suggested Google Forms as a basic workaround for collecting maintenance requests.
Request intake plus photos, updates, repair history, cost tracking, and PDF export - not just a form submission.
“Getting too many maintenance requests from Tenant”
A landlord was dealing with frequent tenant maintenance requests and needed a way to separate real issues from noise.
Request frequency, issue categories, inspection notes, vendor outcomes, and resolution history.
“coordinating maintenance across multiple trades... is a constant time drain”
A landlord described the burden of coordinating plumbers, electricians, HVAC vendors, pest control, and remote work.
Vendor assignment, status, notes, access details, invoice records, and follow-up reminders per issue.
“please submit your maintenance request through your AppFolio portal”
A property manager described redirecting tenants away from email/text and into a formal portal.
A single documented intake path while preserving written records and tenant-visible status.
“digging through bank statements, Google Photos, email threads”
A renter described scrambling for records when landlord disputes arise.
A tenant-side record packet: photos, notes, payments, requests, timestamps, and exportable timeline.
“loose texts can still get messy”
A small landlord wanted to know how to track a repair from first text/email through completion.
Date reported, unit, issue, status, vendor, cost, follow-up date, and completion date.
“tenant disputes a charge and you have zero documentation”
A post described how tenant maintenance issues can become disputes when there is no record.
Charge basis, repair notes, tenant communication, photos, invoices, and decision history.
“app that 'loses' them constantly”
A tenant said their building's maintenance app lost requests and left issues unanswered.
Submission confirmation, status history, tenant-visible timeline, and an exportable record that a request was made.
“each property is its own project”
A property manager considered using Asana projects to organize maintenance requests by property.
A purpose-built property/unit/issue structure instead of forcing rental work into generic task software.
“tenants to call or text us”
A growing small property-management company had a maintenance-request system based on calls and texts.
Structured request intake, written record, unit assignment, status, and follow-up history.
“across email, texts, and portals”
A post described tenant email overload and repeated follow-ups because status was unclear.
Clear status updates, tenant-visible progress, internal notes, and fewer 'just checking in' messages.
“demanding seeing the invoice and all the repair documentation”
A landlord dealing with an AC repair dispute faced demands for repair records and invoices.
AC timeline, vendor visits, temporary mitigation, rent credit, invoice, photos, and tenant communications.
“too far away to drive over and inspect”
A long-distance landlord needed a record that a small winterization task had been completed.
Photo confirmation, due date, tenant note, landlord verification, and completion timestamp.
“requests for maintenance are constantly ignored”
A tenant said repair requests were ignored and the issue escalated into a mold concern.
Initial request, photos over time, landlord responses, escalation history, and habitability timeline.
“use the date stamps from the maintenance requests”
A tenant wanted to know whether request timestamps could prove how long a landlord ignored repairs.
A clean, date-stamped maintenance history suitable for review, negotiation, or attorney handoff.
“repair requests were ignored for days or weeks”
A tenant described repeated ignored or poorly handled repair requests and later deposit issues.
Chronological repair log, communication record, photos, move-out notes, and deposit-dispute records.
“a maintenance request was created for me”
A tenant said a portal generated a request in their name after a walkthrough, then weeks passed without clarity.
Who created the issue, why it was created, inspection notes, tenant acknowledgment, and status history.
“tenant ... did NOT report an allegedly 'long, slow leak'”
A dispute centered on whether a leak had been reported and whether maintenance would have noticed damage.
Leak photos, first report date, follow-up messages, maintenance visits, and damage progression.
“track the basics. Tenant info. Rents. Repairs. Move in dates.”
A landlord wanted basic software without a complicated full property-management platform.
Simple property/unit records focused on repairs, move-in condition, tenant notes, and maintenance records.
“documented conditions”
A public complaint involved disputed maintenance conditions and records submitted by the resident.
Records with photos, timestamps, condition notes, and a clean dispute packet.
“no documentation on file indicating that the key was missing”
A dispute turned on whether there was documentation that an issue existed at move-in or was ever reported.
Move-in checklist, missing-item report, photos, tenant acknowledgment, and follow-up record.
“no record of any work orders or maintenance requests”
A complaint response turned on whether maintenance requests were ever formally submitted or recorded.
Submission receipts, issue IDs, tenant-visible history, and exported request timeline.
“repeated emails, calls, and follow-ups”
A public review described maintenance requests ignored for long periods and follow-ups going unacknowledged.
Centralized request status, response log, escalation trail, and follow-up record.
“Months of repeated maintenance requests”
A public review described repeated unresolved issues including doors, hot water, and appliances.
Repeated request history, issue severity, photos, status changes, and management responses.
“Maintenance requests took forever to be addressed”
An employee review described unclear direction and slow maintenance response creating resident frustration.
Internal assignment, clear status, issue owner, tenant communication, and completion visibility.
The product is deliberately narrow: structure the issue record before everyone has to reconstruct it from scattered fragments.
Who reported the issue, when, where, and with what records.
Before, during, and after photos tied to the issue - not buried in a camera roll.
Vendor visits, landlord updates, tenant responses, and completion dates in order.
Amounts paid, who paid, vendor records, and supporting receipts.
A running maintenance record by property and unit.
A clean PDF when a tenant, landlord, owner, vendor, or attorney needs the facts.
For landlords who need a response record. For tenants who need a submission record. For property managers who need a timeline others can review.