Recurring scrutiny, with findings that turn into corrective work.
Inspections run on a recurring cycle: fire, elevator, boiler, and whatever else your jurisdiction requires. Each inspection produces findings, and each finding is one defect with its own severity, problem code and photo evidence. A finding becomes a corrective work order in one step, and that work order stays linked back to the finding that raised it.
The gap that costs money sits between the inspection report and the repair. A PDF from an inspector lists twelve defects and then sits in an inbox. In Prova each defect is a live record with an owner and a status, so at the next audit you can show which findings were closed, by whom, and with what proof attached.
The inspections register, with the authority responsible for each inspection.
How it works
Inspection
A recurring cycle per building and obligation type, on the same scheduling machinery as maintenance plans.
Finding
One defect each: severity, problem code, photo evidence.
Corrective work order
Raised from the finding in one click, linked in both directions.
Photo verification
Statutory inspection work orders require photo evidence before they can be closed.
In practice
The annual fire inspection at Milan Ovest turns up twelve defects.
The fire inspection cycle is configured to the Italian statutory interval, and raises its own work order when due.
The work order requires photo evidence before it can be closed.
The inspector attends and records twelve findings. Each is a separate record with its own severity, problem code and photograph, not twelve lines in one report.
Finding 7 is a blocked fire escape. It becomes a corrective work order in one click, assigned to the site manager, due within 48 hours.
It closes with a photograph of the cleared escape, still linked back to finding 7 in both directions.
The remaining eleven findings run their own course, each with an owner and a status.
At next year’s inspection the inspector asks what happened to finding 7. You show the corrective job, the date it closed, who closed it and the photograph. The alternative is a PDF in an inbox and the phrase “I think so”, which is not a compliance position.
Illustrative walkthrough. Not a customer record.
What we will show you in a demo
Twelve defects as twelve live records with owners and statuses, instead of one PDF.
What happens when somebody tries to close an inspection work order without photo evidence.
Which findings from the last cycle were closed, by whom, and with what proof attached.
Findings are recorded against the inspection regardless of who performed it. Contractors sit in the same directory as your own staff.
Does it prove the work was done, or only that it was logged?
Photo evidence attaches at the finding, and closure requires it where you have configured that. The photo is attached to the record, not filed near it.
Can we use our own defect vocabulary?
Problem codes come from a failure code catalogue your organisation owns and edits.
Insurance, contracts and spending limits as live records with dates on them, not folders somebody forgot to open. Contractors and suppliers sit in one central register with their service agreements,…
Every euro attributed, and a changed number that leaves a trace. Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building…
Proof attached to the thing it proves, not merely filed somewhere near it. Photos attach at the exact place they belong: the finding, the job, the asset. They are captioned,…
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
English (UK)
