Describe the problem clearly
Record the location, observed issue and impact. “Bathroom problem” is difficult to assign; “water leaking below the basin when the tap runs” gives the next person something to investigate.
Use photographs when they clarify the issue, while keeping private information out of the frame. Record what was observed without claiming a diagnosis that has not been confirmed.
Triage before scheduling
Set a priority that reflects the impact and required response. Assign a responsible person and a next action. Where specialist assessment is needed, record that as the action rather than guessing a repair.
Escalate urgent issues through the business’s established process. A software priority label is not an emergency response service.
Keep approval with the ticket
Where owner approval is required, provide the scope and available estimate and record the owner’s decision. Keep work blocked from completion until the required decision exists.
If the scope or amount changes materially, seek the appropriate updated decision. Do not treat an earlier approval as permission for unrelated work.
Record the resolution and actual cost
Explain what was done and what remains unresolved. Record actual costs separately from estimates. If another visit is needed, make that next action visible.
Review before-and-after evidence where it is useful. Publish a concise owner update only after the result is ready to share.
Learn from the property history
Before opening another ticket for a recurring issue, review the earlier resolution. The historical record can help the manager ask better questions and identify repeated temporary fixes.
At the monthly review, compare open work and recorded maintenance expenses by property. Keep currencies separate and reconcile against external invoices or accounting records before treating the summary as a financial statement.
Example: handle a recurring leak
A cleaner reports water below the kitchen sink. The manager opens the property history and finds an earlier repair involving the same area. The new ticket records the current observation and notes that there is relevant previous work. It does not assume the cause is identical.
The responsible maintenance person reviews the description and available evidence, then records the proposed next action. If owner approval is required, the manager shares the scope and estimate and waits for the recorded decision. The ticket remains open while the decision is pending.
After the visit, the technician records the actual work and any remaining uncertainty. The manager reviews the outcome and publishes an appropriate owner update. If a further visit is required, create the next action explicitly instead of closing the ticket with an ambiguous note such as “monitor.”
Define priority through impact and response
A priority label should have an agreed meaning inside the business. Consider the effect on access, use of the property and the next scheduled activity. Keep emergency escalation outside the normal software queue when the situation requires immediate professional help.
Record the reason for a high priority so another manager can understand it. An overdue cosmetic repair and an urgent active leak should not become interchangeable simply because both appear in an attention list. The software can group them, but a responsible person still needs to triage the work.
Review tickets that remain in the same stage for a long time. The blocker may be approval, access, parts or a missing appointment. Name the blocker and assign the next decision. Repeatedly changing a due date without explaining the cause hides the operational problem.
Connect costs without turning the ticket into accounting
Record estimates and actual costs in the intended minor units and currency. Keep an explanation of the work covered by the amount. If several visits or invoices belong to one issue, reconcile them through the business’s accounting process before treating a total as complete.
A recorded cost does not establish that a supplier has been paid. Likewise, a published owner report is an operational summary, not proof of a bank transaction. Keep external invoice, payment and tax responsibilities clear, and use exports to support the appropriate reconciliation process.
Put the process into practice
Start with one property and one complete workflow. Review the outcome with your team before expanding.