Bid Business Rules¶
Why This Exists¶
This document defines business rules for the Bid Domain.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Rules protect bid execution quality, accountability, approval discipline, and submission readiness.
Rule Catalogue¶
| Rule ID | Area | Rule |
|---|---|---|
| BID-RULE-001 | Workspace | A Tender Workspace must reference a TenderOpportunityId and OrganizationId. |
| BID-RULE-002 | Opportunity boundary | Opportunity owns tender records, matching, and recommendations. |
| BID-RULE-003 | Bid ownership | Bid owns workspace state, artefacts, approvals, and submission records. |
| BID-RULE-004 | Compliance boundary | Compliance facts and readiness must be referenced, not overwritten. |
| BID-RULE-005 | Organization boundary | Organization profile, capabilities, people, resources, and experience must be referenced from Organization. |
| BID-RULE-006 | Intelligence boundary | AI output becomes Bid state only after accepted into workspace. |
| BID-RULE-007 | Tasks | Bid tasks must have status and owner or queue. |
| BID-RULE-008 | Proposal draft | Proposal sections must be versioned and reviewable. |
| BID-RULE-009 | SBD forms | SBD forms must be validated before submission pack approval. |
| BID-RULE-010 | Pricing | Pricing workbook must be reviewed before final submission. |
| BID-RULE-011 | Submission | Final submission requires checklist completion and approval. |
| BID-RULE-012 | Outcome | Bid outcome should be captured once known. |
| BID-RULE-013 | Contract boundary | Awarded contract delivery belongs to Contract Domain. |
Submission Rule¶
Bid may support electronic submission requests and manual submission packs. It must record submission support state and evidence, but actual external platform guarantees are implementation-specific.