Features & tools
Job history by plant: the building's technical memory
Job history by plant is the ordered archive of all maintenance work carried out on each plant in the building: lift, heating, pressure booster, lighting, automatic gates. Each entry records date, firm, description, outcome and cost, linked to the plant record. This technical memory turns a series of isolated jobs into a readable picture that reveals recurring faults, cost trends and the health of the common parts. Keeping it in order helps the manager fulfil the duty to preserve the building's technical documentation under Article 1130 of the Italian Civil Code and eases the arrival of a new manager.
Why record jobs by plant
A job recorded by plant is worth more than a job recorded only by date. By linking each task to the item it was carried out on, you build a record that tells the story of that plant: how often it failed, with which firms, with what results. It is the difference between a list of invoices and a real technical memory.
This organisation answers concrete questions that keep coming up. When was the last lift part replaced? How much did we spend in a year on heating between repairs and servicing? Is a plant that fails often still worth repairing or should it be replaced? Without history by plant, these answers require digging through scattered documents.
Spotting recurring faults
The most immediate value of history is surfacing problems that repeat. Three call-outs in a year on the same pump are not three separate episodes but the symptom of a structural fault. Seeing them side by side in the plant record changes the perspective and shifts the decision from constant repair to a reasoned replacement.
This reading has a significant economic side. Documenting that a plant has generated repeated costs makes the case for an extraordinary job at the meeting far stronger. Owners approve an expense more readily when they see the ordinary maintenance figures that the expense aims to avoid in future.
Costs over time and informed choices
By aggregating costs per plant and per period, history offers an objective basis for the next year's budget estimate. You do not guess in the dark; you start from what maintenance actually cost in previous years, adjusted for observed trends.
The same archive also helps evaluate suppliers. If a firm keeps working on the same plant and the problems recur, the data is visible and open to discussion. History makes transparent not only the state of the plants but also the effectiveness of those who work on them.
Support for the handover
When the manager changes, history by plant is among the most valuable documents to transfer. The new manager inherits not just the invoices but an understanding of how the building's plants behave, avoiding a fresh start and the repetition of mistakes already dealt with.
AmministraPro keeps job history linked to each plant record, with costs that aggregate over time and recurring faults highlighted, ready for the handover too. The features are described on /funzioni and the plans with their limits are summarised on /prezzi.
Frequently asked questions
What is the difference between history by date and history by plant?
History by date is a chronological list of jobs, while history by plant links each task to the item it was carried out on. Only the latter lets you read the story of a single lift or the boiler, spotting recurring faults and accumulated costs, information that a date-based list leaves scattered.
How does history help decide between repair and replacement?
It shows how often a plant has failed and how much repairs cost over time. Frequent faults and repeated costs on the same plant suggest that replacement may be cheaper than constant maintenance. These figures also strengthen the case for an extraordinary job to put before the owners' meeting.
Is job history useful for the budget?
Yes, it is an objective basis. Aggregating the real maintenance costs per plant over previous years avoids estimating budget items in the dark. You start from historical data and adjust for observed trends, producing forecasts that are more credible and easier to defend at the meeting.
Why is history important at a change of manager?
Because it transfers the building's technical memory, not just the invoices. The new manager understands how the plants behave, which ones caused problems and with which firms, avoiding a fresh start. It is part of the documentation the manager must keep and hand over under 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.