# Individual survey response document profile

The **Individual survey response** profile helps you compare one respondent's stated answers. It belongs to the customer voice family.

## Recognize the source

One completed response, not aggregate survey report. Question IDs and scales retain meaning; detailed questions can become fields only after schema review.

Review the document itself before applying the profile. Similar labels, dates, parties, or amounts can appear in another document type with a different meaning. Use the source context to distinguish them.

## Expected fields

Core fields form the profile’s main structure. Recommended and optional fields add supported detail. None of these designations permits guessing a value that is absent or ambiguous.

| Field | Type | Inclusion | Meaning and extraction rule |
| --- | --- | --- | --- |
| Survey name | text | Core | The source-stated survey name for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Response reference | text | Core | The source-stated response reference for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Response date | date | Core | The source-stated response date for this document and its identified subject. Normalize an explicitly stated date only when unambiguous. Do not infer missing day, month, year or timezone. |
| Question answer excerpt | text | Core | A contiguous exact source excerpt preserving one identifiable survey question and its response. Other distinct question answers can become additional named columns during schema resolution. Do not concatenate unrelated answers or present a generated summary as a response. |
| Overall score | number | Optional | An overall score explicitly stated by the source for this response. Do not substitute a single question score, average question ratings or calculate a total; leave null when no overall score is stated. |
| Score scale | text | Optional | The source-stated score scale for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Free text comment | text | Optional | The source-stated free text comment for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |

## Missing, ambiguous, and repeated values

Missing or ambiguous fields remain null with a reason. Null is not zero, false, an empty statement, or proof that a document-wide fact does not exist. Inspect unresolved states and their supporting passages before accepting the table.
This document type can contain repeated records such as **question-answer pairs or respondents**. The profile uses one row per document; do not compress repeated records into a scalar field or confuse a line value with a document-level total.
Additional supported fields can be considered when the extraction experience allows them. Review their definitions and types explicitly; changing a field’s meaning requires a new extraction preview.

## Review the result

Select evidence-backed cells and read the retained source. Text should preserve the relevant source spans and qualifications. Numbers and dates must be stated unambiguously and normalized safely; do not calculate unstated values or infer missing units, currency, scale, date parts, or time zones.

Verify the result against the captured document before acceptance. Source support does not independently establish perfect OCR, exhaustive field discovery, or correct domain interpretation.

See [profile modes](/docs/documents/profiles), [table review](/docs/tables/review-and-accept), and [captured evidence](/docs/documents/citations-and-evidence).