Every action recorded, none overwritten


Nothing is overwritten1. An action occurs: Document, verification, alert, training, authorization. 2. It is recorded: With date, owner and outcome. 3. It is corrected: The correction is added as a new record; it does not replace the original. 4. It can be reconstructed: What was known on a past date and who approved with that in view.NOTHING IS OVERWRITTEN1An action occursDocument, verification, alert,training, authorization.2It is recordedWith date, ownerand outcome.3It is correctedThe correction is added as anew record; nothing is replaced.4It can be reconstructedWhat was known on a past dateand who approved with it in view.
Not just what documentation a contractor has today: what documentation it had on the day of the accident, and who had approved its site access with that information in view.

The question that comes up in an audit, an inspection or a lawsuit always takes the same form: what was done with this third party, on what date, who approved it and with what information in view. Answering it requires a record that does not depend on anyone's memory or on the inbox of someone who may no longer work at the company.

Verdana records every action and interaction between the organization and the third party: documents requested, uploaded, approved or rejected with the reason; verifications performed and their outcome; alerts and how they were closed; training and acknowledgments, with version; tasks, controls and evidence; site access authorizations granted and revoked; classification changes; and exceptions with their justification and signer. The design principle is that nothing is overwritten: every correction is added as a new record and the original is preserved.

That makes possible something a well-organized folder cannot: reconstructing what was known on a past date. Not just what documentation a contractor has today, but what documentation it had on the day of the accident, and who had approved its site access with that information in view.