Skip to main content

Managing the policy and document library

The library at sidebar Compliance Evidence holds your managed documents and policies. ReFresh ships with 171 pre-built templates and 33 pre-built policy requirements.

Written by Harrison Kennedy

The library at sidebar → Compliance → Evidence holds your managed documents and policies. ReFresh ships with 171 pre-built templates and 33 pre-built policy requirements. Each library item links to controls and frameworks and serves as evidence automatically.

  • The library splits into two sub-pages: Documents and Policies

  • Documents are managed records, registers, plans, and assessments

  • Policies are documents that workers may need to acknowledge or sign

  • Both link to controls and serve as evidence for those controls

  • Each item has a status (Complete, Needs Evidence, Due Soon)


Documents vs Policies

ReFresh splits the library into two sub-pages:

  • Documents (sidebar → Compliance → Evidence → Documents): managed records, registers, plans, assessments, procedures, and other documentation tied to controls and framework requirements

  • Policies (sidebar → Compliance → Evidence → Policies): documents intended to be read and acknowledged or signed by workers, with sign-off tracking

Both sub-pages share the same layout and behaviour; the distinction is whether worker sign-off applies.


What each library row shows

Column

Meaning

Name

The document or policy title

Expires

When the current version expires (or "-" if no expiry set)

Frameworks

Which active frameworks the item satisfies

Status

Complete, Needs Evidence, or Due Soon

The page header shows your overall completion percentage with a Complete / Needs Evidence / Due Soon legend.


Pre-built templates

ReFresh ships with:

  • 171 pre-built document templates covering registers, procedures, assessments, plans, communications, logs, reports, checklists, and training records

  • 33 pre-built policy requirements covering the policies most psychosocial frameworks expect

  • 161 document requirement specifications describing what each document should contain

When a framework is activated, the relevant templates appear in your library with Needs Evidence status. You can fill out a template using its in-platform editor or upload your own document that meets the requirement.


Adding a new document or policy

Open the relevant sub-page (Documents or Policies) and either:

  • Pick a pre-built template and fill it out

  • Upload your own document that satisfies the requirement

Each item moves through Draft → Submitted for review → Current Evidence (see "Uploading evidence to a control", 4.4).


Auto-linking as evidence

When you upload or update a document or policy, it automatically serves as evidence for any control that references it. This means you do not have to attach the same file to multiple controls; the library is the source of truth.


Related articles

  • Uploading evidence to a control (4.4)

  • Policy version control and renewal tracking (4.11)

  • Workers acknowledging policies (4.12)

  • Viewing and acknowledging policies (worker view) (7.6)

Did this answer your question?