> ## Documentation Index
> Fetch the complete documentation index at: https://reyda.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Requirements

> Review every buyer requirement Reyda extracts from the tender documents, grouped, classified and linked to its source page.

The **Requirements** tab lists what the buyer asks for, extracted from the documents in the Bid Room. Use it to check eligibility, plan your response and make sure nothing is missed before submission.

## How extraction works

When buyer files arrive in a Bid Room, Reyda reads each one and pulls out the requirements automatically. You don't need to start anything. While this runs, the tab shows **Extracting requirements** and requirements appear as they are found. When new files are added, extraction runs again.

Requirement titles stay in the language of the buyer's documents.

Each requirement links to its **Source**: a page number in a PDF or Word file, or a sheet name in a spreadsheet. Check the source when wording matters.

## Groups

Requirements are grouped so you can work through them in order:

| Group | What it covers |
| - | - |
| **Critical requirements** | Eligibility, deadlines, and submission blockers |
| **Evidence and declarations** | Proof, certificates, references, and bidder statements |
| **Structured responses and signatures** | Buyer-defined fields, schedules, and signing work |
| **Proposal guidance** | Response structure, content, and evaluation signals |
| **Contract terms** | Commercial and legal obligations |
| **Other requirements** | Additional extracted instructions and information |

## Columns

* **Required**: **Mandatory** or **Optional**.
* **Requirement**: the requirement in plain words.
* **Classification**: what kind of requirement it is, for example something that shapes your response structure, affects scoring, or must be done to submit.
* **Priority**: how serious it is if you miss it. It runs from **Blocker** through **High**, **Medium** and **Low** to **Info**. Missing a blocker can get the bid excluded, for example a missed deadline or an unsigned offer.
* **Source**: where the requirement appears in the buyer documents.

## Search and filter

Use **Search requirements** to find a topic, such as "insurance" or "references". Use the **Type** filter to show only **Mandatory** or **Optional** requirements.

> [!WARNING]
>
> **Always check the source.** Extraction is thorough but not infallible. Before you rule a bid in or out on a single
> requirement, open the source page and read the buyer's exact wording.

## Ask Emma

Emma reads the same requirements and the buyer documents behind them. She can explain them, check them against your company profile and library, and point out gaps. You decide what to do about each gap.

Ask Emma

List every mandatory requirement we can't evidence yet from our library or company profile, with
the source page for each.

Ask Emma

Run a compliance check on this Bid Room and tell me which requirements are blockers.

Ask Emma

Which requirements affect scoring most? Summarise the evaluation criteria and weightings.

## Related

> [card] [Documents and editor](https://reyda.mintlify.site/bid-room/documents-and-editor.md)

> [card] [Final package](https://reyda.mintlify.site/bid-room/final-package.md)

> [card] [Library](https://reyda.mintlify.site/knowledge/library.md)

> [card] [Bid/no-bid report](https://reyda.mintlify.site/pipeline/bid-no-bid-report.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.