Tender-to-Contract Glossary¶
Executive Summary¶
This glossary defines process-specific language for the Tender-to-Contract process wave.
Why This Exists¶
Tender-to-Contract work involves multiple Domains, Practices, Digital Professionals, approvals, and events. Controlled language prevents ownership confusion and supports AIOS reasoning.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
A shared glossary improves process consistency, onboarding, audit review, and cross-Practice collaboration.
Terms¶
| Term | Definition |
|---|---|
| Tender-to-Contract | End-to-end process wave from tender discovery to contract award transition. |
| Tender Discovery | Process of identifying and indexing public or private tender opportunities. |
| Tender Qualification | Process of assessing relevance, fit, eligibility, readiness, risk, and pursuit value. |
| Bid/no-bid Decision | Executive decision on whether the customer should pursue a tender. |
| Bid Workspace | Bid-owned operating workspace for a pursued tender. |
| Bid Plan | Plan that defines tasks, owners, deadlines, dependencies, reviews, and risks. |
| Briefing Management | Process of tracking tender briefing sessions, notes, clarifications, and bid implications. |
| Proposal Preparation | Process of preparing proposal artefacts and narrative using governed source facts. |
| SBD Form | Standard bidding document form required by certain South African procurement processes. |
| Pricing Coordination | Process of coordinating commercial inputs, BOQ references, assumptions, and approvals. |
| Submission Review | Final readiness review before approval and submission packaging. |
| Submission Pack | Approved bid artefact set prepared for electronic or manual submission. |
| Tender Submission | Process of supporting submission and recording submission evidence. |
| Outcome Capture | Process of recording tender outcome, award status, loss feedback, or cancellation. |
| Award Transition | Handoff from won bid into Contract Domain setup without modelling delivery. |
| Lessons Learned | Structured capture of pursuit, bid, submission, outcome, and feedback learning. |
| Pursuit Decision | Human-approved decision to continue or stop tender pursuit. |
| Submission Evidence | Proof of submission time, channel, recipient, confirmation, or manual handoff. |
| Lifecycle Event | Business event that starts, advances, blocks, or closes a process stage. |
| Process Exception | Condition where the process cannot follow its expected path. |
Cross-Reference Notes¶
- Opportunity Domain owns tender opportunity records and matching facts.
- Compliance Domain owns compliance readiness, requirements, verification, and risk.
- Bid Domain owns bid workspace, bid artefacts, approval workflows, submission records, outcome, and lessons learned.
- Contract Domain owns award transition and future contract delivery state.
- AIOS orchestrates process execution but does not own source facts.