Track each rental maintenance issue in one record tied to its property and unit. Include the original report, supporting photos, current status, person responsible, and next action. Update that same record as the job moves forward so a text, phone call, or vendor update does not become a separate loose end.
You can use a shared list or a property management app. The goal is to open a request and immediately understand what is happening and who needs to do something next.
Start one record for each issue
Give the request a specific title: “Kitchen cabinet hinge loose” tells you more than “Repair needed.” Then capture the tenant's description in their own terms. Keep what they observed separate from any later diagnosis.
For a routine request, collect:
- Property and unit.
- Date and time reported.
- A description of the issue and its location.
- Photos, if useful and safe to obtain.
- Contact and scheduling information needed for follow-up.
- Current status and the person coordinating the job.
- Next action and follow-up date.
Not every tool has a separate field for every detail. A consistent note format can fill a gap, provided everyone involved knows where to find it.
Keep emergency reporting instructions separate and prominent. A routine maintenance queue should not be presented as an emergency response channel.
Give each open request a next action
A status such as “In progress” is useful, but it does not explain what is preventing completion. Pair it with a concrete next action.
Consider this illustrative request:
- Issue: bedroom closet door comes off its track.
- Status: in progress.
- Responsible person: landlord coordinating with the repair vendor.
- Next action: vendor to confirm the replacement part and appointment options.
- Follow-up: review on Thursday if no response arrives.
That is easier to act on than a note saying “Vendor contacted.” When someone else helps manage the property, they can continue the work without reconstructing the whole conversation.
Choose statuses you will use consistently. “New,” “In progress,” and “Done” may be enough for a small portfolio. If your tool does not support a separate “Waiting for parts” state, record that detail in the update rather than assuming the status tells the full story.
Make the vendor handoff complete
Before assigning a job, gather the address and unit, a useful description, relevant photos, the contact person, and the agreed scheduling information. Confirm access arrangements through your normal process; do not assume a tenant's repair request automatically settles when someone may enter.
Avoid including access codes or unrelated tenant details in broadly shared notes. Give the vendor the information needed for the job through an appropriate channel.
Record the handoff and expected next response. If the vendor replies by email or phone, summarize the outcome in the request record. The next person reviewing the job should not need access to your entire inbox.
In UnlockAbode, tenants can submit requests with photos through the portal, and landlords can create work orders and assign vendors. The maintenance walkthrough explains the current workflow, including vendor email behavior.
Keep the tenant updated when plans change
A request can be active even when nobody is currently at the property. A part may be on order, a visit may need rescheduling, or you may be waiting for the vendor's findings.
Share the practical update: what has happened, what happens next, and when you expect to have more information. Avoid promising a completion date the vendor has not confirmed.
Keep a record of the update alongside the issue or in its associated conversation. If you use both a messaging tool and a work-order list, give the records a clear reference so you can connect them later.
Close the request with an explanation
Before marking a job done, record what was completed and when. Note who performed the work and any follow-up still needed. Where useful, retain a completion photo or the vendor's written description.
If the reported problem remains unresolved, keep that visible rather than closing the request simply because a visit occurred. If the same symptom returns later, reference the earlier work so the next vendor has context.
Track the invoice or expense against the correct property and unit. The repair history explains what happened; the expense record explains its cost. Give them a common reference if your tools do not link them directly.
UnlockAbode's expense walkthrough describes how to record that cost. Do not assume marking a repair complete automatically records or pays its invoice.
A maintenance record you can reuse
Copy these labels into your own process and fill in the details as the request progresses:
- Request title:
- Property and unit:
- Reported on:
- Reported issue and location:
- Photos or supporting records:
- Status:
- Person responsible:
- Vendor and handoff date:
- Next action and follow-up date:
- Scheduling arrangements:
- Latest tenant update:
- Work completed and date:
- Invoice or expense reference:
- Remaining follow-up:
This is an organizational checklist, not a substitute for technical diagnosis or local repair and access requirements.
Review the queue, not just the newest message
Set a regular review time for ordinary open requests, while handling urgent reports through your established process. Look for jobs without an assigned person, requests waiting on a response, missed follow-ups, and work that is finished but still missing its records.
The oldest unresolved item can be easy to overlook when newer messages keep arriving. Review by outstanding next action as well as by date received.
If scattered texts have become your maintenance system, start by consolidating your open jobs. You do not need to reconstruct every old repair before making today's work easier to follow.
Try the workflow in UnlockAbode
Read how to handle a maintenance request to see the product steps, or invite a tenant if you are setting up their portal.
You can review current pricing and create an account when you are ready. If you want to check how your existing process fits, talk to a person.