How to track maintenance for multiple rental properties

To track maintenance for multiple rental properties, you need to know on any morning which requests and jobs are open, who is waiting on whom and what each one will cost the owner. With one unit you can keep that in your head. With twenty units and five owners, a forgotten leak can turn into a ceiling stain and an invoice nobody approved.

This guide is for property managers who already have a way to take requests and now need to keep every job across every property in view. It covers what to record, how to set up a maintenance log that stays current, and the weekly routine that keeps jobs from slipping.

Why tracking matters more as you grow

Each new property adds tenants, pros and an owner with their own expectations. The number of open jobs grows, and so does the number of people asking about them. Owners want to know what was spent on their units. Tenants want to know when the plumber is coming. Pros want to know whether the extra work was approved.

When you can answer those questions in a minute, owners trust your reports and tenants stop chasing you. When every answer means scrolling through chats, your week goes into looking for information.

Why spreadsheets fall behind

Most managers start with a spreadsheet, and that's a good start. The trouble is that the work happens somewhere else. The tenant reports a leak on WhatsApp. The pro sends the estimate by email. The owner approves it on a call. Someone has to stop and type each step into the spreadsheet.

On a busy day nobody does. Rows stay on "waiting for estimate" after the job is done. Two people on the team keep their own copies. Photos and invoices live in a phone gallery and an inbox, not next to the row they belong to. After a few weeks, the sheet no longer matches what's happening, and the team stops trusting it.

If you're ready to leave the spreadsheet behind, our guide on switching from spreadsheets to property management software covers the move step by step.

How to track maintenance for multiple rental properties

1. Keep one list for every property

Use a single maintenance log for your whole portfolio, with one row per request and a column for the property. When the owner approves the work, the request becomes a job, and it keeps the same row and number. With one list you can sort by property, owner or status, and nobody on the team has to remember which file to open. If you keep a file per building, you can't see which jobs are stuck across all of them.

Give every row the same columns:

• Number (a simple running number) and date reported
• Property and unit, plus the owner
• What's wrong, in one short line ("Kitchen faucet leaking at the base")
• Reported by and how to reach them
• Urgency: act now, assess promptly or plan it
• Pro assigned
• Estimate amount and approved by, with the date
• Visit date
• Status (next step) and status changed on, the date it last moved
• Final cost, invoice received and paid date
• Link to photos and documents

2. Use a short set of statuses

A status should tell anyone on the team what happens next. Keep the list short and use the same words everywhere:

1. New: reported, not reviewed
2. Waiting for estimate
3. Waiting for approval: the estimate is with the owner
4. Scheduled: there's a date and a pro
5. Work done: the pro sent a photo of the finished work
6. Confirmed: someone has checked the result. In an occupied unit, ask the tenant. For a vacant unit, a common area or recurring work, you or someone on your team checks it. Note who checked and when
7. Paid: the invoice is paid and recorded

Add a "next action" column with a name and a date ("Ana, call the owner, Thu"). If that column is empty, nobody is working on the job.

3. Bring every request into the log

Whatever channel a request arrives through, it goes into the log the same day, with a number. Tell tenants where to report problems and what to include. Judge the urgency as soon as a request arrives: a gas smell, a burst pipe or no heat in winter gets handled first, following your emergency procedure and the rules where the property is, and logged right after. Everything else gets its row before anyone starts work, and its follow-up goes into the weekly review. The number then goes into every message about the request, so the pro, the tenant and the owner can all point to the same one.

Write down the approval rules for each owner next to their properties. When a job needs the owner's yes, the status says so, and the "status changed on" date shows how long it has been waiting. Our guide on maintenance approval limits covers what to agree on with each owner.

4. Keep recurring maintenance on its own schedule

Repairs that come from a request and maintenance you plan are different kinds of work. Keep a second tab with recurring tasks per property: furnace service, gutter cleaning, smoke alarm checks, water heater flushing. Each task needs a property, how often it repeats, the last date it was done and the next due date.

When a task comes due, open a job for it in the main log, so it goes through the same statuses as any repair. Our preventive maintenance checklist lists the tasks most rentals need and how often to do them.

5. Review open jobs every week

Pick a fixed time each week, sort the log by status and go through every open job. For each one, ask three questions:

• Is the status still true?
• Who has the next action, and by when?
• Has it been stuck longer than it should? The "status changed on" date tells you.

Follow up first on jobs waiting for an owner or a pro, because nobody on your side is pushing them. Close jobs that are done, and check that each closed job has its photo and invoice. With a team, do this review together, so everyone leaves with the same picture.

6. File the proof with the job

A job is closed only when its record is complete: the tenant's photos, the estimate, the approval, a photo of the finished work and the invoice. Save them in one folder per job, named with the property and the job number, and link the folder from the row. A year later, when the same pipe leaks again or a tenant moves out, you'll find the history in seconds.

7. Report to each owner from the log

Filter the log by owner at the end of each month. You get the list of jobs, what was approved, what was spent and what's still open. That's most of the maintenance section of your monthly report, and the owner sees the same numbers you see.

Common mistakes that make jobs disappear

• Several lists. One per team member, one per building, one in a notebook. Nobody knows which one has the latest status.
• Statuses nobody updates. Keep the log open where the team works, so changing a status takes seconds.
• Approvals only by phone. Write a short message after every call ("As agreed, you approved $350 for the water heater valve") and note it in the row. The amount is only an example.
• No date on the next step. "Waiting for the pro" with no date can wait forever.
• Closing a job on "work done". Checking the result and paying the invoice are steps of their own. Keep them apart so you can see what's still pending.

How RentalThread will make it easier

We're building RentalThread around this kind of tracking. Each repair will get its own shared thread with the request, the photos, the estimate, the approval, the finished work and the payment, and everyone involved will see the same status. Recurring maintenance will come with reminders, so planned tasks don't depend on someone checking a tab.

For managers, all owners and properties will be in one view, with approval limits per owner and monthly owner statements built from the same records. AI will draft updates and messages for you to review before they're sent. See what's planned for property managers.