BidScript monitors your drafts as you work and flags content gaps - places where information appears to be missing, incomplete, or out of step with the question, the tender documents, or your approved knowledge.
The point is to catch these while you can still act on them, rather than discovering them during a final compliance check.
What a content gap is
A content gap is raised when BidScript detects that your draft is missing key information, examples, evidence or alignment compared with:
The original tender question
The tender documentation uploaded to the project
The Bid Libraries you have selected, and your wider organisational knowledge
Project-specific context and metadata
Review a flagged gap
When a gap is detected, a yellow warning flag appears at the top of the Answer Workspace.
Click the flag to open the Content Gap Card, which sets out:
What information is missing
Why that information matters
How to resolve it
Resolve a content gap
There are two routes, and which you choose depends on where the missing information actually lives.
Update the draft
Best for small additions and clarifications where you already have what is needed.
Add the missing information to the relevant part of the draft.
Mark the content gap as Resolved.
Update the source
Best where the gap is a formal policy, certificate, example or approved content piece that your knowledge base does not yet hold.
Upload the material to the Bid Library or the Q&A Store.
Regenerate the draft, or use inline editing, to bring the new content in.
This route takes slightly longer but fixes the gap permanently: every future draft benefits from the addition, and the same gap stops recurring across bids.
Where all gaps are logged
Every content gap is logged in the Bid Library Health Dashboard as a Flagged Issue. From there you get:
Visibility of gaps across every question in one place
Traceability between a flagged gap and its project
The ability to prioritise gaps and assign resolution to someone
This is where to look if you want to see the pattern rather than the individual gap - recurring flags usually point at something genuinely absent from your Bid Library.
Best practice
Watch for flags while drafting rather than checking at the end.
Resolve gaps early, so they do not become last-minute compliance risks.
Prefer source updates over draft-only fixes where the information should exist in your library anyway.
Combine resolution with inline regeneration to bring new source material into the draft cleanly.
Related articles
Evaluating and critiquing answers with BidBot - a broader assessment of how the answer will score.
BidBot in the Answer Workspace - regenerating a section after updating your sources.
Comments and feedback - gaps raised by people rather than the platform.