Rental Property Maintenance Request Triage Template: Fields, Statuses, and Rules

The most useful rental property maintenance request triage template is a small operating record. It should answer what is happening, who owns it, what evidence exists, and when the next decision occurs. This structure works in a spreadsheet, database, or focused application.

Recommended record fields

| Field | Why it exists | Update point | |---|---|---| | Property and unit | Prevents the record from depending on memory or an inbox search | Capture the request | | Issue description | Prevents the record from depending on memory or an inbox search | Assess urgency and missing evidence | | Photo or video | Prevents the record from depending on memory or an inbox search | Assign an owner or vendor | | Safety or habitability signal | Prevents the record from depending on memory or an inbox search | Coordinate access and updates | | Access instructions | Prevents the record from depending on memory or an inbox search | Verify completion | | Priority | Prevents the record from depending on memory or an inbox search | Capture the request | | Assigned owner | Prevents the record from depending on memory or an inbox search | Assess urgency and missing evidence | | Tenant update | Prevents the record from depending on memory or an inbox search | Assign an owner or vendor | | Completion evidence | Prevents the record from depending on memory or an inbox search | Coordinate access and updates |

Suggested statuses

Use workflow statuses that describe reality: Capture The Request → Assess Urgency And Missing Evidence → Assign An Owner Or Vendor → Coordinate Access And Updates → Verify Completion. Add Waiting only when you also capture a waiting reason and review date. Add Closed—Not Completed when an item legitimately ends without the desired outcome.

Follow-up rules

• When the request mentions water, electrical, security, heat, or another safety signal, assign a next action and review date.
• When required photos or access details are missing, assign a next action and review date.
• When a vendor misses the scheduled window or reports a changed scope, assign a next action and review date.

Avoid reminders with no stop condition. A rule should say when it starts, who receives it, what counts as a response, and when a person should take over.

Example records

• A tenant texts a blurry photo of water under a sink after business hours
• A vendor cannot enter because access instructions were never confirmed
• A repair is marked complete but the tenant reports the symptom returned

For each example, write the current status, next action, owner, and supporting evidence. This makes the template testable with real work rather than idealized sample data.

Quality-control rules

• Local emergency and legal requirements remain outside the tool's automated judgment
• Urgency decisions require a reason and reviewer
• Tenants receive a clear next-update time
• Completion requires evidence, not only a status click

Before adding automation, run the template manually for a week. Remove ambiguous fields and confirm that two different users classify the same situation the same way. Consistency matters more than having a long form.

Next step

Explore the Maintenance Triage Board workflow concept and record whether this is painful enough to justify a focused tool.

For the adjacent workflow, see Unit Turnover Runbook.