FEATURES · POLICIES, DOCUMENTS & EVIDENCE

Policies that get read and acknowledged.

Policies go through a defined approval workflow, are versioned and acknowledged by employees. Documents and evidence are kept with all their versions in the same place.

Request a demo Try it free

WHAT YOU GET

Approval workflow per policy, never self-approval
Acknowledgement by employees, with the rate on the dashboard
Adopt existing documents that are already approved
Documents & evidence with unchangeable versions

Approval workflow under the four-eyes principle

Every policy has its own approval workflow with approvers in a fixed order. A new version only takes effect once all approvers have approved it; the person who submitted it cannot approve it themselves.

Draft, In review, Valid, Superseded
Rejection with a reason and comment
Submission blocked if nobody else could approve

View of top management: notice “Approve version v1” with sign or reject, below it the submitted version with the reason for the change and the pending signature. — The approver sees the reason for the change and the file, and signs or rejects with a reason.

Acknowledgement by employees

Anyone who needs to read a policy gets a task and confirms that they have read it. The dashboard shows how many acknowledgements are missing.

Adopt existing approvals

If you have already approved policies outside Varmo, you adopt the first version with its date and evidence. The four-eyes principle applies here too: a second person from the approver role confirms the adoption, and only then does the version take effect.

Documents & evidence

Procedures, contracts, reports and evidence are kept with all their versions in one archive. A version is approved under the four-eyes principle and stays unchanged afterwards; documents can be linked to requirements as evidence.

Versions with status and responsible person
PDF, Office files and images up to 50 MB
Archive instead of delete for evidence
Every file is scanned for malware before it is saved

Versions of a piece of evidence: version 1 with the status “Valid”, the person who recorded it, the date and the shield icon noting that the file was scanned for malware. — Every file is scanned for malware before it is saved; the shield icon records this.

Roles & approvals
Who may approve.
Audits & ISMS governance
Training and acknowledgement as part of governance.

Frequently asked questions

Can we keep using our Word documents?

Yes. A policy can consist of a file (PDF or DOCX) or a link. Varmo manages approval, versions and acknowledgement; you write the content as usual.

How close are you to ISO/IEC 27001?

In a personal demo, we show you the way to the readiness report, with no obligation. Or try it free for 30 days with every feature.