Today, on Remembrance Day, we pause to honour the fallen and reflect on the service and sacrifice of all who have served and continue to serve Canada. We remember. #RemembranceDay
2
Site-specific certification needs site-specific evidence. Our locations page lists credentials by location and identifies other sites as depots. Which record does your ITAD review need first? #ITAD
Electronics life extension has several outcomes. Canada's proposed roadmap separates repair and reuse, refurbishment, and recycling in the waste hierarchy. We ask: which decision needs better evidence? #CircularEconomy
1
Staying inside the organization or leaving it? NIST includes that boundary in media sanitization decisions, along with data sensitivity and reuse. We ask: where does your ITAD workflow capture it? #ITAD #DataSecurity
2
Returned products need an assessment before a route is chosen. For OEM returns, inspection can inform repair, refurbishment or recycling. Our question: which assessment result is hardest to standardize? #ReverseLogistics
2
One device, many material questions. A Department of Energy R&D project is testing whole-unit recovery to measure critical materials in e-waste. We ask: which device should researchers study first? #RecyclingInnovation
6
E-waste reporting starts with two metrics: what a site generated and its diversion rate. ITU's digital infrastructure guidance includes both. We want to know: which input is harder to reconcile? #ESGReporting
6
Hardware can outlast its software support lifecycle. EU ecodesign rules address operating system updates for covered smartphone models. We ask: which support date shapes your device reuse decision? #CircularEconomy
3
Required data moves first. Canada's Cyber Centre advises backing it up before IT decommissioning and transferring it to supported systems. Review your plan with us: ers-international.com/contac… #ITAD
2
Quality control or facility monitoring: where would AI sorting in recycling help first? NIST’s new review notes standalone AI detection for both uses. We ask: what would your team test? #RecyclingInnovation
2
Supplier record, internal system, handoff: supply chain traceability must connect across them. NIST’s 2026 framework links data across manufacturing ecosystems. We ask: where does continuity break? #Traceability
6
Collection points, prepaid labels or incentives? EU guidance includes each option for electronics take-back. We ask: which return route creates the least friction for your customers? #ReverseLogistics
4
Reuse, refurbishment or recycling? Circular electronics programs need shared terms before choosing a pathway. ITU's current ICT guidance defines the concepts. We ask: which term causes confusion? #CircularEconomy
4
An IT asset retirement checklist goes beyond media sanitization. Canada’s Cyber Centre advises revoking credentials and removing assets from access lists and monitoring. We ask: which closeout check is hardest? #ITAD
5
Traction battery recovery needs shared process language. NIST's 2026 reference model maps technical processes and information needs. We ask: which handoff is hardest for your team to document? #BatteryRecycling
3
Product disassembly is more than taking items apart. NIST's model includes mechanical separation, stream isolation and component testing. We ask: which handoff needs clearer criteria? #RecyclingInnovation
4
Reuse candidate or broken equipment? ITU guidance calls for separate e-waste storage areas before treatment. We want to know: which intake decision helps your team protect the reuse option? #ElectronicsRecycling
1
16
Parts, tools, instructions: smartphone repair depends on all three. EU ecodesign rules address parts availability, repair information and disassembly. We ask: which gap slows your workflow most? #CircularEconomy
1
Encryption alone is not cryptographic erase. NIST defines it as sanitizing one or more keys protecting target data. Which device types need this distinction in your retirement plan? #ITAD #DataSecurity
1
6
Returns analytics should answer more than how many items came back. We use reporting to make return trends and root causes visible. Which reason code needs better definition in your program? #ReverseLogistics
2
