How pickup works
Document the handoff. Then make the pile go away.
The process is built around accountable intake: what was picked up, whether data-bearing media was present, what documents were requested, and where each class of asset is routed.
Operating flow
Four steps, clear and documented.
- Scope
You send rough counts, asset classes, pickup city, media sensitivity, loading constraints, and requested documentation.
- Pickup
Sentinel records the handoff with a pickup receipt, custody notes, photos when useful, and exception notes.
- Intake
Assets are sorted into reuse, resale, part-out, data-media, return, destruction, and downstream recycling paths.
- Disposition
You receive the appropriate package: receipt, asset/media log, certificate/report, or downstream documentation.
Documents available
Proof depends on what actually happened.
Client, location, job ID, material classes, storage-media flag, custody notes, and signatures.
Asset IDs, serials/WWNs where captured, media type, planned disposition, and exceptions.
Only issued from real tool output, verification evidence, destruction evidence, or downstream documents.
General liability coverage in place. Pickup receipts and documented custody provided on every job.
Data-bearing media
Handled separately.
Drives and removable storage are separated from general equipment. Depending on the job, media can be returned, held, wiped, destroyed, or routed through a certified downstream partner.
- Serial/WWN capture where required
- Method and verification recorded when sanitization is performed
- Failed media gets a documented exception path
Compliance boundary
Claims stay tied to evidence.
Sentinel claims R2v3, NAID, or certified data destruction only when the specific job, tooling, and downstream documents support it. Taking responsibility for other people's data means saying only what the evidence supports.
Start clean
Tell us what documentation you need before pickup.
If your client requires a certificate, asset log, or downstream documentation, say that up front so the job is scoped correctly.