Importing Security Questionnaires

Step-by-step instructions for importing, mapping, validating, and exporting Excel-based security questionnaires at scale.

Security Questionnaires (like VSA, SIG, or custom Excel sheets) are notoriously tedious. Velocibid has a specialized "Excel Mode" to handle these automatically.

How "Excel Mode" Works

Unlike PDFs where questions are just text, Excel files have a structured grid. Velocibid needs to know which column contains the Question and which contains the Answer.

Step-by-Step Guide

  1. Create a Project to get started.
  2. Inside the project dashboard, locate the Actions dropdown menu in the top right corner.
  3. Select Add Questions from Excel from the menu.
  4. Upload your `.xlsx` file containing the questionnaire.
    Note: Only one Excel file can be imported at a time to ensure correct column mapping.
  5. Map Columns: A preview of your sheet will appear.
    • Header Row: Click the row number that contains your headers (e.g., "Requirement", "Response").
    • Question Column: Select the column letter (A, B, C...) that has the questions.
    • Answer Column: Select the empty column where you want Velocibid to write answers.
  6. Click Import Questions.

Handling Yes/No Questions

Many questionnaires ask for a "Yes/No" or "Compliant/Non-Compliant" response along with a comment.

Velocibid's AI is trained to detect these requirements. It will attempt to answer "Yes" if your Smart Library indicates you have that security control, and add the supporting detail in the comments field.

Exporting Back to Excel

Once you have reviewed and approved the answers in Velocibid, click Export. The system will generate a new Excel file identical to the original, but with the Answer column filled in.

Practical Implementation Notes

This guide is designed to help proposal, security, and operations teams execute Importing Security Questionnaires consistently inside Velocibid. If you are onboarding new contributors, use this page as a standard operating reference and pair it with related documentation so your team follows one repeatable workflow.

For stronger outcomes, combine this playbook with adjacent guides in the same lifecycle stage (discovery, response, compliance, and delivery). Cross-functional teams that align their process across these modules typically reduce rework and improve proposal quality.