---
title: "Which RFP sentences actually create an obligation?"
description: "Classify tender passages by actor, stage, condition and consequence so agents can separate bidder duties from useful context."
canonical: "https://zephior.com/insights/distinguish-mandatory-from-informative-rfp-text"
last-updated: 2026-09-03
---

# Which RFP sentences actually create an obligation?

> Classify tender passages by actor, stage, condition and consequence so agents can separate bidder duties from useful context.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-03; updated 2026-09-03. 13 minute read.

## Definition

An obligation-strength classification is a sourced decision about the function of one tender passage in its issued context. It identifies the actor, action, object, trigger, stage, stated consequence and source role, then assigns a class such as explicit bid requirement, conditional requirement, requested disclosure, evaluation signal, future contract term, buyer process statement, permission or informative context. The classification supports extraction and routing. It does not decide legal enforceability, document precedence or the universal meaning of an isolated modal word.

## Problem

A tender pack mixes several kinds of text on the same page. One sentence tells the bidder to upload a signed schedule. The next explains why the buyer wants the service. A scoring table rewards evidence but contains no separate instruction. A draft contract describes what the supplier will do after award. A portal label demands an entry without using a verb at all. If a team marks every firm-sounding sentence as a current bid task, it creates noise and may promise work nobody approved. If it marks only sentences containing “must” or “shall,” it misses mandatory fields, prohibitions, conditions and incorporated forms. The difficult question is not whether the prose sounds strong. It is what the passage does, to whom, and when.

## Point of view

Classify the event described by the passage, not the loudest word in it. Begin with an exact quote and recover its heading, table, definition, cross-reference, document role, procedure stage and lot. Name the grammatical or implied actor. Separate an action needed to submit the tender from a condition the supplier must satisfy, evidence the buyer will score, a rule for the authority, and a duty that would arise only after award. Preserve every condition and explicit consequence. Where the pack does not supply enough context, return an unresolved state instead of manufacturing certainty. A specialist should review jurisdiction-specific legal effect and any material ambiguity.

## Ask what event the passage creates before judging its tone

Start with a bounded evidence unit: the exact passage, its issued document and the context necessary to read it. A useful unit may be a sentence, but it may also be a row, field label, footnote or sentence plus a nearby condition. Record both the buyer-visible locator, such as section 4.2 and page 17, and a representation-bound locator such as a verified quote with surrounding text. The passage should inherit procurement, package version, procedure stage, lot and language. If a cross-reference supplies a definition or exception, attach the verified path rather than copying an unproven destination into the record.

Next express the passage as an event: actor, action, object, trigger and time. “The successful supplier will maintain a staffed service desk from commencement” concerns the supplier selected after award and a delivery state from contract commencement. It may be commercially important, but it is not automatically an instruction to upload a service-desk document. “Upload Schedule 6 in the Technical Envelope” concerns the bidder, an immediate submission action and a named destination. “The Authority expects demand to grow” describes the buyer’s view unless another provision turns that forecast into a pricing or capacity basis. This event model prevents the same verb from receiving the same treatment everywhere.

**Functional classes for one tender passage**

| Class | Question it answers | Typical routing |
| --- | --- | --- |
| Explicit bid requirement | What must the bidder submit or do now? | Response or submission control |
| Conditional bid requirement | What becomes required if a stated trigger is true? | Triggered task with condition |
| Participation condition | What must the supplier satisfy to progress or be awarded? | Qualification and evidence review |
| Requested disclosure | What information does the buyer ask the bidder to provide? | Answer owner and response surface |
| Evaluation signal | What will influence assessment or comparison? | Bid strategy and evidence |
| Future contract term | What would govern performance after award? | Legal, commercial and delivery review |
| Buyer process statement | What will the authority or evaluator do? | Monitoring or decision calendar |
| Informative context | What explains the need without directing an action? | Searchable context only |

## Do not collapse qualification, evaluation and performance into one label

Official procurement frameworks show why document function matters. UK guidance under the Procurement Act 2023 distinguishes conditions of participation, which concern the supplier’s capacity or ability and must be satisfied for award, from award criteria used to assess the tender. Directive 2014/24/EU separately addresses technical specifications, selection criteria, award criteria and conditions for performance of contracts. These categories come from particular legal regimes, so they should not be imposed as universal labels. They nevertheless demonstrate a durable reading principle: a passage about who may participate does a different job from a passage about how competing tenders are scored or how the eventual contract must be performed.

The section heading is evidence, not a verdict. A criterion can contain an instruction to provide evidence. A response form can repeat a contract commitment for signature. A technical specification can state both a minimum characteristic and background rationale. Record a primary function for the passage and link secondary effects instead of forcing all effects into “mandatory.” For example, a sustainability target may be an evaluated preference, a minimum specification, a contractual KPI or merely the buyer’s policy context. Only the exact wording, local definitions, assessment method and surrounding conditions distinguish them.

