Features & tools
The life cycle of a maintenance ticket: from statuses to closure
The life cycle of a maintenance ticket is the sequence of statuses a report goes through from arrival to closure. Defining these statuses clearly answers a simple but crucial question: where is this job and who needs to move it now. A well-designed flow distinguishes what is waiting on the manager, what is waiting on the supplier and what is done. In condominium software this structure makes technical management measurable and links each report to the building documentation the manager must keep updated under Article 1130 of the Italian Civil Code.
Why defined statuses matter
Without statuses, a report is just a message that can get lost. With defined statuses, each ticket explicitly declares the phase it is in and who is responsible at that moment. This reduces ambiguity: it is no longer about remembering who was meant to do what, but about reading the status written in the system.
Statuses also make work measurable. Knowing how many tickets have been open for more than a week, or how many are on hold awaiting a quote, gives an honest picture of the operation. It is the basis for improving response times, which owners perceive as service quality.
The typical statuses of a ticket
A simple, robust flow uses few statuses, each with a single meaning. What matters is not having many phases, but that each is clear and that moving from one to another corresponds to a real event, such as awarding a job to a firm or completing the work.
An on-hold status is useful for cases where the job cannot proceed for external reasons, for example waiting for a meeting resolution on extraordinary expense. Distinguishing on-hold from open avoids confusing genuinely stalled cases with those in normal progress.
- Open: report received, still to be assessed
- Taken on: the manager has reviewed the case
- Assigned: work order awarded to a supplier
- In progress: job under way
- On hold: paused awaiting a quote or resolution
- Closed: job completed with recorded outcome
The critical steps in the flow
The points where tickets get stuck are almost always the same: the move from open to taken on, when a report goes unanswered, and from assigned to executed, when the supplier is slow. Spotting these bottlenecks is half the work of solving them.
Software helps by flagging tickets stuck too long in the same status. An automatic reminder on a report open for days pushes you to close or assign it, rather than letting it slip. The speed of transition between statuses, more than the absolute number of tickets, tells the health of the operation.
Closing a ticket well
Closure is not just a status change: it means recording the outcome, the supplier, the cost and the date, and linking any invoice. A ticket closed poorly, without this information, loses value for the history and for reporting to the meeting. A ticket closed well becomes part of the building's job register.
AmministraPro manages maintenance tickets with clear statuses, reminders on stalled cases and closure with outcome, cost and invoice linked, so every report leaves a useful trace. The features are described on /funzioni and the plans with their limits are summarised on /prezzi.
Frequently asked questions
How many statuses should a maintenance ticket have?
Few and clear beats many and confusing. A robust flow typically uses open, taken on, assigned, in progress, on hold and closed. Each status must carry a single meaning and the move between phases must correspond to a real event, such as awarding the job to a supplier or completing the work.
What is the on-hold status for?
It distinguishes tickets paused for external reasons from those in normal progress. A job awaiting a quote or a meeting resolution on extraordinary expense is on hold, not open. This distinction avoids confusing genuinely blocked cases with those that are proceeding normally.
How do you keep tickets from stalling?
The software can flag tickets left too long in the same status with automatic reminders. An alert on a report open for days pushes you to close or assign it. Monitoring the speed of transition between statuses, rather than the total number, helps spot bottlenecks and cut response times.
What should be recorded at ticket closure?
The outcome of the job, the supplier who carried it out, the cost, the date and any linked invoice. A complete closure turns the ticket into part of the building's job history, useful for reporting to the meeting and for future decisions, in line with the documentation required by Article 1130 of the Italian Civil Code.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.