Compliance SOPs

Why This Exists

This document defines SOP areas for repeatable Compliance Practice work.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

SOPs make readiness review, document operations, expiry monitoring, tender-specific checks, risk reviews, and corrective actions repeatable and auditable.

SOP Catalogue

SOP ID	SOP	Purpose	Primary Digital Professional
COMP-SOP-001	Procurement Readiness Review SOP	Review readiness score, documents, gaps, and risk posture.	Lex
COMP-SOP-002	Compliance Document Operations SOP	Coordinate document collection, status review, and evidence readiness.	Lex
COMP-SOP-003	Expiry Monitoring SOP	Monitor expiry dates and trigger reminders or escalations.	Lex
COMP-SOP-004	Tender-Specific Compliance Check SOP	Compare tender requirements against compliance readiness state.	Lex
COMP-SOP-005	Compliance Risk Review SOP	Classify risk level, impact, and response plan.	Lex
COMP-SOP-006	Corrective Action SOP	Coordinate resolution of missing, expired, weak, or unverified evidence.	Lex
COMP-SOP-007	Compliance Escalation SOP	Escalate high-risk compliance blockers to Executive Office.	Lex
COMP-SOP-008	Compliance Reminder SOP	Request and review reminders through Notification.	Lex
COMP-SOP-009	Compliance Reporting SOP	Prepare compliance performance and readiness report inputs.	Lex

SOP Execution Flow

flowchart TD
    Trigger[Expiry, requirement, or readiness signal]
    SOP[SOP]
    Review[Lex review]
    Action[Corrective action]
    Command[Compliance-owned workflow]
    Notify[Notification request]
    Report[Report input]

    Trigger --> SOP
    SOP --> Review
    Review --> Action
    Action --> Command
    Action --> Notify
    Review --> Report

SOP Rules

• SOPs must preserve source references.
• Compliance state changes must use Compliance Domain commands/workflows.
• SOP outputs must distinguish operational support from legal advice.
• Tender-specific checks must cite source tender requirements.