R2v3 Competence and Training Requirements for Processing Staff

If there is one area where R2v3 audits produce the most corrective action requests, it is competence and training. Not environmental requirements. Not data security. Training records — or rather, the absence of them, the incompleteness of them, the gap between what the training program says it does and what the records actually show.

I have worked through this with well over 200 clients at this point, and the pattern holds almost without exception: facilities that struggle with training documentation are not failing because they don't train their people. They're failing because they haven't connected their training activities to the specific competence requirements the R2v3 standard actually names. That's a solvable problem, and this article walks through exactly how to solve it.

What R2v3 Actually Requires: The Core Standard Language

R2v3 addresses competence and training primarily through Section 3, Core Requirement 3 — the Environmental Health & Safety (EHS) management system requirements — and through the broader management system obligations that mirror ISO 14001:2015 Clause 7.2 and ISO 45001:2018 Clause 7.2.

The standard requires that any person doing work that can affect the organization's R2 performance — EHS outcomes, downstream data security, responsible reuse and recycling outcomes — must be competent. Competence is defined as the ability to apply knowledge and skills to achieve intended results. That definition matters because it shifts the burden from "did we train them?" to "can they actually do the job to the standard required?"

R2v3 Section 3 specifically requires that organizations:

• Determine the necessary competence for persons doing work that affects R2 conformance
• Ensure those persons are competent based on education, training, or experience
• Take action to acquire the necessary competence and evaluate the effectiveness of that action
• Retain appropriate documented information as evidence of competence

That last bullet is where most audits live and die. "Appropriate documented information" has to be real, retrievable, and tied to specific roles and responsibilities — not just a sign-in sheet from a safety meeting three years ago.

Which Roles Are Actually in Scope

One of the questions I get most often is: does this apply to every employee, or just certain ones? The honest answer is that R2v3 casts a wide net here. If a person's work can affect your facility's conformance with the R2 standard — including EHS performance, data sanitization practices, downstream vendor management, or reuse and recycling decisions — that person is in scope for competence requirements.

In practice, that typically covers:

Processing Floor Staff — technicians performing de-manufacturing, component sorting, data destruction, and material grading. These folks are the core of the competence requirement because they are the ones whose decisions directly affect whether your R2 outcomes are met.

Data Sanitization Technicians — anyone performing or verifying data destruction to NIST 800-88 or equivalent standards. R2v3 treats data security as a material issue, and the people executing it need documented competence in the specific methods your facility uses.

Dock and Receiving Staff — personnel who make the initial determination about whether incoming material is acceptable, screened against your Focus Materials list, and properly segregated. A receiving technician who doesn't know your Focus Materials policy can create a cascading compliance problem that reaches all the way to an audit finding.

EHS Coordinators and Safety Personnel — anyone responsible for managing hazardous materials, conducting safety inspections, or responding to spills and incidents.

Supervisors and Quality Personnel — people who oversee the work that affects R2 conformance are themselves subject to competence requirements for that oversight function.

If someone touches the material, makes a decision about it, or oversees someone who does — they're in scope.

The Competence Determination Step Most Facilities Skip

Before you can train anyone, R2v3 expects you to have done something most facilities haven't formally documented: a competence determination for each in-scope role.

This is not a job description. A job description tells you what the person does. A competence determination tells you what they must be able to do well to keep your R2 conformance intact — and what knowledge, skill, or experience baseline they need to get there.

Think of it this way: a processing technician might need to be competent in:

• Identifying Focus Materials and the correct handling procedure for each
• Grading functional versus non-functional equipment to your written criteria
• Using your data destruction equipment and logging results per your documented process
• Recognizing and reporting an EHS incident correctly
• Following your downstream vendor separation protocols

Each of those is a distinct competence element. Your training program has to address each one. If your training covers general electronics recycling safety but doesn't specifically address your Focus Materials handling procedure, you have a gap — and an auditor will find it.

The competence determination is the document that connects roles to requirements. It's what makes the rest of your training program defensible.

What Documented Evidence Has to Look Like

R2v3 requires you to retain documented information as evidence of competence. Auditors are looking for a few specific things when they pull training records.

Linkage between training content and competence requirements. The training record has to show not just that the training happened, but what competence element it addressed. A sign-in sheet for "Annual Safety Training" does not accomplish this. A training record that identifies the topic, the competence requirement it addresses, the date, the trainer, and the employee — that does.

Evidence that the training was effective. This is the piece most facilities are weakest on. R2v3 requires that you evaluate the effectiveness of actions taken to achieve competence. That can be a skills demonstration, a written assessment, a practical evaluation by a supervisor, or documented observation of on-the-job performance. It does not have to be elaborate, but it has to exist.

Currency. Training records need to reflect that competence is maintained over time, not just established at hire. If your data sanitization process changed 18 months ago, the training records need to show that affected personnel were trained on the updated procedure.

Coverage. Every in-scope employee in every in-scope role needs a complete record. One or two missing records in an otherwise solid program can still generate a finding. Auditors sample across shifts, departments, and tenure lengths.

A Practical Framework for Building the Program

Here is the approach I walk clients through at Certify Consulting. It works whether you're building from scratch or trying to fix a program that's been generating audit findings.

Step 1: Map Your Roles to R2 Requirements

