We count visits with Google Analytics cookies and Vercel Web Analytics to see which pages help readers most.

Cookie settings
The Assurance Desk

39 of 55

discussions we read raised finding or reusing evidence

Customer security questionnaires: stop starting from scratch

What our study of customer security questionnaires reveals about finding proof, using AI and preparing for the next request.

A customer security questionnaire asks how your business keeps data and services safe. The buyer sends it to check the security of a supplier it plans to rely on. Your job is to explain what you do and provide evidence to support your answers.

Why filling in the form takes more than writing

Questions can cover who can access data and how your business would recover from a security incident.

An answer describes what your business does. Evidence is the material that backs it up, such as a written process or an audit report. The buyer can ask for that material alongside the form.

We wanted to understand what this work involves for the people doing it. On 15 October 2026, we analysed 124 posts and comments across 55 Reddit and Hacker News discussions. They describe experiences of answering customer forms and reviewing suppliers.

Finding or reusing evidence appeared in 39 discussions, compared with 15 for repeating answers or formats. Teams described searching scattered documents and reusing existing reports. That gives you a useful place to start: organise the material behind your answers.

Keep that material with a library of answers you can use again. It still needs someone to look after it. One respondent owned the spreadsheet, chased specialists and checked whether old answers remained true.

Start with a recent completed questionnaire. For each answer worth reusing, keep its supporting document, the person who can check it and the date last reviewed. Use that record as the starting point for the next customer.

discussions

  • Finding or reusing evidence 39 of 55
  • Accepted approach or useful workaround 30 of 55
  • What the review covers or how much proof is needed 28 of 55
  • Workload or questionnaire size 23 of 55
  • Who handles or checks the work 21 of 55
  • Repeating answers or formats 15 of 55
Chart values
Evidence featured most often in the discussions
Measurediscussions
Finding or reusing evidence39 of 55
Accepted approach or useful workaround30 of 55
What the review covers or how much proof is needed28 of 55
Workload or questionnaire size23 of 55
Who handles or checks the work21 of 55
Repeating answers or formats15 of 55
Selected themes in 55 public discussions, analysed 15 October 2026. Themes overlap and include successful approaches. Counts show mentions, not causes of delay.

most of the questions overlap but we still end up answering them from scratch

Give AI a clear job and a human reviewer

Teams in our study used AI tools to draft answers from their existing documents. Their experiences show why completing the questionnaire still needs a person.

An IT team checked each response its AI tool produced. Another team had an evidence library and AI help, but still entered answers into customers’ online forms and arranged human reviews. Producing a draft left those jobs to do.

A tool also needs a clear process to describe. One respondent knew how the company handled staff leaving but could find no agreed written process. Completing the form felt like inventing policy.

Waiting was a different problem again. A sales engineer described submitting answers quickly, then waiting weeks or months on the customer. Faster drafting would not address that reported wait.

Before choosing a tool or changing the process, name the work that is stuck. Use the questions below to decide what to tackle. Record time spent doing the work separately from time spent waiting for a reply.

Find the work that needs attention
Where work stopsAsk your teamNext move
Drafting answersHave we answered this before?Draft from checked answers and source documents, then review.
Finding proofWhich document supports the answer?Link the evidence and name someone to keep it current.
Agreeing a processHas the business agreed what it does?Get the decision from the person responsible before describing it.
Sending and checkingWho enters the answer and who signs it off?Assign both jobs before the response is due.
Waiting on the customerWho is reviewing it, and what is still open?Track the customer decision separately from your writing time.

Ask what the customer will accept

Before completing every box, find out what the buyer needs to see. Several accounts described customers accepting existing documents instead of a full new response.

A small software team was asked which AI models it used, what data they touched and how it governed their use. The team wrote its own PDF. The customer accepted it, even though the author felt the document was thin.

A different company described a document showing how its product design met its standards. It said customers usually accepted that document, with few follow-up meetings. In another account, a buyer accepted existing security reports after suppliers challenged requests they considered too large.

Other teams still completed long forms alongside their audit reports. Ask early which existing evidence the customer will accept and which questions still need a specific answer.

Start that conversation before copying answers into a new format. Agree what the review covers, offer the documents you already hold and confirm which questions still need answering.

