← All articles
🏑

How to Log and Track Repair Requests Across Units (2024)

πŸ”§ Maintenance & Repairs August 10, 2026 Β· 6 min read repair request tracking maintenance log rental property management landlord tools tenant maintenance requests multi-unit maintenance property maintenance records
TL;DR: Track every repair request with four fields β€” unit, date reported, category, and status β€” in one shared log rather than scattered texts and voicemails. A basic spreadsheet or a maintenance app works; the key is that nothing lives only in your memory or a single phone thread. Landlords who log requests within 24 hours resolve them roughly twice as fast as those who don't.

_Last reviewed: July 2026 Β· 7 min read_

You've got tenants texting one number, calling another, and leaving notes on the porch, and by the time you remember which unit had the leaky faucet, three weeks have passed. That gap is where small repairs turn into big bills and unhappy tenants turn into vacancies. Here's how to build a tracking system that actually holds up across multiple units.

Okoniq Property Hub logs each repair request with the unit, date, and status in one place so nothing gets lost between a text message and a follow-up call.

Why does every repair request need a written record?

Because memory and text threads fail exactly when you need them most, usually during a dispute or an inspection. If a tenant claims they reported a leak in March and you have no record, you're left arguing dates instead of facts. A written log with a timestamp protects both sides and gives you a paper trail if a repair delay ever becomes a legal issue, like a habitability claim.

This matters even more with slow-building problems. A slab leak under the floor or a chimney flashing leak often gets reported once, ignored as minor, then resurfaces months later as major water damage. Without a dated log entry, you have no way to prove when it was first flagged or what you did about it.

What fields should you track for each request?

At minimum, track five things: unit number, date reported, category, priority, and current status. Category matters because plumbing, electrical, and structural issues need different response windows and often different vendors. Priority separates a running toilet from a gas smell. Status should move through at least three stages β€” reported, scheduled, completed β€” with a completion date logged.

Some owners add a sixth field: estimated cost versus actual cost. Over a year, this tells you which units are costing more than others and whether a property is aging out of routine fixes into bigger capital repairs, the kind you'd see coming from patterns like foundation cracks or repeated gutter issues on the same building.

Spreadsheet or app β€” which one actually gets used?

The one you'll actually update consistently, which for most owner-operators managing 2 to 10 units is a shared spreadsheet at first and a dedicated app once volume grows past that.

| Spreadsheet | Maintenance App | |---|---| | Free, familiar, works offline | Usually $10-30/month, but syncs across devices | | No reminders β€” you have to check it | Sends alerts for open items past 48-72 hours | | Tenants can't submit requests directly | Tenants often can submit and photo-attach directly | | Fine under 5 units | Pays off past 8-10 units or multiple properties |

A spreadsheet fails quietly. Nobody notices a stale row until a tenant escalates. An app forces the issue by flagging anything sitting untouched for more than two or three days, which is usually the window before a minor issue (like a slow drain or a failing exhaust fan, similar to what's described in signs your bathroom fan isn't doing its job) turns into a bigger one.

How do you keep the log accurate across multiple units and multiple people?

You need one intake channel, even if you manage the property alone. If tenants can report issues by text, email, phone, and a portal, requests get duplicated or dropped between channels. Pick one primary method β€” a shared email address or an app form β€” and redirect everything else to it. Post it in the lease and on a fridge magnet if you have to.

Set a rule that every request gets logged the same day it's received, even if you can't act on it yet. A 5-minute entry beats a two-week memory gap. If you use contractors, require them to note the completion date and a one-line summary before you release payment; that closes the loop and gives you a record for tax or insurance purposes later.

What happens if you don't track requests at all?

Untracked requests tend to resurface as disputes, not simple complaints. A tenant who reported a roof leak in October and never heard back is far more likely to withhold rent or file a complaint than one who got a logged response, even an incomplete one, within 48 hours. The paper trail itself often defuses the conflict before it escalates, because it shows good faith even when a repair takes time.

There's also a compounding cost. Issues like a failing attic ventilation system or hidden crawlspace vapor barrier failure rarely show up as one clean request. They show up as three small, seemingly unrelated complaints over six months β€” a musty smell, a slightly damp corner, a spike in the heating bill. Only a log lets you connect those dots before the repair bill hits four figures.

FAQ

How long should I keep repair request records?

Keep them for at least the length of the tenancy plus 3 years, since most landlord-tenant disputes and small claims filings fall within that window in most states.

Should tenants be able to see the status of their own request?

Giving tenants visibility, even just a "received" and "scheduled" status, cuts follow-up calls significantly and reduces the chance they'll escalate to a formal complaint or withhold rent.

What's the fastest way to start if I have zero system right now?

Open a spreadsheet today with five columns β€” unit, date, category, priority, status β€” and log every open issue you can remember from the last 90 days before adding new ones going forward.

Do I need separate logs for each property or one combined log?

One combined log with a unit or property column is easier to maintain and lets you spot patterns, like which building keeps generating drainage or gutter complaints, that you'd miss with separate files.

How fast should I respond to a logged request?

Emergency issues like gas leaks or active flooding need same-day response; routine issues like a slow drain or a broken cabinet hinge should get a scheduled date within 3-5 business days.


This is educational information, not legal advice. Consult your state's landlord-tenant statutes or a local attorney about specific repair-response deadlines and habitability requirements in your area.

Get seasonal maintenance tips by email

Gutter-cleaning, filter-changing, before-it's-a-$3,000-problem guides. No schedule, no spam β€” unsubscribe anytime.

Prefer to dive in? Get started free β†’