Every file the audit programme touches lives on the platform's document subsystem. Reusable checklist templates, the evidence files attached to findings, auditor competency certificates and training records, and the generated audit reports all use the same upload and download handlers — version-controlled, linked to the audit or the auditor, and reachable from the record they belong to. Reports are generated as HTML and PDF snapshots. Nothing is filed in a folder off to the side.
Document control has two jobs: hold what auditors and auditees upload, and produce the records an audit generates. On the shared platform both are the same subsystem — the template you upload, the evidence a finding carries and the closure report you generate are one linked set of documents, not files scattered across drives and mailboxes.
Because the audit and its files sit on the same document subsystem, each step attaches to the record the next step reads. The template, the evidence and the report are all reachable from the audit they belong to.
Every item below is a native part of the shared document engine — the template, the evidence, the certificate and the report are the same linked documents read across the suite, not files copied into a separate archive.
Fast Audit doesn't keep a bolt-on file store. Checklist templates, evidence files against findings and auditor certificates all upload through the platform's document subsystem — the same upload and download handlers as every document on the platform — and each attaches to the record it belongs to. A template lives against its audit type, evidence lives against the finding, and it stays reachable from the checklist entry the auditor ran.
What an audit report showed the day it closed is the record the certification body relies on. Fast Audit generates the product/process audit report, the supplier and system audit reports and the NC summary as HTML and PDF snapshots, re-served from the document store. Because it's a snapshot, it doesn't change as later data moves — the closed report stays exactly as signed, alongside the dashboards and reports that show the live picture.
When templates sit on a drive, evidence in a mailbox and reports in a folder, the audit trail is only as good as the person who remembers where things went. On the shared document engine there is no side archive: the template, the evidence, the certificate and the report are the same linked documents, and one party master and one user master are shared across the suite. The auditee on a finding, the auditor on a certificate and the supplier on a report are the same records everything else uses — so a file the audit links is the same file Fast Quality reads when a finding escalates to an 8D.
The reusable question bank per standard and audit type, held on the document subsystem, version-controlled and copied into each planned audit.
Photos, documents and records that back up a finding upload through the same handlers and attach to the finding — evidence and NC together.
Auditor certificates and training records stored against the competency record, beside criteria scores and authorised audit types.
Product/process, supplier and system audit reports and the NC summary generated as HTML/PDF snapshots — the record of what closed, re-served from the store.
Every file is version-controlled and linked to the audit, finding or auditor it belongs to, so the audit trail is intact and the current version is never in doubt.
One party master and one user master across the suite, so the file the audit links is the same file Fast Quality reads on escalation.
In a 30-minute demo we'll upload a checklist template, attach evidence to a finding, link an auditor certificate, and generate a closure report as an HTML/PDF snapshot — all on one document store.
