The evidence library holds your reusable documents, such as policies, reports, screenshots and certificates. It keeps the exact version of each and shows where it is used. One document can support several requirements across your programmes.
Who can do this
An owner, editor or contributor of your workspace can add documents, edit them, replace their files and link them to requirements. A viewer can read the library.
Find the library
Open Evidence library in the sidebar, under Records & evidence. The counts show All documents, Current, Needs review, Unavailable and No review date. Search by name or description, and filter by Owner, Department and Freshness. Switch between Table and Grid.
Add a document
Press Add evidence.
- Under Add the document, choose the File, and give its Name and Description.
- Under Assign ownership and review, choose the Owner and Department, and set a Review date.
- Under Define scope and save, describe the Document scope: what the document covers and what it does not.
Press Save evidence.
A document is not an assessment, and it is not a malware certificate. Linking it to a requirement does not mark the requirement met.
File checks
Each document shows the state of its file:
- Scanned and integrity checked: the file was scanned for malware at its source, and the stored copy matches the digest recorded at upload.
- Integrity checked: the stored copy matches the digest recorded at upload. It has not been scanned for malware.
- Integrity check pending or Integrity check failed.
- Withdrawn.
A preview is available once the required checks pass and you are allowed to see the file.
On a document
Open a document, or press Open details. From there you can:
- Download current file.
- Edit details & scope. Say why under Reason for this change.
- Replace file. The earlier version stays under the document's versions, and you can preview any of them.
- Manage requirement links, to say which programme requirements it supports.
Where used lists the requirements it is linked to now, and those it was linked to before. Change history lists every change.
Keep it fresh
Set a review date on every document. When the date passes, the document moves to Needs review. A document with no review date is listed under No review date, so it does not drift out of sight.
Common questions
"Can one document support several requirements?" Yes. Link it to each one. Each requirement is still assessed on its own.
"Why is a document unavailable?" Its file has not passed its checks. Open it and press Refresh status.