Bid Policies¶
Why This Exists¶
This document defines policies that govern Bid behavior and event reactions.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Policies make bid planning, drafting, approvals, validation, submission support, and learning consistent.
Policy Catalogue¶
| Policy | Runs when | Decision made | Outputs |
|---|---|---|---|
| Workspace Creation Policy | Pursue decision occurs. | Whether Tender Workspace can be created. | TenderWorkspaceCreated. |
| Bid Planning Policy | Workspace created. | Required milestones and initial tasks. | Bid plan and tasks. |
| Task Assignment Policy | Plan or task changes. | Who owns task or queue. | BidTaskAssigned. |
| AI Draft Acceptance Policy | Intelligence proposes draft content. | Accept, reject, or request edit. | Proposal section update. |
| SBD Validation Policy | SBD form prepared. | Whether form is complete enough for review. | Validation state. |
| Pricing Review Policy | Pricing workbook updated. | Whether pricing can move to approval. | Pricing status. |
| Submission Checklist Policy | Pack assembled. | Whether submission pack is ready. | Submission readiness status. |
| Approval Policy | Approval requested. | Whether bid is approved, rejected, or changes requested. | Approval decision. |
| Outcome Capture Policy | Outcome known. | Whether outcome record is complete. | BidOutcomeCaptured. |
| Lessons Learned Policy | Bid closed. | What learning should be captured. | LessonsLearnedCaptured. |
Policy Flow¶
flowchart TD
Workspace[Workspace Created]
Plan[Planning Policy]
Draft[Drafting and AI Acceptance]
Validate[Validation Policies]
Approve[Approval Policy]
Submit[Submission Support]
Outcome[Outcome and Lessons]
Workspace --> Plan
Plan --> Draft
Draft --> Validate
Validate --> Approve
Approve --> Submit
Submit --> Outcome
AI Policy Boundary¶
Intelligence can suggest drafts and tasks. Bid decides whether those suggestions become workspace state.