The Decision Form Is Not Just a Signature Page
The certification decision form (FR.233) is the document that records the formal decision to grant, maintain, renew, or refuse certification. It is the single most important document in the certification process because it represents the point at which the CB formally attests that the client's management system meets the requirements of the applicable standard.
This document is not a formality. It is evidence that the CB followed a structured, impartial, competent decision-making process as required by ISO/IEC 17021-1:2015 Clause 9.5. And the order in which signatures appear on this document matters.
The Required Signing Order
The FR.233 decision form follows a specific sequence:
- 1. Committee members sign first. Each member of the certification decision committee reviews the audit file, the stage reports, the NC closure records, and the auditor's recommendation. They form their independent judgment and sign the decision form to indicate their concurrence (or dissent).
- 2. The certification manager signs last. The CM reviews the committee's input, confirms that the process was followed correctly, and signs to finalize the decision. The CM's signature is the formal authorization to proceed with certificate issuance.
This order exists for a reason. The committee's role is to provide independent review. If the certification manager signs first, the committee members are no longer providing independent judgment. They are confirming a decision that has already been authorized. The entire purpose of the committee review is undermined.
What Happens When the Order Is Wrong
Consider "Atlas Certification," a CB with a three-member decision committee and a certification manager. The CM is under pressure to issue certificates quickly. A client has been waiting for their ISO 9001 certificate and is getting impatient.
The Stage 2 report is complete. The NCs are closed. The file looks clean. The CM reviews it, sees no issues, and signs the FR.233 form. Then the CM sends it to the committee members for their signatures.
All three committee members sign. The certificate is issued. Everyone is happy.
Six months later, an AB assessor reviews this file. They look at the FR.233 and check the timestamps. The CM signed at 09:14 on March 3rd. Committee Member A signed at 14:22 on March 3rd. Committee Member B signed at 10:05 on March 4th. Committee Member C signed at 16:30 on March 4th.
The CM signed before any committee member. The assessor raises a major nonconformity against the CB's certification decision process. The finding states that the certification decision was not made by an independent committee as required by Clause 9.5, because the authorizing signature preceded the committee review.
Atlas Certification must now demonstrate that they have corrected their process, which may include re-reviewing the affected decisions. Depending on the AB's assessment, the certificates issued under this flawed process may need to be re-evaluated.
Why Manual Systems Cannot Enforce This
In a manual system, the decision form is typically a PDF or Word document. Someone fills it in, saves it, and emails it to the signers. There is nothing preventing the CM from signing first. There is nothing preventing signers from signing out of order. The document does not know or care who signs when.
Even if the CB has a procedure that specifies the signing order, procedures without enforcement are just guidelines. Under time pressure, with impatient clients and busy schedules, the procedure gets bypassed. Not maliciously, just practically. The CM is available now. The committee members will sign later. What difference does it make?
The difference is that the decision is procedurally invalid. And that difference matters when the AB assessor reviews the file.
How Certiva Enforces the Signing Order
In Certiva, the FR.233 decision form has a defined signing chain. Committee members are presented with the form first. They can review the audit file, examine the reports and NC records, and sign the form within the platform.
The certification manager's signature field is locked until every assigned committee member has signed. The CM literally cannot sign the form until the committee review is complete. There is no override. There is no workaround. The system enforces the sequence.
This means the CM never has to worry about accidentally signing out of order. The system handles it. And when the AB assessor reviews the file, the timestamps will always show the correct sequence: committee members first, certification manager last.
The Broader Principle: Signing Chains as Process Enforcement
The FR.233 signing order is one example of a broader principle in Certiva: signing chains encode process rules. Every document with multiple signers has a defined order, and the system enforces that order.
The audit plan requires the lead auditor to sign before the client. The audit programme requires the CB to sign before the client. The impartiality declaration requires the individual auditor to sign.
These are not arbitrary constraints. Each signing order reflects a process requirement. The lead auditor must finalize the plan before the client can approve it. The CB must commit to the programme before asking the client to agree.
By encoding these rules in the signing chain, Certiva eliminates an entire category of procedural errors. Staff do not need to memorize which document requires which signing order. The system presents the right signature field to the right person at the right time.
The Cost of Getting It Wrong
A procedurally invalid certification decision is one of the most serious findings an AB can raise against a CB. It calls into question whether the CB's certifications are based on competent, impartial review. It can trigger a review of all decisions made under the flawed process. In severe cases, it can lead to suspension of the CB's accreditation for the affected standard.
All of this because someone signed in the wrong order.
The signing order is not a suggestion. It is a requirement.
Certiva enforces it so your team never gets it wrong. See how at getcertiva.com.