The Three Gates Before Stage 1
A Stage 1 audit is the first substantive contact between the audit team and the client's management system. It sets the direction for the entire certification cycle. But many certification bodies treat the preparation phase casually, starting Stage 1 before foundational documents have been properly signed and recorded.
This is a problem because accreditation bodies expect every step to be documented and traceable. If you cannot demonstrate that the audit programme was agreed, that every team member declared their impartiality, and that the client approved the audit plan, you have a gap in your paper trail that an AB assessor will find.
Certiva enforces three mandatory gates before a Stage 1 audit can begin. These are not optional checklists. They are system-enforced blockers that prevent the audit from progressing until each one is complete.
Gate 1: The Audit Programme Must Be Signed
The audit programme (FR.222) defines the full certification cycle: initial audit dates, surveillance windows, recertification timing. It is the overarching plan that governs all audit activity for the client.
In a manual process, the audit programme might exist as a Word document or spreadsheet. It might be emailed to the client, maybe signed, maybe not. There is no guarantee it is finalized before the first audit happens.
Consider a CB called "Alpine Certification." Their planner schedules a Stage 1 for a client manufacturing automotive components. The auditor arrives on site, begins the document review, and everything proceeds normally. Six months later, an AB assessor asks to see the signed audit programme for that client. Alpine Certification finds the document, but it was never signed by the client. The programme exists as a draft. The AB raises a finding because the certification cycle started without a formally agreed programme.
In Certiva, the audit programme is generated from live audit-set data and requires a visual signature from both the CB representative and the client before Stage 1 can be initiated. The system will not allow the audit to move forward without this signature. The signed PDF is flattened, timestamped, and stored in the audit set's document history.
Gate 2: Impartiality Declarations Must Be Signed (FR.224)
ISO/IEC 17021-1:2015 requires that every person involved in the audit process declares any potential conflict of interest. This is not a one-time form. Each team member needs a separate impartiality declaration (FR.224) for each audit engagement.
In manual workflows, impartiality declarations are often treated as afterthoughts. A planner sends a template by email, the auditor signs it and sends it back, the planner files it somewhere. Sometimes the declaration is signed after the audit. Sometimes it is never signed at all.
Now imagine "Baltic Standards," a CB with a five-person audit team. One of their auditors previously consulted for a client they are now assigned to audit. Without a signed impartiality declaration, there is no formal record that this conflict was evaluated and managed. If the AB discovers this gap, the entire audit's validity is in question.
Certiva generates an FR.224 form for every team member assigned to the audit. Each person must sign their declaration individually within the platform. The system tracks which declarations are outstanding. If any team member has not signed, the Stage 1 gate remains closed.
Gate 3: The Client Must Sign the Audit Plan
The audit plan (FR.223) details the specific schedule, scope coverage, auditor assignments, and objectives for the upcoming audit. The client needs to review and accept this plan before the audit begins. This is both a professional courtesy and an accreditation expectation.
Without a signed audit plan, there is no formal evidence that the client agreed to the scope, timing, and team composition. Disputes can arise after the audit about what was and was not covered.
A CB called "Summit Assessments" sends an audit plan by email. The client replies "looks good" in the email body. Is that a signed audit plan? An AB assessor would say no. There is no formal signature, no timestamp, no document that can be filed as evidence of agreement.
In Certiva, the audit plan is generated from the audit set data and presented to the client through the client portal. The client reviews it and signs visually within the platform. The signed plan is stored as a flattened PDF with a timestamp. Until the client signs, the Stage 1 gate does not open.
What Happens When You Skip These Gates
In a manual system, nothing stops you from starting Stage 1 without these three documents. The auditor shows up, the audit happens, and the paperwork gets sorted out later, or it does not.
The consequences surface at the worst possible time. During an AB surveillance assessment, the assessor pulls a sample of audit files and checks for completeness. Missing or unsigned documents result in nonconformities against the CB. Multiple findings of this type can escalate to major nonconformities, threatening the CB's accreditation status.
The operational cost is also significant. Staff spend hours chasing signatures after the fact, reconstructing timelines, and explaining gaps in the record.
How System Enforcement Changes the Dynamic
When the gates are enforced by the system, the dynamic shifts entirely. Planners know that they cannot schedule a Stage 1 until the programme, declarations, and plan are signed. This means they handle the paperwork proactively, during the planning phase, rather than reactively after the audit.
Auditors know their impartiality declarations are mandatory before they can access the audit. Clients know the plan needs their signature before the process moves forward.
The result is a complete, signed, timestamped paper trail for every audit, built as a natural part of the workflow rather than as a retroactive compliance exercise.
Three signatures. Three gates. Zero gaps.
Certiva enforces these gates because accreditation does not accept "we meant to get that signed." Book a demo at getcertiva.com to see how system-enforced gates eliminate documentation gaps before they become findings.