The Email Application Workflow
At most certification bodies, the application process starts with an email. A prospective client writes to the CB expressing interest in ISO 9001 certification. An admin downloads the application form from a shared drive, fills in what they can from the email, and sends it back for completion. The client fills it in — sometimes by hand, sometimes in a Word document — and emails it back.
The admin then opens the returned form and begins re-keying the information into whatever system the CB uses: a spreadsheet, a CRM, a database. Company name, address, number of employees, scope description, standards requested, number of sites. Every field typed by hand.
Then the downstream documents begin. The quotation needs the same company details. The contract needs the same scope description. The audit plan needs the same employee count and site information. Each document is another opportunity to introduce a transcription error that propagates through the entire certification lifecycle.
This process is slow, error-prone, and entirely avoidable.
Where Transcription Errors Do Damage
A transcription error in the application phase is not a one-time mistake. It is a seed that grows into every document the CB produces for that client.
Consider "Pinnacle Certification Services." An admin re-keys a client's employee count as 180 instead of 108. This error flows into the audit time calculation, which produces an overestimate. The quotation is too high. The client questions the price, causing delays. When the error is eventually caught, the quotation must be revised, the audit time recalculated, and the plan updated. Hours of work caused by one transposed digit.
Or consider a scope description that is slightly wrong. The client's application says "design and manufacture of industrial valves." The admin keys it in as "manufacture of industrial valves," dropping the design function. The scope exclusion is now incorrect. The audit plan does not cover design processes. The Stage 1 report describes the wrong scope. The committee reviews an inaccurate file. The certificate, if issued, does not reflect the client's actual activities.
These are not hypothetical scenarios. They are the daily reality of CBs that rely on manual data entry.
Certiva's Online Application Form
Certiva replaces the email-based application workflow with a public, branded, self-service application form. No login is required. The prospective client navigates to the form, which is accessible from the CB's website, and completes it directly.
The form is structured to capture every piece of information the CB needs to begin the certification process:
Standard Selection
The applicant selects which standards they are seeking certification for. The available standards match the CB's accredited scope. Multi-standard applications are supported from a single form submission.
Company Details
Legal name, trade name, address, contact person, phone, email, website, tax identification — all entered once by the person who knows the information best: the applicant.
Standard-Specific Fields
This is where Certiva's form diverges from generic contact forms. When the applicant selects a standard, the form dynamically presents fields that are specific to that standard's audit time calculation methodology.
For standards governed by IAF MD 5, the form collects the personnel breakdown required for audit time calculation: total employees, employees in administrative roles, employees in production or service delivery, part-time employee counts, and shift patterns. This is the data that drives the audit time bands, and collecting it accurately at intake prevents the re-keying errors that produce incorrect calculations downstream.
For ISO 27001, the form may collect additional information about IT complexity that feeds into the ISMS category determination. For ISO 22000, food safety-specific inputs are captured. Each standard's intake requirements are reflected in the form.
Consultant Referral Code
If the applicant was referred by a consultant, they enter the consultant's unique referral code. This code links the application to the referring consultant's profile, enabling attribution tracking without any manual intervention by CB staff.
What Happens on Submission
When the applicant submits the form, Certiva performs several automated actions:
- 1. Audit Set Creation. The system creates a new audit set for the applicant, which becomes the container for all certification activities related to this client and standard combination.
- 2. Stage Auto-Creation. The initial audit stages (Stage 1, Stage 2) are automatically provisioned within the audit set. The planner does not need to manually set up the stage structure.
- 3. Client Portal Account Provisioning. The applicant receives credentials for the client portal, where they can track the status of their application, upload additional documents, and communicate with the CB. This happens automatically — no admin intervention required.
- 4. Planner Queue Entry. The new application appears in the planner's work queue, ready for review. The planner sees the complete application data, already structured and validated, and can begin the quotation and planning process immediately.
Zero Re-Keying
The key outcome is that no human at the CB types the client's information. The data flows from the applicant's keyboard directly into the system. The quotation pulls from this data. The audit plan pulls from this data. The stage report pulls from this data. The committee decision form pulls from this data. The certificate pulls from this data.
Every downstream document inherits the accuracy of the original submission. If the client entered their company name correctly on the form, it will be correct on every document for the life of the certification. If they entered their employee count correctly, the audit time calculation will be correct.
And if the client made an error on the form? It is corrected in one place, and every document generated after the correction reflects the update. There is no cascade of manual fixes across multiple spreadsheets and templates.
The Planner's Experience
From the planner's perspective, the application review process transforms from data entry into data review. Instead of typing fields from a scanned PDF, the planner opens a structured record with all information pre-populated. They verify that the scope is reasonable, that the employee count makes sense, and that the standards selected match the client's industry. Then they proceed to quotation.
This shift from data entry to data review is significant. It is faster, less error-prone, and allows the planner to focus on judgment calls rather than transcription.
Ready to eliminate re-keying from your application process?
Book a demo at getcertiva.com and see how Certiva's online application intake creates structured audit records from the first interaction.