01 / Consulting
We build the management system with you
End-to-end implementation from scope definition through to your certification audit. For R2v3, RIOS or ISO. You end up with a system your team runs, not one that depends on us.
Certification consulting means someone who has sat on the other side of the audit table works alongside your team to build the management system a certification body will accept — defining scope, closing gaps, writing what needs writing, and getting the evidence in place before the auditor asks for it.
The failure mode we see most often isn't a company that can't do the work. It's a company that does the work and can't prove it. Processes run well, decisions get made, corrective actions happen, and none of it is recorded in a way an auditor can verify. A lot of consulting is turning what you already do into evidence.
What implementation actually includes
Scope varies with the standard and how much you already have. These are the pieces that appear on nearly every engagement.
- Scope definition
Which sites, processes and materials are in, and for R2v3, which appendices apply. Getting this wrong is the most expensive early mistake.
- Gap analysis and roadmap
Requirement by requirement against your actual operation, with owners, effort estimates and a dated plan.
- System build
Procedures, controls, records and the routines that keep them current, built with your people rather than handed to them.
- Training and handover
The team learns to run it while it's being built, so nothing stalls when we leave.
- Audit preparation
Internal audit, management review, corrective actions closed, then the certification audit itself.
Which standard
Consulting on either side
The method is the same. The requirements, the evidence and the auditor's questions are not.
-
Recycling & ITAD
R2v3 & RIOS Electronics recyclers, ITAD providers, refurbishers and brokers. Take the R2 path → -
Manufacturing & services
ISO standards Quality, environmental, health & safety and energy management. Take the ISO path →
Organizations starting from scratch, or with a system that has drifted far enough that patching it costs more than rebuilding. If you're mostly there and just need it checked, auditing is the cheaper answer.
Questions
Common questions
How long does an implementation take?
Three to six months for a single-site ISO certification starting from scratch. Four to six months for R2v3, extending toward twelve for large, multi-site or complex-scope operations.
How much of the work falls on our team?
Less than you'd fear, more than zero. We write the documentation and design the system, but your people have to describe how the operation actually runs and take ownership of the routines. A system built entirely without your team fails its first surveillance audit.
Do you use templates?
We start from proven structures rather than a blank page, then rewrite them around your operation. What we don't do is hand over a generic pack and call it a system. That's one of the faster ways to collect findings.
What if we already have part of a system?
Common, and it usually shortens the project. The gap analysis establishes what's usable, what needs rewriting and what's missing, so you're not paying to rebuild things that work.
Next step
Ready to scope an implementation?
Tell us the standard and where you stand. You'll get an honest read on effort and timeline before anyone talks about fees.