The Fear That Stops CBs From Switching
The number one reason certification bodies stay with inadequate systems is not satisfaction — it is the fear of transition. They imagine weeks of downtime, lost data, confused staff, and angry clients. They picture a chaotic switchover where nothing works and everyone reverts to spreadsheets.
This fear is understandable. It is also largely unfounded when the implementation is structured properly.
Certiva implementations follow a four-week framework designed to get a CB operational without disrupting ongoing audits. No big bang. No all-at-once migration. A phased approach that builds confidence at each step.
Let us walk through what this looks like for a fictional CB — Northstar Certification — with 12 auditors, 180 active clients, and certifications across ISO 9001, ISO 14001, and ISO 45001.
Week 1: Document Template Configuration
The first week is about making Certiva look like Northstar's CB — not the other way around.
What happens: Northstar provides their existing document templates — the Word files they currently use for audit plans, stage reports, certificates, impartiality declarations, NC forms, and any other FR-numbered documents. These are the documents their auditors and clients already know.
Certiva's implementation team configures these templates within the platform. Each template's fields are mapped to data points in the system. The client name field in the report template maps to the client record. The auditor name field maps to the team assignment. The standard and scope fields map to the engagement configuration.
What it means: When Certiva generates a document, it produces Northstar's document — with Northstar's branding, Northstar's layout, and Northstar's field structure. Auditors who receive a Certiva-generated audit plan see their familiar format, not a generic template they have never seen before.
What the CB does: Provide templates. Review the configured output. Confirm the mapping is correct. Flag any fields that need adjustment. This typically requires 2-3 hours of the operations manager's time spread across the week.
Week 2: Auditor Profiles and Qualification Import
The second week is about getting the people into the system.
What happens: Northstar provides auditor information — CVs, qualification records, approved standard and EA code lists. Certiva's AI-assisted CV parsing reads the uploaded CVs and extracts relevant qualification data: education, work experience by sector, audit experience by standard, formal certifications.
The extracted data is presented to Northstar's operations manager for review. They confirm or adjust the AI's extraction — verifying that the system correctly identified each auditor's qualified standards, EA codes, and experience levels. Once confirmed, each auditor has a complete profile in the system.
Auditor accounts are created, and each auditor receives access to their portal. At this stage, the portal is empty — no audits are assigned yet — but the auditor can log in, see their profile, and familiarize themselves with the interface.
What the CB does: Upload CVs and existing qualification records. Review AI-extracted data and confirm accuracy. Distribute portal access credentials to auditors. Time commitment: approximately 3-4 hours for the operations manager, plus brief individual logins for each auditor.
Week 3: Standard and Scope Configuration, First Test Audit
The third week is about configuring the certification scope and running a trial.
What happens: Certiva is configured with Northstar's accredited standards, the EA codes they cover, and their scope descriptions. The committee is set up with members, their qualifications, and the signing rules that apply to certification decisions.
Then the first test audit is created. Northstar picks a real client — ideally one with an upcoming surveillance — and sets up the engagement in Certiva. The team is assigned (with qualification validation). The audit plan is generated (from Northstar's template). Impartiality declarations are generated for each team member.
This is a dry run with real data. The planner walks through the complete workflow: engagement creation, team assignment, document generation, signing, NC creation (if applicable), committee review, and certificate generation. Any configuration issues are identified and resolved.
What the CB does: Provide standard and scope configuration details. Participate in the test audit setup and walkthrough. Identify any process steps that need adjustment. Time commitment: approximately 4-5 hours for the operations manager, plus brief participation from one auditor and one committee member.
Week 4: Staff Training and Parallel Run
The fourth week is about adoption and confidence building.
What happens: Training sessions are conducted for each user group:
- •Planners learn engagement management, team assignment, document generation, and workflow monitoring. This is the most comprehensive training because planners interact with the most features. Typical session: 2 hours.
- •Auditors learn the auditor portal: viewing assigned audits, signing documents, uploading evidence, creating and managing NCs. Typical session: 45 minutes. The portal is designed to be intuitive enough that most auditors are comfortable after one real audit.
- •Committee members learn the review and signing workflow for certification decisions. Typical session: 30 minutes.
During week 4, Northstar runs their normal operations in their existing system while simultaneously processing a small batch of new engagements through Certiva. This parallel run serves two purposes: it validates that Certiva produces correct outputs, and it gives staff real experience with the system before it becomes the primary platform.
What the CB does: Attend training sessions. Process 3-5 real engagements through Certiva alongside the existing process. Report any discrepancies or issues. Time commitment: training hours plus normal operational time for the parallel engagements.
What Happens After Day 30
At the end of four weeks, Northstar has:
- •All document templates configured and validated
- •All auditor profiles created with verified qualifications
- •Standards, scopes, and committee structure configured
- •At least one complete audit cycle processed through the platform
- •All staff trained on their respective roles
The transition from parallel running to full adoption is Northstar's decision. Some CBs switch fully on day 31. Others run parallel for another two weeks for additional confidence. The existing system remains available as a reference during the transition period.
What Certiva Does Not Require
It is worth noting what this process does not involve:
- •No process redesign. Certiva configures to Northstar's existing process. If they have a specific document review step between Stage 1 and Stage 2, that step is built into the workflow. The CB does not change how they work to fit the software.
- •No data migration panic. Active client records can be entered as new engagements are created. Historical records can be migrated in batches after go-live. The CB does not need to stop operations to load years of historical data before they can start using the system.
- •No extended downtime. Because the implementation is additive — new engagements go into Certiva while existing ones finish in the old system — there is no moment where nothing works.
The Real Timeline Variable
The four-week framework is consistent, but the actual calendar timeline depends on one factor: the CB's availability. A CB that can dedicate 10-15 hours of operations manager time across four weeks will hit the timeline. A CB whose operations manager is traveling for audits three out of four weeks will take longer — not because the work is more complex, but because the review and confirmation steps require their input.
The implementation does not require a dedicated IT team. It does not require a project manager. It requires the person who knows how the CB operates to spend a few hours each week confirming that the system reflects their reality.