Wiki or platform
Keep your wiki. Move the evidence work.
Wiki pages and lists are quick to build. But approvals, deadlines and evidence are kept up by hand. Complass takes that over, and your filing stays.
Built in-house or Complass
What changes day to day, point by point.
| Topic | Built in your wiki | With Complass |
|---|---|---|
| Approving documents | Approval by mail or comment, the version sits in the file name. | Versions with approval and a reason for the change, with a four-eyes principle you can switch off. |
| Read and understood | A group email and a list of who has confirmed. | A distribution list per document, confirmation per release, a reminder after 7 days, exportable as evidence. |
| Review | The review date lives in one person’s calendar. | Next review per document, a reminder 30 days ahead and when overdue. |
| Requirements | Standards are copied into pages and maintained by hand. | Frameworks are ready. One measure counts for every framework that requires it. |
| Evidence | Files in folders. Nobody knows for sure whether they are still valid. | Evidence sits at the requirement, with a validity date and a reminder before it expires. |
| Who changed what? | The page history shows text, not approvals. | Every release is stored immutably with a SHA-256 checksum, plus a change history per field. |
| Audit | Pages are exported and gathered just before the audit. | Audit export as a ZIP with checksums, straight from the current state. |
Your filing stays where it is
Complass does not have to store everything itself. Evidence can stay where your team finds it today.
Evidence as a link
Instead of uploading a file, link to it in your own filing, for example SharePoint, OneDrive or your intranet. Complass stores the as-of date and the review date.
Network drives
Paths such as \\server\share are stored as text with a copy button.
For the auditor
Auditors see the list of links with as-of and review dates. For auditors without access to your intranet, you attach a copy.
Which fits you?
Building it yourself is enough when …
- you maintain one framework with a few documents.
- no external audit is coming up.
- one person keeps track and has a stand-in.
Complass fits better when …
- several frameworks require the same measures.
- approvals, reviews and read confirmations have to be provable.
- auditors should see the current state without anyone gathering pages.
You do not have to retype existing lists: Complass takes over CSV and XLSX files with a preview before anything is saved.
Try Complass with your own data
Set up your trial yourself, with a sample project per framework if you like. If you would rather see Complass first, request a demo.