Submission Package & Gates

The submission package is the war-room's checklist of documents your team must produce for a bid. Combined with mandatory-criteria compliance, it drives the submission gates that decide when a bid can be marked submitted.

Deliverables

Each deliverable is one document in the bid package. A row shows the document name, an optional "optional" tag for non-required items, and a status pill you can change from a dropdown.

Statuses

Only Final counts toward readiness and the deliverables gate — "in review" is not done.

Adding and removing

• Add any document with the input at the bottom of the panel (new items start as Missing and required).
• Remove items that don't apply to this bid with the delete control on the row.
• Each item can be marked required or optional — only required items gate submission.

The standard template

If the bid has no checklist yet, one click on Start from the standard template seeds a default package for Canadian public-sector bids:

The seeder is a no-op if deliverables already exist, and everything it creates can be renamed, re-flagged, or removed afterward.

Submission gates

Two gates control the Mark submitted action:

1. All mandatory requirements compliant — every mandatory requirement extracted from the linked RFP must be assessed as fully met. Partially met, cannot meet, and unassessed requirements all count as open gaps. If no mandatory requirements have been extracted at all, this gate passes informationally rather than blocking bids that were never analyzed.
2. All required documents final — every required deliverable must have status Final, and at least one deliverable must exist on the bid.

The gates appear live in the war-room's intelligence rail, each with a pass/fail mark and details of what remains open.

Marking a bid submitted

When both gates pass, the header shows Mark submitted. Clicking it:

• Sets the opportunity's status to Submitted (the pill in the header updates)
• Records the status change in the opportunity's activity log
• Moves the bid out of the "in progress" count on the Active Bids list

A bid already marked submitted cannot be marked again.

Force override

While gates fail, the header shows a "N blockers" button instead. Clicking it opens a dialog that:

1. Lists exactly which gates are open
2. Requires a written reason before the override can proceed
3. On confirm, marks the bid submitted anyway — with the override and your reason recorded in the activity log

Next steps

• The War-Room - The full per-bid workspace
• Active Bids Overview - How bids enter the workspace
• Bid Analysis - Extracting the mandatory requirements that feed the compliance gate