# How to handle requests for security or compliance docs
> Learn how to answer security and compliance document requests on LinkedIn, qualify the reviewer and turn the ask into a technical call before review starts.
- HTML: https://getkinlead.com/reply-to-prospect-asking-for-security-docs
- Markdown: https://getkinlead.com/reply-to-prospect-asking-for-security-docs.md

**Short answer:** When a prospect asks for security or compliance docs on LinkedIn, reply that you can send them and ask one qualifying question before you do. Use the request to book a short technical call, confirm who reviews the documents and which framework they need. Then send the right file within the hour with a note that maps it to their concerns.

## What a security document request actually means

A request for a SOC 2 report, a security whitepaper or a filled questionnaire usually arrives after a prospect has decided your product might fit. They are checking whether their company can say yes. That makes the request useful. It gives you a reason to ask about their setup without sounding like you are stalling.

The same message can mean two different things. Sometimes the buyer needs a box ticked for procurement and will move once the file lands. Other times the IT or security team is the real decision maker and will reject anything that does not match their checklist. You cannot tell which one you have from the LinkedIn message alone.

Your job is to find out before you send a 40-page PDF into a queue. A short reply that agrees to send the docs and asks one question does more for the deal than a fast attachment.

**Send the file and wait**

- Reply with the PDF attached and no question
- Hope the reviewer finds the sections that matter
- Follow up a week later asking if they looked at it

**Ask one question first**

- Say you can send the docs and ask who will review them
- Ask which framework or checklist they use
- Offer a 10 minute call to confirm what to send

## Reply without sending the file first

The reply should do three things: confirm you have the document, show you take the review seriously, and give the prospect a small next step. Keep it short. Long security emails read like legal notices and get postponed.

Frame it as ten minutes to make sure the file you send answers the reviewer's questions. That is a reasonable request and most buyers accept it.

If the prospect says they only need the PDF, send it, but add one question in the same message. Ask which part of their review it needs to satisfy. That question keeps the thread alive and tells you what to follow up on.

- **them:** Can you send your SOC 2 report? My IT lead wants to review it before we go further.
- **you:** Yes, I can send it today. So I don't send the wrong version, who will review it, and are they working from a specific checklist? If it helps, I can take 10 minutes tomorrow to confirm what your IT lead needs.
- **them:** It's our security lead. She uses a vendor checklist based on SOC 2 and GDPR.
- **you:** That helps. I'll send the SOC 2 report and the GDPR summary, and I'll flag the sections that match her checklist. Does 10:30 tomorrow work for a quick call?

## Qualify the reviewer and framework on a short call

On the call, do not walk through your whole product. Ask about the review process. You need to know who can say no, what they check, and what has caused vendors to fail before.

Start with the reviewer. A procurement officer, a security lead and an external auditor care about different things. Procurement wants paperwork and signatures. A security lead wants evidence that controls exist. An auditor wants a trail. Your answers change based on who is reading.

Then confirm the framework. Some companies need SOC 2. Others need ISO 27001, HIPAA, GDPR or a custom vendor questionnaire. Sending a general security whitepaper when they need a specific report wastes everyone's time.

1. **Ask who reviews the documents.** Get a name or a role. Ask if that person can approve a vendor alone or if the review goes to a committee. This tells you how much work is ahead.
2. **Confirm the checklist.** Ask for the framework, questionnaire or internal checklist they use. If they can share the blank checklist, ask for it. You can answer the exact questions instead of guessing.
3. **Find the common rejection reason.** Ask what usually stops a vendor from passing their review. Listen for missing encryption details, subprocessors, data residency or incident response. Address that point in your follow-up.
4. **Ask for the timeline.** Find out when the review starts and when they need a decision. A review that starts next month changes how you follow up.

## Send the documents with context

Send the file within an hour of the call while the details are fresh. Attach the report, then write three or four lines that connect the document to what the reviewer said. Do not make the buyer hunt for the answer.

