A created maintenance ticket proves that a report was recorded. It does not prove the right person accepted it, a contractor attended, or the resident's issue was resolved.
Define ticket created, triaged, assigned, handoff accepted, attendance confirmed, completed, and resolved according to the manager's process. Avoid using one “handled” metric for all of these states.
Link each state to evidence
Connect the original call, request, staff owner, contractor work order, and outcome where reliable identifiers exist. Preserve the event time and reporting cutoff. A delayed update should not silently rewrite when the work happened.
Keep repeat calls separate from unique requests. Several calls may concern one unresolved issue, while one call can create multiple independent requests at different units.
Calculate a fictional weekly view
A portfolio receives fifty maintenance reports. Forty-five tickets are created, thirty-five receive staff acceptance, and twenty-five have recorded completed work by the cutoff. Five reports are awaiting property clarification, and ten created tickets remain unassigned or unaccepted.
The ticket-creation rate is forty-five divided by fifty, or 90%. That is not a 90% resolution rate. The report should show the unaccepted and unresolved work rather than treating recorded intake as completion.
| Metric | Required evidence |
|---|---|
| Ticket created | Verified request record |
| Staff accepted | Recorded ownership acknowledgment |
| Contractor assigned | Work-order assignment |
| Work completed | Approved operational completion status |
| Request resolved | Manager-defined verified outcome |
The figures are illustrative, not measured portfolio results.
Make unknowns actionable
Include missing links, uncertain writes, duplicate candidates, unclaimed tickets, and disputed completion. Each material exception needs an owner and next action. A report should help staff repair gaps rather than hide them in a success percentage.
More detailed reporting requires consistent staff updates and integration work. Begin with a reconciled request-to-owner table and add later stages only when evidence is reliable. Do not infer resolution from silence or from a contractor notification alone.
Review appointment state boundaries for the general principle of keeping a recorded request separate from a verified commitment.
Questions about maintenance reports
Can a closed ticket count as resolved?
Only if the manager's closure process supports that meaning. Administrative closure and verified resolution may differ.
Should repeat calls be counted as failures?
They are interactions requiring context. They may indicate delayed work, new facts, or a different request; classify them explicitly.
What should managers review daily?
Unclaimed work, unacknowledged escalations, aging requests, and disputed completion are often more actionable than total tickets created.