Skip to content

Compliance Relationships

Why This Exists

This document explains how the Compliance Practice relates to domains, Practices, Digital Professionals, SOPs, and KPIs.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Relationship clarity ensures Compliance supports procurement readiness without duplicating source facts or bypassing domain ownership.

Practice Relationships

Practice Compliance relationship
Executive Office Receives high-risk escalations, readiness summaries, and decision support.
Business Analysis Provides organization context and capability evidence signals.
Procurement Intelligence Uses readiness and compliance risk in opportunity qualification.
Bid Management Uses tender-specific compliance checks before submission.
Procurement Academy Receives compliance learning gap signals.
Business Intelligence Receives compliance KPI and trend inputs.
Platform Administration May receive support or governance context for compliance-related support cases.

Domain Relationships

flowchart TD
    Practice[Compliance Practice]
    ComplianceDomain[Compliance Domain]
    Organization[Organization]
    Opportunity[Opportunity]
    Bid[Bid]
    Intelligence[Intelligence]
    Notification[Notification]
    Analytics[Analytics]
    Executive[Executive Office]

    ComplianceDomain -->|facts and readiness state| Practice
    Organization -->|organization context| Practice
    Opportunity -->|tender requirements| Practice
    Bid -->|bid readiness context| Practice
    Intelligence -->|analysis support| Practice
    Practice -->|reminder requests| Notification
    Practice -->|KPI inputs| Analytics
    Practice -->|escalations| Executive

Relationship Rules

  • Compliance Domain owns compliance facts and readiness state.
  • Compliance Practice owns operational compliance capabilities, SOPs, reviews, and KPI accountability.
  • Lex executes and coordinates compliance work but does not override domain ownership.
  • Intelligence can support analysis, but compliance changes require Compliance-owned commands/workflows.
  • Notification delivers reminders and escalations but does not own compliance facts.

Cross-Practice Handoff

Compliance handoffs should include:

  • Compliance source references.
  • Tender-specific requirement references where applicable.
  • Risk level.
  • Corrective action need.
  • Deadline or expiry urgency.
  • Recommended receiving Practice action.