Bid Lifecycle¶
Why This Exists¶
This document defines the lifecycle of a bid workspace.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Lifecycle clarity keeps bid execution controlled from pursue decision through planning, drafting, approval, submission, outcome, and learning.
Lifecycle States¶
| State | Meaning |
|---|---|
| Created | Workspace created from selected opportunity. |
| Planning | Bid plan and team are being defined. |
| In Progress | Tasks, drafting, forms, pricing, and collaboration are underway. |
| Internal Review | Proposal sections, SBD forms, pricing, and checklist are being reviewed. |
| Approval Pending | Approval workflow is active. |
| Approved For Submission | Submission pack approved. |
| Submitted | Submission has been recorded. |
| Withdrawn | Organization chooses not to continue. |
| Closed | Bid is closed after submission, withdrawal, or missed deadline. |
| Outcome Captured | Result, feedback, and lessons are captured. |
State Diagram¶
stateDiagram-v2
[*] --> Created
Created --> Planning
Planning --> InProgress
InProgress --> InternalReview
InternalReview --> ApprovalPending
ApprovalPending --> ApprovedForSubmission
ApprovalPending --> InProgress
ApprovedForSubmission --> Submitted
InProgress --> Withdrawn
Submitted --> Closed
Withdrawn --> Closed
Closed --> OutcomeCaptured
OutcomeCaptured --> [*]
Lifecycle Rule¶
Final submission requires approval and submission readiness validation unless an approved exception policy applies.