Validation and versions
Manage pending, approved, rejected or needs-review status. Terminal decisions protect evidence from later changes.
Operational loop
Evidence that retains context, integrity and review status.
An operational repository for documents and proof: not an isolated archive, but the connection point between a control, policy, supplier, audit and register.
Evidence repository
Every piece of evidence stays connected to its audit, with category, validation status and expiry date.
What it includes
Retention and legal hold
Record retention period, expiry and legal hold to make the document’s lifecycle conditions explicit.
Requests with multiple controls
Every evidence request can be linked to several controls at once and sent to suppliers, customers or internal recipients.
Acknowledgement with OTP
Ask a recipient to confirm they read a message via email OTP, with or without an attached document: confirmation automatically creates an evidence record as proof of acknowledgement.
How it works
Create the request
Choose the linked controls, the recipient (supplier, customer or internal) and the mode: upload, acknowledgement, or both.
Share the link
The recipient receives a public link with a dedicated token, an expiry date and rate limits.
Collect or confirm
The recipient uploads the document, or confirms they read the message via OTP.
Convert into evidence
The resulting evidence inherits every control linked to the request, and its notes reproduce the original message line by line.
Available with
Modules: Evidence, Third-party suppliers
AuditReady supports compliance work; it does not replace the customer’s assessments, obligations, or decisions.
Connects with
Audits and controls with a clear chain of responsibility.
Define scope, objectives, standards and deadlines. Connect controls, systems, assets, policies and evidence without reconstructing the context for every review.
ExploreTurn a finding into verifiable remediation.
Centralise findings from audits, incidents, tests, privacy or manual entry and keep severity, owner, deadline, action and closure proof together.
ExploreBring RoPA, DPIA, DSAR and breaches into one scope.
GDPR workflows do not stay static templates: they become registers with responsibility, deadlines, links to processing activities and available evidence.
ExploreFrequently asked questions
Can a request be linked to several controls?
Yes, since version 2.0 every evidence request can be linked to multiple controls at once, and all of them are inherited by the resulting evidence.
Is a document always required for acknowledgement?
No. You can request confirmation that a message was read, with no attachment, or combine it with a document.
How is the public link protected?
The link uses a long, random token, has a configurable expiry, and sensitive actions such as sending an OTP, uploading, or confirming are rate-limited.