Most tenant maintenance requests never touch a portal or a form. They arrive as texts: “hey, the bathroom sink is dripping again,” sent at 9:40 pm, sandwiched between a group chat and a food delivery update. You reply “thanks, I’ll take a look,” and both of you feel like something happened. Two weeks later the tenant texts, “any update on the sink?” — and you realize nothing did. If you own one to twenty units, you don’t need work-order software built for a 400-door management company. You need a small, repeatable system that turns each text into a tracked repair. Here is one that works whether you run it in a notes app, a spreadsheet, or a tool built for the job.
Answering a text is not tracking a repair
A reply closes the social loop — the tenant knows you saw the message. It does nothing to close the repair loop. The repair loop has four parts: someone owns the issue; there is a defined next action; there is a date when that action happens (or gets chased); and the fix is confirmed with the tenant before the issue is closed.
A friendly text covers none of these. That’s why the failure mode is so common it has a shape: request → warm reply → silence → tenant re-asks → apology → rushed fix. The tenant experiences it as being ignored, even though you answered within minutes. Answering was never the problem. Owning was.
The minimum record: four fields
You can track maintenance on an index card if the card has these four things:
- Property/unit. “Unit 3B” or “the Maple St house” — not just the tenant’s name. When a plumber asks “which unit?”, “Jess” is not an answer.
- Issue. One line, specific enough to distinguish it from every other issue. “Bathroom sink drips from cold handle,” not “sink.”
- Date reported. The day the first message arrived. This anchors everything else: how long the issue has been open and whether your follow-through is slipping.
- Next action. The most useful field and the one everyone skips. Not the goal (“fix sink”) but the next physical step: “text plumber for a Thursday slot,” “waiting on tenant photo,” “confirm the part arrived.”
- Add an owner (you, a vendor, or the tenant if you’re waiting on them) and a follow-up date, and you now record everything a professional work-order system tracks that actually matters at your scale.
One issue, one thread
The most damaging habit in text-based maintenance is letting a single issue scatter: the first report by SMS, a photo by email, a “when can someone come by?” tacked onto an unrelated conversation, and one phone call nobody wrote down.
Scattered updates force you to reconstruct history from screenshots and memory — usually at the worst moment, standing in the unit with a contractor. The fix is a rule, not an app: every update lives with the original issue.
Run manually, the rule looks like this: reply about an issue only in the chain where it was reported. When a tenant raises a second issue mid-thread, split it: “Logging the dishwasher as a separate item so it doesn’t get lost.” When something arrives by phone, write a one-line summary into the thread or your log immediately: “Called 6/2 — drip is now a steady stream.”
This is also where purpose-built tools earn their keep. Tenvo, for example, turns each incoming tenant text or email into its own ticket and attaches every later reply to it, so “the sink thread” is one thing you can scroll rather than an archaeology project across three apps. But even with no software at all, one-issue-one-thread will spare you most of the reconstruction pain.
Acknowledge fast — without promising a timeline
Keep two messages separate that you’ll be tempted to merge. The receipt: “Got it, thanks — I’ve logged this and will update you by tomorrow evening.” Send this fast, ideally within the hour. The plan: “Plumber is coming Thursday between 1 and 3.” Send this only once it’s true.
The receipt should never contain a diagnosis (“probably just the washer”) or a repair promise (“we’ll have it fixed this week”). You haven’t seen the problem yet. Commit only to the one thing you fully control: when you will next communicate. “I’ll update you by tomorrow evening” is a promise you can keep even if the plumber ghosts you.
That ten-second acknowledgment prevents the double-text, the phone call, and the slow erosion of trust that silence causes — and it costs you nothing when the repair itself takes longer than anyone wants.
Review open issues weekly — a digest, not an audit
Tracking systems don’t fail at intake. They fail at review: requests get logged, and then nobody looks at the log.
Put a ten-minute review on your calendar once a week — daily if you’re above ten units — and scan five questions:
- What is still open?
- What has no next action or no owner?
- Which promised update is now late?
- Which scheduled visit needs a confirmation text today?
- Which “completed” repair was never confirmed with the tenant?
A digest beats an audit trail — with one honest caveat
A short digest — every open thread with its status and next action on one screen — is the single highest-leverage habit in small-portfolio maintenance. A spreadsheet filtered to “status is not closed” is a perfectly good digest. What matters is that it exists and that you look at it on a schedule, not when something breaks loudly enough to remind you.
One honest caveat: an operational log like this is for running your rentals, not for winning a court case. Jurisdictions have their own rules about written notice, entry notice, and repair timelines, and what counts as adequate documentation varies. Keep your records — but don’t treat a digest as a legal audit trail. If a dispute is brewing, ask a local landlord attorney what your state actually requires.
The one-minute test
Whatever you build, the test is the same: when a tenant texts “any update?”, can you answer in under a minute, from the record, without scrolling your camera roll? If yes, your system works. If no, tighten the weakest step — usually the missing next action or the skipped weekly review.
And if most of your requests already arrive by text and you’d rather the threading, the instant receipt, and the daily review list happened on their own — with you still approving every message before it goes out — that’s the exact job Tenvo does: $29/month, built for landlords with 1–20 units, nothing for your tenants to install or sign up for.