Part of the Maintenance Documentation pillar guide. This article goes deeper on stage 1 (the request) and stage 2 (the triage) of the five-stage record in the pillar.
When you have five units, a tenant texts you about a leak. You text a plumber. The plumber goes. You forget which one of you paid until you check your card statement six weeks later.
This works. It works until somewhere around unit eleven or twelve.
Then a tenant says they reported a problem three weeks ago and you have no record of the conversation. A vendor invoices you for a job you can’t tie to a unit. A small claim shows up over a repair that “should have been done” and you can’t prove when you found out about it.
Ad-hoc isn’t a workflow. It’s the absence of a workflow that hasn’t broken yet.
What actually breaks at 10 units
People assume the failure point is scale, more units, more requests, more chaos. That’s not quite right. The failure point is concurrency.
At five units, you might have two open maintenance issues at any given moment. You can hold both in your head.
At ten units, you’ll have four to seven open issues at all times. You can’t hold seven open issues, four vendor relationships, and three pending tenant communications in your head, not while also doing leasing, accounting, and your day job.
The specific things that break:
- You lose track of who reported what. Three tenants reported issues in the same week and you can’t remember which one was waiting on the dishwasher and which one was waiting on the garage door.
- Vendors fall through the cracks. A plumber scheduled a Tuesday visit. He didn’t go. Nobody followed up because nobody had it on a list.
- You pay for work that may or may not have been done. An invoice arrives. You don’t remember authorizing it. You pay it anyway because the alternative is calling four people.
- Tenants don’t feel responded to. Even when you fix things fast, tenants don’t know you responded fast unless you tell them. Silence reads as inaction.
A workflow that scales doesn’t make these problems impossible. It makes them visible before they cost you money.
The five stages of a request worth designing around
Every maintenance request, regardless of complexity, moves through five stages:
- Intake. Tenant reports a problem.
- Triage. You decide what kind of problem it is, how urgent, who handles it.
- Assignment. A vendor (or you) gets the work.
- Execution. The work happens.
- Sign-off. Someone confirms it’s done, and at what cost.
In a broken workflow, these stages live in different places: intake in text messages, triage in your head, assignment in email, execution on a phone call, sign-off nowhere. The work isn’t bad, the record is.
In a working workflow, all five stages produce a written artifact tied to a single ticket or record number.
Intake: one channel, not five
The most common mistake is accepting maintenance requests through every channel a tenant might use, text, email, phone, in-person, paper note slipped under your door.
You feel responsive. You also have a maintenance system with no single source of truth.
Pick one primary intake channel and make it public:
- A web form is best for written documentation.
- A dedicated maintenance email address is acceptable.
- A maintenance phone line is fine if you log every call into a ticket within an hour.
Then enforce it gently. When a tenant texts you about a broken faucet, your reply is: “Got it, to make sure this gets tracked properly, can you also submit it at maintenance@property.com? I’ll log it now so you don’t have to wait.”
Within three months, tenants will use the right channel by default. Within six months, you have searchable records of every request you’ve ever received.
The intake itself should capture, at minimum:
- Tenant name and unit.
- Date and time of report.
- Description in the tenant’s own words.
- A photo if applicable.
- Whether they consider it an emergency.
- Permission to enter, with conditions.
That last one matters more than people realize. Half of scheduling delays come from confusion over when the tenant will be home and whether a vendor can let themselves in.
Triage: three tiers, written down
Every maintenance request belongs in one of three tiers. The tiers determine speed, who pays attention, and what gets bumped.
Tier 1, Emergency. Active leaks, no heat in winter, no AC in extreme heat, no hot water, electrical hazards, gas smell, security failures (broken locks, broken windows on ground floor), sewage backup. Response time: same day, often within two hours.
Tier 2, Urgent. Single appliance failure (refrigerator, stove, dishwasher), minor leaks, partial HVAC issues, water-heater performance, pest activity, recurring plumbing slowdowns. Response time: 24 to 72 hours.
Tier 3, Standard. Cosmetic damage, slow drains, cabinet hardware, screen repair, lightbulb replacement (if it’s your responsibility per the lease), squeaky doors, paint touch-ups. Response time: 7 to 14 days.
Write your tiers down. Share them with tenants on lease signing. The single biggest reason tenants get angry isn’t slow service, it’s mismatched expectations.
For the full breakdown of which problems belong where, see emergency versus non-emergency maintenance.
Assignment: named vendors per category, not “I’ll find someone”
A workflow that scales has a pre-named vendor for every common category, with a backup. You don’t go shopping for a plumber during an active leak.
Build the list before you need it:
- Plumbing. Primary and backup, both reachable on weekends.
- HVAC. Same.
- Electrical. Licensed only. The unlicensed handyman is for non-electrical work.
- Appliance repair. Often brand-specific. A Sub-Zero specialist isn’t the same person as a generic appliance shop.
- General handyman. For the long tail of small jobs.
- Pest control. Annual contract is often cheaper than per-visit.
- Locksmith. For lockouts and re-keys between tenancies.
- Cleaning. For turnovers and post-construction.
Each vendor should know upfront: how to invoice you, what your approval threshold is, how to document the work, and what to leave with the tenant. The first job with each vendor is the most important, that’s where you set expectations for the next fifty.
For the broader vendor relationship, vendor management for property managers covers contracts, insurance, and quality standards.
Approval thresholds
Decide in advance what a vendor can do without checking with you. Common thresholds:
- Under $200: vendor proceeds, no call needed.
- $200 to $750: vendor calls or texts before proceeding.
- Over $750: written approval required, often with a second estimate.
Without thresholds, every job becomes a phone call and your day disappears. With thresholds, vendors handle the small stuff at their own pace and you only get pulled in when it matters.
For deeper coverage, see owner approval thresholds.
Execution: status updates the tenant didn’t have to ask for
Tenants don’t expect instant repairs. They expect to know what’s happening.
The cheapest tenant-satisfaction win in property management is unprompted status updates. Send them at three moments:
- When you’ve received and triaged the request. “Got your request about the dishwasher. Tier 2, vendor scheduled to call you within 48 hours.”
- When the vendor is scheduled. “Smith Appliance will come Thursday between 9 AM and noon. They’ll call before they arrive.”
- When the work is complete. “Job marked complete. Let us know within 48 hours if anything isn’t right.”
Three messages. Tenants stop calling to “check in.” Renewals tick up.
Most property managers think their job is fixing things. It’s not. Their job is fixing things and being seen to fix things.
Sign-off: the step everyone skips
Here’s where 90% of maintenance workflows still fall apart, even at scale.
A vendor finishes the job. They text you “done” or send an invoice. You pay it. The tenant assumes it’s complete. The record ends there.
Three months later, the same problem recurs. Was it the same root cause? Did the vendor actually fix it the first time? Was the work warrantied?
You don’t know. Because there’s no completion record, no tenant sign-off, no before-and-after photos linked to the original ticket.
A maintenance workflow that scales requires three things at sign-off:
- Before and after photos from the vendor, linked to the ticket.
- A written description of what was actually done and what parts were used.
- Tenant acknowledgment that the work appears complete and the unit was left in acceptable condition.
The acknowledgment piece is what landlords resist. It feels formal. But it’s the only thing that prevents the “you never fixed it” conversation six weeks later. And it takes a tenant about thirty seconds to confirm.
This is exactly what a Maintenance Record PDF produces, request, vendor, work performed, photos, receipt, and tenant sign-off, in a single document at $5 per record.
The recordkeeping layer: where most software fails
Property management software covers leases, accounting, and sometimes online rent collection. Where most of it falls short is at the evidence layer for maintenance.
You can mark a work order “complete.” You can attach a vendor invoice. What you can’t easily produce is a single PDF that a tenant signed, that’s dated, that includes the photos, and that a judge or insurance adjuster could read.
That’s the gap DiscoveryMark fills. Not the dispatch, not the ticketing, those parts your existing tools handle. The signed, dated, court-ready document at the end.
For broader thinking on this layered approach, see property management software and paper trails.
When to add automation, and when not to
Landlords with under 20 units overspend on software. Landlords with over 50 units underspend on it.
Some practical thresholds:
- Under 10 units. A shared inbox, a spreadsheet, and a habit of capturing photos is enough. Don’t pay for software you don’t need.
- 10 to 50 units. A simple maintenance-ticketing tool (Latchel, Property Meld, AppFolio if you’re already on it) earns its cost back in saved time.
- 50 to 200 units. You need workflow automation, vendor scoring, and tenant-facing status pages. The cost of not having these is paid in tenant turnover.
- 200+ units. You’re running an operation. Custom dashboards, dedicated maintenance coordinator, on-call rotation.
What never scales: the founder/owner doing maintenance triage personally past 20 units. That’s the role to hire out first.
The closing thought
A maintenance workflow that scales is not about handling more requests. It’s about producing more evidence per request, evidence that protects you, satisfies the tenant, and survives the dispute that might come later.
Five stages: intake, triage, assignment, execution, sign-off. One source of truth per stage. One PDF at the end. The Maintenance Record flow gives you the last piece, the signed, dated, defensible document that turns a closed ticket into a closed case.