If the reviewer asked about data encryption, point to the page or section that covers it. If they asked about subprocessors, name the section. If they use a checklist, answer the checklist items in the email or in a separate document.

Keep the email plain. The buyer may forward it to IT, so write it for someone who was not on the call. Avoid jokes, internal shorthand and anything that sounds like marketing.

```
Subject: Security docs for [Company] review

Hi [Name],

Thanks for the call today. Attached are the documents we discussed:

- SOC 2 Type II report
- Security whitepaper
- GDPR data processing summary

For your reviewer: the encryption section is on page 12, the subprocessor list is in appendix B, and the incident response process is on page 18. I have also answered the three checklist items you mentioned in the body below.

If your security lead has follow-up questions, I can join a call or answer them by email. What date works for you to review the documents together?

[Your name]
```

## What to do when you lack the certification

Sometimes the honest answer is that you do not have the report they asked for. Do not fake it or send a different document and hope they do not notice. Say what you have, say what you are working toward, and give them a way to evaluate the risk.

A security whitepaper, a completed questionnaire, a pen test summary and a clear description of your controls can carry a deal when a formal certificate is missing. What matters is whether the reviewer can verify your claims. Offer evidence, not assurances.

If the missing certificate is a hard requirement, ask who set the requirement and whether there is an exception process. Some companies allow a vendor review with compensating controls. Others do not. You need to know which one you are dealing with before you spend weeks on a review that cannot pass.

> If you do not have the document, say so in the first reply. A clear gap is easier to handle than a surprise found by the reviewer.

## Keep the review moving without chasing

Security reviews stall for boring reasons: the reviewer is busy, the questionnaire is long, or your email landed in a shared inbox. Your follow-up should make the next step easier. A status update does not do that.

Send a short note with one useful item. Offer to fill in the questionnaire on a call. Ask if the reviewer needs a specific section. If you have a deadline, say what you need and why.

Use a table to track what the buyer asked for and what you sent. This is also a good way to keep your own team honest when a prospect comes back with a follow-up question two weeks later.

| | Request | What you send | Who reviews it | Next step |
| --- | --- | --- | --- | --- |
| SOC 2 report | SOC 2 Type II PDF | Security lead | Confirm receipt and offer a call |
| GDPR summary | Data processing addendum and subprocessor list | Legal or privacy lead | Ask if the standard DPA works |
| Vendor checklist | Completed checklist with evidence links | Procurement | Review answers together on a 15 minute call |

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line are not kept. When a prospect replies asking for security docs, the reply lands in the unified inbox classified by intent, with interested replies first.

Each campaign chooses how replies are handled. Hand-off mode gives the conversation to you at the first reply, which is the right setting when you want to qualify the reviewer before any document goes out. You can read and edit queued messages on the Actions page, pause a campaign, and set the send window in the lead's time zone. Outreach runs from your own LinkedIn account through Unipile, and Kinlead never stores your LinkedIn password.

You can start a free trial at [sign up](/signup).

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Unified inbox](https://getkinlead.com/features/unified-inbox.md)
- [AI reply modes](https://getkinlead.com/handling-limits-with-ai-reply-modes.md)

## Common questions

**Should I send my security docs in the first message?**

No. Sending docs before you know who reviews them makes it harder to book a call and easier for the file to sit in a queue. Wait until the prospect asks, then use the request to ask one qualifying question.

**What do I do if I don't have a SOC 2 report yet?**

Say so in the first reply. Send the evidence you do have, such as a security whitepaper, a completed questionnaire or a pen test summary, and explain what is in progress. Ask whether their process allows compensating controls.

**How do I handle a prospect who refuses to call before seeing the docs?**

Send the documents, but include one specific question about their review in the same message. Ask which checklist item matters most or who will read the report. That gives you a reason to follow up without asking for a status update.

**Who should I ask for on the security call?**

Ask for the person who can reject the vendor. That is often a security lead, a procurement officer or an external auditor. If they cannot share a name, ask for the role and the checklist they use.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
