These are the failures that show up again and again in store estates. None of them is caused by people being careless; they are what happens when the number of sites outgrows the method used to track them.
The fault is reported to a person, not a system
A chiller fails and the store manager phones or messages an area manager, who forwards it to somebody else. By the time it is fixed, nobody can say when it was reported, who attended, or what it cost.
In Prova
The store manager raises it from the shop floor against their own store. It is a work order from the first minute, linked to the building, the unit and the asset, and every status change and approval lands on one timeline through to closure.
One spreadsheet holds compliance for every store
A cell is only as accurate as the last person who touched it. Worse, an empty cell looks exactly like a store with nothing due, so a missing certificate reads as good news.
In Prova
Every obligation for every store sits on one grid, computed at the moment it is read rather than stored by hand. A certificate that has never been filed shows grey, which is a different state from one about to expire showing amber.
A new store is missed for months
A site opens and quietly sits outside the maintenance routines and the compliance register until an audit or an incident finds it.
In Prova
Creating the building is the only manual step. Rule-based segments pick it up on their own, the compliance matrix gains a row, the scope tree gains a leaf so the regional manager can see it, and the country’s business calendar applies to everything inside it.
A contractor’s insurance lapses and work carries on
A regional contractor covering thirty stores keeps picking up jobs because the renewal email went to somebody who was on leave. The exposure only surfaces after an incident.
In Prova
The policy sits on the contractor record with its expiry date. The day it lapses they stop being assignable, so the control is enforced rather than remembered, and the certificate and dates are on file when somebody asks.
The same unit keeps failing and there is no case to replace it
Refrigeration and air conditioning break repeatedly across the estate, but the argument for capital is anecdotal, so the repairs continue.
In Prova
Each breakdown closes with a coded failure record: problem, cause, remedy, severity and downtime. Because everybody codes the same fault the same way, recurrence becomes countable, and the case becomes an interval, a downtime figure and a cost.
Spend per store is only visible at year end
Invoices arrive from many contractors against many sites. Which store is expensive, and which contractor routinely comes in above quote, is not a question anybody can answer in the moment.
In Prova
Costs attach to the job as lines and roll up by building and by trade, with the invoice attached to the line. Labour is valued at the rate in force on the day it was logged, so old jobs are never restated when rates change.