Maintenance requests that arrive at midnight, by message

A tenant sends a photo at 23:40: water under the kitchen sink. You reply that you will call the plumber in the morning. You do. The plumber goes on Thursday, fixes it, and sends an invoice by email a fortnight later. You pay it.

Now answer the owner's question in December: what did that flat cost me this year?

The rent is in one place. The repair is a conversation in a messaging app, a call log, and an invoice in an inbox. Nothing connects them, so the honest answer is "give me an afternoon".

Why maintenance is the hard part

Rent is predictable: a fixed amount, on a fixed day, from a known person. Maintenance is none of those. It arrives at random, through whatever channel the tenant uses, involves a third party, and is paid late. That makes it the part of property management most likely to live outside the records.

The consequences are small and constant:

• The same repair happens twice, because nobody remembers the boiler was looked at in March.
• Owners are surprised by costs, because they hear about a repair when the invoice arrives, not when the problem did.
• A property looks more profitable than it is, because the rent is recorded and the repairs are not.
• Tenants chase you, because "did the plumber come?" has no answer anyone but you can give.

A ticket, tied to a property, tied to an expense

The fix is not complicated in principle. Every repair becomes a ticket on the property it belongs to. The ticket has a status — reported, scheduled, done — and, when the invoice arrives, the expense is attached to the same ticket.

That is how the property management system we built handles it: maintenance tickets are tied to expenses, and both sit on the property alongside its leases and rent. When the owner asks what the flat cost this year, the answer is a screen, not an afternoon. The same records feed occupancy and revenue numbers per property.

Property management firmRents, arrears and maintenance for a rental portfolio

What you can do without a system

If you manage a few properties, you can get most of the benefit with habits:

1. One folder per property, and every invoice goes in the folder of the property it was for, the day it arrives.
2. A simple repairs log per property: date reported, what it was, who fixed it, date done, cost. A spreadsheet is fine.
3. Tell owners when a repair is reported, not when it is paid. A one-line message saves a difficult conversation later.
4. Ask tenants to report through one channel. It will not always happen, but a stated channel makes it the normal one.

When the habits stop being enough

Habits break when there is more than one person handling repairs, more than a couple of dozen properties, or owners who expect a regular statement. At that point the log and the folders are three places to keep in step, and they drift.

If that is where you are, tell us how repairs reach you today — the messy version, including the chat screenshots. That is usually where the design starts.