Record what the issuer requires, set type and priority, track progress in a table or on a board, change several statuses at once, decide whether you can meet each requirement, and give it notes and an owner.
The Requirements tab holds everything the issuer asks for: the technical, financial, legal and administrative conditions your bid must answer. For each requirement you record its type and priority, track your team's progress, and decide whether your organisation can meet it. Response sections, the compliance matrix and the readiness check all work from this list.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Everyone on the tender's team with View Tenders can read the requirements. Adding, editing, deleting and changing a requirement's status, disposition, notes or owner needs Create & Work on Tenders (tender:manage-workspaces). See Who can do what.
Once the tender is submitted, its requirements are read-only; they record what you bid against.
Requirements reach the list in four ways:
you type them on the Requirements tab;
you tick them in the review after uploading the tender documents; see Start a tender;
the Tender Assistant adds them during a conversation; see Work with the Tender Assistant;
you accept an improvement suggestion that adds a requirement; see Analyse the RFP and run assessments.
Wherever they come from, they behave the same way.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Open the tender and choose the Requirements tab.
In Describe a requirement…, enter the requirement. Quote or paraphrase the issuer's wording, and include its clause number so you can trace it, for example "4.2.3 The supplier shall hold ISO 27001 certification covering the hosting service".
Choose the type and the priority.
Choose Add.
The requirement is added at the end of the list with the status Not started and the disposition Undecided. Add does nothing while the text is empty.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Field | What it records | Values and default |
|---|---|---|
Text | What the issuer requires. | Required. Up to 20,000 characters. |
Type | The kind of requirement, for sorting your work and for reports. | Technical, Financial, Legal, Administrative or Other. Default Other. |
Priority | How much the requirement matters to winning, for example Critical for a pass/fail condition. | Low, Medium, High or Critical. Default Medium. |
Status | Your team's progress on answering it. | Not started, In progress, Addressed or Not applicable. Default Not started. |
Disposition | Whether your organisation can meet it. | Undecided, Can meet, Partial or Cannot meet. Default Undecided. |
Reasoning | Why you can or cannot meet it. | Optional. Up to 20,000 characters. |
Notes | Anything the team needs to know while answering it. | Optional. Up to 20,000 characters. |
Owner | The person responsible for answering it. | Optional. One person. |
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
The Table view shows one row per requirement: the text, its type and priority, the status and disposition lists, and the actions.
The status and the disposition are saved as soon as you choose a value.
Edit lets you change the text, type and priority; choose Save or Cancel.
Find evidence searches your existing documents for material that already addresses the requirement. The matches appear under Reusable evidence for this requirement, each with its vault, a match percentage and the reason it matched. A confident match is linked to the requirement automatically, and the row says so. Choose Cancel to close the matches. See Analyse the RFP and run assessments.
Delete asks Delete this item?; choose Delete to remove the requirement.
Requirements stay in the order they were added.
To set the same status on several requirements, select them in the table and set their status in one action. This is quicker than changing rows one by one when, for example, a whole lot does not apply to your bid.
You can narrow the list to requirements with one status, for example only those Not started, to see what still needs work.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Choose Board above the list to see the requirements as cards in four columns, one per status, each with a count. A card shows the requirement, its type and its disposition.
Drag a card to another column to change its status; the change is saved when you drop it. An empty column shows Drag items here. To change a status with the keyboard, switch back to Table and use the status list.
The board is useful in stand-ups: a long Not started column a week before the deadline shows where to put people.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
The disposition answers Can we meet this requirement?. It is separate from the status: the status says how far the answer has got, and the disposition says whether your organisation can meet the requirement at all.
Choose Can meet, Partial or Cannot meet in the disposition list.
A reasoning row appears under the requirement with the disposition and Reasoning:. Choose Add reasoning.
Write why, including caveats and what would close a gap, for example "Certified for the primary data centre; the disaster-recovery site is audited in January".
Choose Save.
No reasoning recorded yet. shows until you add it. Choose Edit to change the reasoning; save it empty to remove it.
Dispositions feed the Bid decision on Overview: many Cannot meet entries on critical requirements are a reason not to bid. They also decide what the readiness check expects; see Where requirements are used.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Edit a requirement to add notes or to name the person who owns its answer, then save it.
Notes are for the team: open questions, internal contacts, where the evidence lives. They are not part of any document you submit.
The owner is one person; search by name. They are notified in the app and by email, according to their notification preferences. Use owners to share out the requirements, for example giving every Legal requirement to your contracts manager.
To clear the owner or the notes, empty the field and save.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
When a requirement is unclear, raise a clarification question to the issuer on the Q&A tab and link it to the requirement. The question then shows Linked to requirement with the start of the requirement's text, and the answer you record sits beside it. See Track deadlines, formalities and clarifications.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Edit a requirement whenever the issuer's wording changes, for example after a clarification answer. The change is visible at once in the compliance matrix and in the sections that address it.
Deleting a requirement also removes:
its links to response sections, so sections no longer count it as addressed;
answers proposed for it from bid products on the Products tab that nobody has accepted.
If bid products have accepted answers for the requirement, you are asked what should happen to them before it is deleted. Clarification questions linked to it are kept, without the link. If someone else changed the requirement after you opened the page, Could not save your change. Reload and try again. appears; reload and make your change again.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
Where | How requirements are used |
|---|---|
Overview | The Requirements tile counts requirements marked Addressed out of all requirements except those marked Not applicable. |
Response sections | Each section can be linked to the requirements it answers. See Plan output documents and the response structure. |
Compliance matrix | Lists every requirement with its disposition, status and what addresses it. A requirement is covered when a linked response section has content, or when a document is attached to it. See Check compliance and coverage. |
Submission | The readiness check blocks submission while a requirement marked Can meet or Partial, and not Not applicable, is not covered. Undecided and Cannot meet requirements do not block. See Validate, package and submit. |
AI assessments | Readiness, improvement and gap assessments read the requirements, their dispositions and statuses. |
Products | Proposed answers are drawn from the bound product configurations for each requirement. See Bid products. |
Reports | The Tender Requirement Disposition & Progress report summarises dispositions and progress across tenders. |
Status is your team's marker and is not changed for you. Mark a requirement Addressed once its answer is written and reviewed, and Not applicable when it does not apply to your bid, such as a lot you are not bidding for.
Product location: /tender/workspaces/{workspaceId} (fallback: /tender/workspaces). Open Tenders, then choose the tender's name in the list. Choose the Requirements tab.
The review after upload added 34 requirements to "Regional Health Framework 2026 – Lot 2".
Set Critical on the pass/fail conditions: ISO 27001 certification, UK data residency and professional indemnity cover of GBP 5 million.
Give each Legal requirement to the contracts manager as owner, and each Technical requirement to the solution architect.
Go through the dispositions with the solution architect. Mark disaster recovery Partial with the reasoning above, and the 24-hour on-site support requirement Cannot meet.
For the on-site support requirement, raise a clarification on Q&A asking whether remote support with a four-hour response is acceptable, linked to the requirement.
Select the three requirements for Lot 1 and set them to Not applicable in one action.
The bid manager now has what they need for the Bid decision, and the board shows who is working on what. When the issuer's answer arrives, update the requirement and its disposition.
