Your maintenance spreadsheet is fine until it isn't

Try this before you change anything. Open your spreadsheet and answer three questions about one unit, out loud, in under two minutes: what has broken there in the last two years, what did it cost, and where are the photos.

If you can, stop reading. Your spreadsheet works. Most of what follows is about the point where that stops being true, and it arrives later than software vendors like to admit.

What a spreadsheet is genuinely good at

It is free. You already know how to use it. It totals a column better than most software does, it filters and sorts however you want, and it never sends you an email about a feature update.

For one to three units with a stable tenant and one or two vendors, a spreadsheet with date, unit, problem, vendor, cost, and status is a complete maintenance system. Anybody who tells you otherwise is selling something.

A reasonable version has one row per job and these columns: date reported, unit, description, vendor, date scheduled, date completed, cost, repair or improvement, and a link to the invoice. People leave that last column out, and it is the column that earns its keep later, when the question stops being what happened and becomes what proves it.

Failure one: the record is in four places

The spreadsheet holds the row. The photos are in your camera roll. The tenant’s report is in a text thread. The invoice is in email, or in a drawer.

Nothing is wrong with any of those individually. What breaks is assembly. Reconstructing one repair means opening four applications and knowing roughly when it happened, and the whole reason you want the record is for the moment when somebody else is asking and you do not have an afternoon.

This is usually the first failure people hit, and it does not depend on how many units you own. It depends on how long ago the repair was.

Failure two: it does not do anything

A spreadsheet is a record of what you did. It cannot send the tenant an acknowledgment, offer the vendor three time windows, remind you that the furnace service is due, or tell you that a request has been open for eleven days.

So the coordination stays in your head, and the spreadsheet becomes the place you write down what your head already did. That is a real limit, not a small one, because the coordination is the part that takes the time. Getting out of the middle is mostly a description of work a spreadsheet cannot do.

Failure three: only one person can use it

Fine when the only person is you.

It stops being fine the moment you add a partner, a property manager, a family member covering a trip, or a bookkeeper. Version conflicts, a copy on somebody’s desktop, and no way to see who changed a row. A shared cloud sheet fixes some of that and creates a new problem, which is that everyone can now edit everything.

Failure four: nobody is looking at it

The subtle one. A spreadsheet is only as current as your discipline, and discipline is highest in month one.

The tell is the gap: rows through March, nothing in April and May, then a burst in June when you tried to catch up from memory. Look at your own sheet and see whether it has one. The data that matters most, dates and costs, is exactly the data that decays when it is entered late.

The honest test

You have outgrown it when two or more of these are true:

1. You cannot find a repair from last year in under two minutes.
2. Somebody other than you needs to see or update it.
3. You are re-typing the same information into a text, a spreadsheet, and an email.
4. A tenant has asked about a repair you had no record of.
5. Your accountant has asked for a per-unit or per-building expense breakdown you had to build by hand.

That last one has money attached. The IRS safe harbor election for small taxpayers is calculated per building, capped at the lesser of 2 percent of the building’s unadjusted basis or $10,000, so a total that only exists at the portfolio level does not answer the question. Capital improvements versus repairs has the rest of that.

What software has to earn

Do not switch for features. Switch for the four failures above, and only the ones you actually have.

What software should give you that a sheet cannot: intake the tenant can use from their phone with photos attached, a work order the vendor can act on without calling you, timestamps created automatically rather than remembered, the invoice attached to the job, and per-unit history that is there whether or not you kept up with data entry.

What it should not cost you: your ability to export. Ask before you sign up whether you can get a CSV of your maintenance history out. If the answer is unclear, that is the answer. LeaseRooster’s maintenance is built around the job record rather than a ticket queue, and our pricing starts free for a single unit.

If you are staying on the sheet

Three edits that fix most of failure one, today:

• Add an invoice link column and actually paste links into it
• Name photo files with the unit and date, in one folder per unit
• Add a “tenant told” column with a date, so you can see silence

That will not solve coordination or multi-user access. It will make your existing sheet a lot more useful in the situations where a maintenance record earns its keep, and it costs you an hour. If you want the cost side rather than the tracking side, the property management cost calculator is a reasonable place to sanity-check your numbers.

This is general information, not legal or tax advice. Rules change and local ordinances vary. Confirm current requirements with your city, county, or an attorney before you act, and talk to a CPA about your own return.