Maintenance coordination
A maintenance ticket log that survives the vendor call
Capture the symptom, access, photos, approval limit, and completion evidence before closing a repair.
Published · 1 minute read
On this page
What to control
- Record the property and the exact symptom
- Attach photos and access instructions
- Name the spend limit and approver
- Close only with completion evidence
Operating context
Maintenance tickets fail at the handoff between guest, coordinator, and vendor. A log keeps the three views aligned: what the guest reported, what the coordinator verified, and what the vendor did.
Open with the symptom in plain language and the time it was reported. Add the guest's availability and the access method. If the guest must be present, say so before dispatching a vendor.
A workable routine
Attach photos and a short video where safe. A photo of a leaking valve is more useful than the word plumbing. Remove personal information from images before sharing.
Record the approved spend limit and the person who approved it. A vendor who arrives without a limit will ask the coordinator to decide on the doorstep.
Review and evidence
Close the ticket only with completion evidence: a photo, an invoice, or a vendor note. A ticket marked done without evidence is a future repeat call.
For related operating guidance, review the [turnover handoff brief](/blog/str-turnover-cleaner-handoff-brief) and the [guest response window guide](/blog/str-guest-message-response-windows). The [CISA cybersecurity performance goals](https://www.cisa.gov/cybersecurity-performance-goals) provide public baseline context for access and account controls.