Compliance and audit evidence
Know who has read the current version.
See who has read and confirmed the current version of every procedure, and show it to an auditor.
SOP requirements
Six things every SOP needs
And where each one lives in How2MapIt.
- Define the processActivities, owners, warnings and timeframes.Who, when, how and why on every activity
- Name who owns itA role for every activity.Roles and teams, never names
- Make it visiblePublished to everyone it applies to.Learn your work, by role
- Record who has read itEach user confirms each version.Read and confirm, per version
- Follow the timeframesActions inside the required periods.Control tests and reviews, with due dates
- Keep the evidenceProcess and confirmations, on record.Version history and confirmations
Risks, controls and rules
Risks and rules where the work happens
Attach each risk, control and rule to the exact activity it applies to, so the people doing the work see it while they work.
Establish the legal entity
Version history
A record an auditor can follow
- Version 10 · current
- Version 5
- Earlier
Which version was in force, and when
Every version kept, with who published it and when.
Who confirmed which version
Per user, per version. Changes are confirmed again.
Evidence without edit rights
Auditors get read-only access to confirmations.
Attestation and evidence
Proof the auditor can check
Export every confirmation as a single file for your auditor. Drop it back in later to prove it hasn’t been altered. The check runs in your browser and nothing is uploaded.
All features
Compliance, feature by feature
Read confirmations
Per user, per activity, per version. A confirmation can’t be undone, and changed activities are confirmed again.
See how it works →Risks, controls and rules
On the activity they apply to, with scores, appetite, treatment and a heat map. Paste in the register you have.
See how it works →Evidence packs
For the whole company, a department, a process or a sample, with a check that shows it hasn’t been altered.
See how it works →- Review and publishAuthors submit, reviewers approve on the web or a phone, readers are told. A publish without review is shown.→
- Versions and historyEvery version of a process and every change to a register entry kept. Compare and restore.→
- Control testsRecord each test as effective or deficient, with when it is next due.
- Owners and review datesAn owner, authors and reviewers for each process. Processes and register entries come due for review, with reminders.
- Who is currentWho has confirmed what, by user, process and department, with CSV downloads.→