Contract Policies¶
Why This Exists¶
This document defines policies that govern Contract behavior and event reactions.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Policies make contract creation, delivery planning, variation control, risk handling, financial tracking, closeout, and lessons learned consistent.
Policy Catalogue¶
| Policy | Runs when | Decision made | Outputs |
|---|---|---|---|
| Contract Creation Policy | Award or contract creation event occurs. | Whether contract workspace can be created. | ContractWorkspaceCreated. |
| Delivery Planning Policy | Workspace created. | Required milestones, deliverables, owners. | Delivery plan. |
| Milestone Monitoring Policy | Milestone changes or due date approaches. | Whether milestone is on track or overdue. | Notification or risk. |
| Variation Control Policy | Variation requested. | Whether review, approval, or rejection is required. | Variation decision. |
| Invoice Review Policy | Invoice recorded. | Whether invoice is ready, disputed, or needs approval. | Invoice status. |
| Payment Tracking Policy | Payment recorded or overdue. | Whether payment state affects contract health. | Payment status and risk. |
| Contract Risk Policy | Risk trigger occurs. | Risk level and mitigation path. | ContractRiskIdentified. |
| Closeout Policy | Delivery appears complete. | Whether closeout can proceed. | Closeout checklist or block. |
| Lessons Learned Policy | Contract closes. | What learning should be captured. | ContractLessonsLearnedCaptured. |
Policy Flow¶
flowchart TD
Award[Award Event]
Create[Creation Policy]
Plan[Delivery Planning]
Monitor[Milestone and Risk Monitoring]
Finance[Invoice and Payment Policies]
Closeout[Closeout Policy]
Lessons[Lessons Learned]
Award --> Create --> Plan --> Monitor --> Finance --> Closeout --> Lessons
Intelligence Policy Boundary¶
Intelligence may recommend actions or identify risks. Contract policies decide whether those recommendations become Contract state.