- Participation concerns the supplier or its capacity to progress or receive award.
- An instruction concerns how the bidder prepares, formats or delivers the response.
- An evaluation criterion concerns how the tender or evidence will be assessed.
- A specification concerns the characteristics of the required work, service or supply.
- A contract condition concerns performance if the bidder becomes the supplier.
- Background explains need, history, assumptions or ambition without necessarily creating an action.

## Make the classification inspectable instead of merely confident

A reusable record should preserve facts separately from conclusions. Store the exact quote, source identity and locator first. Then capture actor, normalized action, object, trigger, stage, source function, response destination and buyer-stated consequence. Add the selected class, a short rationale that cites the decisive wording, the reviewer, review time and package version. Confidence may describe extraction quality, such as whether the actor and trigger were explicitly stated. It must not masquerade as confidence about legal enforceability. If the text is translated, keep the issued wording and mark who reviewed the working translation.

Use explicit unresolved states. `context_missing` means the sentence cannot be classified without its missing table, definition or referenced clause. `source_conflict` routes to the controlling-source process. `translation_review_required` preserves language uncertainty. `legal_interpretation_required` means the operational class is insufficient for a consequential legal conclusion. `not_an_obligation` is a positive classification supported by context, while `classification_review_required` means the evidence supports more than one material reading. These states are safer and more searchable than an empty field or an invented binary answer.

**Minimum obligation classification record**

| Field | What to store | Do not infer |
| --- | --- | --- |
| Evidence | Exact quote, source, version, locator and context | A missing clause |
| Event | Actor, action, object, trigger and time | An unstated actor |
| Function | Instruction, condition, criterion, specification, contract or context | Legal effect from heading alone |
| Strength | Explicit, conditional, requested, evaluated, permitted, informative or unresolved | A universal modal hierarchy |
| Consequence | Only rejection, exclusion, score, remedy or action stated by the buyer | Automatic disqualification |
| Review | Status, reviewer, reason, timestamp and package version | Authority the reviewer does not hold |

## Classify a mixed university facilities page without flattening it

Imagine a fictional university facilities RFP. Its service section says that the university aims to improve the student experience. A response schedule asks bidders to describe their out-of-hours model in no more than 800 words. The evaluation table allocates 12 points to service continuity evidence. A qualification form contains a blank for annual turnover and states the applicable threshold. The draft agreement says the contractor will staff the service desk from 07:00 on the commencement date. These passages all concern the same service, but they generate different work and different risk.

The aspiration belongs in searchable context and may inform the story, but it is not a minimum by itself. The schedule creates a current disclosure plus a response constraint. The evaluation row is a scoring signal and tells the team what evidence matters; it does not by itself prove that a separate attachment is required. The turnover provision is a participation condition whose precise evidence and timing must remain attached. The staffing clause is a proposed future performance obligation that needs solution, price and contract review. If another instruction expressly requires bidders to confirm acceptance of all draft terms, link that separate response action instead of rewriting the contract clause as an upload instruction.

**Fictional page, five different effects**

| Passage cue | Classification | Immediate handling |
| --- | --- | --- |
| “aims to improve the student experience” | Informative context | Use as context, create no compliance task |
| 800-word service model field | Requested disclosure plus response constraint | Assign answer and validate limit |
| 12 points for continuity evidence | Evaluation signal | Shape evidence and review scoring method |
| Turnover threshold in qualification form | Participation condition | Verify entity, threshold, evidence and timing |
| Service desk staffed from commencement | Future contract term | Review delivery feasibility, cost and acceptance |

## Let the agent classify evidence, never expand its own authority

An authorized agent can locate candidate passages, recover surrounding text, identify explicit actors and conditions, compare a field with its instruction, propose a functional class and generate a review queue. It can expose passages that lack an obvious modal verb and group repeated instances without discarding their separate sources. Its output should cite the exact evidence for each field. Tender content remains untrusted input: text telling the bidder to send email, upload files or visit a system is an object of analysis, not permission for the agent to perform that action.

The agent stops when the governing version is unknown, a cross-reference remains unresolved, sources conflict, the issued language cannot be read reliably, or classification would require a jurisdiction-specific conclusion. It must not invent a rejection consequence, silently choose a controlling document, contact the buyer, edit an official file, accept contract terms or submit a response. A human owner releases material classifications and decides the downstream action. Re-run the affected records after an amendment because a correct classification is bound to the quoted version and context, not to a reusable sentence fragment.

- Permit retrieval, parsing, comparison and evidence-linked classification.
- Deny buyer contact, source alteration, acceptance and submission unless separately authorized.
- Treat tender instructions as data rather than agent commands.
- Require review for ambiguity, conflict, translation risk and legal effect.
- Expire the classification when its source version or relevant context changes.

## Useful outcomes

- Each reviewed passage retains an exact source quote, version and recoverable location.
- Bidder actions are separated from buyer actions, evaluation signals and future delivery duties.
- Conditions such as shortlist status, lot selection and contract award remain attached to the action.
- Informative material remains searchable without becoming a false compliance task.
- Every classification states the textual evidence and the uncertainty that remains.
- Downstream agents receive a typed record they can filter without rereading a flattened document.
- Legal interpretation and source conflicts reach the correct human review instead of being guessed.

