When something happens on site, the record holds.

• The inspector's question. How is this known hazard controlled, and how do you know it works? Without a record the answer is a description; with one it is a register.
• The insurer's question after an incident. Had this happened before, and what was done about it? Memory answers that badly; dated, signed incidents answer it well.
• The ISO 45001 surveillance audit. Clause 9.1.1 asks you to monitor and measure performance, hazard controls included. The audit pack maps to it and to 6.1.2, 7.5.2, 7.5.3 and 10.2.
• The fine in Slovenia. An employer without a written safety statement with risk assessment faces €2,000–€40,000, its responsible person €500–€4,000 (ZVZD-1, Art. 76). Risk assessments were the labour inspectorate's most frequent finding in 2024: 2,289 violations, about a quarter of all. A register of near misses shows the assessment follows what actually happens on site.

It ends with a method-and-boundaries section that states what the data does not show, and a mapping to ISO 45001 clauses 6.1.2, 7.5.2, 7.5.3, 9.1.1 and 10.2. It carries a document reference, an issue number and the issue history, so a later re-issue is a new version of the same document rather than an unrelated file. The pack prints a fingerprint of the records it covers, which anyone can recompute, and the registry keeps the fingerprint of the issued file itself, so any copy can be checked against it.

Evidence images are purged on a stated schedule — 72 hours by default, and every customer sets its own period. One confirmed incident can be kept for one case, with a named owner and an end date, and never longer than a year. The incident, its fingerprint and the fact of the purge stay. The database is backed up every hour and, with the images, every day; the copies are kept on the registry's server, and we test restoring them every week.

• The record, not the reflex. Prova records and classifies for audit. It does not warn, slow or stop any vehicle, and it is not a safety component. That way it adds evidence to your site without becoming one more safety function on it.
• Built on the current Axis platform. The full package runs on AXIS OS 12.11.72 or a later 12.x, or AXIS OS 13, and Prova has been verified on AXIS OS 13.0.114 (ARTPEC-8). Cameras below that floor, and 32-bit cameras on any AXIS OS 11.11 to 12.x, get the evidence package: the camera's own events (restarts, storage, tampering, settings) and partner-ACAP alerts, signed on the camera.
• Privacy by construction. No faces, no identity, no biometrics. A record carries an object type (person or vehicle), where it was, and when — never who. Colour and clothing attributes the camera reports are dropped at the door and never stored. If Prova ever stops unexpectedly, nothing from its memory is written to the camera.
• Your detection, our evidence. Prova reads what AXIS Object Analytics already sees — people and vehicles — and adds no model of its own. The classes in your records are the ones your Axis camera already trusts, with nothing extra to license, tune or explain. To it a vehicle is a vehicle: a forklift, a van and a truck read alike, so a rule drawn for forklifts fires for every vehicle in its zone.
• Your video stays yours. Prova never uploads, stores or streams footage. One still per incident, anonymised on the camera by your policy — or none at all. Recordings stay in your own system, where they already are. The one exception, and you switch it on: pictures for drawing zones show the whole scene, are kept only in working memory and are deleted after at most 24 hours.
• The picture follows the record. The camera sends the object image as the object leaves the scene, so a brand-new record may show “image pending” for a few minutes. That is by design, and the record says so.
• Nothing goes missing quietly. Stills need Object snapshot switched on in the camera. Prova counts every detection that arrived without one, so a gap is a number you can see, never a silence.
• One clear view per camera. On multi-sensor cameras you choose the channel the rules read, so every record is clear about which lens it speaks for.
• Answers with citations. Ask the registry — “how many incidents in the last seven days?”, “which camera?” — in English, Serbian, Slovenian or German, and every answer cites the records it comes from. Built on your records, not on guesswork.
• Made for your auditor, not instead of one. The audit pack maps incidents to ISO 45001 as a ready starting point for your audit. It supports your auditor's judgement; it is not a certificate.