Purpose. This standard operating procedure (SOP) defines how electronics and IT assets move from arrival at your facility to final disposition, with complete traceability, consistent quality, and audit-ready records.
Who should use this. Warehouse leads, receiving techs, triage technicians, data-wipe teams, inventory controllers, and compliance managers.
Outcomes. Every asset is (1) received against paperwork, (2) uniquely identified, (3) evaluated and routed, (4) tracked through each status change, and (5) closed with final disposition evidence.
1) Scope, Roles, and Definitions
Scope. Applies to all incoming lots: business ITAD pickups, consumer drop-offs, OEM returns, municipal programs, and internal transfers. Includes loose devices, palletized mixed e-waste, and serialized IT equipment (laptops, desktops, servers, networking, storage, mobile).
Roles.
- Receiving Lead: controls dock schedule, verifies documentation, signs chain-of-custody, opens lots in the inventory system.
- Receiving Tech: pallet counts, visible damage check, tagging, quarantine flagging.
- Triage Tech: functional grading, cosmetic grading, part-out decisions, hazard isolation.
- Data Team: data sanitization, verification, exception handling.
- Inventory Controller: status changes, bin moves, cycle counts, discrepancy resolution.
- Compliance Manager: record reviews, nonconformity (NC) management, corrective actions.
Key terms.
- Lot/Shipment ID: unique ID for the whole intake (e.g., YYMMDD-CLIENT-###).
- Asset ID: unique ID per unit; never reused.
- Chain of Custody (CoC): documented control from pickup to final disposition.
- Final Disposition: reuse/resale, parts harvesting, recycling, or approved destruction.
2) Pre-Arrival Controls (before the truck backs in)
- Schedule & paperwork
- Confirm pickup reference, client program, and special requirements (e.g., do-not-test, destroy-on-arrival, encryption notes).
- Pre-create Lot ID with expected lines: device categories and counts.
- Dock readiness
- Assign trained staff; prepare PPE for battery and CRT risk where applicable.
- Stage quarantine area (clearly marked) for restricted or unknown materials.
- System prep
- Open the Receiving Worksheet in your inventory tool with fields preloaded (client, carrier, ETA, expected pallets).
3) Receiving Procedure (dock to check-in)
Step 1 — Carrier handoff & CoC verification
- Match BOL/pickup manifest with your Lot ID.
- Record truck arrival time, seal number (if present), carrier name, and driver signature.
- Note any seal mismatch or packaging breach as a potential NC; photograph.
Step 2 — Pallet inspection & count
- Count pallets; scan or tag each pallet with Pallet ID (Lot ID + “P##”).
- Visual check for crushed corners, bulges, liquids, loose batteries.
- If hazard suspected, move pallet to Quarantine and notify Compliance.
Step 3 — Unload & staging
- Move pallets to Receiving Staging. Keep aisle clear; maintain separation between lots.
Step 4 — Initial reconciliation
- Compare received pallet count and gross weights against paperwork.
- Log discrepancies (over/under counts, extra categories).
- If variance > agreed tolerance, flag Discrepancy for client approval before further processing.
Evidence to capture (mandatory):
- Photos: pallet faces, any damage, seal, truck plate if needed.
- Documents: signed BOL/manifest, CoC form with Lot ID, arrival timestamps.
4) Asset Identification & Tagging (creating traceability)
Tagging rules.
- One unique Asset ID per device (barcode + human-readable). Printed label goes on a clean, visible spot; avoid vents and screws.
- Never reuse IDs. If a label is damaged, void it in the system and reprint.
Minimum data captured at tag time.
- Lot ID, Pallet ID, Asset ID
- Category (laptop/desktop/server/phone/monitor/etc.)
- Brand, Model, Part No., Serial Number (SN)
- Presence of storage media (Yes/No/Unknown)
- External condition (quick code A/B/C/D)
- Power adapter included? (Y/N)
- Data classification (client-declared if provided)
- Photos (optional but recommended for disputes)
Field capture sequence.
- Scan Lot → 2) Scan Pallet → 3) Print/scan Asset ID → 4) Enter SN → 5) Select Category/Model → 6) Media presence → 7) Save.
Pro-tip for accuracy: Use scan validation for serials (checksum patterns where available), and force “unknown” rather than leaving blanks.
5) Triage & Grading (deciding the best path)
Goal. Determine if the asset is:
- Reuse candidate (resale/remarketing)
- Refurbish candidate (parts needed, repairable)
- Parts harvest (remove RAM, SSD, screens, etc.)
- Recycling (beyond economic repair or unsafe)
Standard triage test (fast and consistent).
- Power test (adapters ready at benches, universal cables): powers on Y/N.
- POST/BIOS check: reach BIOS/UEFI? record CPU/RAM/disk presence.
- Screen/Display: no cracks, acceptable pixel performance.
- Keyboard/Ports: quick scan for missing keys/ports.
- Battery check (laptops/tablets): present Y/N; if swollen → Hazard and quarantine.
- Casing: cracks, severe dents, corrosion → downgrade.
- Security locks: BIOS/MDM/Activation lock; if locked → route to Exception.
Grading codes (example).
- A: Fully functional, minor wear.
- B: Functional, moderate wear or minor defect.
- C: Functional but notable defects; may need parts.
- D: Non-functional, salvage or recycle.
Routing logic.
- A/B → Data Sanitization (if media present) → QC → Ready for Remarketing.
- C → Refurb Bench (parts request auto-created) → retest → Data Sanitization → QC.
- D → Harvest (target parts list pre-defined) → Commodity Recycling with weight capture.
Required records at triage.
- Triage result (A/B/C/D + decision)
- Tech name and timestamp
- Any hazards detected
- Exception ticket (if activation-locked, missing SN, etc.)
6) Data Sanitization Routing (if storage media present)
Default rule. Any device with internal or attached storage goes to Media In location with a pending wipe status before any other work (unless client policy is destroy-on-arrival).
Wipe SOP essentials.
- Confirm Asset ID matches label and system before starting.
- Use approved sanitization methods per media type (e.g., clear/purge/destroy equivalents) with automated verification logs.
- For failed wipes, open an Exception and route to Physical Destruction if required.
- Attach wipe certificate/log ID to the Asset ID record.
Final check. No asset leaves Media area without a pass/fail record; status cannot advance to QC or Final without this field populated.
7) Asset Tracking & Inventory Controls (no black holes)
Location model (simple and effective).
- ZONE > AISLE > RACK > BIN (e.g., RCV-A2-R3-B07).
- Every status change requires a bin move in the system, enforced by barcode scan.
Mandatory statuses.
- Received → Tagged → Triage → Media In → Media Pass/Fail → Refurb → QC → Ready for Sale → Shipped
- Recycling: Received → Triage D → Harvest → Weighed → Commodity Out
Cycle counts & audits.
- Daily: spot-check 10 random Asset IDs per active zone.
- Weekly: cycle count of one full zone.
- Monthly: reconcile “Ready for Sale” vs. physical bins; investigate variances.
Discrepancy handling.
- Open a Discrepancy Ticket when quantity, serial, or location doesn’t match.
- Root cause categories: mis-scan, wrong bin, duplicate tag, untagged move, theft/loss.
- Close only with corrective action (e.g., retrain, change bench layout, add second scan step).
8) Final Disposition & Evidence (closing the loop)
Reuse/Remarketing.
- QC checklist complete (boot, network, keyboard, ports, camera, battery health, cosmetics).
- Product record: specs (CPU/RAM/SSD), grade, photos, accessories.
- Shipping record linked to Asset IDs with carrier, tracking, destination, and invoice/reference.
Recycling.
- Harvest log (parts removed with part ID/quantity).
- Commodity weights by stream (e.g., mixed metal, plastics, PCBs, batteries).
- Downstream vendor ID and transfer reference captured for traceability.
Destruction (if applicable).
- Destruction method, date, operator, and device count/weights.
- Certificates/plant receipts captured against Lot ID.
Closeout review.
- Compliance Manager verifies a sample of records per lot (e.g., 10% or minimum of 10 assets).
- Sign off only when all exceptions are closed and final statuses are consistent.
9) Exception Handling (the things that break your flow—make them routine)
Common exceptions and resolutions.
- Activation/MDM lock: open ticket; attempt client unlock; if unresolved within SLA, route to recycle.
- No serial number: use motherboard/IMEI or label as “No SN,” photo evidence attached.
- Swollen battery/damage: bag/box per hazard SOP; move to battery cage; record weight and ID.
- Mismatched paperwork: isolate affected pallets; request client correction before proceeding.
- Wipe failure: retest; if repeat fail, physically destroy per policy.
SLA targets (set and measure).
- Exceptions acknowledged within 4 business hours.
- Resolution or client update within 3 business days.
- Monthly review of top exception types → targeted training or process tweaks.
10) Documentation & Records (what auditors expect to see)
Per Lot.
- Signed BOL/manifest and CoC form
- Arrival/departure timestamps, seal number (if used)
- Pallet count and weight reconciliation
- Photo set (arrival, damage, unusual items)
- Discrepancy notes and resolutions
Per Asset.
- Asset ID, Lot ID, Pallet ID, Category, Brand/Model/SN
- Triage grade and decision, technician name/time
- Data sanitization result with log/certificate ID
- Location history (bin moves)
- Final disposition (sale/recycle/destroy) and evidence (invoice/COA/weight ticket)
Retention. Keep records per your legal and client requirements (often 3–7 years). Use immutable storage or version-controlled document library.
11) KPIs to Prove Control (and improve it)
- Receiving accuracy: (Count matched ÷ Count received) ≥ 99.5%
- Tagging accuracy (SN match): ≥ 99.0%
- Cycle count variance: ≤ 0.5% by value/month
- Media pass rate on first attempt: ≥ 97% (by device type)
- Exception closure within SLA: ≥ 95%
- Dock-to-triage lead time: median ≤ 2 business days
Review KPIs weekly; if thresholds are missed, log a corrective action with root cause and owner.
12) Templates You Can Recreate (no downloads needed)
Receiving Checklist (printable).
- Lot ID / Client / Date / Carrier / Seal #
- Pallets expected / received / variance
- Visible damage? Y/N (describe)
- Photos taken? Y/N
- BOL & CoC signed? Y/N
- Discrepancies logged? Y/N
- Receiver name & signature
Triage Worksheet (bench view).
- Asset ID / Category / Brand / Model / SN
- Power Y/N, POST Y/N, Display OK, Keyboard/Ports OK
- Battery condition (N/A/OK/Swollen)
- Cosmetic grade A/B/C/D (notes)
- Decision: Resale / Refurb / Harvest / Recycle
- Tech name & time
Asset Tag Format.
- Code 128 barcode:
ASSET-YYYY-####### - Human readable under barcode; include Lot ID in small print.
Location Labeling Standard.
- Zone sticker color by process (Receiving = grey, Media = blue, QC = green, Ready for Sale = purple).
- Large bin IDs legible from 2 meters.
13) Training & Competency (keep it simple but real)
- Onboarding: shadow for two full shifts; demonstrate correct tagging and two bin moves with zero errors.
- Quarterly refreshers: 30-minute micro-training on top exceptions (e.g., locks, swollen batteries).
- Authorization matrix: who can change statuses, who can close exceptions, who can sign CoC.
Maintain a training log: person, topic, trainer, date, quiz score (if used).
14) Change Control (so the SOP stays true to reality)
- When tools or client requirements change, update this SOP within 10 business days.
- Version control: increment minor versions for text edits, major for flow changes.
- Communicate changes via daily standup and post at benches; require acknowledgment in the training log.
Final Notes
A good intake-to-disposition SOP is about discipline and visibility. If you can answer, at any moment, “Where is this asset? What happened to it? Who touched it? What’s next?”—you’re running a controlled operation. The steps above give you that control without bloat: clear tags, short tests, mandatory scans, tight exception loops, and records that stand up to scrutiny.
Leave a Reply