A maintenance request workflow should make the next action clear. The process does not need to be complicated, but every open request should have a property, an issue, an owner, a status, and a next review date.
This guide is an organization aid for self-managing US landlords. It does not provide legal, tax, financial, safety, contractor, or emergency-response advice. It does not recommend a provider or include affiliate links.
Create one intake route
Start with one preferred route for maintenance requests. That could be a tenant portal, a dedicated form, or a shared email address. The exact tool matters less than making the route clear and checking it on a schedule you can maintain.
Tell tenants what to include:
- property and unit;
- a short description of the issue;
- where it is located;
- when it started or was noticed;
- photos or documents when useful; and
- the best way to arrange access or follow-up.
Keep a separate method for a situation that needs immediate attention under your own property procedures. This guide does not decide what counts as an emergency or provide safety instructions. Set those rules for your properties with appropriate local and professional input.
A single intake route also helps with duplicate reports. If the same issue arrives by text and email, keep one primary record and link or note the duplicate rather than opening two unrelated tasks.
Use a request record that survives the repair
Create a record as soon as a request arrives. The record should be useful before, during, and after the repair. At minimum, include:
- property and unit;
- tenant or lease reference;
- date and channel received;
- issue description and location;
- photos, documents, or message links;
- current status;
- person responsible for the next action;
- access notes agreed with the tenant;
- vendor contact and work-order details;
- quoted or actual cost, if known; and
- completion date and closeout note.
Use status labels that describe what is happening rather than how worried you feel. For example:
- New: the request has been received but not reviewed.
- Needs information: a missing detail prevents the next decision.
- Assigned: a landlord, vendor, or other responsible person has the next action.
- Scheduled: a visit or repair has been arranged, but the work is not closed.
- Waiting: progress depends on a response, part, access arrangement, or other external step.
- Completed: the work is finished and the record is ready for closeout.
- Closed: the final note, cost information, and tenant communication are stored.
These labels are a practical operating structure, not a provider requirement. Avail presents maintenance tracking with in-app messages, photos, and automatic maintenance records.[1] Its maintenance guidance also describes uploading the details of a request for future reference.[2] Those examples support the value of keeping a durable record, but they do not mean every provider offers the same features.
Review the request before assigning work
Read the request once before forwarding it. Confirm the property, unit, issue, location, and any access information. If a key detail is missing, ask one focused question rather than sending a long list of requests that the tenant may not understand.
Then choose the next action:
- request more information;
- inspect the issue yourself if that fits your process;
- contact a known vendor;
- create a routine maintenance task; or
- place the item in a waiting queue with a follow-up date.
Do not mark a request as scheduled merely because you sent a message. Record the actual next step and who owns it. If you are waiting for a reply, the request should have a follow-up date so it does not disappear into an inbox.
Move from request to work order
A work order should give the person doing the work enough context without forcing you to repeat the entire conversation. Include the property and unit, issue description, relevant photos, access instructions, tenant contact details that are appropriate to share, and the action you are asking the vendor to take.
Keep a copy of what was sent and when. Ask the vendor to confirm receipt and record whether the job was accepted, scheduled, declined, or still awaiting a response.
TurboTenant describes a workflow in which landlords can receive tenant requests, create their own requests, communicate with renters, coordinate repairs, and keep a record of completed work.[3] Its help documentation also says that a work order can email request details directly to a preferred maintenance professional.[4] The same documentation makes an important limit clear: sending a work order does not automatically schedule the repair or confirm that the contractor accepted the job.[4] Keep those steps separate in your own record.
Communicate without losing the record
Use the request record as the source of truth. If a tenant calls, add a short note with the date, the issue discussed, and the next action. If a vendor sends an update by text, copy the useful detail into the request record rather than relying on a personal phone history.
A simple update can answer three questions:
- What has happened since the last update?
- What is the next action?
- When will the next review happen?
Avoid promising a completion date before the responsible person has confirmed it. When the schedule changes, update the tenant using the agreed communication route and retain the update in the record.
Close the request deliberately
A repair is not ready to close just because someone visited the property. Before closing, confirm that:
- the work or inspection is complete;
- the final status is recorded;
- the relevant invoice, receipt, or cost note is attached;
- the tenant has received the intended update;
- access details and temporary notes are no longer active; and
- any follow-up task has been created separately.
If the issue is recurring, link the new request to the earlier record. Note what was observed, what action was taken, and what remains uncertain. Do not rewrite an old record to make the history look cleaner. Add a dated correction or follow-up note instead.
Spreadsheet or software?
A spreadsheet can be enough when you have a small number of properties, one intake route, few open requests, and a reliable habit of updating records. A tool may be worth comparing when you are repeatedly losing photos, forwarding the same details, missing follow-up dates, or trying to track requests across several properties.
Compare the workflow, not just the feature list. Ask:
- Can each property and unit be identified clearly?
- Can requests from calls, email, and portals be kept in one history?
- Can photos and documents be attached to the right request?
- Can the current owner and next action be seen quickly?
- Can a work order be created without retyping the whole request?
- Can completed work, costs, and notes be retained?
- Can you export or retain the records you need outside the provider?
- What happens if a request is duplicated, cancelled, or reopened?
Check current provider documentation before relying on a specific feature, price, limit, or workflow. This guide does not recommend a provider and contains no affiliate links.
Weekly maintenance review
Set aside a recurring review time and work through the open-request list:
- New requests have been reviewed.
- Missing information has a clear question and follow-up date.
- Assigned requests have an owner.
- Scheduled requests have a confirmed date or a next check.
- Waiting requests explain what they depend on.
- Completed requests have cost and closeout notes.
- Recurring issues link back to earlier records.
- Duplicate or abandoned requests are marked clearly rather than silently deleted.
This review is useful even when there are no new requests. It catches items that were acknowledged but never assigned, scheduled but never closed, or completed but never recorded.
What this guide does not decide
This guide is an organization aid, not legal, tax, financial, safety, contractor, or emergency-response advice. It does not decide what work a landlord must perform, what a tenant must pay, which vendor is qualified, how a property should be inspected, or which records a local authority or tax professional may require. Confirm those questions with appropriate local and professional sources.
- Avail: Rental Maintenance Software and Landlord Tracking System. Retrieved October 27, 2026. The page describes messages, photos, maintenance records, repair progress, and repair notes and costs.
- Avail: How to Manage Avail Maintenance Requests. Retrieved October 27, 2026. The page describes uploading maintenance details for future reference.
- TurboTenant: How Do I Manage Maintenance Requests?. Retrieved October 27, 2026. The page describes tenant and landlord-created requests, communication, repair coordination, and completed-work records.
- TurboTenant: How Do I Send a Work Order to a Maintenance Professional?. Retrieved October 27, 2026. The page describes sending request details to a preferred maintenance professional and notes that sending does not automatically schedule or confirm the repair.
Review date: October 27, 2026. Provider workflows and product details can change. Confirm current terms directly with a provider before relying on a specific feature.
