Catch what gets bids rejected before you seal the envelope

What the Submission Guard checks

• One row per mandatory item the tender names, keeping the tender's own reference where it has one, and G-01, G-02 and so on where it does not.
• Standard items the tender left unsaid. Where the tender is silent on items commonly required in its procurement framework, such as a signed bid form, power of attorney, company registration, tax clearance, audited accounts, separate technical and financial envelopes, page initialling or copies on USB, it may add them as optional rows with a note to confirm in the instructions to bidders.
• Notes on each row for format, signature, notarisation, validity period, amount and expiry warnings.
• A status on each row: Missing, In progress, Ready or N/A, plus, where it finds one, a link to the vault item that satisfies it.

How it works

1. 1Upload and analyse the tender pack. The analysis supplies the mandatory documents, bid security, validity, deadline and submission rules the checklist is built from.
2. 2Put your evidence in the Company Vault. Certificates, licences, insurances, financial statements and CVs live there, each with its expiry date where it has one. On the Configure step, Bidligence lists what the tender needs that only you can supply, such as certificates, financials, bonds and signed forms, so you can upload them before the run.
3. 3Generate the package. The run prices the BOQ first if the bid has none yet, writes the documents you ticked, then builds the Submission Guard checklist whatever you ticked. The Bid Preparation Report closes it.
4. 4Read the checklist. Each row shows the vault item or generated document it is linked to. The readiness score and the pre-submission audit sit above the rows, the countdown to the deadline beside them.
5. 5Close the gaps. Link or upload evidence from the row, change a status, write a note, or add a row the tender needs that the checklist missed. Rebuild draws the checklist again from the current analysis and package.
6. 6Export and submit. The Submission Checklist exports as an editable DOCX or XLSX, and travels in the package ZIP as a DOCX with the vault files linked on it. Signing, sealing and delivery are your team's.

What you see on the Guard & export step

• A readiness score: the share of mandatory rows marked Ready, as a percentage and as "x of y mandatory items ready". Rows marked N/A are left out of the count.
• A pre-submission audit in plain sentences: the number of mandatory items still missing; the bid security the tender requires, with its type, amount and validity where the analysis found them, and a reminder to check amount, wording and validity against the instructions to bidders; linked evidence that has expired; unverified claims flagged in the generated documents, to confirm or remove; a missing priced BOQ; and a deadline two days away or less, with a reminder to allow for courier or portal upload time.
• A clean result that still asks for a person. When none of those lines applies, the audit reads clean and asks for a final human read-through of every form. Rows still In progress, such as forms waiting for a signature, do not stop it reading clean, so check them and the readiness score too. While the expiry of linked evidence is still being checked, it says so instead of reading clean.
• A countdown to the closing date and time in the tender's own time zone, with the submission method and address.
• The evidence on each row: the linked vault item with its expiry date, in red once it has expired and in amber within 60 days of expiry. A searchable picker over the whole Evidence Vault lets you change or remove the link, and linking an item marks the row Ready.
• Upload from the row. On a row with no link, pick a file from your computer: it goes into your Company Vault, links to the row and marks it Ready. This shortcut does not run the vault's extraction, so it spends no credits, but it also records no expiry date and the file is not read into your bids; set both in the vault.
• Your own rows. Add a requirement the checklist missed, such as a notarised joint venture agreement, with its category. It gets an M- reference, such as M-14, and is kept every time the checklist is rebuilt.

Documents from the package are linked by fixed rules

When an addendum changes the rules

• adds the documents it reads as new to the checklist as Missing rows, with a note naming the addendum, and skips any already there by reference or by the opening words of the requirement;
• moves the bid deadline when the closing date changed, but only to a date that has not passed. If the new date cannot be read, has already passed, or would pull the deadline earlier without a recorded deadline change, the deadline is left alone and you are told to set it by hand;
• flags the generated documents that need updating, with the reason;
• files the bidder questions the addendum answers as clarifications on the bid;
• notifies the bid's team.

The most recent addendum review can be undone. If the analysis has been edited since, Bidligence refuses the undo rather than throw those edits away, and asks you to make the changes by hand or keep the review. Rows an addendum review added are kept when the checklist is rebuilt.

Work out your bid validity and bid security dates

How it connects to the rest of the bid desk

