Datasets hold the structured facts BidBot finds in your tender documents, such as the buyer's requirements, in one place your bid team can check and correct. Each value links back to the passage it came from, and every change is kept in a history you can restore from.
This article covers how to find a dataset, check where a value came from, edit it, restore an earlier version and choose how BidBot applies its changes.
Where to find it
In the left-hand sidebar, click Bid Analysis and open an opportunity.
Open the Resources tab.
Click Datasets in the switcher at the top of the tab.
Each dataset has a tab along the bottom of the page, showing its name and how many records it holds. If an opportunity has several datasets, click the search icon and type part of a name to filter the tabs.
Read a requirement
The Buyer requirements dataset has one card per requirement. The header line shows how many need your attention, for example "6 requirements · 2 review required · 3 clear · 1 unassessed".
Each card has two tables. Field holds what the buyer asked for: the title, reference, detail, category, whether it is mandatory and whether it is Pass/fail or a Judgement call. Assessment holds your answer to Can we meet it?, with any caveat, the reason, the action needed and its owner.
What each status means
Clear
You can meet the requirement.
Review required
The answer is "Yes, with a caveat", or "No" on a judgement call. Someone should decide whether the caveat or gap is acceptable.
Blocker
The answer is "No" on a pass/fail requirement. BidScript flags it, but the decision to bid stays with your bid team.
Unassessed
Nobody has answered Can we meet it? yet.
Check where a value came from
On a requirement card, click Sources.
Read the quoted passage in the Sources panel. It shows the document and the page number.
Click the arrow next to the document name to open the document itself.
Check the source before you rely on a value, especially a mandatory one. A requirement copied from the wrong clause reads just as convincingly as a correct one.
Edit a value
Click the pencil icon next to the value.
Make your change. Press Shift+Enter for a new line.
Press Enter to save, or Esc to cancel.
Your bid team sees the change straight away, along with anything on a board that shows the same value.
To add a requirement BidBot missed, click Add requirement at the top of the dataset. To remove one, click the bin icon on its card.
Restore an earlier version
Click Change history at the top of the dataset.
Find the version you want. Changes are grouped by day, with who made them and which values changed.
Click the restore icon on that version.
Restore before you make further edits, so you are working from the version you meant to keep.
Choose how BidBot applies changes
BidBot can update a dataset when you ask it to. You decide whether it waits for your approval first.
In the top bar, click Open BidBot.
Click the mode button below the message box.
Choose Review or Auto.
Review
BidBot proposes changes and waits. Approve applies the whole proposal to your data and to any boards that show it. Reject leaves the data as it was.
Auto
BidBot applies valid changes straight away. They still appear in Change history, so you can restore an earlier version.
Best practice
Start with Review mode until you trust what BidBot extracts from a buyer's documents.
Work through every Review required and Blocker card before your bid decision meeting.
Name an owner for every action, so gaps don't wait for someone to notice them.
Check the source of every mandatory requirement before you answer it.
Related articles
Bid Analysis: Overview - what Bid Analysis does and how its pieces fit together.
Creating and managing opportunities - set up the opportunity a dataset belongs to.
Document Workspace: Overview - the tender documents that datasets are built from.