Start with your current org chart and map every role that affects R2 conformance. Don't be conservative here — if in doubt, include the role. For each role, identify the specific R2 requirements that person's work touches: Focus Materials handling, data security, EHS management, downstream vendor separation, or reuse/resale decisions.

Step 2: Write a Competence Determination for Each Role

For each role, document what the person must be competent to do, what baseline knowledge or experience is required before training begins, and what the evidence of competence will look like. This document becomes the backbone of your training program.

Step 3: Map Existing Training to Competence Gaps

Audit what you're already doing against the competence determinations. Most facilities have more training activity than they think — the problem is that it isn't documented in a way that connects to R2 requirements. Sometimes this step closes more gaps than you expect. Sometimes it surfaces real content gaps that need to be addressed.

Step 4: Build or Revise Your Training Content

For each gap, either create new training content or revise existing content to specifically address the competence element. The content doesn't have to be elaborate — a one-page procedure with a practical demonstration can satisfy the requirement for many tasks. What matters is that the content is specific to your process and your materials.

Step 5: Establish an Effectiveness Evaluation Method

For each competence element, decide how you will evaluate whether the training worked. Practical skills assessments work well for hands-on tasks. Written assessments work for knowledge-based competence. Documented observation by a supervisor is often the most realistic option for complex, multi-step processes.

Step 6: Build a Maintenance Schedule

Competence isn't a one-time event. Build a schedule that triggers retraining when procedures change, when equipment changes, when audit findings identify gaps, and on a regular cadence (most facilities use annual) regardless of changes. Document the schedule and make someone responsible for executing it.

How R2v3 Training Requirements Compare to Prior Versions

R2v3 raised the bar relative to R2v1 in ways that still catch long-established facilities off guard.

R2v3 also brought contractors and temporary workers into the competence requirement more explicitly. If your facility uses temp labor — and many do — those workers are in scope during the period they are performing work that affects R2 conformance. The documentation burden for temps is real, and it catches facilities by surprise.

The Contractor and Temp Worker Problem

In my experience, contractor and temporary worker training is the single most common source of major nonconformances in this area. The logic is straightforward: the standard doesn't care whether your badge says "employee" or "contractor" — if you're doing work that affects R2 conformance, you need documented competence to do it.

What that means practically is that your facility needs a process for ensuring temporary workers receive role-specific orientation before they start performing in-scope work, that the orientation is documented, that competence is evaluated before or shortly after they begin, and that the records are retained even after the worker leaves.

Many facilities lean on their staffing agency to handle training, which is fine as far as it goes — but you cannot outsource the documentation or the effectiveness evaluation. Those have to live in your records, not the agency's.

What Auditors Are Actually Looking for on Audit Day

When an R2 auditor walks into your facility to review competence and training, here is the sequence they typically follow. They will ask to see your competence determination process — the documented methodology for figuring out what competence is required for which roles. They will then pull a sample of employee training records across different roles and shifts and check whether those records link to specific competence requirements. They will ask about your effectiveness evaluation method and look for evidence that it actually happened. They will often conduct interviews with processing staff to test whether the training content actually landed.

That last piece is one that facilities consistently underestimate. An auditor asking a technician "walk me through how you identify Focus Materials at intake" is an effectiveness evaluation in real time. If the technician's answer doesn't match what your training records say they were trained on, you have a finding regardless of how clean your documentation looks.

The documentation is necessary. It is not sufficient. Your people have to actually know the material.

Statistics Worth Knowing

According to SERI (Sustainable Electronics Recycling International), training and competence nonconformances consistently rank among the top five finding categories across R2 audits globally. Facilities that operate across multiple shifts see disproportionately higher rates of training-related findings — the afternoon and night shifts are where documentation gaps most commonly live.

R2v3's competence requirements align with ISO 14001:2015 Clause 7.2 and ISO 45001:2018 Clause 7.2, both of which have been in effect long enough that auditors treat them as a mature expectation, not an emerging one. The standard gives no grace for facilities that are "working toward" compliance with these requirements.

NIST SP 800-88 Rev. 1, the data sanitization standard that R2v3 references for data destruction competence, distinguishes between Clear, Purge, and Destroy methods — and the competence requirement extends to knowing which method applies to which media type, not just knowing how to operate the equipment. That distinction matters in training content design.

Facilities with a formal competence determination document — separate from job descriptions — report significantly fewer training-related nonconformances at initial and surveillance audits. It's one of the highest-ROI documents you can invest time in before your next audit.

Building a Program That Holds Up Over Time

The facilities I've seen maintain clean training records year over year share a few habits. They treat the competence determination as a living document that gets reviewed when procedures change, not just when an audit is coming. They assign ownership for training documentation to a specific person — not a department, a person — who is accountable for completeness and currency. They build effectiveness evaluation into the training activity itself, so there's never a separate step to forget.

And they train their supervisors to understand that a verbal correction on the floor does not substitute for a documented training event when a procedure has changed. The correction might be faster. The documentation is what keeps you compliant.

If you're looking at your current program and seeing gaps, the right move is to start with the competence determination step. Everything else — the training content, the records, the effectiveness evaluations — flows from knowing precisely what competence you need and for whom. Get that right and the rest of the program has a foundation to stand on.

For help building or auditing your R2v3 competence and training program, explore our R2v3 certification consulting services or review our R2v3 audit preparation resources to see where your current program stands.

Last updated: 2026-05-15