The Work Order Is Still Open
A delayed repair does not always destroy resident trust. Silence, uncertainty, and the need to repeatedly ask for updates often do.
A resident submits a maintenance request.
The automated confirmation arrives immediately: Your request has been received.
Then nothing happens—at least from the resident’s perspective.
No one explains whether the issue was reviewed. No appointment is scheduled. No technician calls. The portal continues showing the same status. Days pass, and the resident contacts the office.
The office checks with maintenance. Maintenance is waiting for a part. The part was ordered, but no one documented the expected delivery date or told the resident. Another employee promises to follow up.
Several days later, the resident asks again.
Inside the management company, the work order may be progressing. Someone inspected the problem, diagnosed the failure, requested approval, contacted a vendor, or ordered a replacement.
To the resident, the work order is simply still open.
That difference between internal activity and the resident’s visible experience is where trust begins to erode.
The repair and the experience are two separate things
Maintenance is not always predictable.
Parts become unavailable. Vendors cancel. Technicians encounter more extensive damage than expected. Specialized contractors have limited schedules. Emergencies interrupt routine work. Owners may need to approve an unexpected expense.
Not every repair can be completed quickly.
Communication usually can be.
A resident may be surprisingly understanding when told:
What the property knows
What has already been done
Why the repair is delayed
What will happen next
Who is responsible
When another update will be provided
Without that information, residents are left to interpret the delay themselves.
They may conclude that the request was forgotten, the office does not care, maintenance is disorganized, or no one intends to complete the work unless they continue applying pressure.
The longer the silence continues, the less charitable that interpretation becomes.
Maintenance is a retention issue
Work orders are not merely operational tasks. They are repeated tests of the resident-management relationship.
AppFolio’s 2026 renter research found that residents satisfied with maintenance were considerably more likely to plan to renew or remain in their homes than residents who were dissatisfied. Fifty-six percent of maintenance-satisfied residents planned to renew or stay, compared with 31% of dissatisfied residents. The same research found that 83% of satisfied residents would recommend their property management company, compared with only 28% of dissatisfied residents. AppFolio 2026 Renter Preferences Report
Communication also showed a strong relationship with renewal intentions and recommendations.
That connection makes sense.
Residents may interact with a leasing professional several times before moving in, but maintenance interactions continue throughout the tenancy. Each one tells the resident something about the company’s competence, reliability, and respect for the people living at the property.
A well-handled work order says:
We heard you. We understand the problem. Someone owns it. We will keep you informed.
A poorly handled one says:
You will have to keep reminding us.
An acknowledgment is not an update
Automated confirmations are useful. They reassure residents that a request entered the system and provide a record of submission.
They are not a substitute for meaningful communication.
“Your request has been received” answers only one question. It does not tell the resident:
Whether the request has been reviewed
How urgent it was determined to be
Whether additional information is needed
Who has been assigned
When someone will enter the apartment
Whether the resident must be present
Whether a vendor is involved
Whether a part was ordered
When the next update will occur
A good maintenance process distinguishes among several communication points:
Confirmation: The request entered the system.
Triage: The issue was reviewed and assigned a priority.
Scheduling: A technician or vendor is expected at a stated time.
Diagnosis: The problem was inspected and the next action identified.
Delay: A part, approval, vendor, or additional work is required.
Completion: The work was performed.
Verification: The resident confirms the problem is resolved.
Not every work order requires a message at every stage. Longer or more complicated repairs often do.
“Waiting” is not a complete status
Property-management systems frequently contain statuses such as:
New
Assigned
Scheduled
In progress
Waiting
Completed
Canceled
These labels may help staff organize work. They may not provide enough information for residents or supervisors.
“Waiting” could mean:
Waiting for a part
Waiting for owner approval
Waiting for a vendor
Waiting for the resident to provide access
Waiting for another repair to be completed first
Waiting for materials to dry
Waiting for an estimate
Waiting because no one has followed up
Those circumstances require different actions.
Every delayed work order should have:
A documented reason
A named owner
A specific next step
A target or follow-up date
A resident communication record
A status without a next action is where work orders disappear.
The resident should not be the project manager
When residents must repeatedly call the office, contact maintenance directly, submit duplicate requests, or ask multiple employees for help, the property has transferred its coordination work to the resident.
That creates more work for everyone.
Duplicate calls interrupt office staff. Additional work orders distort reporting. Maintenance personnel receive conflicting information. Residents become more frustrated with every repetition. Managers spend time reconstructing a history that should already exist in the system.
A resident should not need to determine:
Which employee has the request
Whether a vendor was contacted
Whether a part arrived
Whether management approved the repair
Why an appointment was missed
When someone will return
Whether the work order was closed
That information should be managed internally and communicated outward.
Residents are responsible for reporting problems, providing accurate information, arranging access when needed, and following reasonable instructions.
They should not be responsible for keeping the company’s workflow alive.
Closing the work order is not the same as resolving it
A technician may complete the assigned task without resolving the resident’s original problem.
The drain was cleared, but it clogged again the next day. The appliance was adjusted, but it still does not operate correctly. The leak was stopped, but the damaged material remains wet. The smoke alarm was replaced, but the new unit continues chirping. The vendor visited, but no one knows what was done.
A work order can appear complete in the software while remaining open in the resident’s life.
Before closing a request, the record should answer:
What was reported?
What was found?
What work was performed?
Were parts installed or ordered?
Is additional work required?
Was the apartment left clean and secure?
Was the resident notified?
Did the resident confirm that the problem was resolved?
Resident confirmation may not be possible in every case. A brief completion message still gives the resident an opportunity to report that the repair was unsuccessful.
That feedback should not be treated as a new and unrelated complaint. It may be evidence that the original work order was closed prematurely.
Urgency must be defined before the request arrives
A maintenance team should not invent its triage standards during an emergency.
Properties need written categories that identify which requests require immediate response, same-day attention, prompt scheduling, or routine service. Those standards should reflect applicable law, lease obligations, building systems, resident safety, weather, and property-specific risks.
Potential emergencies may involve conditions such as:
Fire or active smoke
Suspected gas leaks
Major uncontrolled water intrusion
Electrical hazards
Loss of essential services under dangerous conditions
Security failures affecting entry
Sewage backups
Conditions posing an immediate threat to health or safety
Employees who receive requests should know how to recognize escalation language and how to reach the appropriate on-call person.
They should also know not to make legal, medical, or safety judgments beyond their role.
Requirements for repair timing and resident remedies vary by jurisdiction and circumstance. Communication never replaces compliance with applicable habitability, access, emergency-response, or fair-housing obligations.
Residents need different communication for different delays
A delayed work order is not one communication problem. It can be several.
Waiting for a part
Tell the resident what was ordered, when it is expected, whether the current condition can be used safely, and when the property will provide another update.
Waiting for a vendor
Confirm that the vendor was contacted, provide the appointment window when available, and explain whether the vendor or property will coordinate access.
Waiting for approval
Internal approval processes are the management company’s responsibility. The resident should still receive an expected timeline and any interim measures available.
Waiting for resident access
Document every attempt to schedule. Make the requested action clear and provide simple ways for the resident to respond.
Additional damage discovered
Explain that the original issue was more extensive than expected, identify any immediate action taken, and describe the next phase.
No firm completion date
Do not invent one.
Provide the information available and commit to a specific update date:
We do not yet have a confirmed installation date. We expect an update from the supplier by Thursday and will contact you that afternoon, even if the delivery date has not changed.
That final phrase matters. It prevents the resident from interpreting another period of silence as abandonment.
Good communication should be specific
Weak maintenance messages often contain vague assurances:
“We’re working on it.”
“Maintenance has been notified.”
“Someone should be there soon.”
“The part is on order.”
“We’ll let you know.”
“The vendor is backed up.”
These statements provide little usable information.
A stronger update includes concrete facts:
Our technician inspected the dishwasher Tuesday and determined that the circulation pump needs replacement. The part was ordered Wednesday and is expected to arrive between September 3 and September 5. We will contact you by September 5 to schedule installation or provide an updated delivery date.
Specific communication creates accountability internally as well as reassurance externally.
It establishes what should happen next and when someone needs to verify it.
Maintenance teams also need visibility
Poor communication is not always the result of indifferent employees.
Maintenance technicians may receive incomplete work orders, inaccurate contact information, missing access instructions, unclear priorities, or verbal requests that never reach the system. Office staff may not know whether the technician visited, what was diagnosed, or whether another appointment is needed.
A strong process gives both sides access to the same current information.
Every work order should include:
A clear description of the problem
Relevant photographs when useful
Date and time received
Priority
Permission-to-enter information
Preferred contact method
Assigned employee or vendor
Scheduled date
Notes from each visit
Materials or approvals needed
Next action and follow-up date
Completion details
Resident communication history
Technology can make that record easier to maintain. It cannot compensate for a company culture in which documentation is considered optional.
Supervisors should manage the age of the backlog
The total number of open work orders tells leadership very little on its own.
Ten requests opened this morning are different from ten requests that have remained unresolved for three weeks.
Maintenance reporting should show work orders by age:
Less than 24 hours
One to three days
Four to seven days
Eight to fourteen days
Fifteen to thirty days
More than thirty days
Managers should also review:
First-response time
Time to initial inspection
Time to completion
Time since the last resident update
Emergency response
Work orders waiting for parts
Work orders waiting for vendors
Work orders waiting for approval
Repeat requests for the same issue
Reopened work orders
Requests closed without completion notes
Resident satisfaction after service
Backlog by technician, vendor, property, and repair category
An aging report should trigger action, not merely appear in a meeting packet.
Every older request should have a credible explanation and next step.
Repeated work orders reveal larger problems
Some requests are not isolated repair events.
Repeated leaks may indicate a failing building system. Frequent drain clogs may reveal a pipe condition requiring more than routine clearing. Recurring heating complaints may point to equipment sizing, insulation, controls, or preventive-maintenance problems. Multiple requests from the same building may reveal an issue invisible when each ticket is reviewed separately.
Properties should look for patterns by:
Unit
Building
Equipment type
Repair category
Vendor
Technician
Season
Previous repair
Cost
Frequency
Fixing the same symptom repeatedly can appear less expensive than addressing the source. Over time, repeated labor, resident dissatisfaction, damage, emergency calls, and eventual replacement may cost considerably more.
The work-order system should function as an early-warning system—not simply a list of tasks.
Prevention is part of the resident experience
The best work order may be the one a resident never needs to submit.
Preventive maintenance can reduce emergencies, extend equipment life, support budgeting, and demonstrate care for the property.
A useful program may include:
HVAC servicing and filter schedules
Roof and gutter inspections
Plumbing and leak checks
Smoke and carbon-monoxide alarm testing
Exterior lighting inspections
Drain and sewer maintenance
Appliance evaluations
Weatherization
Pest-management monitoring
Water-heater inspections
Common-area safety reviews
Seasonal property walks
Preventive work should also be documented. Otherwise, leadership cannot determine whether it occurred, what was found, or whether recommended follow-up was completed.
A work order is not the beginning of maintenance. It is often the point at which preventive maintenance has already missed an opportunity.
Create a communication standard
Every property should have a simple maintenance communication standard understood by office employees, technicians, vendors, and supervisors.
It might require:
Immediate automated confirmation
Human review and triage within a defined period
Prompt contact for emergencies and urgent conditions
Scheduling information when an appointment is required
An update whenever the status materially changes
A resident update after a stated number of days without completion
A documented next action for every delayed request
Clear completion notes
Resident notification before closure
Follow-up when the same problem returns
The exact timing should reflect the property, staffing, repair type, legal requirements, and severity of the issue.
The principle is universal:
No open work order should remain silent.
The final update matters
A resident who submits a request wants to know three things:
Did you hear me?
Are you doing something?
Is the problem actually resolved?
A strong maintenance process answers all three.
It does not promise what the team cannot deliver. It does not conceal legitimate delays. It does not send meaningless automated messages while the request sits untouched.
It provides visibility, ownership, and follow-through.
Repairs will sometimes take longer than anyone wants. Parts will be delayed. Emergencies will disrupt schedules. Vendors will disappoint.
Those realities are unavoidable.
Leaving the resident to wonder what is happening is not.
The work order may still be open.
The communication should not be.
