Evidence your quality regime. Don't just assert it.

The problem this page is for

Sign-off answers one question: did a qualifying supervisor approve this certificate before it went out. It doesn't answer a different question a scheme assessment, a contract review or an ISO-style quality process will eventually ask: how do you know the certificates going out are consistently right, and can you show it. Most firms answer that with a verbal assurance — "the QS checks them" — because building and running an actual sampling regime by hand, on top of everything else, rarely happens in practice.

What QS Audit does

A supervisor or QS lead pulls a sample of completed certificates and works a structured checklist against each one — the audit itself becomes a record, sitting alongside the certificate it reviewed. That record is what a firm can point to when it needs to demonstrate its own quality regime, rather than describing it.

The add-on ships with 15 starter checklist templates, one per certificate type, across all four certificate families. Any workspace with the add-on can copy a starter and edit it to match how that firm actually works.

How this differs from sign-off

Sign-off and QS Audit are two different controls. Sign-off is the two-stage gate every certificate passes through before it can go out — see how that works on remote QS sign-off. QS Audit runs afterwards, on a sample of certificates that already passed sign-off, checking the work against a checklist rather than approving it for release. One is a release gate; the other is ongoing quality assurance.