When the Vendor Won't Answer
Five of the 21 third-party risk teams we spoke with this fall asked the same uncomfortable question in different words. What do you do when a vendor won't respond? When they won't share their SOC report without an NDA that takes three weeks? When a very large supplier simply refuses to use your portal or fill in your spreadsheet?
One team mentioned vendors that had started charging customers to answer questionnaires. Another asked a sharper question: if vendors already refuse shared questionnaire platforms, why would they agree to upload documents anywhere else?
Every TPRM program has a list of these vendors. It is usually longer than anyone admits.
Why vendors stop answering
It helps to start from the vendor's side. A mid-sized software company might receive hundreds of security questionnaires a year, each slightly different, each asking for the same information in a new format. Large vendors receive thousands. For them, answering questionnaires is a cost with no end, and the rational move is to standardize: publish a trust center, offer the SOC report under a click-through NDA, and decline custom questionnaires.
From the vendor's side, that is not evasion. It is the only answer that scales. From the risk team's side, it looks like a refusal, and the instinct is to escalate. Escalation rarely works with a vendor whose leverage is bigger than yours.
Size changes what "answer" means
The first step is accepting that non-response means different things for different vendors.
For very large, well-documented vendors, the major cloud providers and household-name software platforms, the information you need almost always exists already in public or semi-public form. They are not going to answer your questionnaire, and they don't need to. The work is reading what they publish: the SOC report from their trust portal, their subprocessor list, their security documentation, their contractual commitments.
For small vendors, non-response often means something else. They don't have the answer, or don't know how to give it. A small vendor with no SOC report and no security team may go quiet because the honest answer is uncomfortable. That is a risk signal in itself, and it deserves a conversation, not another reminder email.
For mid-sized vendors, non-response is usually friction: the wrong contact, a long questionnaire, nobody assigned to it. This is the group where asking for less makes the biggest difference.
Ask less, and ask later
The most effective fix for non-response is sending fewer questions. If the evidence a vendor has already published answers most of your questionnaire, the remaining handful of questions is far more likely to get a reply than 200. A short, specific ask signals that someone actually read their documentation. A long generic one signals the opposite.
Several teams described wanting to collect documents first and decide on questions second: ask the vendor to upload what they already have, review it, then send only what is left. That order respects the vendor's time, and vendors respond to it.
Get the documents without the email chain
The NDA problem is real. Many trust portals require an NDA before releasing a SOC report, and the NDA can sit with legal for weeks. A few practical approaches:
- Keep a standing mutual NDA template for vendor security documentation, separate from commercial NDAs, so legal isn't reviewing a fresh one every time.
- Ask for the SOC report during procurement, while the vendor is still trying to win the business.
- Write documentation access into the contract: the right to receive the current SOC report and bridge letter every year.
- Let vendors upload documents directly, so security reports don't travel through email and personal inboxes.
The contract point matters most. Once a vendor is signed, your leverage drops. Requests that are contractual obligations get answered. Requests that are favors get queued.
Decide what silence means
Eventually some vendors will not answer, and the program needs a policy for that rather than an open ticket that ages forever. Silence is information. A critical vendor that won't provide evidence is a vendor whose risk can't be assessed, and it should go to a decision maker as exactly that: an unassessed risk, with the business owner asked to accept it, mitigate it, or find an alternative.
Documenting that decision protects everyone. The examiner sees a program that found the gap and escalated it. The business owner understands what they are accepting. The risk team stops carrying an open item it has no power to close.
The vendor is not the adversary
The deeper shift is in posture. Third-party risk often treats the vendor as a respondent who owes answers. In practice, the vendor is a counterparty with its own constraints, and most vendors are trying to give customers what they need in a way they can sustain.
Programs that read what vendors already publish, ask only what's left, and make access a contract term get more answers with less chasing. The ones that keep sending the long questionnaire get the same silence, and a longer list of vendors who won't respond.