Profile
An audit is mostly a matter of collecting evidence that already exists but is scattered.
As a result, the weeks before an audit take a disproportionate amount of time spent searching, while the work itself was done long ago.
The Audit Preparer keeps track, for each requirement in the standard, of which evidence exists, what is out of date and what is missing.
What it does, step by step
- Read in the requirementsThe requirements of the standard that applies to you.
- Link the evidenceWhich document, record or log belongs to which requirement.
- Flag gaps and outdated evidenceMissing evidence, expired documents and records that stopped being kept.
- Assign actionsTo the process owner, with a deadline.
- Prepare the fileOrganised by requirement, so the auditor does not have to search.
Works with these systems
SharePoint
OneDrive
Confluence
Jira
Jira Service Management
- Databases
- APIs
- Microsoft 365
Is your system not listed? We can connect any system, even if there is no standard integration. View all integrations.
What runs automatically and what does not
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
- What can happen automatically.
- What is put forward for approval first.
- When a person is brought in.
- What information is stored.
- How actions are logged.
Is this a fit for your organisation?
A good fit if
- Organisations with ISO 9001, ISO 27001 or a similar certification.
- Companies with recurring audits or customer audits.
- Situations where preparation is always a peak in workload.
Less of a fit if
- Carrying out the audit itself.
- Judging whether a control is effective: that is a judgement.
What it can deliver
- Less of a rush before an audit.
- Knowing sooner where evidence is missing.
- A file that is in order all year round.
Directions, not promises. As soon as there is evidence from a client project, it will appear here as a substantiated result.
Frequently asked questions
Can an AI employee help with an ISO 27001 audit?
With the preparation, yes: collecting evidence per requirement, flagging what is out of date and assigning actions. The audit itself, and the judgement on whether a control works, stay with your auditor and your quality manager.
Does it know which evidence belongs to which requirement?
Once it is set up, yes. We make that mapping together with your quality manager, because it is specific to your organisation. A standard mapping would give false certainty.
Does it flag issues in between, or only before an audit?
Continuously, and that is the point. You want to know about records that stopped being kept in the month itself, not three weeks before the audit.
Does this also work for customer audits and supplier questionnaires?
Yes. That is often the same evidence in a different format, and that is exactly where a lot of duplicate work goes.
How to put this to work
- 1A short callTogether we look at your process and your systems, and whether this task is the best place to start.
- 2Set up on your rulesIntegrations with your own systems, and agreeing what may run automatically and what a person approves.
- 3Measure and adjustFirst alongside your team, only then on its own. We look at what it delivers and adjust.