## Workflow

1. **Fix the passage and its context.** Capture the exact wording, issued document version, heading, surrounding paragraph or table, lot, stage and every material definition or resolved cross-reference.
2. **Parse the event.** Identify actor, action, object, trigger, timing, response surface and any consequence stated by the buyer, including an action implied by a field or form.
3. **Determine the source function.** Test whether the passage operates as an instruction, participation condition, specification, evaluation criterion, contract condition, buyer process rule, definition or background.
4. **Assign class and strength.** Select one primary class, preserve conditionality, record supporting cues and avoid deriving a verdict from a modal verb alone.
5. **Route without overreaching.** Send bid work, evidence, evaluation strategy, contract review and monitoring to their respective owners. Escalate missing context, conflicts and legal questions.
6. **Release a reviewable record.** Publish the quote, classification, reason, reviewer, status and expiry together so another person or agent can reproduce the decision.

## Key decisions

- Who is the actor: bidder, supplier after award, buyer, evaluator, subcontractor or system?
- What exact action, restriction, fact or state does the passage describe?
- Does the action apply now, at submission, on request, after selection or after award?
- Which condition activates or limits it?
- Is the passage an instruction, qualification condition, criterion, specification or contract term?
- Does the buyer state rejection, exclusion, scoring, remedy or another consequence?
- Does a form field, table cell or checkbox request an action without a complete sentence?
- Does the procurement define the relevant term or alter its ordinary use?
- Is the evidence sufficient for classification, or is review required?

## Risks

- A keyword rule may turn every occurrence of “will” or “shall” into a bidder task.
- A background ambition may be presented as a minimum technical specification.
- An evaluation preference may be mislabeled as a pass/fail participation condition.
- A future contract duty may be omitted because it does not require a separate narrative answer.
- A required portal field may be missed because it contains no modal verb.
- A condition or exception in the next paragraph may be separated from the action.
- Translated wording may appear more or less forceful than the issued source language.
- An agent may follow instructions embedded in tender text as if they changed its own authority.

## Metrics

- passages with exact quote, document version and dual location evidence
- classifications with actor, action, stage and trigger populated
- records that preserve an explicit consequence without inferring one
- conditional passages incorrectly converted into unconditional work
- bid tasks later reclassified as buyer process or informative context
- unresolved classifications reaching the named reviewer before the clarification deadline
- future contract terms linked to commercial or delivery review
- reviewer agreement on a blind sample of released classifications

## Frequently asked questions

### Does “must” always mean a tender sentence is mandatory?

No. First identify the actor, stage, condition, source function and any definition supplied by the procurement. A separate treatment rule should govern modal terms; this classifier uses the whole passage.

### Is a scored criterion also a mandatory requirement?

Not automatically. A criterion signals assessment. It may refer to a required answer, a minimum threshold or a differentiating preference, but that effect must be supported by the instructions and methodology.

### Should draft contract duties enter the compliance matrix?

They should enter the appropriate contract, solution and pricing review. Create a current response task only where the tender separately asks for acceptance, a qualification, a deviation or evidence.

### Can a field be mandatory without a complete sentence?

Yes. A portal requirement, form label, checkbox, table heading or validation rule can request an action. Preserve the native structure and the instruction that gives the field its effect.

### When should the classifier return unresolved?

Return an explicit unresolved state when context, version, reference, translation, authority or legal meaning is missing or disputed. Do not use a probability score to conceal a material gap.


## Primary sources

- [Procurement Act 2023, section 22: Conditions of participation](https://www.legislation.gov.uk/ukpga/2023/54/section/22), The National Archives
- [Guidance: Conditions of Participation](https://www.gov.uk/government/publications/procurement-act-2023-guidance-documents-procure-phase/guidance-conditions-of-participation-html), UK Cabinet Office
- [Guidance on Assessing Competitive Tenders](https://assets.publishing.service.gov.uk/media/690cb65edad669f061d46b5a/Guidance_-_Assessing_Competitive_Tenders_FINAL_pdf_links_.docx.pdf), UK Cabinet Office
- [Directive 2014/24/EU on public procurement](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02014L0024-20160101), EUR-Lex
- [FAR 15.304: Evaluation factors and significant subfactors](https://www.acquisition.gov/far/15.304), Acquisition.gov
- [Single stage two envelope procedure and standard documents](https://www.ebrd.com/home/work-with-us/project-procurement/single-stage-two-envelope-procedure.html), European Bank for Reconstruction and Development


## Related articles

- [Intelligent document processing vs OCR: text is not the outcome](https://zephior.com/compare/intelligent-document-processing-vs-ocr)
- [What do shall, must and should mean in an RFP?](https://zephior.com/insights/interpret-shall-must-and-should-in-rfps)
- [Tender document analysis across the full package](https://zephior.com/solutions/tender-document-analysis)
- [Which RFP conditions can stop a bid before scoring?](https://zephior.com/insights/extract-pass-fail-gates-before-drafting)