How to manage maintenance across multiple properties

One building runs on presence. You drive by. You know the boiler's moods. You know which tenant exaggerates, and which one never calls until the ceiling is coming down. Repairs get handled because you see, hear, or remember everything yourself. It works, genuinely.

Then you add buildings. The same method turns into the problem. You can't drive by five properties. The boiler knowledge doesn't transfer. And every repair now routes through one fragile hub: your phone. Tenant texts you. You text the plumber. Plumber asks a question. You ask the tenant. Tenant answers. You relay it back. Five messages of pure forwarding per job, times every job, times every building. Somewhere in there a message slips. A repair sits for two weeks. You find out from an angry call. Nothing broke except the method. Presence and memory don't scale past the first property.

What replaces them is a small set of principles. Managers land on these on their own, because they're the only shapes that survive at portfolio size.

1. One intake channel, not five text threads

At one building, requests come in by text, call, and hallway ambush. You survive it. Across a portfolio it guarantees losses. The request that came in during another building's crisis is the one that vanishes. The fix is one front door for every request, at every building. Tenants get one obvious way to report a problem. It has to be easier than texting you, or they'll keep texting you. In RQ200 that's a QR code on the building. The tenant scans it and reports the issue with photos in about thirty seconds. No app, no login. Requests from other sources file themselves into the same queue, including AppFolio maintenance requests if your listings and books live there. Everything lands in one place, stamped with its building and unit. Not in whichever pocket you were carrying that day.

2. Per-job records, not conversations

A conversation is sorted by time. Work is sorted by job. The moment two repairs share a text thread, the details start to blur: which faucet quote was this? Which unit's keys? A portfolio needs every piece of work to be its own record. This job, at this unit, in this building. Its own photos, costs, status, and history. That's what lets you answer "what's happening at Maple Street?" in ten seconds. It's what lets you hand the work off later, when you make your first hire and need someone else to see state without asking you. And it's the only structure that leaves proof the work happened once it's done.

3. Contractors who self-coordinate while you direct and approve

Most of the phone-hub traffic is scheduling. The contractor and the tenant negotiate a visit through you, two hops at a time. Cut yourself out of that loop. Give the contractor the job with the tenant's contact attached. Let them arrange the visit directly. They're both adults with phones. Your role moves up a level. You assign the job, watch the photo updates come in, and approve or send back the finished work. In RQ200 that's the built-in shape of a job. It carries the unit and tenant contact. The contractor acknowledges it, works it with photo and video updates, and submits it for your review. You direct and approve from wherever you are, instead of being the switchboard.

4. Recurring work that schedules itself

At one building you remember the gutter cleaning. At five, "remember" is a strategy with a 100% eventual failure rate. The misses cost real money, because recurring work is preventive. The skipped boiler service is next winter's emergency call. Enter every recurring item once: filter changes, gutter runs, common-area walkthroughs, seasonal inspections. Then it should generate itself on schedule, assigned to the right contractor, with no one summoning it from memory. In RQ200, recurring tasks respawn on their cycle. Open work that sits too long escalates in priority on its own. The thing nobody's touched in three weeks raises its own hand, instead of waiting for you to notice.

5. A view of the whole board

The last thing presence gave you was awareness. You saw the building, so you knew. Across a portfolio you have to rebuild that on purpose: one view that shows every property and where the open work piles up. RQ200's version is a map, with every building color-coded by the state of its open work. Next to it, the numbers that tell you how the operation runs: how long jobs take to close, what's aging, how much completed work carries photo proof. The point is to see the cluster forming across town before the phone rings, not after. That's the difference between managing a portfolio and being managed by it.

The through-line

Every one of these principles is the same move. Take something that lived in your presence, your memory, or your phone. Give it a structure that works without you standing there. One front door for requests. One record per job. Contractors who set up their own visits while you keep the decisions. Recurring work on rails. One view of everything. That's what RQ200 is. Not software bolted onto the old method, but the system for this exact stage: more buildings than you can drive past, run by fewer people than it seems to need.