Compliance Meetings¶

Why This Exists¶

This document defines the meeting and coordination cadence for the Compliance Practice.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

Compliance meetings convert readiness signals, expiry risks, tender-specific requirements, and corrective actions into coordinated work.

Meeting Catalogue¶

Meeting	Purpose	Cadence	Led by	Outputs
Compliance Readiness Review	Review Procurement Readiness Score, document status, and priority gaps.	Weekly or onboarding.	Lex	Readiness actions and risk notes.
Expiry Risk Review	Review expiring documents and escalation needs.	Daily or weekly depending on risk.	Lex	Reminder and corrective action queue.
Tender-Specific Compliance Review	Check tender requirements against readiness state.	Event-triggered by Opportunity or Bid.	Lex	Compliance check outcome.
Corrective Action Review	Review progress on missing, expired, or weak compliance items.	Weekly.	Lex	Updated corrective action status.
Compliance Escalation Review	Review high-risk compliance blockers.	Event-triggered.	Lex with Executive Office.	Escalation decision and follow-up.
Compliance Performance Review	Review KPIs and trend reports.	Monthly.	Lex with Pulse.	Improvement actions.

Meeting Flow¶

sequenceDiagram
    participant Opportunity
    participant ComplianceDomain as Compliance Domain
    participant Lex
    participant Bid
    participant Exec as Executive Office

    Opportunity->>Lex: Tender compliance requirement
    ComplianceDomain->>Lex: Readiness and document state
    Lex->>Lex: Review risk and corrective actions
    Lex-->>Bid: Compliance check outcome
    Lex-->>Exec: Escalation if high risk

Meeting Rules¶

Meetings must produce check outcomes, corrective actions, reminders, escalations, or no-action records.
Tender-specific reviews must cite tender requirement references.
Corrective action reviews must track owner and due date.
Executive Office coordinates priority conflicts and escalations.