How can we help?

Open the audit template master, choose the audit type, and add the checklist sections and categories, drawing each question from the question bank. Set the objective, frequency and number of audits, then save it. It becomes a reusable template you configure once. See Audit Templates & Checklists.

One template holds the whole checklist for an audit type. When the plan generates an audit, it copies the template's sections and questions into that audit, so every audit of that type starts from the same released checklist. Update the template and future audits pick up the change — you never re-key the questions. See Audit Templates & Checklists.

System and process audits (ISO 9001 and IATF 16949), EHS audits (ISO 14001 and 45001), supplier audits, product and process audits, and customer or certification-body audits. Each audit type gets its own reusable template, and the checklist is configurable for other audit types your organisation runs. See ISO 9001 & IATF 16949 audits.

Pick a plant, a location and an audit objective — which pulls the matching template — then a start date, a frequency and a number of audits. The system generates one audit per occurrence, spacing due dates by the frequency and copying the checklist, address and contacts into each. See Audit Planning & Calendar.

The monthly plan scopes the same engine to a single month, giving auditors and coordinators the near-term calendar of what is due. A calendar view shows planned audits by day, week or month so nothing slips, and a competent auditor is assigned to each audit before it is released. See Audit Planning & Calendar.

A generated plan is routed to the Plant Quality Head for approval by email. Once approved and released, each audit moves from draft to released status and appears on the assigned auditor's worklist, ready to conduct. Nothing is auditable until it is released. See Audit Planning & Calendar.

Each candidate auditor is scored against a competency framework — criteria category to specification to score — and marked eligible when they meet it. The record is sent to the Plant Quality Head to approve and authenticate, so only qualified auditors are eligible for assignment. See Auditor Competency.

An authorisation matrix records which audit types each auditor may conduct — system, EHS, supplier, product and so on. When an audit is assigned, only auditors authorised for that type appear on the list, so an unqualified person is never put on an audit they can't perform. See Auditor Competency.

Supporting evidence — certificates, training records and qualification documents — attaches to each auditor's competency record through the platform's document subsystem, and carries a due date for re-qualification. The evidence lives with the auditor, so an assessor can see why someone was authorised. See Document Control & Evidence.

The auditor's worklist shows their due, released audits, and opening one presents the checklist question by question. It is mobile-friendly for on-floor use — answer each question with a conformance verdict, score, clause number and observations, with answered-versus-total progress shown per section. See Audit Execution & Checklist Entry.

Each question carries a compliance verdict. Anything other than fully complied, an opportunity for improvement, or not-applicable is treated as a non-conformance — so raising an NC is a by-product of honest answering, not a separate step. Each NC carries its clause and a discrepancy description. See Audit Execution & Checklist Entry.

A product or process audit adds parameter checks to each question — a specification, up to five sample observations, and defect A/B/C counts with a remark — so a dimensional or parameter check on the floor is captured against the audit. The product audit report then prints those checks per requirement. See Product & Process Audits.

A finding is anything recorded against a checklist question. A non-conformance is a finding whose verdict is not met — graded major or minor by NC category, carrying a clause number and discrepancy description, attributed to the auditee and auditor, and flagged fresh or repetitive on the NC register. See Findings, NC & CAPA Closure.

Corrective action is an append-only history per finding with due dates and remarks. Closure is a multi-role sign-off: the auditee submits an action plan, then the system coordinator and the auditor verify it. Reminder emails chase overdue actions, and only when every NC is actioned does the audit move to closure. See Findings, NC & CAPA Closure.

Fast Audit closes NCs on its own, but a major non-conformance is the natural entry point to Fast Quality's formal 8D / CAPA workflow. Because both products share one document engine, a finding can escalate into a corrective-action document without re-keying — an upsell, not a dependency. See Fast Quality 8D / CAPA.

The auditee dashboard surfaces pending actions and due audits; the auditor dashboard shows assigned and pending audits with open findings and answered-versus-total progress; the HOD dashboard rolls status up across the plant. Each role sees only what is theirs to act on. See Dashboards & Audit Reports.

The NC summary register lists every non-conformance — audit number, date, type, department, requirement, clause, discrepancy, fresh-versus-repetitive flag, auditee, auditor and per-role closure status — with prepared-by and approved-by blocks. It is the evidence pack a certification body or customer expects to see. See Dashboards & Audit Reports.

Beyond the NC register, there are product and process audit reports with parameter checks, samples and defects, plus supplier and system audit reports and a customer/certification-body audit summary. Status tracking makes planned-versus-conducted-versus-closed visible per plant, type and period. See Dashboards & Audit Reports.