Case Studies is in beta. It is available to selected organisations. To ask for access, contact [email protected].
Case Studies holds the past projects your organisation has delivered, ready to use when a tender asks for relevant examples. BidScript reads the documents in your Bid Library, pulls out the projects it finds, and links every fact back to the document it came from. Nothing becomes team knowledge until a reviewer approves it.
This article covers how to review what BidScript finds, add your own case studies, find the right one for a bid, and how BidBot uses them.
Where to find it
In the left-hand sidebar, click Bid Library.
Click Case studies.
On the Case Studies page, the count next to Case studies shows how many are still waiting for a verdict. Elsewhere in the Bid Library it shows the total. Inside the page, the view switch shows the approved count next to Case studies and the waiting count next to Review.
Who can use it
Reviewers
Admins, and anyone with edit access to the Bid Library. They approve and reject case studies, create new ones and resolve duplicates. To review a particular case study, you also need Editor access to every document behind it, unless you're an Admin. Without it, you can open the case study but don't see its decision controls, evidence actions or file actions.
Everyone else with Bid Library access
Can browse and search approved case studies, but doesn't see the review controls or the Duplicate resolution view.
Whatever your role, you only see a value if you can open a document behind it. A case study marked Includes documents some team members can't see may look different to your colleagues.
The three views
Case studies
Your approved case studies, ready to use in a bid.
Review
New case studies BidScript found in your documents, waiting for a verdict.
Duplicate resolution
Pairs of case studies that may be the same project under different names. Only reviewers see this view.
Review a case study
Open Review and select a case study.
Check the Fields. A dashed value is an unconfirmed suggestion from the source. Click Accept or Dismiss on each one, including those under Suggested from source.
Fix anything BidScript got wrong, using the Sources to check each fact.
Click Approve, Reject or Not a case study.
To change a verdict, click the highlighted button again to clear it, or click Move back to review on an approved case study. The Undo bar in Review reverses your last action. Click it again, or press u, to step further back through up to 50 actions.
What the details show
Confidence - hover the percentage to see how many documents and rows back the case study, their average confidence and any fields where the sources disagree. The percentage is hidden once a case study is approved.
Delivery - whether the project was delivered. BidScript classifies it from the documents, and you can change it. Your choice stays even when new documents are linked. Picking Unknown, or the value BidScript suggests, hands it back to BidScript's classification.
Work type and Outcomes - edit each one separately. An outcome taken from a tender or bid is marked as promised, not yet shown to be delivered. No outcome claim means the source names none.
Added by hand - a reviewer created the case study rather than BidScript finding it.
from a project - the case study came from one of your BidScript projects.
list-like document - a warning that the source names three or more unrelated bids, so check each fact came from the right one.
Check the evidence
Click Open full screen or Show all evidence to see where sources disagree, the names the project goes by, and every place it's mentioned.
If a mention is about a different project, click Not this project to move it out. If a row belongs to a separate project, press s to expand the rows, then press the row's number key to split it out. BidScript creates a new case study, named the way its source names it.
Link a project
The Project field links a case study to one of your BidScript projects. If you're a reviewer, click Link to this project or Not this project to settle a suggestion, or Link a project to search for one.
Review new evidence
When BidScript finds new evidence for an approved case study, reviewers see it under New since approval. The notification about it opens the case study with its details showing.
For each item, click Use new value to update the field or Approve to keep the evidence and the existing values. When there's more than one item, Skip moves to the next. More actions gives Move to its own case study and Remove from this case study. Approve all approves every item at once.
Review in bulk
In Review, select case studies with their checkboxes, or press x, then choose Approve, Reject, Not a case study or Deselect. Undo decision appears when a selected case study already has a verdict. Select all matching selects every case study that matches your filters.
To decide every matching case study at once, use Approve all or Reject all in Review. They skip case studies that are already reviewed and take up to 100 at a time, so narrow the filters first if more match. If more than 50 match, the button changes to Approve N? or Reject N?. Click it again to confirm. The result stays on screen for 40 seconds with an Undo button.
Resolve duplicates
The same project often turns up under different names. Duplicate resolution shows the pairs BidScript won't join on its own, the most likely matches first.
Open Duplicate resolution.
Narrow the pairs with the High, Medium and Low chips.
Click Same project to merge a pair, or Different to keep it apart. Click the highlighted button again to clear your verdict.
Merge all and Keep apart all resolve every matching pair that is still open. Each verdict can be undone from the message that confirms it.
Create a case study
Reviewers can add a project your documents don't cover yet.
In the Case studies view, click New case study.
Enter a Project name of up to 200 characters.
Optionally, click Add files to attach documents or photos.
Click Create case study.
If a similar name already exists, BidScript lists it under Already in your case studies. Click Open it instead rather than creating a duplicate. A new case study goes straight into the library and opens, so you can fill in the details.
Add files and notes
Use Attached files for anything that backs up a case study - photos, certificates, feedback letters. Click Upload to add a file from your computer, or From library to attach one already in the Bid Library.
Supported formats: PDF, Word (.docx, .doc), PowerPoint (.pptx, .ppt), Excel (.xlsx, .xls) and images (.png, .jpg, .jpeg, .webp).
Documents are read for facts. Images are marked Not scanned, because they're kept with the record but not read. Removing a file takes it off this case study, and the file stays in the Case studies library.
Use Notes for anything the team should know, such as who to ask, what to leave out or where the photos are. Notes save when you click away and hold up to 4,000 characters. The line under the case study title shows who last edited the case study, and when.
Find a case study
Search by name. In Review, search also covers buyer, place, services and documents, and you can put a phrase in quotes.
In Case studies and Review, click Filters to narrow by confidence, status, number of documents, year and which fields are filled in. Each count shows how many case studies that option would leave. Click Show N results to apply them, or Clear all to start again.
These options appear in Review only:
Quick views - ready-made filters such as High confidence, unreviewed and Missing dates
Include weaker evidence - adds possibly-delivered work and lower-confidence mentions
Only with a project link - case studies with a suggested link to one of your projects, shown when at least one has a link
Still gathering evidence - case studies without enough evidence yet while your library is being read, shown when there are any
In Review, sort by Best evidence or Confidence. Confidence is High at 75 and above, Medium from 50 to 74, and Low under 50.
Keyboard shortcuts
These work in the Review view. In Case studies and Duplicate resolution, only u works.
j and k - move between case studies
o or Enter - open the details
x - select (reviewers only)
a, r and n - Approve, Reject and Not a case study (reviewers only)
u - undo
s - expand the evidence rows
1 to 9 - after pressing s, split a row into its own case study (reviewers only, when there's more than one row)
/ - search
Esc - step back: clear the selection, then leave full screen, then close the details
With case studies selected, a, r and n apply to the selection. Otherwise they apply to the open case study and move on to the next unreviewed one.
While your library is being read
BidScript reads your Bid Library for past projects in the background. Until the first case studies are ready, the page shows how many of your documents have been read, and Case studies appear here as we find them. After that, a strip at the top shows Reading your library and how far through it is.
If the Case studies view is empty, nothing has been approved yet. Click Go to Review and approve one.
If you're a reviewer, click Refresh in the Case studies view to group the projects found in your documents into case studies again.
How BidBot uses case studies
In chat, BidBot can list and open your case studies, approved ones first. If it uses one that's still in review, it says so and keeps it apart.
BidBot takes facts about a past project only from its approved fields and their cited excerpts, plus passages from that case study's own source documents. It cites those passages as unreviewed source text. It never invents a past project, and never fills the gap with other Bid Library content, the tender, the web or general knowledge.
If no approved case study fits, BidBot tells you none was found. It won't edit your draft with past-project facts it can't support, and when BidScript drafts an answer, the gap goes into the Missing information list.
If a case study's library isn't selected, BidBot asks you to select it with the library button on the chat input bar.
When drafting for a tender, BidScript picks up to 10 case studies that best match it on buyer, scope, sector, value, location, recency and delivery role. Each comes with the reason it was selected.
Best practice
Start with the High confidence, unreviewed quick view, then check low-confidence case studies one at a time.
Check the sources before you approve, because approved fields are what BidBot cites.
Resolve duplicates early, so one project doesn't appear twice in a bid.
Set Delivery yourself when you know the outcome. Your choice survives new documents.
Related articles
Bid Library: Overview - how the libraries Case Studies reads are set up.
Using Specific Libraries - selecting libraries in BidBot chat.
BidBot: Overview - what BidBot can do.





