A healthcare estate usually does the work properly. What it struggles with is producing the proof on demand, and showing that the right people were told at the right time.
The evidence exists, but assembling it takes days
Certificates sit on a shared drive, job records in another system and photographs in somebody’s inbox. When an inspector asks about one test, three people stop what they are doing.
In Prova
The chain is one path. Open the compliance cell and the certificate is pinned to it; from the certificate, the work order that produced it; from the work order, the technician’s photographs and the comment thread. Every step was created as a by-product of doing the work, not assembled afterwards.
Twelve findings become one PDF
An annual fire inspection turns up a dozen defects and produces a single report. The individual defects lose their owner and their due date the moment the report is filed.
In Prova
Each finding is its own record, with its own severity, problem code and photograph. Any one of them becomes a corrective work order in a click, assigned to a named person with a due date, and linked back to the finding in both directions.
Nobody can prove the responsible person was warned
A certificate lapses and the review asks who knew. “We always send reminders” is a description of intent, not evidence, and it does not survive scrutiny.
In Prova
Reminder rules fire at a set interval before expiry to a named audience, and the dispatch ledger records who received what and on what date. The answer to the question is a name and a date, not a policy.
Downtime on critical equipment is never measured
Imaging or theatre equipment goes down, gets fixed, and goes down again. Each event is handled well and none of them is ever assembled into a pattern, so the capital case is anecdotal.
In Prova
Every breakdown closes with problem, cause, remedy, severity and downtime, coded from a shared failure catalogue. Because the coding is consistent, mean time between failures and mean time to repair become trends instead of impressions.
Access is all or nothing
A ward manager needs to raise a job but has no business seeing estate-wide spend. A contractor needs their own jobs and nothing else. In practice everybody ends up with more access than they should have, because restricting it is work.
In Prova
Permission is denied by default and granted against a node of the estate tree. One grant on a site covers every building beneath it, now and in future. A contractor scoped to one building sees the jobs assigned to them, and not the compliance matrix or anybody’s costs.
Every obligation runs on a different cycle
Water hygiene, medical gas, fire and electrical all have their own statutory intervals, and standby power is measured in hours run rather than months elapsed. One shared calendar cannot hold all of that.
In Prova
Each obligation category carries its own interval and its own reminder cadence, per building. Maintenance plans can run on usage instead of dates, so a standby generator is serviced when the counter passes its threshold rather than on a date somebody chose.
