Anyone actually solved the multi-unit tracking chaos?

Question

Talked to a landlord a while back who described managing five units as a full time archaeology job. Digging through old texts and spreadsheets just to figure out what happened with a tenant three months ago.

That stuck with me. Most people don't lose money on rent. They lose it on the stuff that falls through the cracks because nothing's actually tracked in one place.

I build systems for exactly this. Not templates, something built around how a specific portfolio actually runs. Curious how the multi unit owners here are handling it right now. Anyone found something that actually works, or is it still the group chat and Excel life for most of you.

Pratik Poddar · Answer

+1 to Igor's "one note per unit, date plus what happened." If you're on AppFolio or Buildium, both already have notes on tenant and unit records, so make those the shared record your team can see. The gap people describe is quick personal context ("gate code 4411", "prefers text") that you want in front of you the second a record opens. I built a small Chrome extension, UnitPilot, for that: sticky notes that reappear on each AppFolio or Buildium record and are searchable with Ctrl+K. Caveat: they live in your own browser, so they're personal notes, not shared team notes.

Matthew Tregoning · Answer

I’d test the export before committing to any system. Pick one unit and try to pull its notes, photos, invoices, and open items into something another person can actually use. If changing software means losing the history or manually downloading hundreds of attachments, you’ve just moved the archaeology problem somewhere else.

Leo Stein · Answer

For a multi-unit portfolio, pick the market where you can actually staff operations—not just the prettier comps. A spreadsheet or PM platform can organize the data, but the ongoing risk is maintenance and vacancy without a local chain of custody. Before you add another market, ask who unlocks for repairs at 7pm, how invoices get approved, and where the unit-level record lives. Those answers matter more than which MLS looks friendlier this week.

Araba Ayomide · Answer

The 5 doors line is the most useful number I've heard on this. Most people can't tell you where the wall is, they just describe hitting it after the fact.

Curious what your setup actually is once you cross that line. Still the running log, or did something end up replacing it?

Igor Ganapolsky · Answer

the archaeology thing hits way earlier than most people think. i had a situation where i couldn't remember if i'd already credited a tenant for a repair they said they handled, and it took me two hours of digging through texts to figure it out. that's not a software problem, that's a "everything lives in my head" problem.

honestly the tracking chaos isn't really about the tracking. it's about the decisions you make wrong because you had incomplete info. you think the tenant's behind on rent but they paid cash and you forgot to log it. you think the repair wasn't done but it was, you just never got the confirmation. the spreadsheet doesn't save you there, the habit does.

what actually worked for me was dead simple — one note per unit, just date and what happened. no fancy categories, no color coding. just a running log i could scroll through in thirty seconds when something came up. the landlords who struggle aren't the ones without software, they're the ones who think they'll remember.

and to answer your question — it definitely hits at 5 doors. i've seen people with 3 units get tangled up because they treated each property like a separate thing instead of a portfolio. once you're juggling multiple tenants and multiple vendors, you need one place that tells you what's going on without you having to reconstruct it from memory.

Mark Updegraff · Answer

I think the need starts earlier than most people realize, but the reason changes as you scale.

At 5-10 doors, you're building the system mostly so you don't have to rely on your own memory. At a few hundred units, you're building it so you don't have to rely on any one person's memory.

We manage a few hundred units and that's where I've seen the real difference. A maintenance issue may touch the tenant, property manager, maintenance staff, an outside vendor, accounting and eventually the owner. If the process only works because one person knows what's going on, you don't really have a process.

I agree with the completed vs. closed distinction too. "Vendor says it's fixed" and "we've verified the problem is resolved, documentation is in, invoice is accounted for and there's no further action" are two very different things.

The software matters, but I've become much more interested in whether the workflow makes ownership and the next action obvious. Who owns this right now? What has to happen next? How do we know it actually happened?

If those answers aren't obvious, things eventually fall through the cracks regardless of whether you're using a spreadsheet or a $500/month PM platform.

So yes, I'd start building the discipline at 5-10 doors. You'll probably think it's overkill then. You'll be very happy you did when it's 50.

Araba Ayomide · Answer

This thread is honestly better than most property management courses. Vannessa's workflow point is the piece most systems miss, completed and closed being different statuses is exactly right, and it's usually where things quietly fall apart. A repair gets marked done because the vendor said so, but nobody confirmed the tenant actually agrees.

To answer directly: yes, I've built verification into a system before, not just as a record tool. The way it worked was close to what you described, status moves from completed to verified only when photo proof and tenant confirmation are both attached, otherwise it sits in a "needs verification" queue so it can't quietly disappear. Mike's point about legal-weight records living in their own lane rather than buried in general notes is the same principle applied to compliance, some data needs to be structurally separated because of what it has to prove later, not just categorized for tidiness.

Curious how deep people here actually want that kind of structure. Is it mostly the multi-unit owners feeling this, or does it hit even at 5 to 10 doors?

Drew Sygit · Answer

There are soooo many solutions already out there to address this issue.

Mike Fisher · Answer

Five units being an archaeology job is the right way to put it. The thing I'd add after doing this a long time is that unit level tracking isn't really about neatness. It's about the handful of moments the record actually gets tested, and if you build for those the day to day sorts itself out.

The moments I mean: a security deposit itemization when a tenant moves out, an eviction where you have to show a clean ledger, an insurance claim, an inspection, or handing the portfolio to someone else. Every one of those asks the same question, which is "show me everything that happened at 2B," and it usually asks it months or years after the fact. If you can export that on demand you're fine. If it lives in a group chat you lose the deposit case or the claim.

So the way I keep it: one running log per unit, append only, one line per event, date plus what happened plus who plus dollars plus a link to the photo or invoice. It takes thirty seconds like Aaron said, and it doubles as the handoff doc, so the disaster continuity file and the new manager file end up being the same file. Vannessa's point about verified vs closed is real too. A repair isn't done until the photo and the tenant confirmation are attached to that unit's line.

One thing specific to my market that I'd pull out rather than lump into general notes: the records that carry legal weight. In Illinois that's the per unit security deposit accounting, the smoke and CO detector test dates, and the dates and method you served any notice. Those are the ones a judge or a code inspector asks for by name, so you want them in their own lane, never buried, so a deposit or a habitability question doesn't turn into archaeology. The software Josh listed will hold all of it, but the tool is the easy part. The discipline that makes any of them work is funneling every tenant and vendor interaction back into one channel so the record assembles itself instead of you rebuilding it from old texts.

I run MF CashFlow Property Management (M Property Group LLC) in the Chicago south and southwest suburbs and have invested in the area since 1991, so most of what I track is shaped by what I've had to prove later. Happy to compare notes on what a unit level file should actually contain.

Anyone actually solved the multi-unit tracking chaos?

14 Replies