Column matching decides which imported values power project behavior. A correct Summary mapping supports tables and finding drawers. A correct requirement mapping supports standards coverage and reports. An incorrect mapping can make a project look complete while placing data in the wrong background field. Review column matching is therefore a required quality step, not a cosmetic preview.
How suggestions are produced
- Exact and fuzzy header aliases are checked in the detected language.
- Representative cell values are profiled as dates, URLs, emails, workflow values, WCAG references, SOC 2 references, or other structured content.
- Program and Library configuration limits the available target fields.
- Negative evidence prevents common collisions such as Summary versus Actual Result or Control Owner versus Assignee.
- AI is used only for unresolved columns and must return a supplied canonical target with high confidence.
What to review first
- Confirm Summary or Title. Every normalized record needs a clear human-readable subject.
- Confirm the requirement, criterion, or control reference. Reports cannot infer a standard mapping from unrelated prose.
- Separate finding assignees from business control owners and process owners.
- Separate workflow Status from Validation and Evidence Status.
- Confirm Severity, Due Date, Page URL or affected target, Remediation, and Evidence fields.
- Leave unknown columns preserved when the source meaning is specific to the engagement.
Preserved and additional fields
A preserved column is not discarded. Its header, order, values, and approximate width remain in the original-grid snapshot. When it becomes a supplemental project field, it appears in Additional Details rather than pretending to be a standard voiqq field. This keeps the imported project usable while retaining information that belongs to the source workflow.
After project creation
Check the first, middle, and last imported records. Use Full view to confirm fields that were not selected for Compact view. Open Edit Table to adjust visibility without changing canonical background identities. Generate a draft report only after requirement mappings and workflow states have been reviewed. When a problem is found, correct the project record; do not rely on a report override to hide bad source mapping.