Skip to content
Answer Stack
Open menu

What documentation should a mid-market ITAD engagement produce?

✓ Verified Last reviewed by AnswerStack Next review due Dec 14, 2026

Every claim is sourced below

A mid-market ITAD engagement should produce a file that accounts for every device you handed over. That file holds the inventory you made before pickup, signed custody records for the shipment, the provider's inventory of what it received, a sanitization or destruction record for each device that stored data, a record of where the hardware went afterward, and a settlement for anything resold. You should be able to pick any serial number from your list and follow it to one recorded outcome. If you can't, the file has a gap, however many certificates it contains.

Start with a list you made before pickup

The first document is yours. Before anything leaves the building, list each device by make, model and serial number, and add your asset tag where you use one. Every later record gets compared with this list. If nobody at your company works on asset disposal full time, that comparison should be something one person can do in a spreadsheet.

NIST makes the case for the list in its media sanitization guidelines, revised in September 2025. Sanitization records are most useful, it says, when you also keep records of when media entered your environment, when it left the place it was last used and when it reached its destination afterward. If tracking breaks down before that last stage, the certificates show that particular media were sanitized. They don't show that all of your media were.

What the custody record covers

The custody record covers the trip from your site to the provider's. Greentec, an ITAD provider with a processing facility in Ontario, describes what goes into one in its account of its chain-of-custody service. The customer sends a manifest or inventory list with each shipment, along with a bill of lading. The driver checks and signs the bill of lading, which describes the materials and gives the number of skids or containers, their weights, the pickup location and time, and the destination. When the shipment arrives, Greentec says each container or skid is checked against the manifest and the bill of lading. Any discrepancy is written on the bill of lading and reported to the logistics supervisor.

A bill of lading records the number of containers and their weight, so it can show whether the same count arrived that was picked up. Which devices were inside is a question for the two inventories, yours and the provider's. Keep the signed copy from pickup, and ask for the receiving record with any discrepancies noted on arrival.

Inventory and sanitization evidence are separate records

Once the equipment is unpacked, the provider makes its own inventory. On its enterprise ITAD page, Greentec says its inventory lists each item's make, model and serial number, along with diagnostics and an asset tag or location. This is the record you match against your own list, line by line.

An inventory line shows that a device was received. It says nothing about the data on it. That takes a second record. NIST says a certificate of sanitization should be completed for each storage medium, as your organization's policy directs. It should give at least the manufacturer, model and serial number, the media type and source, the method and technique, the tool and its version, the verification method, and who verified and validated the result, with a date, location and signature. NIST's sample form is an example, and an electronic record serves as well.

Verification and validation are two steps in that record. Verification checks that the technique finished properly, for instance by reading the tool's completion status and errors. Validation is the decision to accept the result as effective or reject it. NIST's example is degaussing a solid-state drive: the operation can complete while no sensitive data is sanitized. So a line that says "completed" is evidence that a tool ran. The method, the media type and the name of the person who accepted the result let you judge whether that method suited the device.

Greentec's process shows why the two records have to be read together. It says drives are wiped with licensed software, and any device that fails to wipe is physically shredded. It issues a certificate of data erasure backed by the serialized inventory. For shredded devices, it describes a certificate of destruction that gives the services performed, the time of destruction, and the make, model and serial number of each device. Shredding happens at its plant or at the customer's site with a mobile shredder.

So one laptop can start on the erasure path and end on the destruction path. The file should show that change against its serial number. If it doesn't, a failed wipe and a missing certificate look the same from your side.

Where the hardware and the money go

Sanitization isn't the end of the device. It gets resold, destroyed or broken down for materials, and the file should say which. Greentec describes those three paths on its enterprise page. Devices that can be remarketed are resold, with rebate value passed back to the customer. A device that fails wiping goes to the shredder. The rest, electronics that can't be refurbished, are broken down for copper, steel, aluminum and precious metals. Greentec documents each of those material streams by weight in a certificate of recycling.

A certificate by weight is the right record for material, but it can't identify a device, because shredded steel carries no serial numbers. So the outcome for each device has to come from the inventory, where every line should end in resold, destroyed or recycled. If equipment leaves your provider for another processor, the record should name that company. Whether you get that name is a term to settle in the contract.

The money needs its own statement. Resale proceeds are a commercial term, so the contract decides how they're calculated and reported. We'd ask for the settlement by serial number: the sale price or agreed value for each resold device, any fees deducted, and the amount paid to you. Then a resold serial number can be matched to its erasure certificate. A device that appears in the settlement with no sanitization record is the case you most want to catch.

