Semantic validation
Validate answers against natural-language constraints — 'must be a Swedish org number' — checked at submit, not just regex.
Every field type carries its structural validation automatically — email format, number and rating bounds, choice membership, text length. Semantic validation goes further: attach a plain-language constraint to a field and it’s checked when the respondent submits.
Examples that work well:
- “must be a Swedish organization number”
- “should be a company name, not a person’s name”
- “must describe a physical address in Sweden”
Failed checks show the respondent a clear message on the field. Like all adaptive features it’s capped per plan and degrades gracefully — a constraint check never strands a respondent.
How is this different from required or format checks?
Structural checks (required, email format, number bounds) are built into field types and always free. Semantic validation understands meaning and runs through the AI layer.