Buyer guide · Evidence

Custody is not a status. It is a sequence of attributable possession changes, discrepancies, and closures.

What a defensible custody history should record before, during, and after an asset crosses organizational boundaries.

Buyer question

Could an independent reviewer reconstruct where the asset was, who had it, what changed, and how discrepancies were resolved?

What this guide should leave you with

Preserve the same asset identity across handoffs.
Record sender, receiver, time, context, and evidence for each material transfer.
Treat receiving discrepancy as a first-class exception.
Connect custody to erasure, processing, downstream outcome, and settlement rather than ending at receipt.

One identity must survive the handoff

A custody record is weak if each organization creates a new representation of the asset.

Preserve serial/service tag and governed asset ID.
Associate manifests and package identifiers without replacing asset identity.
Record configuration or component changes when they affect evidence.

Make transfer attributable

Possession changes should have enough context to explain the movement without relying on recollection.

Sender and receiver.
Time and location context.
Signature, photo, manifest, device, or other configured proof.

Keep discrepancies visible

A missing or damaged asset should not vanish into a general project exception.

Record expected versus received state.
Assign accountable owner and next action.
Preserve resolution evidence and timing.

Continue beyond receiving

Custody should connect to sanitization, processing, resale, recycling, and final close.

Component media remains attributable after removal.
Downstream handoffs inherit required evidence.
Final disposition and settlement can reference custody history.

Decision framework

Custody evidence test

Identify

Confirm the asset or component being transferred.

Proof to inspectIdentity persists across source systems and organizations.

Transfer

Record who handed off to whom, when, and under what project context.

Proof to inspectHandoff evidence is attributable and reviewable.

Reconcile

Compare expected and received state.

Proof to inspectDiscrepancies become explicit exceptions, not notes.

Close

Connect final security and disposition outcomes to the same history.

Proof to inspectThe evidence trail reaches final economic and disposition close.

Evaluation checklist

Questions worth carrying into the room.

Use these as diligence prompts, RFP tests, design-review questions, or executive-briefing anchors.

01Asset identity persists across organizations.
02Sender and receiver are attributable.
03Manifest relationships do not replace asset-level identity.
04Receiving discrepancies remain visible until closure.
05Component removal preserves parent relationship.
06Downstream custody is represented where required.
07Final outcome links back to the custody history.

References + basis

Trace the argument.

External sources are references, not claims of certification or automatic compliance. Internal references point to the product, methodology, and proof architecture behind the guide.

01
Chain-of-custody methodology ITAD Lens · internal
The public methodology behind attributable possession changes and exception handling.
02
Sample custody history ITAD Lens · internal
Representative artifact showing how custody events and discrepancies can be presented.

Continue the decision

Related product, proof, and methodology.

Next step

Bring the operating question, not a generic demo agenda.

ITAD Lens is easiest to evaluate against a real disposition decision your organization already owns.

Request an executive briefing Explore the platform

Resolving the asset history

Buyer guide · Evidence

Custody is not a status. It is a sequence of attributable possession changes, discrepancies, and closures.

What a defensible custody history should record before, during, and after an asset crosses organizational boundaries.

Buyer question

Could an independent reviewer reconstruct where the asset was, who had it, what changed, and how discrepancies were resolved?

What this guide should leave you with

Preserve the same asset identity across handoffs.
Record sender, receiver, time, context, and evidence for each material transfer.
Treat receiving discrepancy as a first-class exception.
Connect custody to erasure, processing, downstream outcome, and settlement rather than ending at receipt.

One identity must survive the handoff

A custody record is weak if each organization creates a new representation of the asset.

Preserve serial/service tag and governed asset ID.
Associate manifests and package identifiers without replacing asset identity.
Record configuration or component changes when they affect evidence.

Make transfer attributable

Possession changes should have enough context to explain the movement without relying on recollection.

Sender and receiver.
Time and location context.
Signature, photo, manifest, device, or other configured proof.

Keep discrepancies visible

A missing or damaged asset should not vanish into a general project exception.

Record expected versus received state.
Assign accountable owner and next action.
Preserve resolution evidence and timing.

Continue beyond receiving

Custody should connect to sanitization, processing, resale, recycling, and final close.

Component media remains attributable after removal.
Downstream handoffs inherit required evidence.
Final disposition and settlement can reference custody history.

Decision framework

Custody evidence test

Identify

Confirm the asset or component being transferred.

Proof to inspectIdentity persists across source systems and organizations.

Transfer

Record who handed off to whom, when, and under what project context.

Proof to inspectHandoff evidence is attributable and reviewable.

Reconcile

Compare expected and received state.

Proof to inspectDiscrepancies become explicit exceptions, not notes.

Close

Connect final security and disposition outcomes to the same history.

Proof to inspectThe evidence trail reaches final economic and disposition close.

Evaluation checklist

Questions worth carrying into the room.

Use these as diligence prompts, RFP tests, design-review questions, or executive-briefing anchors.

01Asset identity persists across organizations.
02Sender and receiver are attributable.
03Manifest relationships do not replace asset-level identity.
04Receiving discrepancies remain visible until closure.
05Component removal preserves parent relationship.
06Downstream custody is represented where required.
07Final outcome links back to the custody history.

References + basis

Trace the argument.

External sources are references, not claims of certification or automatic compliance. Internal references point to the product, methodology, and proof architecture behind the guide.

01
Chain-of-custody methodology ITAD Lens · internal
The public methodology behind attributable possession changes and exception handling.
02
Sample custody history ITAD Lens · internal
Representative artifact showing how custody events and discrepancies can be presented.

Continue the decision

Related product, proof, and methodology.

Next step

Bring the operating question, not a generic demo agenda.

ITAD Lens is easiest to evaluate against a real disposition decision your organization already owns.

Request an executive briefing Explore the platform