An ISO 9001 audit, from setup to finished report.

An ISO 9001 audit platform: an auditor picks the standard and the sector, runs the audit on a phone on site, and exports the report and the non-conformance notice.

Client
ISO 9001 audit platform
Industry
Compliance & legal ops
Standard
ISO 9001
Surfaces
Web · mobile web
Our role
Design and build

The standard is the structure of the audit.

An ISO 9001 audit is a day of asking questions and recording what was observed. Around it sits administration: building the question list, typing evidence into a template afterwards, following a non-conformance through to closure, and formatting the report.

The platform uses the standard itself as the structure. The auditor picks the standard and the sector, and the clause framework and process list come with it. From then on the auditor is answering questions, not building a document.

The report is generated from the audit record, and can be exported to PDF, printed, or emailed once the last question is answered.


Set the audit up once.

A five-step wizard: the standard, the EA code that classifies the organization's sector, the audit details, the processes in scope, and a review. The sector choice determines the processes offered, so the question set is in place before the audit starts.

  • The ISO 9001:2015 clause framework, built in
  • EA code sector list, searchable by name or number
  • Processes pre-loaded from the sector, editable in step four
  • Review before anything is committed

Run it on site, on a phone.

Each question carries its clause reference. Evidence is typed a sentence at a time — one sentence, one observation — with photo capture for the things that are faster to show than to write. An evidence score measures how much objective evidence has been captured, so thin answers are flagged during the audit.

  • Clause reference on every question
  • Photo capture alongside written evidence
  • Evidence score, updated as you write
  • Conformity called yes or no, per question

A “no” opens the non-conformance, there and then.

Answer no and the question turns into a non-conformance block: rationale, the responsible person and the planned correction recorded, raised as open against the process it came from. It stays visible in the report sidebar until it is closed, and it exports as its own notice for the auditee — separate from the report, because that is the document they have to act on.


The report is the audit, rendered.

Findings at a glance — completion, evidence score, program progress, open and closed non-conformances — over an executive summary. Three views of the same data: the report itself, an audit matrix, and a program summary across the audit cycle.

  • Export to PDF, print, or email the report
  • Export the non-conformance notice on its own
  • Print the checklist for a paper-first site
  • Audit matrix and program summary alongside the report
Findings at a glance, on a phone

Got a process that still runs on a Word template?

Tell us what the work actually looks like on the day. We'll tell you what's worth building and what isn't.