Level 3: Product Management & Business — Personnel & Function Level 3 comprises product managers, business unit heads, and deployer relationship managers. They provide oversight of the system’s alignment with business intent, deployer satisfaction, and affected person experience, bridging technical monitoring and organisational accountability. Product managers have access to business-level metrics: deployer satisfaction scores, override rates per deployer, complaint volumes, and affected person feedback. They interpret these metrics in the context of the AISDP’s documented intended purpose and the risk assessment’s identified residual risks. Level 3 is the oversight layer most attuned to whether the system is achieving its stated purpose in the real world. Technical metrics may show the system operating within specification; Level 3 detects whether that specification translates into appropriate real-world outcomes for deployers and affected persons. Key outputs

• Business-level metric access and interpretation
• Deployer satisfaction and affected person experience monitoring
• Intent alignment oversight
• Bridge between technical monitoring and organisational accountability

Level 3: Intent & Outcome Drift Detection Level 3 is where intent and outcome drift are most likely to be detected. Three forms of drift are relevant. Purpose creep: deployers using the system beyond its documented intended purpose. Configuration undermining: deployer organisations configuring the system in ways that weaken human oversight. Outcome divergence: the system’s real-world outcomes diverging from expectations set during implementation. These observations represent compliance risks that may not be visible in technical monitoring data. A system whose accuracy metrics are within specification may still be causing harm if deployers are applying its outputs in contexts the AISDP did not anticipate. Product management has the domain knowledge to recognise these patterns and the authority to escalate them. Intent drift detection feeds into the AISDP maintenance process. If deployers are consistently using the system outside its intended purpose, the organisation must either update the intended purpose (with a corresponding conformity assessment impact analysis) or take corrective action to restrict usage to the documented scope. Key outputs

• Three drift forms monitored (purpose creep, configuration undermining, outcome divergence)
• Domain knowledge applied to detect non-technical compliance risks
• AISDP maintenance trigger for intended purpose drift
• Module 7 AISDP evidence

Level 3: Escalation Triggers Level 3 escalation triggers include deployer configuration or usage patterns outside the intended conditions of use, trends in deployer feedback suggesting dissatisfaction with fairness, accuracy, or transparency, affected person complaints (particularly those alleging discrimination or opacity), and any indication that real-world outcomes are diverging from AISDP commitments. Escalation from Level 3 reaches Level 4 (compliance, legal, and data protection), where the regulatory implications of the observed patterns are assessed. Level 3 escalations are often the earliest signal that a compliance issue is developing, before it manifests in technical metrics. Escalation data from Level 3 is aggregated and reported at the quarterly oversight review. Cross-deployer complaint patterns are a particularly valuable Level 3 escalation source. Key outputs

• Four categories of business-level escalation trigger
• Escalation to Level 4 for regulatory assessment
• Early signal of developing compliance issues
• Cross-deployer pattern analysis integration