BUYING · TIMELINES

How Long Does ITAD Take? The Honest Timeline, Clock by Clock

“How long?” has four different answers, because an ITAD engagement runs on four different clocks — scheduling, processing, certification, and settlement. What each clock measures, what compresses it, and what quietly stops it.

By Brian Boynton Published 7 min read

STRAIGHT ANSWER

How long does ITAD take?

For a standard single-site engagement, the sequence runs in days and weeks, not months: scheduling and pickup, then facility processing with per-serial reconciliation, then certificates after verification — with remarketing settlement the longest clock because equipment must actually sell. The biggest delays are preventable and client-side: locked devices awaiting MDM or firmware release, inventories that don't match reality, and unstaged sites.

TL;DR

An ITAD engagement runs on four clocks: scheduling (scoping to pickup — days to weeks for a single site, a project calendar for many), processing (receiving, reconciliation, sanitization or destruction), certification (certificates follow verification, not the truck), and settlement (remarketing proceeds take longest — equipment must sell before value returns). Standard single-site work is measured in days and weeks, not months. The biggest delays are self-inflicted: locked devices, inventories that don't match reality, and unstaged sites.

  • The clock that matters for risk is the first one — every week devices sit in a closet is unmanaged exposure and decaying resale value.
  • Lock releases (MDM, activation locks, firmware passwords) are your team's work, not the vendor's — and the #1 preventable delay.
  • Certificate delivery dates belong in the agreement, not in assumptions.
  • Plan backward from hard deadlines (lease end, audit date) — the office-closure and decommissioning checklists both work this way.

01 / FOUR CLOCKS“How long” is four different questions

Ask a vendor “how long does ITAD take?” and you're really asking four things: How soon can you get here? (scheduling), How fast is the equipment processed? (processing), When do I get the paper? (certification), and When does the money come back? (settlement). The clocks run in sequence with overlaps, and they respond to different levers — which is why one honest article beats one dishonest number. For a routine single-site engagement, the whole sequence is measured in days and weeks, not months; what moves it inside that range is below.

02 / CLOCK ONEScheduling: scoping to truck

The first clock starts with a scoping conversation — counts, media mix, locations, destruction location, lock status — and ends when the truck leaves your dock. For one site with a staged, palletized fleet, this is a scheduling exercise: days to a couple of weeks depending on calendars and geography. For multi-site programs it becomes a wave plan; for remote fleets, mail-back kits put part of the clock in your employees' hands. The lever you control: staging. A site where devices are collected, inventoried, and palletized before pickup day moves at the fast end; a “we'll find everything when you get here” site does not.

03 / CLOCK TWOProcessing: receiving to disposition

At the facility, the sequence is fixed: receive and verify seals, reconcile serials against the intake manifest, then sanitize, destroy, or grade for resale per the disposition policy. The serialized steps add hours, not weeks — what stops this clock is exceptions. A serial on the manifest that isn't in the tote (or the reverse) halts reconciliation until it's resolved, because a certified program can't shrug at a missing drive; that discipline is exactly what you're buying. Clean inventory in, fast processing out.

04 / CLOCK THREECertification: when the paper exists

A certificate of destruction is generated after verification — per serial, method named, reconciled to intake — so it necessarily trails the pickup. For routine engagements, expect the certificate package on a written schedule measured in weeks after collection, and make that schedule contractual: “certificates within N days of processing” is a normal term to ask for. If an auditor or assessor is waiting on the paper, say so in scoping — the sequence can be planned around a date. (What the certificate must contain is covered in the NIST 800-88 explainer.)

05 / CLOCK FOURSettlement: the longest clock, by design

Remarketing proceeds take the longest because the equipment has to actually sell: grading, refurbishment, listing, and sale each take real time, and settlement reporting follows the sales. This clock is measured in months for a typical value-share program — not because anyone is slow, but because markets are markets. Two implications: settlement timing belongs in the contract (period, reporting cadence, audit rights), and the way to make this clock pay more is to start it sooner — resale value decays while devices sit in storage.

06 / WHAT STOPS THE CLOCKSThe delays, ranked by preventability

Locked devices — the champion. MDM enrollment, activation locks, and firmware passwords block resale processing until your team releases them; the vendor cannot do it for you. Run the release checklist before pickup and this delay disappears. Inventory surprises — manifests that don't match physical reality create reconciliation exceptions, and exceptions stop certified programs cold. Unstaged sites — hunting devices on pickup day burns the crew's clock. Approval loops — disposition decisions (resell vs. destroy, by class) left unmade until equipment is already at the facility. The remote fleet — employee returns run on human timelines; the refresh playbook treats them as their own workstream for a reason. Every one of these is on the client side of the fence, which is the good news: the timeline is more in your control than the question implies.

07 / PLANNING BACKWARDWhen the deadline is real

Lease end. Audit date. Assessment window. Data-center power-down. When the end date is fixed, plan the clocks in reverse: certificates by the audit date means processing complete before it, which means pickup scheduled with margin, which means staging and lock release start now. The office-closure checklist runs this pattern against a T-90 real-estate clock and the decommissioning checklist against a project plan; for fleet-scale work, the refresh playbook schedules the waves.

08 / FAQITAD timeline FAQ

How quickly can an ITAD pickup be scheduled?

It depends on scope and location. A standard single-site pickup is a scheduling exercise measured in days to a couple of weeks; multi-site programs and remote-fleet collections are planned as waves on a project calendar. The honest answer arrives in the scoping conversation — and a vendor who quotes a date before asking about counts, locations, and lock status is guessing.

How long until we receive certificates of destruction?

Certificates follow processing, not pickup — each device has to be received, reconciled against the intake manifest, sanitized or destroyed, and verified before its certificate exists. For a routine engagement that's typically a matter of weeks after collection, and the delivery date should be written into your agreement rather than assumed.

What delays an ITAD project the most?

Locked devices are the leading self-inflicted delay: units still enrolled in MDM or carrying activation locks and firmware passwords can't be processed for resale until released, and releases require your IT team, not the vendor. The other classics: inventory that doesn't match reality (reconciliation exceptions stop the clock), sites that aren't staged for pickup, and remote employees who take weeks to return devices.

Does faster ITAD mean worse ITAD?

No — speed and rigor aren't in tension; staging is. The serialized scanning, sealed custody, and verification steps add hours, not weeks. What actually takes time is everything before the truck arrives: decisions, approvals, lock releases, staging. A well-prepared engagement is both faster and better documented than a rushed, unprepared one.