Property Management Work-Order Updates: 4 Tenant Templates

A property-management work order needs more than an open date and a completed date. Between those points, the tenant needs to know who has the request, what happens next, and when another update is due. A clear status process also gives the landlord or property manager a written record of what was promised and done.

The Four Statuses That Cover Most Work Orders

Many routine repairs can be tracked with four statuses. Tell the tenant which one applies and what happens next.

• Received: the request is logged and someone owns the next step.
• Scheduled: a visit or vendor appointment has a date or window.
• Waiting on Parts or Vendor: the work is real but blocked on something outside your control right now.
• Completed: the repair is done, with any follow-up clearly stated.

You do not need a complicated service desk to communicate well. A small set of shared statuses gives tenants and your team a common language, and pairing each status change with a short message matters most when it affects access, timing, or the tenant's next action.

A Copy-Ready Status Template for Each Work Order

A short status line and one plain-language sentence can cover the useful details. Tenants do not need your internal notes; they need to know where their request sits and what happens next. Below are four messages you can paste, edit, and send.

Received. “We received your request about the [problem] in unit [number]. It is now logged and assigned to [name or team], and we will follow up with the next step as soon as we have one.” This confirms the report landed and names who owns it.

Scheduled. “A visit is planned for [date] between [start] and [end]. Please let us know if you need to be home or if there is anything to clear beforehand, such as access under the sink.” Use a time window when a vendor has not confirmed an exact arrival time.

