1. The economics are all about cycle time and handling
| Machine | Cycle | Drives per hour | Handling impact |
|---|---|---|---|
| T-1.5 | < 5 sec | ~720 | Fastest — best where the crusher is not the bottleneck |
| T-5 | < 20 sec | ~180 | Digital cycle counter gives a per-client log |
| T-1 / T-1.2 | ~20 sec | ~180 | Adequate at moderate volume |
| T-4 | < 1 min | ~60–90 | Secure-room and tender work; slower for production |
| PDS-100 | 8 sec auto | ~450 | Sensor-triggered; rear output slide removes the manual ejection step |
| PDS-75 | 5–8 sec manual | ~450–700 | Varies entirely on operator speed |
| PDS-30 | 5 sec manual | ~700 | Highest manual throughput; smallest capital outlay |
2. The register is the deliverable
An ITAD's product is not the destruction; it is the evidence of destruction. A well-run register closes the job and is what a bank, a government department or a PSU client will audit. The fields that matter:
- Client and job reference — so the register can be issued per client.
- Asset tag and serial number — one row per asset, never batched.
- Media type, capacity, data classification — evidences the method matched the medium.
- Machine model and serial number — identifies the equipment.
- Per-cycle verification value — the field reading, where the machine provides one.
- Method applied — degauss, crush, shred, and in which order.
- Operator name and signature — the trained person who did it.
- Client custodian signature — closes the chain of custody in front of the client.
- Volume reconciliation — assets in, assets destroyed, exceptions, discrepancies.
- Scrap and recycler reference — closing the chain to the e-waste recycler.
Reconcile the register against the client's asset list at the end of the job and state the exceptions. An unexplained discrepancy is the one thing that will be escalated.
3. Adding destruction to an existing ITAD service
- Assess your current drive volume and the media mix — including how much is flash, which most ITADs under-count.
- Decide whether destruction is in-house or sub-contracted, and document the decision.
- Specify the cell against volume: degausser, crusher, shredder, and consumables.
- Define the register format — ideally a client-specific export from your asset system.
- Train and certify operators, keeping training records for client audits.
- Establish the recycler relationship and the documentation you will present.
- Add the cycle verification value to the register; on a T-5 the digital cycle counter is a genuine selling point to bank clients.
- Put a maintenance schedule in place — a failed degausser stops revenue immediately, and a weak one produces evidence you cannot stand behind.
- Set up periodic client audits and self-audits so the first audit is not the first review.
4. Winning bank and government work
- Show the machine. Bring the T-4 or T-5 to a client demonstration. An NSA-listed machine with a live field reading sells itself.
- Show the register. A completed, signed register from a previous job, redacted, is the most persuasive document you can hand over.
- Show the verification certificate. Independent field verification of your own machine is what distinguishes a serious provider from a scrap merchant.
- Offer witnessed runs. Many banks require the client custodian to witness destruction. Build that into the service.
- Document your chain. Media intake, secured storage, destruction, scrap transfer to an authorised recycler, with a record at each step.
- Get the paperwork right first time. Most ITADs lose time to client-specific formats. Ask us for templates, or ask the client for their format before the job.
5. Common ITAD mistakes
- Under-counting flash. A job that looks like 400 drives may include 200 SSDs and 150 phones that need a shredder and a different line time.
- Batch-registering. Clients' auditors notice, and it undermines every other row in the register.
- Destroying before degaussing. It saves minutes and destroys the evidential basis of the job.
- No maintenance schedule. A capacitor failure mid-contract is both a revenue and a credibility problem.
- Not separating scrap streams. Magnetic scrap, flash scrap and general e-waste have different handling requirements and different recyclers.
- Battery-in-shredder. A safety incident on a client site ends the relationship.