Record What it records What it leaves open
Your inventory, made before pickup Which devices you meant to retire, by serial number Whether the list was complete
Signed bill of lading and receiving record Containers, weights, pickup time and place, and discrepancies on arrival Which devices were inside
Provider's serialized inventory Which devices the provider received, and their condition What happened to the data
Certificate of sanitization or erasure The method, tool, verification and sign-off for a serial number Where the device went next
Certificate of destruction That a serial number was physically destroyed, and when What became of the material
Certificate of recycling Material streams by weight The outcome for any one device
Settlement statement What each resold device earned and what you were paid Whether the data was removed first

Matching totals can hide a mismatch

Suppose you retire 300 laptops from two offices. Your list has 300 serial numbers, and the provider's inventory comes back with 300 lines. The totals match, and it's tempting to stop there.

Now match the serial numbers. Suppose 296 of them appear on both lists. Four of yours are missing from the provider's inventory, and four of the provider's aren't on your list. The count hid this because the two errors cancel.

One harmless explanation is a recording difference. Someone typed an asset tag where the serial number belonged, or your list carries the laptop's serial number and the provider recorded the drive's. A worse one is that four of your laptops never arrived and four devices from somewhere else did. You can't tell which from the totals, so each of the eight lines needs an answer in writing.

That written answer is the exception report. It lists every line that didn't match and says how each one was resolved. Lines that are still open stay on it.

The same check applies to outcomes. Suppose the 296 matched laptops close out as 235 erased and resold and 61 shredded, nine of those after a failed wipe. You should then hold 235 erasure records, 61 destruction records and a settlement covering 235 serial numbers. Each of the nine failed wipes should show an erasure attempt that was rejected, followed by a destruction record. Add the four laptops still open on the exception report and you're back at 300, with each one in exactly one place. The provider's four unmatched lines stay on that report too, until someone says whose devices they were.

What certification and the contract each settle

Greentec says it holds NAID AAA certification for data destruction and R2v3 certification for refurbishment and recycling, and that both are independently audited. A certification like those tells you that a provider's process has been checked against a published standard. That helps when you're choosing a provider. It doesn't decide what your own file has to contain.

What you're required to keep is a separate matter. It depends on the kind of data the devices held, and on the laws, regulators and customer contracts that apply to you. So the provider's certification, your own obligations and the contract answer different questions.

The contract is where you can specify the file. Greentec's public pages describe the documents it issues. Delivery timing, file format, export access and any reporting fees are contract terms, with Greentec as with any provider. In the statement of work, name each document and set a delivery date after processing. Say that the inventory, the device-level certificates and the settlement are reported by serial number, and the recycling certificate by weight. State how long the provider keeps its copy. How long you keep yours depends on your own obligations. No single retention period applies to every company.

What the file leaves open

A complete file shows what was recorded. It can't show that your starting list was complete, because a device you never listed can't turn up as missing. That part belongs to your own asset management.

The file also records work you didn't see. A certificate is the provider's statement that the work was done. If you need more than a statement for some equipment, you can ask to witness the destruction, and having it done at your site is one way to arrange that. We weigh those in whether NAID AAA certification covers onsite hard-drive destruction and whether onsite destruction is worth the premium over offsite.

Sources

NIST SP 800-88 Revision 2, Guidelines for Media Sanitization

National Institute of Standards and Technology

Primary source Verified Sep 15, 2026 Supports: Sec. 4.6 per-medium certificate of sanitization and its minimum field list; optional pre-sanitization categorization; electronic records preferred for retention and search; lifecycle record-keeping rationale that sanitization records alone cannot show whether all media are being sanitized; verificat

“Following sanitization, a certificate of sanitization (see Appendix C) should be completed for each ISM that has been sanitized, per the organization's policies.”

SP 800-88 Rev. 2, Guidelines for Media Sanitization

NIST Computer Security Resource Center

Primary source Verified Sep 15, 2026 Supports: Revision 2 is final, published September 2025, and supersedes SP 800-88 Rev. 1 (12/17/2014)

“Date Published: September 2025. Supersedes: SP 800-88 Rev. 1 (12/17/2014)”

SP 800-88 Rev. 1, Guidelines for Media Sanitization (withdrawn)

NIST Computer Security Resource Center

Primary source Verified Sep 15, 2026 Supports: Revision 1 was withdrawn on September 26, 2025 and superseded by Revision 2, which is why a contract specification citing Rev. 1 is out of date

“Withdrawn on September 26, 2025. Superseded by SP 800-88 Rev. 2”

i-SIGMA Certification Specifications Reference Manual (0925M)

i-SIGMA

Primary source Verified Sep 15, 2026 Supports: Serial-number recordation for hard drives and solid-state devices and return of the log to the data controller unless an opt-out agreement is signed; custody-transfer receipt showing type and quantity; written disclosure of a subcontractor's name and service; advance written description of the destr

