Official source checks
Belgian tender sources: verify notices and submission
Open the official record, identify the buyer and current response task, then verify the documents, language and submission route. A searchable notice is not evidence that a bid has been submitted or that your company qualifies.
start with a known notice
This page is a source-verification checklist for a bid coordinator with an identified Belgian record. For buyer targeting and a first search, use the Belgium supplier playbook.
BOSA's current guidance links the official platform, Tender Bulletin search and participation help. Use those entry points rather than copied instructions for legacy screens. BOSA's 2023 transition notice explains the replacement of e-Notification, e-Tendering and e-Catalogue.
Identify the legal buyer before assigning a market label. A Brussels address alone does not establish Belgian national procurement rules: EU institutions have their own notices and response instructions. Keep that buyer segment separate and consult the EU source overview.
official sources and their limits
| Starting point | Role | Record check |
|---|---|---|
| Belgian e-Procurement | Official platform | Locate the record and document route; inspect its current stage and participation instructions. |
| BOSA application guidance | Current help and workflow | Follow company/account, search and submission guidance; access is not qualification. |
| TED | European notice publication | Match related references and the legal buyer rather than treating a second publication as another lead. |
This is a source map, not a Duke integration inventory. eForms are notice forms, not a separate source: see PIANOo's explanation. Publication rules do not prove that a product has captured every relevant record or attachment.
read the stage and the latest documents
A new publication may report an award or amend an existing procedure. Record what action is actually invited and whether its deadline remains open. Treat a framework award as research, not an invitation to an unappointed supplier to bid for every order.
Keep the original document URL and the latest specification, amendments and clarification answers together. If a changed site list, service window or qualification requirement affects the pursuit, assign a fresh review before reusing an older price or proposal.
Search language, interface language and allowed response language are separate fields. Dutch, French or German search terms may help discovery; none authorises a response in that language. Record the actual language clause and ask through the specified clarification channel if it is ambiguous.
confirm the actual submission route
BOSA distinguishes a personal account, company association and offer submission, and notes that digital signing may be needed. Check the current help and your procedure's instructions for the responsible user, required signature and final action. Do not assume every procedure has identical signing requirements.
Check access before the deadline becomes urgent. Use official help or training material to prepare; do not submit a test offer into a live competition. Retain the confirmation of the real submission rather than treating an uploaded file or a saved draft as proof of receipt.
This checklist does not decide threshold or legal eligibility questions. Record the buyer, regime and contract type and have material uncertainties reviewed against current BOSA procurement guidance and the tender. No historic threshold table should substitute for that check.
save a source-to-response handoff
Buyer and identifiers
Legal buyer, original source URL, procedure and lot identifiers, date checked, and any related TED reference.
Latest evidence
Current specification, amendments and clarification answers; question and submission deadlines with the stated time zone.
Language and delivery
Allowed response language and any service-language obligations, each taken from the documents; delivery sites rather than buyer headquarters.
Submission readiness
Correct company and authorised user, required forms, applicable signing instructions, final submission action and retained confirmation.
Add the pursuit owner, decision and next due date. Mark each gap as unresolved rather than interpreting missing evidence as compliance. Use the notice-reading workflow for the wider qualification record.
illustrative decision: a changed support requirement
A Belgian network-support supplier has shortlisted a hospital tender. It can deliver to the listed sites, but a clarification changes the out-of-hours response arrangement. The team also finds that its intended signatory has not confirmed the necessary platform access.
The bid lead links the clarification to the existing lot record, asks the service lead to recost support and assigns the account owner to verify the authorised response route. The decision stays “clarify” until both gaps are resolved; translating the notice does not settle the service-language or signing requirements.
This is a fictional scenario, not a live tender or a demonstrated customer outcome. For service-specific evidence, use the hospital IT qualification guide.
continue the task
test Duke against your source record
Bring two Belgian notice URLs and a changed document or clarification to a demonstration. Compare the buyer, lot, stage, deadline and source links available in Duke; identify missing evidence and who checks it in the official channel.
No complete national coverage, automatic translation accuracy or notification cadence is certified here. Duke is not the buyer's submission system.
Official guidance checked . Review due 14 December 2026, or sooner after source changes. Not a legal eligibility opinion.