• The Company Vault holds the certificates, licences, insurances and financial statements, with their expiry dates, that the rows link to.
• Evidence-locked AI flags claims in the generated documents that it could not tie to your evidence; the audit counts them and asks you to confirm or remove each one.
• The priced BOQ satisfies the tender's pricing schedule rows, and the audit says so when there is none.
• The Mock Evaluator scores the package criterion by criterion and lists pass/fail issues separately from its score, so content gaps show up beside the paperwork gaps.
• Design drawings link as drafted until a registered engineer signs the set off.
• Deadline tracking: reminder e-mails, sent 7, 3 and 1 days before the deadline (each team member can keep any of those days and drop the rest), say how many mandatory checklist items are still missing, and the dashboard's list of upcoming bids flags the same count.
• Bid exports carry the Submission Checklist as DOCX or XLSX, and the package ZIP adds the vault files linked on it in a company documents folder.
• Hunter, the bid agent, can hand the package run to the panel beside its chat, and that run builds the checklist with the documents.

Its limits, and your control

• It is a check, not a promise of compliance. A clean audit means it found nothing to report, and rows still In progress do not stop it reading clean. Whether the bid is responsive is decided by the procuring entity.
• It only knows what you uploaded. A requirement in a document you did not upload, or in an addendum you have not reviewed, is not on the checklist. Add it as your own row.
• The rows are drafted by Super Intelligence. It reads the tender's requirements and proposes rows and vault links; check them against the instructions to bidders and the bid data sheet. Links to generated documents follow the fixed rules above.
• Signing, originals and delivery stay with you. Signatures, stamps, page initials, notarised documents, the bank's guarantee and the portal upload or hand delivery are your team's to do.
• A rebuild redraws Bidligence's own rows. Rows you added and rows from an addendum review are kept; the rows built from the tender are drawn again, so re-check any status you changed by hand on them.
• Changes need the Finance role or higher. Finance, Technical lead, Bid manager and Admin members can rebuild the checklist, change statuses, links and notes, and add or remove rows; Viewers and Reviewers cannot.
• It uses credits. Building or rebuilding the checklist and running an addendum review draw on the workspace's credits; linking evidence, uploading from a row and editing rows do not.

Which plans include it

Questions

What does the Submission Guard check?

Every mandatory form, certificate, bond, format and submission rule read from the tender, matched against your Company Vault and the documents Bidligence generated for the bid. Its audit lists missing mandatory items, the bid security the tender requires, expired linked evidence, unverified claims in the generated documents, a missing priced BOQ and a deadline two days away or less.

Does a clean audit mean my bid is compliant?

No. It means none of the audit's lines applies: no mandatory item is Missing, the tender asks for no bid security, no linked evidence has expired, no unverified claim is flagged, the BOQ is priced and the deadline is more than two days away. Rows still In progress, such as forms waiting for a signature, do not stop it reading clean. It is a check, not a guarantee: the evaluation is the procuring entity's, and signatures, originals, the bid security and delivery remain your team's job. Even a clean audit asks for a final human read-through of every form.

Will it catch an expired certificate?

Yes, for evidence linked from your Company Vault with its expiry date recorded. Super Intelligence is told to propose only unexpired vault items as links, and a row it links to an expired item is not marked Ready; a linked item that has expired shows its date in red and is counted in the audit, and one within 60 days of expiry shows in amber. The vault and the dashboard flag expiring items too.

Why is a form Bidligence drafted still marked In progress?

Because a drafted form is not a signed one. Rows answered by the Forms & Declarations pack or by the cover letter, such as a letter of bid, read In progress with a note to sign, stamp or attach the required original, unless your own vault evidence was linked to them, and any row whose wording demands a notarised original, a bank guarantee or a sealed envelope never reads Ready on a generated document alone. Mark it Ready yourself once it is done.

What happens when an addendum adds a new requirement?

Upload it and run the addendum review. Documents it reads as new are added to the checklist as Missing rows naming the addendum, the deadline moves if the closing date changed to a future date, and the generated documents that need updating are flagged with the reason.

Which plans include the Submission Guard?

Starter, Pro and Enterprise. The checklist comes with every document generation run, which needs one of those plans; Starter and Pro each start with a 3-day free trial. A free workspace's 500 welcome credits, granted once your e-mail is confirmed, cover analysing a tender, which reads the requirements the checklist is built from, its Bid Score and a priced BOQ.

Sources

Rules and portals change. Check the tender’s own documents and the official source before you rely on any of this.

• World Bank, Standard Procurement Document: Request for Bids, Small Works (Two-Envelope Bidding Process with Rated Criteria), September 2025