RFP requirements

After uploading your RFP, the platform can extract a structured list of every requirement it contains — a requirement ledger. You review and approve these requirements on the Requirements tab, and from there they project automatically into the rest of your workflow.

Why it matters: the ledger is the single source of truth for what the RFP actually asks for. Once it's approved, everything downstream — your checklist, evaluation criteria, lots, bid drafting, and analysis results — stays anchored to those requirements instead of drifting apart.

Extracting requirements

Open Tender documents → Requirements in the workspace sidebar. With at least one parsed RFP document in place, click Extract requirements — the AI reads your uploaded RFP and builds the structured list, capturing each requirement together with where it came from.

Reviewing the matrix

Extracted requirements appear in a matrix. Each row shows:

• Requirement text — what the RFP asks for, in plain language
• Source reference and quote — the section it came from and the exact wording from the RFP
• Priority — whether the requirement is mandatory or optional
• Type — a bidder obligation (something the vendor must do or provide) or a buyer evaluation rule (how bids are scored). Evaluation rules also carry a method, weight, and threshold.

Before requirements project downstream, you can edit any row, approve the ones that are correct, and remove anything that doesn't belong. Only approved requirements flow into the rest of the workflow.

Long lists are split into pages, and Details under a row loads the rest of its information. To act on several rows at once, tick them (or click Select visible) and use Approve selected, Reject selected or Resync selected. Bulk actions apply only to the selected requirements on the current page; changing the page or the filters clears the selection.

How requirements flow downstream

Approved requirements sync automatically into the rest of your workspace:

• They populate your preparation checklist, evaluation criteria, and lots.
• They drive bid drafting, so drafted sections cover what the RFP actually requires.
• Analysis results and the requirements comparison matrix report each vendor against them, so every finding links back to a specific requirement.

This keeps the whole procurement consistent — change a requirement in one place and the downstream views reflect it.

Re-extracting

If you revise your RFP, re-extract to pull the updated ledger. The matrix shows what was added or changed since the last extraction, so you can see exactly what's new. Re-approve the affected requirements, and the downstream projections update to match.