You cleaned it. Now prove it.
Before-and-after evidence tied to the hood it came from, grease readings that mean something, and a certificate your customer can forward to their insurer without being asked what it is.
The evidence is the deliverable, and it lives on a phone
The crew works overnight, in a basement, with a bucket and a headlamp. Photos land in a camera roll. Depth readings get remembered, not written down. Two weeks later a restaurant group asks for last month's report on three sites, and somebody spends an afternoon reconstructing it from memory and a text thread.
That afternoon is the actual cost of not having a system — and it arrives exactly when you are busiest.
Photos with no home
A hundred pictures a night, none of them attached to a hood, a job or a date that anyone can check.
No signal in the plant room
Most software assumes a connection. Yours does not have one, so the app has to keep working and catch up later.
The inaccessible run
Every building has one. If it is not written down with a photograph, the gap becomes yours the day there is a fire.
Built for gloves, grease and no reception
- Scan the hood, start the job
- A tag on the equipment opens the right checklist for that system, on that site, under the rules that govern it.
- Before and after, paired
- Each shot is bound to the hood and the field it answers, so the pair reads as one comparison on the report rather than two loose pictures.
- Depth readings in your units
- Mils or millimetres — whichever the gauge in the van reads. Stored once, printed either way.
- Uploads that finish themselves
- Photos keep uploading after the app is closed and resume when signal comes back. The pending count is always visible.
What lands in your customer's inbox
One link, no login, nothing to install. It opens on the building manager's phone, on the insurer's desktop, and on whatever the fire inspector is carrying.
It carries the things people ask for later
Not because a document looks better with more on it, but because these are the specific questions that get asked when a record is challenged.
- Which code, which edition
- Resolved for the site and frozen to the job when work started, so a later amendment cannot rewrite what this record says.
- Areas not cleaned
- A reason from a fixed list and a photograph for each — printed as prominently as the pass.
- Who did the work
- The technician, their certification number, and the statement they signed on site.
- Proof it has not changed
- A content hash on the face of the document, and an independent timestamp on the digest.
The schedule is the reason to open it
Cleaning frequency follows the equipment — solid fuel is not the same clock as a low-volume kitchen, and the code says so. Provev works out the next due date per system from what the technician recorded, and keeps a calendar of what is coming and what has slipped.
Due and overdue, per system
Not per customer. A site with three hoods on two schedules is two dates, and both of them are yours to book.
Multi-site customers
Restaurant groups get one view across every location, which is usually the thing that wins the contract in the first place.
Your archive, kept
Every record you have ever issued, searchable, with the evidence attached. It stays readable whether or not you are still a customer.