Request for proposal or tender document profile
Track solution requirements and response conditions.
The Request for proposal or tender profile helps you track solution requirements and response conditions. It belongs to the project operations family.
Recognize the source
Requests a solution or bid; distinguish item-price RFQ and supplier's proposal response.
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 |
|---|---|---|---|
| Request reference | text | Core | The source-stated request 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. |
| Buyer | text | Core | The source-stated buyer 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. |
| Required outcomes | text | Core | The source-stated required 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. |
| Submission deadline date | date | Core | The source-stated submission deadline 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. |
| Evaluation criteria | text | Core | The source-stated evaluation criteria 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. |
| Scope | text | Optional | The source-stated scope 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 terms | text | Optional | The source-stated budget terms 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. |
| Procurement contact role | text | Optional | The source-stated procurement contact role 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 requirements and evaluation criteria. 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, table review, and captured evidence.