SIMAP tender support from notice to controlled submission

Operating boundary

SIMAP provides the channel; the package provides the bid case

SIMAP is the shared electronic public procurement platform used by the Swiss Confederation, cantons and communes. Official Swiss guidance describes functions for finding publications, downloading documents, asking questions and submitting tenders. These mechanics are important, but they do not tell a supplier whether an opportunity is winnable or even eligible. That conclusion requires the current complete procurement package and evidence about the bidder.

Support should therefore maintain two connected records. The platform record covers publication identity, account access, files, amendments, forum activity, cut-offs and submission status. The decision record covers requirements, evidence, owners, interpretations, risks and approvals. Combining them makes a late amendment actionable without turning platform status into legal certainty. Thresholds, procedures and authority-specific rules can change, so current official material and the specific documents take precedence over a static web guide.

Bid decision

Qualification must fail closed when decisive evidence is absent

A useful qualification is not a percentage produced from a notice. It is a structured argument linked to the full package. Record formal participation conditions, mandatory proof, lot boundaries, award criteria, contract constraints and delivery capability separately. A weak scoring position may make a bid commercially unattractive, while a missing mandatory declaration can create a different and more immediate risk. Conflating them hides the action required.

Use explicit states. Verified means the evidence has been inspected and applies. Unresolved means an owner and due date exist. Not applicable needs a reason. Failed means the condition is not currently satisfied. A conditional go is legitimate only when each condition has an accountable resolution path and a stop date. Do not invent portal access, signatures, references, insurance, turnover, certifications or partner commitments. Absence of proof is a visible gap, not an invitation to assume.

• Quote the exact source for every knockout assessment.
• Separate formal admissibility, scoring, delivery and commercial attractiveness.
• Record the bidder entity and lot for each proof.
• Give every conditional item an owner, due date and no-bid trigger.
• Escalate interpretation instead of converting uncertainty into confidence.

Change control

Questions and amendments belong inside the requirement system

A clarification is most useful when it identifies the document, section, requirement and decision blocked by ambiguity. Draft it early enough for internal review and official submission. Avoid embedding a sales pitch or disclosing unnecessary solution detail. Once an official answer is published, assess whether it changes eligibility, scope, pricing, evidence, response wording or the bid decision. The answer may apply to all bidders even when another supplier asked the question.

Corrections and replacement files need the same discipline. Preserve the earlier version, mark it superseded and identify every dependent item. A changed price sheet can affect commercial work; a changed annex can invalidate a compliance mapping; a new deadline can alter the internal plan without reducing quality controls. A daily manual check may be appropriate near critical dates even when alerts exist. The objective is not merely to know that something changed, but to prove that the response absorbed it.

• Maintain a question register with official cut-off and owner.
• Link each question to the requirement and blocked decision.
• Record every official answer as controlled source material.
• Run an impact assessment for each correction or replacement.
• Reconfirm package currency before final release.

Portal readiness

Treat submission as a controlled production event

Portal work should not begin when the proposal is finished. Register the organization and users early, assign roles, learn the relevant project workflow and use official training or help resources where available. Confirm which person may perform each action. Technical support can address platform behavior; it cannot decide what the supplier is authorized to promise or sign.

Set an internal release point before the official deadline. Freeze approved files, validate names and formats, scan the manifest for omissions and confirm that price, declarations and narrative are consistent. Upload with enough time to resolve a rejected file or access problem. After release, capture the final state and authoritative receipt, then preserve the submitted package. If any step cannot be verified, report it as pending rather than calling the bid submitted.

• Rehearse login, roles and upload on the relevant account.
• Keep draft, approved and uploaded artifacts visibly distinct.
• Use a final manifest tied to the latest requirement register.
• Require explicit authority for signature and portal release.
• Retain receipt and exact submitted files as the submission record.