“The log of recorded serial numbers is returned to the Data Controller upon the completion of the service, unless the Data Controller has opted out of this requirement.”

NAID AAA Certification | Secure Data Destruction

i-SIGMA

Primary source Verified Sep 15, 2026 Supports: The certification runs an audit program including both scheduled and unannounced reviews, and endorsements define services such as mobile on-site, facility-based operations, and specific media types

“a rigorous audit program that includes both scheduled and unannounced reviews”

Customer Misconception: The Certificate of Destruction Removes Regulatory Liability

i-SIGMA (Bob Johnson)

Supporting Verified Sep 15, 2026 Supports: The certification body's own position that a certificate of destruction does not transfer regulatory responsibility from the client to the service provider and that the client answers for its selection of that provider. Trade association commentary, attributed in text and not treated as a regulator'

“the more significant reason the CoD is not capable of transferring liability is because regulations do not allow for it”

Summary of R2v3 Requirements

SERI (Sustainable Electronics Recycling International)

Primary source Verified Sep 15, 2026 Supports: Core 5 tracking records for inbound, in-process, and outbound streams and the one-year storage limit on negative value streams; Core 7 data security and the two sanitization paths; Appendix A downstream tracking to final disposition, the definition of final disposition, and the allowance to stop tra

“Downstream tracking and verification can stop at the first R2v3 Certified DSV since that vendor has already been audited and verified through the certification process. Facilities that choose to stop tracking at the first R2v3 facility, must register their downstream chain with SERI.”

Discussion on Logical Data Sanitization in R2v3

SERI R2 Guidance and Knowledge Base

Primary source Verified Sep 15, 2026 Supports: Spreadsheet sanitization records invite transcription and copy-paste errors; per-step, per-device technician signoff instead of a batch signoff; Appendix B(13) verification is an actual attempted recovery with commercial software and not a records check; R2v3 sits between NIST's Clear and Purge and

“Appendix B(13) is different than verifying that a record of data sanitization is available for the media. This requirement relies on the technique of actually trying to recover data from the device.”

Morgan Stanley Smith Barney to Pay $35 Million for Extensive Failures to Safeguard Personal Information of Millions of Customers

U.S. Securities and Exchange Commission

Primary source Verified Sep 15, 2026 Supports: September 20, 2022 announcement; $35 million penalty settling charges under the Safeguards and Disposal Rules of Regulation S-P; the firm-run records reconciliation during branch and local office decommissioning that revealed 42 missing servers potentially holding unencrypted customer PII and consum

“A records reconciliation exercise undertaken by the firm during this decommissioning process revealed that 42 servers, all potentially containing unencrypted customer PII and consumer report information, were missing.”

OCC Assesses $60 Million Civil Money Penalty Against Morgan Stanley

Office of the Comptroller of the Currency

Primary source Verified Sep 15, 2026 Supports: October 8, 2020 action assessing a $60 million civil money penalty against Morgan Stanley Bank, N.A. and Morgan Stanley Private Bank, N.A.; the finding that the banks failed to maintain appropriate inventory of customer data stored on decommissioned hardware devices and failed to adequately assess t

“failed to maintain appropriate inventory of customer data stored on the decommissioned hardware devices”

45 CFR 164.310, Physical safeguards

Cornell Law School, Legal Information Institute

Independent Verified Sep 15, 2026 Supports: Device and media controls standard; Disposal and Media re-use are Required implementation specifications; Accountability, meaning a record of the movements of hardware and electronic media and any person responsible, is Addressable; neither specification states a retention period

“Accountability (Addressable). Maintain a record of the movements of hardware and electronic media and any person responsible therefore.”

45 CFR 164.316, Policies and procedures and documentation requirements

Cornell Law School, Legal Information Institute

Independent Verified Sep 15, 2026 Supports: Six-year documentation retention as a Required implementation specification, running from creation or from the date the documentation was last in effect, whichever is later, and applying to the covered entity's or business associate's own documentation

“Retain the documentation required by paragraph (b)(1) of this section for 6 years from the date of its creation or the date when it last was in effect, whichever is later.”

Must Have Elements of a Data Destruction Certificate

Blancco

Supporting Verified Sep 15, 2026 Supports: A data erasure vendor's own element list for certificates its software produces: software and version, sectors reviewed or remapped, erasure start and end time with duration, method and level, pass or fail status, manufacturer, model, serial numbers, report UUID, report date, digital signature, and

“Date and duration of erasure with start/end time... Method used (IEEE 2883, NIST 800-88, etc.) and level of erasure (Clear/Purge)... Status of erasure (pass/fail)”

Revision history

1 revision since publication
Originally published