Tenders and new clients send long security questionnaires, and most of the questions have been answered before in a slightly different form. The improved process drafts answers from your own approved past answers and policies, shows the source for each one, and flags any question that is new or where the evidence is out of date.
Every answer is checked by a person who knows the facts, and a person submits the questionnaire. Nothing is claimed that your own evidence does not support.
The job today
A questionnaire arrives as a spreadsheet or portal form. The operations manager opens last year's answers, copies what looks similar, and asks colleagues about the rest. Answers drift over time, and nobody is quite sure which version is current. Deadlines are tight, and the same work is repeated for every client.
Where it breaks
- The same questions are answered from scratch for every tender.
- Old answers are reused after policies or suppliers have changed.
- Questions are answered by whoever is free, not by the person who knows.
- There is no single approved set of answers to draw from.
The improved process, step by step
- Keep an approved answer libraryPast answers that a person has approved are kept in one library, each with its owner, date and supporting policy or evidence.
- Read the questionnaire AI preparesThe system reads the questions from the spreadsheet or document and matches each one to similar questions in the library.
- Draft answers from the library AI preparesAn assistant drafts each answer from the closest approved answer, with the source shown. It writes nothing that the library does not support.
- Flag new and stale questionsQuestions with no good match, and answers whose evidence is past its review date, are listed for the right owner.
- A person checks and submits A person approvesThe owner of each area checks the answers, and the bid or operations manager approves the full set and submits it. The system never submits.
- Add new answers to the libraryNewly approved answers are added to the library with their owner and date, ready for next time.
Where a person must approve
Every answer is checked by the person responsible for that area, and the questionnaire is approved and submitted by a named person. Anything that sends, changes or cannot be undone waits for that approval.
The system never claims a certification, control or policy that is not in your approved evidence.
The data boundary
- The system reads only your approved answer library, policies and the questionnaire itself.
- It cannot submit to portals or send anything to the client.
- Each draft answer shows the source it was based on.
- Every draft, change and approval is logged with the person and date.
Checklist before you start
- We have past questionnaires and answers we can gather together.
- Our security policies are current and have owners.
- Each area of the questionnaire has a named person who knows the facts.
- We have review dates for evidence and policies.
- We know who signs off a questionnaire before it is submitted.
- We know which information is confidential and must not be shared.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.