Agree the response before rebuilding it

  1. Scope What product, data and service is the customer reviewing?
  2. Evidence Which existing documents and reports will they accept?
  3. Gaps Which questions still need a tailored answer?
Practical questions drawn from the reported experiences.

We wrote a PDF. They took it, but it felt thin.

Prepare for the customer you want to win

The practical question is what to have ready before the next customer asks. A separate UK government survey helps explain why this matters when selling to larger businesses.

In that survey, 48% of large businesses reviewed their immediate suppliers for cyber risks, compared with 12% of micro businesses. These are checks on firms they buy from directly. Supplier checks were more common among larger firms.

This separate survey covered 2,112 UK businesses between August and December 2025. Its results were weighted to represent the business population. These figures measure formal reviews of supplier cyber risks.

Build a pack of checked answers and supporting documents from your next completed review. Keep what the customer accepted and note questions that needed a new decision. Then assign someone to keep it current for the next request.

Take a recent questionnaire to your next team meeting. Use the table below to agree what belongs in that pack. Name who checks the answers, updates the documents and follows up with the customer.

UK businesses reviewing immediate supplier cyber risks

  • Micro businesses 12%
  • Small businesses 22%
  • Medium businesses 30%
  • Large businesses 48%
Chart values
UK businesses reviewing immediate supplier cyber risks
Measure%
Micro businesses12%
Small businesses22%
Medium businesses30%
Large businesses48%
UK Cyber Security Breaches Survey 2025/2026. Weighted percentages reporting formal immediate-supplier risk reviews. Unweighted bases: micro 1,154; small 507; medium 296; large 155.
Turn your last questionnaire into a plan for the next
Bring to the meetingDecide together
The answers already sentWhich can become checked starting points?
The documents used as proofWhere will they live, and who will update them?
The questions that needed a decisionWho has authority to agree the answer?
The finished responseWho checks the facts and handles the customer format?
The open customer questionsWho follows up, and what decision is needed?

How we did the research

The Assurance Desk analysed the material on 15 October 2026. We combined stored records, a focused Reddit collection, Hacker News searches and public-page readings. The study covers posts published from 15 October 2024 to 15 October 2026. We screened for the topic, then read relevant posts and comments for concrete first-hand experiences.

The sample contains 22 opening posts and 102 comments from 118 public accounts, across 48 Reddit and 7 Hacker News discussions. We removed duplicate captures. Each discussion counts once per theme, and themes overlap. Evidence mentions include successful reuse as well as difficulty finding proof.

This is an international discussion study, mainly from software and security communities. It is not a representative survey of businesses. Accounts and outcomes were not independently verified. Public handles do not establish a count of people or companies. The findings identify experiences and practical questions, not UK prevalence, typical completion times or savings caused by a tool.

Searches were limited and did not recover every comment. Reddit keyword discovery covered the past year within the longer study window. The same AI analyst screened and re-read the material, without an independent human review. Removing Reddit leaves 7 discussions; removing discussions with flagged vendor-mention accounts leaves 50. Full methods, theme counts and these checks are in the data download.

These quotations were checked against saved readings of public posts, which may not show later edits. They are public accounts, not interviews or expert endorsements.

What the expanded sample contains
MeasureCountWhat it means
Opening posts22Qualifying first-hand opening accounts
Comments102Qualifying replies, with repeated captures removed
Posts and comments together124The included text items, not survey respondents
Public accounts118Visible platform handles, not verified people
Discussions55Original threads, counted once per theme

Explore the data

Download the dataset or open the cited links in a spreadsheet.

Read next

Sources

  1. The Assurance Desk, Customer security questionnaire public-discussion study (study data and method), checked 16 October 2026
  2. A B2B team, public Reddit post, checked 16 October 2026
  3. A small software team, public Reddit post, checked 16 October 2026
  4. GOV.UK, Cyber security breaches survey 2025/2026, checked 16 October 2026
  5. NCSC, Supplier assurance: having confidence in your suppliers, checked 16 October 2026
  6. NCSC, Supplier assurance questions, checked 16 October 2026

This is an independent editorial guide, not legal advice.