Business & Strategy
Supplier Security Questionnaire Prep: Answers, Evidence, and Assessment Readiness in One Place
Advanced | 4 whiteboard pages · Task board: 4 columns (4 parent tasks, 12 subtasks)
Advanced: Assumes you know the technical terms and methods, and the steps are only outlined. Work through it on your own, guided by decision criteria and points to check.
Use this supplier security questionnaire template to keep your answers, and the evidence behind them, in one place. Each answer gets an owner and an update cycle, so the next questionnaire gets the same replies. The questions repeat across customers, covering security policy and owner, accounts and MFA, software updates, backups, and incident contact. Saying yes without proof is a common trap, so items with outdated or missing evidence become gaps, sorted into fix, explain, or say you cannot. Anything not in the table goes to one contact point, so sales do not promise on the spot. In Japan, METI (the Ministry of Economy, Trade and Industry) is preparing a supply chain security evaluation scheme, with the framework published in March 2026, applications for ★3 and ★4 planned to open in March 2027, and ★5 under study. Check METI's latest announcements for timing and requirements. The whiteboard has 4 pages, and the task board has 4 columns with 4 parent tasks and 12 subtasks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Supplier Security Questionnaire Prep
How to use (4 pages): ① Page 1: purpose, questionnaires and areas (boards①–⑤) → ② Page 2: answers and evidence for 6 items, pitfalls (boards⑥–⑨) → ③ On page 3, decide the gaps: fix, explain, or say you cannot (boards⑩–⑭) → ④ On page 4, set update cycles and the intake flow (boards⑮–⑰)
1/4 Surface what customers ask
① Purpose and scope (start here)
- Why align answers e.g. Keep answers from varying by customer by gathering answers and evidence in one place
- Scope and deadline e.g. Questionnaires from the 3 main customers. Fill in the table of ⑥ by the end of next month
- Preparing for the evaluation scheme e.g. In Japan, METI is preparing a supply chain security evaluation scheme (framework published March 2026, applications for ★3 and ★4 planned to open in March 2027, ★5 under study). Check METI's latest announcements for timing and requirements
② Questionnaires received (by customer)
| Questionnaire type | Due date | Owner | Current status | |
|---|---|---|---|---|
| Customer A | e.g. Own checklist (40 questions) | e.g. End of this month | e.g. Head of administration | e.g. In progress |
| Customer B | e.g. Questionnaire in an industry body format | e.g. Second week of next month | e.g. IT lead | e.g. Not started |
| Customer C | e.g. Annual check | e.g. Before each contract renewal | e.g. Sales to the contact point | e.g. Last year's answers as they are |
| Expected soon | e.g. Screening of a new customer | e.g. Before the contract | e.g. Undecided | e.g. Not yet prepared |
③ Common areas: rules and structure
- e.g. Do you have a security policy and a named owner?
- e.g. Do you manage your subcontractors?
- e.g. Do you disable accounts when people leave or move?
④ Common areas: technical safeguards
- e.g. Do you use multi-factor authentication?
- e.g. Do you keep software up to date?
- e.g. Can you restore from backups?
⑤ Common areas: incident readiness
- e.g. Who do you contact when you notice an incident?
- e.g. Within how many hours do you notify customers?
- e.g. How do you restore the work that stopped?
2/4 Collect answers and evidence
⑥ Answers and evidence for 6 items picked from ③–⑤
| Our answer | Evidence document | Evidence status | |
|---|---|---|---|
| Policy and owner | e.g. Basic policy in place. Owner is the head of administration | e.g. Information security policy and the record of the owner's appointment | e.g. Outdated. Last revised over a year ago |
| Account management | e.g. Accounts are disabled on the day someone leaves | e.g. Offboarding records and the account list in the admin screen | e.g. Outdated. No record of reviewing the list |
| Multi-factor authentication | e.g. Required for email and accounting. Mostly authenticator apps, some SMS | e.g. Screenshots of the admin settings screen | e.g. Exists. Some are still on SMS (weaker than authenticator apps or passkeys) |
| Software updates | e.g. Automatic updates are on for devices | e.g. Device management screen and update records | e.g. Missing. No records are kept |
| Backups | e.g. Taken daily and also stored in another location | e.g. Backup settings screen and records of test restores | e.g. Outdated. The last restore test was 2 years ago |
| Incident contact | e.g. Notify customers within 24 hours of noticing an incident | e.g. Incident response procedure and contact list | e.g. Missing. Only a verbal rule |
⑦ Pitfall: stopgap answers contradict each other later
- What can happen: e.g. You tell customer A everything is encrypted and customer B only some, and they compare notes and trust drops
- How to check: e.g. Line up past answers against the table in ⑥ and mark items where the answer differs
- How to prevent: e.g. Copy the wording from ⑥ as it is, and fix the table first if you want to change it
⑧ Pitfall: answering "yes" with no evidence
- What can happen: e.g. A follow-up asks for documents you cannot produce, and the whole answer is doubted
- How to check: e.g. For rows marked yes in ⑥, see whether you can name the evidence and where it is kept
- How to prevent: e.g. For items with no evidence, write "in preparation" with a target date
⑨ Pitfall: never updating the answers
- What can happen: e.g. You keep sending old answers after a handover or a settings change
- How to check: e.g. Compare when each row of ⑥ was last fixed with when policies or settings changed
- How to prevent: e.g. Set the update cycle in ⑮ and fix the table in ⑥ the week a setting changes
3/4 Decide on the gaps
⑩ Gap analysis (pick one row from ⑥ with evidence outdated or missing)
- As-Is Current state e.g. Software updates are automatic, but there is no record that they succeeded
- Gap and issue e.g. No record showing update status, and nobody checks it
- To-Be Target state e.g. Record update status monthly in the device management screen and show it on request
⑪ Frequency asked × effort to fix (place the gaps from ⑩)
Vertical axis: How often it is asked (higher = more often) / Horizontal axis: Effort to fix (further right = more)
- Often asked, low effort Fix right away. e.g. Switch SMS codes to an authenticator app
- Often asked, high effort Plan and fix. Explain the status and plan until fixed. e.g. Write the incident response procedure
- Rarely asked, low effort Fix when you have time. e.g. Record the owner's appointment
- Rarely asked, high effort Candidate to say you cannot for now. e.g. Obtain a third-party certification
⑫ Fix (what and by when)
- e.g. Switch SMS codes to an authenticator app. By the end of this month
- e.g. Start keeping the update record monthly. From next month
- Once fixed, change the status in ⑥ to "exists"
⑬ Explain (current status and plan)
- e.g. The incident response procedure is being written. Answer with the planned completion date
- e.g. Add one line on the substitute measure you use now
- Never word it to look better than the reality
⑭ Say you cannot (reason and substitute measure)
- e.g. We will not obtain a third-party certification this fiscal year
- e.g. Add one line with the reason and the substitute measure
- Get the owner's approval before telling the customer
4/4 Keep answers up to date
⑮ Where the evidence in ⑥ is kept and how often it is updated
| Location | Update cycle | Update owner | |
|---|---|---|---|
| Policies | e.g. Shared folder "Policies" | e.g. Once a year and when the organization changes | e.g. Head of administration |
| Settings screens | e.g. Shared folder "Settings copies" | e.g. Every 6 months and when settings change | e.g. IT lead |
| Operating records | e.g. Update and backup record sheet | e.g. Every month | e.g. IT lead |
| Copies of answers | e.g. One folder per customer | e.g. Return to the table in ⑥ at every submission | e.g. Contact point for answers |
⑯ What happens when a questionnaire arrives
- Receive Collect at one contact point e.g. Send each questionnaire to the contact point and add the customer and due date to the table in ②
- Copy Answer from the table in ⑥ e.g. Copy items that are in the table and mark items that are not
- Check The owner reviews e.g. Check that the evidence for each yes can be shown and that nothing clashes with the policy in ⑫–⑭
- Submit and keep Submission and a copy e.g. File the copy at the location in ⑮ and return the new answers to ⑥
⑰ Pitfall: sales promises on their own (agreement with sales)
- What can happen e.g. In a meeting someone says "we can do all of it", and a promise you cannot keep stays in the contract
- How to check e.g. Before submission, the contact point checks for answers that differ from ⑥ or new promises
- How to prevent (agreement with sales) e.g. Do not answer anything not in the table on the spot, say "we will check and reply", and route it to the contact point
Task board contents
Not started 16 items
List what is asked
On page 1, write why and for whom you are aligning answers, list the questionnaires received by customer, and sort the questions into 3 common areas. Done when you can see what is due to which customer by when. Press Ctrl+F (⌘F on Mac) and type '3/4' to jump to page 3.
Collect the forms
Search mail and shared folders for "security", "checklist", and "questionnaire", and gather the past year's questionnaires in one folder. Done when customer, due date, and status are in the table of board②. This is only searching and copying, so write no answers yet.
Set purpose, scope
On board①, write why you are aligning answers, which customers and deadlines are in scope, and how you will prepare for evaluation schemes. For Japan's scheme, check METI's latest announcements for timing and requirements first.
Group common areas
Sort the questions from the collected questionnaires into the rules and structure, technical safeguards, and incident readiness areas of boards③–⑤. If a question fits none, add a note to ③–⑤.
Collect answers
On page 2, put your answers and evidence for the 6 most common items into one table and check the pitfalls. Every future answer comes from this table, so it takes the most time.
Write 6 answers
In the "Our answer" column of board⑥, write the answer exactly as things stand today. If something is not done, do not write "yes". Write it as it is.
Check the evidence
For each row of board⑥, write the evidence document's name and its state (exists, outdated, missing). Check policies in the register, settings in the admin screen, and updates and backups in the records.
Check the pitfalls
Check the 3 pitfalls on boards⑦–⑨ against past answers and the table in ⑥, and write a preventive step wherever one applies.
Decide the gaps
On page 3, sort the items from ⑥ with outdated or missing evidence into fix, explain, or say you cannot. This is where your policy for answering customers is decided.
Write 3-step gaps
On board⑩, pick one item from ⑥ and write the current state, what is missing, and the target state. Add notes for other items in the same form.
Rank by frequency
Place the missing items in the 4 areas of board⑪ by how often they are asked and how hard they are to fix. Done when every item sits in one area.
Sort into 3 paths
On boards⑫–⑭, write fix items with a deadline, explain items with the current status and plan, and cannot items with the reason and a substitute measure. Done when the owner approves.
Keep answers fresh
On page 4, decide where evidence lives and how often it is updated, what happens when a questionnaire arrives, and the agreement with sales. Aim to answer the next questionnaire from the same table.
Set places, cycles
In the table of board⑮, write the location, update cycle, and update owner for each type of document. Add a rule to fix the table in ⑥ in the same week a setting changes.
Set intake flow
Rewrite the 4 steps of board⑯ in your own words and add the contact point and owner names. Done when the next questionnaire has gone through this flow once.
Agree with sales
Read the pitfall on board⑰ with sales and agree that anything not in the table is never promised on the spot but routed to the contact point. Done when you have shared the decision with sales.