# Project proposal document profile

The **Project proposal** profile helps you compare proposed scope and outcomes. It belongs to the project operations family.

## Recognize the source

Proposal seeking agreement or funding; distinguish approved plan and sales price quotation.

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 |
| --- | --- | --- | --- |
| Project title | text | Core | The source-stated project title 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. |
| Proposer | text | Core | The source-stated proposer 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. |
| Problem statement | text | Core | The source-stated problem statement 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. |
| Proposed approach | text | Core | The source-stated proposed approach 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. |
| Expected outcomes | text | Core | The source-stated expected outcomes 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. |
| Proposed schedule | text | Optional | The source-stated proposed schedule 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. |
| Budget amount | number | Optional | The source-stated budget amount for this document and its identified subject. Use an explicitly stated value with safe numeric normalization only. Preserve its currency, unit, scale and basis in evidence metadata; do not calculate, estimate or combine values. |
| Currency | text | Optional | The currency explicitly associated with the selected monetary fields. Preserve source representation; do not infer a currency from an ambiguous symbol or company location. Conflicting currencies require separate fields or unresolved values. |

## 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 **work packages**. 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).