# Feature request document profile

The **Feature request** profile helps you compare requested product improvements. It belongs to the customer voice family.

## Recognize the source

Desired future capability rather than existing malfunction; keep stated demand separate from model prioritization.

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 |
| --- | --- | --- | --- |
| Product | text | Core | The source-stated product 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. |
| Requested capability | text | Core | The source-stated requested capability 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. |
| Stated use case | text | Core | The source-stated use case 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. |
| Stated problem | text | Core | The source-stated problem 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. |
| Request date | date | Optional | The source-stated request 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. |
| Reported impact | text | Optional | The source-stated reported impact 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. |
| Requester reference | text | Optional | The source-stated requester 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. |

## 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 **requests and votes**. 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).