Planned Preventive Maintenance vs Emergency Repairs: How a Plan Cuts Breakdown Calls
Planned preventive maintenance is work on a building's systems done on a fixed schedule — filters, drains, pumps, electrical panels, roofs — so that faults are caught before they turn into emergency repairs. In a small facility team the problem is rarely the idea itself; it is that every urgent call eats the hours set aside for the plan. A leak on Monday pushes the weekly plant-room round to Thursday, Thursday brings a tripped breaker, and by Friday the round has simply not happened. If you already have a preventive maintenance schedule for the building, this article is about keeping it alive when the phone rings.
Why emergency repairs crowd out planned work

Emergencies are loud and planned work is quiet. Nobody calls to complain that a filter was not changed this month, so the plan loses every time it competes with a tenant on the phone. In small teams the same pattern shows up again and again:
Urgent requests arrive through every channel. Calls, chats and corridor conversations, with no single maintenance request form that becomes a job, so the technician who answers first drops whatever was planned.
Planned work has no owner and no date. "Check the pumps this month" sits on a list, not in anyone's day.
Nobody sees the balance. The manager cannot say how much of the week went to firefighting, because planned and urgent work live in different places.
Postponed tasks vanish. A visit moved for an emergency is rarely rescheduled; it just disappears until the next breakdown.
Small defects are never logged. The technician notices a dripping valve during a repair but has nowhere to record it, and it comes back later as the next emergency.
None of this is a lack of effort. It is a lack of one place where planned work and urgent repairs compete openly for the same hours.
Planned preventive maintenance vs emergency repairs: what is the difference
Both kinds of work keep the building running, but they behave very differently, and a small team needs to treat them differently.
Planned work
Known in advance, recurring and cheap to do well: inspections, cleaning, adjustments, seasonal start-ups. It can be assigned to a person and a date weeks ahead, and its result can be checked against a standard.
Emergency repairs
Unplanned, time-critical and usually more expensive: a burst pipe, a failed pump, no power on a floor, a door that will not lock at night. They need a quick decision about who goes, and a clear record of what was done.
Deferred defects
The middle ground that decides how many emergencies you get: faults spotted during planned work that are not urgent today. If each one becomes a dated task, it is fixed calmly. If it stays in someone's head, it returns as a breakdown call.
A useful working rule: an emergency is anything that stops people working or threatens safety or property right now. Everything else goes into the plan with an owner and a date. Agree on this definition with tenants and the team, otherwise every request becomes urgent.
How a plan cuts breakdown calls
A plan does not prevent every failure, but it changes which failures you get and how often they surprise you. These steps usually make the difference in a small team:
Turn the list into recurring tasks. Each group of work — the weekly round, monthly filters, quarterly pumps — becomes a repeating task with a date, not a line in a spreadsheet.
Give every task one owner. A technician or a contractor, never "the team".
Protect a slot for planned work. Book it in the calendar like an appointment and decide in advance who covers emergencies during that slot.
Record defects as tasks on the spot. Anything noticed during a round gets an owner and a deadline the same day.
Ask for a photo on key checks. A photo of the cleaned filter or the open panel shows the work was done, not just ticked.
Reschedule, never delete. When an emergency pushes a planned task aside, move it to a new date straight away.
Intervals for each system are only an example here — take them from the equipment manuals, the manufacturer's instructions and your service contractors.
How to handle an emergency request without losing the plan
When the call comes, the goal is a fast, recorded decision rather than a chain of phone calls. Capture who reported it, where it is and what is happening, assign one person who is on shift, and ask for a photo when the job is closed. Then look at what that person had planned for the rest of the day and move it to a new date, so the plan bends instead of breaking.
Over a few weeks the calendar starts to show a pattern. If the same pump or the same section of roof keeps producing emergencies, it belongs in the plan with a shorter interval or a dedicated repair task.
How planned preventive maintenance works in CosaNostra

In CosaNostra the plan and the emergencies share one team calendar. Each group of planned preventive maintenance is a repeating task — weekly, monthly, quarterly or yearly — with an assignee, a time and a checklist. You create it by double-tapping a day or by voice: "Every Monday at 8, plant-room round, assign Pavel, photo of each pump." In the day, week or month view you see the technician's avatar and how far the checklist has progressed.
An emergency request goes in the same way, in seconds. Say "Now, office 305, water leaking from the ceiling, assign Ivan, photo after the repair", or share a screenshot of the tenant's message and the AI fills in who wrote, where and what the problem is. The result is an order with the customer, address, phone, comments, stages and assigned employees, and the technician receives a notification. Shifts — recurring patterns, holidays and replacements — sit in the same calendar, so you can see who is on duty before you assign anyone.
Because planned tasks and urgent orders appear side by side, you can see at a glance how much of the week went to firefighting. There is no separate report to build; you simply look at the week. A checklist item can carry a reference photo, a description and a threshold: the technician closes it with a photo, the AI compares it with the reference and gives a score, and the manager opens only the items below the threshold, comments and sends the work back if needed. Location on the photo is optional. Completed tasks keep their checklist, photos and comments on their date — a working history from which the official logbook can be filled in, not a replacement for it.
Keep the plan visible next to the emergencies
Emergency repairs will never disappear completely, but they should stop deciding what your team does every day. When planned preventive maintenance has dates, owners and photos, and every urgent call is recorded in the same place, the plan survives a bad week and fewer problems arrive as surprises. See how this works for a small building team on the CosaNostra facility maintenance software page.
Frequently asked questions
What is planned preventive maintenance?
Planned preventive maintenance is scheduled work on a building's systems — inspections, cleaning, adjustments and seasonal start-ups — done at fixed intervals so that faults are found before they cause an emergency repair.
What counts as an emergency repair in a building?
An emergency is anything that stops people working or threatens safety or property right now, such as a leak, a power cut on a floor or a failed pump. Everything else should go into the plan with an owner and a date.
How do you keep emergencies from wrecking the maintenance plan?
Record every urgent request in the same calendar as planned work, assign one person who is on shift, and move any planned task the emergency displaced to a new date instead of dropping it.
Does CosaNostra produce maintenance reports?
No. CosaNostra shows planned tasks and urgent orders side by side in the calendar, with checklists, photos and comments on each date. That history is what you use to fill in official logs and reports.



