Philippines staffing guide · Published
On this page
Set up a property maintenance request log for a remote assistant
A maintenance log that captures the request, the property, the access route, the approval, and the close evidence so a remote assistant can coordinate repairs without guessing.
A property maintenance request log gives a remote assistant one place to see what broke, which property it belongs to, and who approved the repair. Without that record, requests arrive through texts, calls, and portal notes that nobody can reconcile. The log turns those fragments into a queue with an owner and a next step. It also protects the assistant from making a spending decision that belongs to the property owner.
The assistant coordinates the flow rather than authorizing the work. The owner or manager approves the vendor and the amount, while the assistant captures the request, schedules access, and collects the completion evidence. Writing that boundary into the log keeps small repairs from becoming unauthorized commitments. It also makes the approval trail visible when an invoice arrives weeks later.
Capture the request before assigning a vendor
Log the date, the person reporting the issue, the property address, and the exact location inside the unit. Ask what the person observed and what they already tried, because a reset breaker is a different job from a failed panel. Record the safety impact, such as water near electrical outlets or a broken lock. The first note should be specific enough for a vendor to quote without another call.
Classify the request as emergency, urgent, or routine and write the rule used for that choice. An emergency gets a call to the owner immediately, while a routine request can wait for the next batch. Do not let the reporter set the priority alone, because every tenant believes their issue is urgent. A consistent classification keeps the queue fair and the response times predictable.
Record property and access details
Add the access method, the gate code owner, the parking note, and any pet or alarm instruction. Store the code in a password manager rather than a plain cell, and record who may share it. Note the best contact for access questions and the hours when entry is allowed. A vendor who cannot get in wastes a trip and may charge for it.
Keep the property record separate from the request record so the same access notes can serve many jobs. Update the property record whenever a tenant changes a code or a lock is replaced. Mark which fields came from the owner and which came from a tenant. When the two disagree, the owner's instruction wins until it is confirmed in writing.
Route approval to the right owner
Name the approver and the spending limit before the first vendor is contacted. Send the approval request with the observed issue, the proposed fix, the quote, and the expected timing. Ask for a written yes or no rather than treating silence as consent. Record the approver, the amount, and the date beside the request. A screenshot of the approval in the thread is helpful, but the log entry is what the next shift will read.
If the owner is unavailable, use a written fallback rule for small recurring repairs and nothing else. The fallback should name a cap, a category, and a person who will review the decision afterward. Never let a vendor start work on the promise that approval will arrive later. An approval that is not written is not an approval the assistant can rely on.
Schedule the visit with a written window
Offer the vendor two or three concrete windows and confirm one in writing. Send the tenant the same window in their time zone, along with the vendor name and a number to call. Ask the tenant to confirm that someone will be present or that the agreed access method will work. A visit without a confirmed window is the most common reason repairs stall.
Record the scheduled time, the vendor, and the arrival confirmation in the log. If the vendor is late, note the time and the reason instead of quietly moving the appointment. Notify the tenant of any change before the original window closes. Keep the communication in the log so the next shift does not repeat the same calls.
Collect completion evidence
Ask the vendor for a short description of the work, the parts used, and a photo of the completed repair. Compare the invoice line items with the approved quote and flag any difference. Record whether the tenant confirmed that the issue is resolved. Close the request only when the work, the cost, and the tenant response are all on file.
If the repair is temporary, keep the request open with a follow-up date and a named owner. A patch that hides a larger problem should not be marked complete just because the vendor left. Note any warranty on parts or labor and set a reminder before it expires. Completion evidence is what protects the owner when the same fault returns.
Review open requests every week
Sort the log by age and look at every request older than the agreed service window. Ask which row is waiting on the owner, which is waiting on the tenant, and which is waiting on the vendor. Send one consolidated update to each party instead of chasing every row separately. A weekly review keeps small delays from turning into a backlog nobody can explain.
Once a month, group closed requests by property and by repair type. A repeated fault may point to a maintenance problem rather than a bad vendor. Share the pattern with the owner and ask whether the preventive work should be scheduled. The log should support decisions about the property, not just record what already happened.
Questions and operating boundary
Can the assistant approve a repair?
Only within a written limit set by the owner. Record the cap, the categories it covers, and the person who reviews the decision afterward.
What should the log keep from a vendor call?
The date, the person spoken to, the quoted amount, the proposed window, and any condition attached to the quote. A short note is enough if it names the source.
How should urgent requests be handled?
Call the named owner immediately and log the time. Do not wait for the next queue review when safety or property damage is at risk.
Source
sba.gov provides authoritative background and does not endorse this service.