The IT logistics market has a noise problem. "White glove," "data center specialists," "chain-of-custody assured" — these phrases cost nothing to put on a website. The vendors who use them range from genuinely excellent to deeply unqualified, and they are often indistinguishable until something goes wrong on your floor.
The good news: the real specialists are easy to identify if you ask the right questions.
1. Certifications — The Ones That Require Third-Party Audits
The most meaningful certifications in IT logistics are the ones that require unannounced or regular third-party audits of the vendor's actual processes — not just paperwork submissions or self-assessments. The relevant ones:
- NAID AAA (National Association for Information Destruction): The highest standard for data destruction. Requires unannounced audits. If your engagement involves any storage media disposal, NAID AAA certification is non-negotiable. Verify the certification number at naidonline.org.
- TAPA TSR (Transported Asset Protection Association Trucking Security Requirements): The benchmark for secure road transport of high-value cargo. Requires GPS real-time tracking, driver security protocols, and third-party audits. Increasingly required by enterprise clients for IT hardware shipments.
- R2 or e-Stewards: Recognized standards for electronics recyclers. If the vendor handles asset remarketing or recycling, require one of these.
- ISO 27001: Information security management certification. Indicates the vendor's internal processes for handling sensitive data have been independently audited.
A vendor who holds none of these certifications is relying entirely on their word. A vendor who holds all four has had their processes verified by parties with no financial interest in the outcome.
The question to ask: "Can you provide your current certification numbers so I can verify them directly?"
A qualified vendor answers this immediately. A vendor who says "we're in the process of certifying" or "we follow NAID AAA standards" — without holding the certification — is telling you something important.
2. Cargo Insurance — What the Policy Actually Covers
General liability insurance is not the right coverage for IT equipment in transit. Ask specifically for the cargo insurance certificate and review it before any equipment moves. The details that matter:
- Does it cover electronics? Some cargo policies exclude electronics or "fragile goods" by category. This exclusion is buried in the fine print and is not unusual.
- What is the per-item limit? A policy with a $50,000 per-item limit is inadequate for a server chassis worth $150,000. Get the per-item and aggregate limits in writing.
- Does it cover the full replacement value of the cargo you are moving? Declared value and market value are often different. The cargo policy should cover replacement value, not depreciated book value.
- Who files a claim, and what is the process? Understanding the claims process before you need it reveals a lot about how the vendor handles problems.
The question to ask: "Can you email me your current cargo insurance certificate before we proceed? I want to verify the coverage limits against the value of equipment we are moving."
A vendor who resists this request — or who takes more than 24 hours to produce a certificate — is a vendor whose coverage you should not trust.
3. On-Site Personnel — Employees vs. Subcontractors
This is the question most buyers forget to ask, and it is one of the most consequential.
Many logistics companies that market themselves as IT specialists operate primarily as brokers or coordinators. When your project begins, the crew that shows up at your facility is a subcontracted team — often sourced through a staffing agency or a local labor broker — whose background checks were done by someone other than the vendor you hired, under standards you did not agree to.
The risks:
- Background check gaps: the vendor you contracted may have a thorough screening process for their employees, but no visibility into the subcontractor's practices
- Training gaps: subcontractors are not trained on the vendor's specific procedures. They bring whatever habits they developed at previous jobs.
- Accountability gaps: when something goes wrong, you have a vendor-subcontractor chain to work through instead of a direct employee relationship
For access to sensitive environments — data centers, server rooms, facilities with compliance requirements — direct employees with documented background checks are the appropriate standard.
The questions to ask: "Will the technicians on our floor be your direct employees? What background check process do they go through, and how recently was it completed?"
A vendor who uses subcontractors is not automatically disqualified, but they should be able to describe the subcontractor's screening process in detail. Vague answers here are a real risk signal.
4. Fleet Specifications — The Right Vehicle for the Cargo
Not all trucks are appropriate for sensitive IT equipment. The physical transport environment matters:
- Air-ride suspension: Air-ride trucks absorb road vibration far better than standard leaf-spring suspension. For equipment with sensitive components — blade servers, networking hardware, storage arrays — this reduces the risk of transport-induced damage. Ask specifically.
- Climate control: Temperature and humidity variations during transport affect sensitive electronics. For long-distance moves or routes through extreme climates, climate-controlled transport is the appropriate standard.
- Vehicle security: Cargo area monitoring, high-security door locks, GPS tracking, and tamper-evident sealing capabilities. A TAPA TSR-certified provider has all of these as standard.
- Dedicated transport: Equipment should move on a dedicated vehicle — not shared with other cargo, not transferred at a cross-dock, not handed off to a regional carrier for the last mile. Each handoff is a chain-of-custody gap and a damage risk point.
The questions to ask: "Do your vehicles have air-ride suspension? Is transport point-to-point on a dedicated vehicle, or does cargo transfer between vehicles or facilities?"
A specialist answers both confidently. A general freight company will tell you shared loads are standard. For IT equipment, they are not acceptable.
5. References — Comparable Projects, Verifiable Contacts
References are the oldest vetting tool, and they remain one of the most reliable — if you ask for the right ones.
Generic references from satisfied clients are not useful. Ask specifically for:
- References from projects comparable in type and scale to yours. If you are decommissioning a 200-rack data center, ask for a reference from a similar decommission — not from a customer who had three servers moved.
- References from organizations in a similar compliance environment. If HIPAA or PCI-DSS governs your project, a reference from another healthcare or financial services client is more meaningful than a reference from a retail company with no compliance requirements.
- Verifiable contacts. Name, company, and direct contact information — not a testimonial on their website. Call them. If you cannot reach a live person, the reference is not real.
When you speak to references, ask three questions: Did they do what they said they would do? Was there anything that went wrong, and how did they handle it? Would you use them again for a project of the same type?
The third question is the most revealing. "Yes, without question" is a very different answer from "Yes, probably" — and both are different from a long pause.
The Shortcut: Let Someone Else Do the Vetting
If this process sounds time-intensive, it is — because the stakes justify it. Moving equipment that is worth hundreds of thousands of dollars, that contains sensitive data, and that your operations depend on is not a procurement decision to delegate to the lowest bid.
Running these five checks takes real time: cross-referencing certification directories, reviewing insurance certificates, evaluating fleet specs, calling actual references. Done properly, that is a week of procurement work per vendor. PowerRoute completes this vetting before providers join the network. Post a project brief and you get proposals from providers who have already passed all five. You still pick who you work with — you just do not run the same checklist twice.