A compliance register is only worth what its worst row is worth. VCMS holds the documents, watches the dates, records the acknowledgements and classifies incidents the way a work health and safety regulator classifies them.
Optical character recognition reads the fields off an upload and puts them in front of a reviewer. It is a typing aid, not an approver. The platform never clears a document on its own.
An incident form whose categories do not match the ones a regulator recognises produces a record that has to be entered again somewhere else. These are the categories in the product.
Severity is recorded alongside, the person involved is classified as visitor, contractor, employee or other, investigation status is tracked, and the report renders to PDF. Nominated incident contacts are configurable per organisation, so the portal tells a contractor who to call rather than showing a platform default.
Licences, insurances and certificates, reviewed by a person and tracked to expiry.
What a trade needs, and what a particular site needs on top of it.
Author the content, assign it, and hold access until it is passed.
Near miss, injury or illness, dangerous incident, security breach, property damage, environmental.
Publish the rules for a site and record who accepted which version, when.
Collecting identity evidence creates an obligation to dispose of it. VCMS treats that as a feature rather than a policy document.
Identity photographs and selfies live in their own store keyed to the verification, so disposal deletes rows rather than relying on somebody remembering to null two columns.
Retention periods per class of data, with a disposal cycle that runs against them and a record of what it disposed of.
Everything held about one person, exported on request or purged on request, as a first-class operation rather than a database session.
Which trades need what, at which sites, and what happens on the day a certificate lapses.