Waiting on Parts or Vendor. “The repair is moving forward, but we are waiting on [a part / the specialist / the vendor's schedule]. I will check in with you by [day] with an update, even if it is just to say there is no new timing yet.” Saying plainly that something is blocking the work keeps the tenant informed without inventing a completion date.

Completed. “The [repair] is done. Here is what was completed and anything worth watching going forward. If the same issue returns, let us know and we will take another look.” Closing with a clear way to report a recurrence ends the ticket cleanly instead of leaving the tenant guessing.

The Minimum Viable Work-Order Record

A work order does not need a complex database to be useful. Whether you track it in a spreadsheet, a notebook, or property-management software, a handful of fields is enough to answer the tenant's next question and hand the job to someone else without confusion. Write these down when the request comes in and update them as the status changes.

Work-order ID or short label. A reference you and the tenant can both point to, such as “Unit 3 — kitchen sink — Sep 18.” It does not need to be a formal ticket number, but it should be unique enough to avoid mixing up two open repairs.

Unit and tenant. Which unit the problem is in and who reported it. If a tenant texts about “the sink” and you manage multiple buildings, the unit number prevents a technician from showing up at the wrong door.

Reported problem in the tenant's words. Copy the original description rather than rewriting it. A tenant who says “water pooling under the dishwasher” gives you different information than “leaky sink,” and the difference matters when the technician is deciding what to bring.

Current status. One of the four statuses above. This is the field the tenant update is built from.

Owner. The person responsible for the next action, whether that is you, a handyman, or a vendor. If nobody is named, the request can sit unowned for days.

Last tenant update and date. What you last told the tenant and when. This prevents sending two contradictory updates or going silent long enough that the tenant files a second request.

Next action and due date. The concrete next step and when it should happen, such as “plumber site visit, Sep 20 afternoon” or “check on part delivery by Sep 23.” If the next action has no date, the work order is drifting.

Work completed and parts used. Filled in at completion. Include what was done, what was replaced, and any warranty or return-policy details for the parts, so a recurrence can be diagnosed without starting over.

Photos, when useful. A photo of the reported problem can help the technician prepare, and a completion photo can document what was done. Do not request or store images that expose unrelated personal information.

That is the whole record. Keep the fields current as the status moves so the next person can see what was promised, what is due, and who owns it.

Escalation and Next-Update Workflow

Statuses answer “where is this job right now.” An escalation workflow answers “what happens when it stalls.” Without one, a request that sits in Waiting on Parts for two weeks quietly becomes a tenant complaint. A simple cadence keeps repairs moving and gives the tenant a predictable rhythm of updates instead of silence.

The workflow below assumes a routine, non-emergency repair. Hazards and loss of essential services do not follow a routine cadence; use your emergency process and local requirements immediately.

1. Acknowledge receipt. Send the Received template promptly so the tenant knows the request is logged and who owns the next step.
2. Schedule or diagnose. If the fix is straightforward, schedule the visit and send the Scheduled template. If it needs diagnosis, tell the tenant when you expect to have a next step.
3. Name the next check-in. Every update should end with a specific date for the next contact, even when that contact may be “no new timing yet.”
4. Follow up when a check-in is missed. Contact the assigned person or vendor instead of waiting for the tenant to ask. Record what you learned and set the next date.
5. Escalate a stalled request based on urgency. If the vendor cannot give a workable date, consider a second vendor and tell the tenant what you are doing. Adjust the response to the repair, lease, and local requirements rather than using one deadline for every job.
6. Close cleanly. Send the Completed template, record what was done and what parts were used, attach useful completion photos, and tell the tenant how to report a recurrence.

This workflow is operational guidance, not a legal standard. Repair timelines and tenant notice requirements vary by lease and jurisdiction, so set check-ins that fit your obligations and the type of repair.

The discipline is not the calendar itself but the rule behind it: every open work order has a next check-in date, and every missed check-in triggers a call rather than another wait. That single habit prevents most of the silence that turns a routine repair into a dispute.

Keep the Work Order Moving Between Statuses

A few habits keep a repair on track from received to completed.

• Acknowledge promptly and repeat the key detail (unit, problem, any safety note) so the tenant can correct a misunderstanding early.
• State what you actually know rather than a completion time you cannot control; commit to the next check-in if a vendor has not confirmed a window.
• Share the appointment date, time window, and access instructions in writing before the technician arrives.
• Record the reported problem, inspection result, work done, parts needed, and any follow-up so the record answers the tenant's next question.
• When marking complete, tell the tenant what was done and how to report a recurrence.

This approach replaces the silence between a tenant reporting a problem and receiving the next useful update. It also leaves the next coordinator with the current status, the last promise made, and the next action due.

If someone else picks up the work order, the record should show the current status, the last tenant update, and the next action due.

See how Rentway keeps requests, messages, photos, and vendor follow-up together in maintenance tracking.

Frequently asked questions

How quickly should a landlord respond to a maintenance request?

The right response time depends on the severity of the issue, lease terms, and local requirements. For routine requests, acknowledge receipt the same day and tell the tenant when to expect the next update. Hazards and loss of essential services require an emergency response process.

What should a landlord include in a maintenance update?

Include the issue being addressed, the current status (received, scheduled, waiting on parts or vendor, completed), any appointment window or access requirement, and when the tenant should expect another update. Keep the message factual rather than promising a completion time that has not been confirmed.

What should a minimum work-order record contain?

A work-order ID or short label, unit and tenant, the reported problem in the tenant's words, current status, owner, last tenant update and date, next action and due date, work completed and parts used, and useful photos when appropriate. That is enough to answer the tenant's next question and hand the job off without confusion.

When should a landlord escalate a stalled maintenance request?

Escalate when the promised check-in passes without a useful update or the issue becomes more urgent. Contact the assigned person or vendor, consider a backup vendor when timing is unclear, and set the next update in writing. The repair, lease, and local requirements determine the response; one deadline does not fit every job.

Should a landlord tell a tenant when a part is on order?

Yes. Say that the part has been ordered, name the expected next step, and state when you will check in again. The tenant then has the current status in writing.

How should a landlord close a maintenance request?

Tell the tenant what was completed, note any follow-up or monitoring needed, and give a simple way to report a recurrence. Keep the repair notes, messages, and vendor details attached to the work order for future reference.