Walk into the audit with the proof already gathered.

Every approval and acknowledgment lands on the record as you work, each tied to its version. When an auditor, a surveyor or a customer’s reviewer asks, the answer is a filter and an export away.

Start a TrialBook a Demo (opens in a new tab)

30-day trialUnlimited free viewersNo credit card required

From the request to the answer, in five steps

The evidence builds as you work. Each step links to the part of the product that keeps it.

  1. 01

    Approvals on record

    Every approval is logged with the person and the time, step by step, for every version.

    Approval Workflows
  2. 02

    Acknowledgments by person and version

    Each record holds the name and email, the version, the time, the statement and the IP address.

    Policy Distribution and Access
  3. 03

    Evidence beside the policy

    Attach training records, certificates and inspection results to the policy they prove.

    Audit Trail and Export
  4. 04

    Every change logged

    Versions, tag and access changes, reminders sent and cancelled requests with their reasons all land in the log.

    Audit Trail and Export
  5. 05

    Hand it over

    Filter by date, person or action and export a PDF or CSV, or give the auditor a one-time code to open the document.

    External Viewers

The version on any date

When the question is what the policy said at the time, the answer is in the version history.

Evidence kept with the policy

Training records, certificates and inspection results sit beside the policy they prove.

Who asks to see it

Inside the company and outside it, people ask the same question: show me the current policy, who approved it and who has it.

Inside the company

  • Internal auditThe same evidence the external auditor will ask for, ahead of time.
  • The board and audit committeeThat policies are approved, current and acknowledged.
  • LegalWhich version was in force on a date, and who had it.
  • Department headsWhich of their policies are due for review.

Outside it

SOC 2, Trust Services Criteria CC1.1, CC2.2

Communication and acknowledgment

Auditors sample new hires for code of conduct acknowledgment and look for evidence that policies were communicated to the people they cover.

  • Acknowledgments by person and version
  • The sample filtered by date
  • Exported as a PDF or CSV

ISO 9001 and ISO/IEC 27001, clause 7.5

Documented information

Documents approved, identified by version, available where needed and kept as evidence, with changes controlled.

  • Every version kept with its dates
  • Approvals on record
  • Evidence attached to the policy

US DOJ, Evaluation of Corporate Compliance Programs

Communication of policies

Prosecutors ask how policies were communicated to all employees and relevant third parties, and how the company confirms it.

  • Every policy sent to the people it covers
  • Third parties included as external users
  • Each acknowledgment on record

Wherever you are inspected

Inspections and surveys

Inspectors, surveyors and assessors in every country ask for the current written program and proof each person received it.

  • The current version, ready to show
  • Proof of receipt by person
  • Every earlier version kept

Bring your own rules

Your region’s laws, the standards your customers ask for, and your own house rules. Write each one as a policy, approve it, and send it to the people it covers.

  • Laws of every country and state you work in
  • Standards and certifications
  • Customer and contract requirements
  • Your own policies and procedures
Check what your laws requirePolicy and Compliance lists the documents a business has to have in writing, by country and business type.Check your laws (opens in a new tab)

For every audit, survey and review

The event changes. The proof you show does not.

  • SOC 2 audit
  • ISO certification audit
  • Customer security review
  • Regulatory inspection
  • Accreditation survey
  • Insurance renewal
  • Due diligence
  • Internal audit
  • Employment claim
  • Supplier audit

Who can do what

EditorsSee and export the log of their own documents.
AdminsSee the workspace log across every document, and export it.
AuditorsOpen a single document with a one-time code, without an account.
ViewersAcknowledge what covers them. Their records stay after they leave.

Need help writing the policies? Find a consultant for your standard.

Questions

Can I prove acknowledgment for an audit?

Yes. Filter the record by date, person or action and export a PDF or CSV, with each person’s version, time and statement.

Can the auditor see the policy without an account?

Yes. Add them as a one-time viewer and they open that document with a one-time code.

Can I show which version was current on a date?

Yes. Every version is kept with its dates, for 3 months on Startup and 3 years on Scale, and acknowledgments are recorded by version.

Can we bring our own standard?

Yes. Write the policies your standard calls for and run them through the same cycle. Need help? Find a consultant for your standard.

Can we attach evidence?

Yes. Attach training records, certificates and inspection results to the policy they prove.

What happens to records when people leave?

Their completed acknowledgments stay on record.

Try AllyMatter free for 30 days

  • No credit card needed
  • 30-day money-back guarantee
  • Free migration on yearly plans
Start a TrialBook a Demo (opens in a new tab)