A useful client spreadsheet may use unfamiliar language, local professional terms, or several languages in one workbook. Copying it into an English-only template creates extra work and can change meaning. The multilingual importer identifies each structured sheet, detects its language, maps recognized concepts to the selected voiqq Program and Library, and preserves the original grid so the reviewer can compare the result.
Check workspace access first
English spreadsheet imports are available on Free. Dutch, French, German, Spanish, Italian, and Polish imports are available on Pro, Team, Business, and Enterprise. Free and Starter users can see the detected language, but the language selector remains disabled and an upgrade action is shown. After an upgrade, reopen the importer or wait for the workspace plan to refresh; the selector and multilingual import path become available. After a downgrade, existing projects remain usable but new non-English imports are paused.
Prepare the source
- Use XLSX, CSV, or a public Google Sheets link. Keep private Google Sheets downloaded as a file for this MVP.
- Keep one regular header row and one issue, control, evidence request, gap, or remediation item per row.
- Remove passwords, secret keys, health information, or personal data the engagement does not need.
- Know the Program, Library, standard version, target level, report target, and scope that should govern the resulting project.
- Keep an unchanged source copy outside voiqq when your contract or evidence policy requires separate source retention.
Analyze and import the workbook
- Open Projects and choose Import Spreadsheet.
- Select the team and Program before analyzing the source.
- Upload the file or paste a public Google Sheets URL, then start analysis.
- Review how every sheet was classified. Covers, dashboards, pivots, and irregular notes pages should remain excluded.
- For each included sheet, review its project name, automatically detected spreadsheet language and confidence, Library, and Program-specific project requirements.
- If your paid workspace needs a correction, choose a different supported spreadsheet language for that sheet.
- Open Review column matching and inspect every mapping, especially Summary, requirement or control, status, validation, severity, assignee, business owner, date, affected target, evidence, and remediation.
- Keep uncertain source columns as imported data instead of forcing them into an unrelated field.
- Confirm the number of projects and complete the import. One selected structured sheet becomes one normal voiqq project.
Workbooks with mixed languages
Language is detected per sheet, not per workbook. A German ASVS findings sheet and a French SOC 2 evidence-gap sheet can be reviewed independently. Configure each included sheet with the Program and Library that describes its records. If one sheet mixes languages internally, select the language that best represents its headings and workflow values, then inspect the mappings manually. The importer does not translate cell prose just to make mixed data look uniform.
Verify the created project
- Open the project in Full view and compare the first, middle, and last records with the source snapshot.
- Confirm Summary, status, validation, severity, due date, assignment, remediation, affected target, and evidence values.
- Open several finding drawers and inspect View Details, View More Details, and Additional Details.
- Confirm every report-relevant requirement or checkpoint is connected to the selected canonical Library.
- Generate a draft export and review localized headings and workflow values beside unchanged source evidence.
- Correct project records before distribution; do not use a report override to conceal an incorrect import mapping.
If the detected language is wrong
A short sheet with generic headings such as Item, Owner, and Notes may not contain enough language evidence. The detector also cannot know the intended business meaning of organization-specific abbreviations. On a paid plan, select the correct language and review mapping again. If the source uses a language outside the current seven, keep the original grid, map clear fields manually, and preserve uncertain columns. Do not choose a supported language merely to bypass review.
- If the selector is disabled, confirm the workspace is on a paid plan and that the upgrade or trial completed for this organization.
- If the plan has just changed, close and reopen the modal after the billing update is confirmed.
- If no valid sheet is detected, select a regular table rather than an executive summary or dashboard.
- If a required Title or Summary mapping is missing, open Review column matching and assign the correct source column.
- If a requirement does not map, confirm that its standard and version belong to the selected Library.
- If AI review is unavailable, continue with deterministic matches and preserved source columns; the import should not invent a result.
Privacy and source integrity
The original sheet name, headers, row order, values, available widths, source type, warnings, and field mappings are retained as an import snapshot. Formula code is not executed. Multilingual deterministic matching runs in the application. Only genuinely ambiguous column classification may use the existing server-side AI chain, with bounded examples and allowed targets. The final server checks the sanitized snapshot language and current workspace plan before creating any project.