Skip to content

ITAD KNOWLEDGE CENTER

ITAD Chain of Custody: What to Document Before Pickup

By · Published · Updated

Retired business laptops, SSDs, server hardware and barcode labels organized on an ITAD intake bench for chain-of-custody documentation.
AI-generated editorial illustration; not an actual TBR facility or customer project.

ITAD chain of custody is the record of who controlled retired equipment, when it changed hands and how its identity was maintained. Before pickup, agree the equipment list, authorized contacts, handoff evidence and exception process. A collection receipt is useful, but it is not the complete project record.

Build the release list before collection

List equipment types, quantities and available identifiers. Separate each office or collection location. Flag loose drives, systems without storage and devices with special handling needs. Keep leased or third-party equipment out of the release until ownership and authorization are resolved.

Choose the identification level deliberately. Some projects need serial-level reconciliation; others begin with grouped counts. Agree the scope and any later identification work rather than assuming every proposal includes the same service.

Attach the project instructions

The handoff should refer to the agreed data-handling and disposition scope. Identify who can authorize a changed processing route, an inventory correction or an additional collection. Keep instructions with the project records, not only in an individual employee’s inbox.

Complete required backups and internal release procedures before retirement. Do not place passwords or sensitive customer information on a public packing list. Your security team should decide how necessary restricted instructions are communicated.

Record each authorized handoff

  • Project reference and collection location.
  • Date, releasing contact and receiving party.
  • Equipment identifiers or the agreed grouped counts.
  • Transport and packaging details where required by the scope.
  • Discrepancies, additions and the person approving them.

For a multi-location Tampa Bay pickup, keep each location recognizable through receiving. If one office adds two laptops on collection day, record the change. Do not silently merge it into another location’s count.

Reconcile intake and processing

Compare the received equipment with the release record. Investigate missing, unexpected or differently identified assets. Keep exceptions open until there is a documented resolution; an unexplained mismatch should not disappear from the closing pack.

Link data-processing records to the relevant media or asset identifiers. A custody record shows control and movement, while processing evidence explains what was done. Neither should be presented as a substitute for the other. See the separate guide to sanitization versus physical destruction.

Close the chain with usable records

Agree what the final pack will include: received inventory, processing results, exception resolutions, disposition information and any financial settlement. Confirm how partner transfers are recorded and which party supplies each document. Have an internal contact reconcile the pack before closing the project.

TBR’s sample project documentation illustrates record relationships using fictional data. It does not certify that equipment has been processed.

Common questions

Is a signed pickup receipt enough?

It records a handoff. The complete project may also require intake, processing and final disposition evidence.

What if equipment changes after the quote?

Record the change and confirm its effect on scope, identification, timing and charges.

Source note

NIST SP 800-88 Revision 2 informs media sanitization planning. The custody checklist is practical project guidance, not a claim of universal legal requirements.

How TBR Trade Group can help

TBR can help define collection, identification and reporting expectations before retired equipment leaves your site. Send the pickup locations, approximate inventory, data instructions and required records. Review our ITAD process and request an assessment. We confirm the agreed tracking scope, handoff responsibilities and exception path for your project.

Put Your ITAD Plan Into Practice

Tell us the equipment, location and data requirements for your project.