Back to help

Evidence guide

Build an evidence vault that is useful when it is reviewed.

Evidence should show what happened, when it happened and which task, document or register it supports. Keep files private, named clearly and linked where possible.

Recommended flow

1

Choose the record

Upload certificates, policies, screenshots, reports, minutes or other supporting files.

2

Link it

Attach the file to a task or management-system record so the context is not lost.

3

Add expiry dates

Use expiry dates for certificates, insurance, policies and records that need review.

4

Review the vault

Use the evidence page to check expired, expiring and archived files.

What belongs in evidence

Evidence records demonstrate that work has been done or checked.

  • Certificates, insurance documents, approved policies and review records.
  • Screenshots, confirmations, meeting minutes and signed-off reports.
  • Completed inspection forms, training records and audit evidence.
  • Supporting files for ISO registers, findings, actions and controlled documents.

Keep the vault tidy

A tidy vault saves time when a manager, adviser or auditor asks for proof.

  • Use meaningful filenames before upload where possible.
  • Attach files to the task or record they support rather than leaving everything unlinked.
  • Archive old evidence instead of deleting it when it may still be useful for history.
  • Set expiry dates when the evidence should be renewed or reviewed later.

Related guides

Important boundary

Obligary supports organisation and evidence. It does not replace professional judgement.

Use Obligary to manage tasks, owners, reminders, documents, evidence and reports. Your organisation remains responsible for deciding what applies and taking legal, regulatory or certification advice where needed.