Maintenance Request Workflow 2026 — From Ticket to Sign-Off

A maintenance ticket has two clocks running: the habitability clock (legal) and the satisfaction clock (renewal). Both start when the tenant hits submit. Below: the triage SLA, the vendor dispatch sequence, the tenant comms cadence, and the 20-step ticket lifecycle checklist that closes the loop.

A slow maintenance response is the single biggest predictor of non-renewal — bigger than rent increases, bigger than neighborhood issues. Industry surveys put the threshold around 48 hours: respond within that window and renewal probability holds; miss it and renewal drops 12-18%. On a $1,800/mo unit, a lost renewal costs you roughly $3,200 in turn costs plus 14-21 days of vacancy. This is the workflow that keeps that clock under control.

The two clocks you're racing

Habitability clock (legal): Most state habitability statutes give you 24 hours for emergencies (no heat in winter, no water, gas leak, sewage backup) and 7-30 days for non-emergencies. Miss either and the tenant has rent-withholding or repair-and-deduct remedies depending on state.

Satisfaction clock (commercial): Tenants expect acknowledgment in under 4 hours and a vendor on site within 48-72 hours for non-emergencies. They don't read your lease's "reasonable time" clause. They check Yelp and decide.

Your workflow has to serve both. The triage SLA below is built backwards from those two clocks.

Triage SLA by priority

Every ticket gets categorized within 1 business hour of submission. Categorization drives the timeline.

If you only set one rule, set this: every ticket gets a human acknowledgment within 4 hours during business hours and 30 minutes for P1 regardless of hour. Automation handles the rest, but the tenant needs to know a human is reading.

The 20-step ticket lifecycle

This is the standard operating procedure from submission to closure. Each step has an owner and a status code so nothing falls off.

Intake (steps 1-4)

• Tenant submits via portal, text, email, or phone — all routes funnel to the same ticket queue
• Auto-acknowledgment goes out instantly with ticket number and expected next contact time
• PM (or dispatcher) triages within 1 business hour: priority, category, billable-to (owner vs tenant)
• Ticket photographed if tenant didn't include images; tenant prompted via text for one if needed

Approval (steps 5-7)

• Estimate against owner's pre-authorization cap (typical: $300-500 for repairs, $0 for cosmetic)
• If above cap, owner notified with photos and estimate; 24-hour deemed-approval clause if PMA allows
• If below cap, dispatch immediately

Dispatch (steps 8-12)

• Vendor selected from trade matrix (primary + backup per trade)
• Work order sent to vendor with unit access instructions, gate code, and contact preferences
• Tenant notified of scheduled window (4-hour windows max, not "between 8 and 5")
• Vendor confirms within 2 hours or PM escalates to backup
• Day-of: tenant gets a "vendor en route" text 30 minutes before arrival

Execution (steps 13-16)

• Vendor completes work, photos taken before and after
• Vendor uploads invoice with itemized labor + materials within 48 hours
• PM reviews invoice against scope before posting to owner ledger
• Follow-up text to tenant within 24 hours: "Did this resolve the issue?"

Closure (steps 17-20)

• Tenant confirmation (yes/no) logged in ticket
• If no, ticket reopens and skips back to step 8 with original vendor
• Ticket closed with resolution code, total cost, and time-to-resolve
• Metrics rolled up weekly: avg resolution time by priority, % resolved on first visit, vendor performance

Vendor dispatch rules

A vendor list of "the plumber I used last time" doesn't survive a P1 ticket on a Saturday night.

Build the trade matrix. Per trade — plumbing, electrical, HVAC, appliance, locksmith, drywall, painter, cleaner — keep two vendors: primary and backup. Backup gets called when primary doesn't confirm within 2 hours.

Negotiate trip rates. Most vendors charge a $75-150 trip fee per visit. Negotiate a flat rate for tickets under 1 hour to avoid the trip fee stacking on small jobs.

Set a 30-day insurance refresh. Vendor COIs expire silently. A vendor working without current insurance is your liability problem. Auto-reminder 14 days before expiration.

Track first-visit resolution rate. If a vendor's first-visit fix rate is under 80%, you have a scoping problem (your dispatch lacks detail) or a vendor problem (they're undertraining). Either way, look at it monthly.

For the broader vendor management framework — onboarding, payment, 1099 prep — see our vendor management guide.

Tenant communication cadence

The single biggest reason tenants escalate to bad reviews isn't slow repair — it's silence. The cadence below keeps them informed without overwhelming them.

Tenants who get this cadence rate maintenance experience 30-40% higher in satisfaction surveys than tenants who get one "we'll send someone" message.

Common mistakes

1. No priority categorization. Treating every ticket as urgent burns out vendors and trains tenants that nothing is actually urgent. Categorize on intake.
2. Approving work without photos. Owners burned by phantom repairs stop trusting your work orders. Every approval request includes at least one photo of the issue.
3. Letting vendors invoice without itemization. "Plumbing repair — $480" is not an invoice. Itemized labor hours, parts, and materials, or it doesn't get paid.
4. Closing tickets without tenant confirmation. A ticket closed without the tenant saying "yes, fixed" reopens in 3 weeks at the worst possible time. Confirm before closing.
5. No vendor backup list. When your primary plumber is on vacation, P1 tickets sit. Backup vendor matrix is not optional.
6. Manual reminders to yourself. If the only thing keeping a ticket alive is your memory, it's going to fall through. Status changes drive notifications, not the calendar.

Tooling shortcuts

The workflow above runs at scale only with the right plumbing.

• Single intake queue. All channels (portal, text, email, phone) land in one ticket list. Multi-channel inboxes are how things get lost.
• Auto-categorization. Set rules: "no heat" tickets between Nov-Apr auto-prioritize P1; "leak" keywords auto-prioritize P2.
• Vendor portal. Vendors confirm, upload invoices, and close out via a portal — not email attachments you have to chase.
• Owner statement integration. Work order costs flow to the owner statement automatically; no manual re-entry on D+1 of month-end.
• Resolution metrics dashboard. Median time to first response, time to resolution, % first-visit fix — visible daily, not quarterly.

Built-in maintenance workflows with vendor dispatch, tenant comms, and owner billing — without bolt-ons — is something Proprietio handles natively for portfolios of mixed portfolios.

FAQ

What's a reasonable response time for a non-emergency on a weekend? Acknowledge within 4 hours regardless of day. Schedule the visit for Monday unless it's a P1 or P2. Tenants accept "we'll be there Monday at 10" — they don't accept silence until Monday at 10.

Who decides if a repair is owner-billable vs tenant-billable? Per the lease. Most leases assign tenant-caused damage (broken window from a thrown object, clogged drain from improper use, pet damage) to the tenant. Wear-and-tear and system failures are owner-billable. Document the cause with photos and vendor diagnosis before assigning the bill.

How do I handle a tenant who submits duplicate tickets for the same issue? Merge them in your system, not the conversation. Reply on the original ticket: "I've merged your follow-up into ticket #1234. Status is [X]." Don't tell them to stop submitting — they're submitting because they're worried.

What if a vendor no-shows on a P1 emergency? Backup vendor gets called immediately. After action, the no-show vendor gets a strike. Three strikes in 12 months and they're off the matrix. Document each strike with date and ticket number.

---

Run mixed portfolios? Try Proprietio free for 15 days — residential, condo, and commercial in one workspace, no per-door fees. proprietio.com