aicomply.
Lesson10 minChapter 5 of 8

Market Surveillance

How authorities monitor AI systems in the market.

Learning Objectives

By the end of this chapter, you will be able to:

  • Explain the market surveillance framework established by Articles 74-78
  • Identify surveillance triggers and proactive monitoring mechanisms
  • Understand authority powers during surveillance activities
  • Prepare for inspections and respond to surveillance actions
  • Navigate cross-border surveillance coordination

Market Surveillance Framework Overview

Market surveillance ensures AI systems remain compliant throughout their lifecycle—from market placement through deployment and ongoing operation. Unlike one-time conformity assessment, surveillance is continuous and reactive to market developments.

Legal Framework

ArticleTitleKey Content
Article 74Market surveillance and controlAuthority powers, surveillance activities
Article 75Mutual assistanceCross-border cooperation
Article 76Procedure at national levelNational enforcement procedures
Article 77Powers of authorities protecting fundamental rightsEU-wide protective measures
Article 78Formal non-complianceProcedural violations

Surveillance Objectives

ObjectiveActivitiesOutcome
Compliance verificationTesting, documentation reviewConfirm ongoing compliance
Risk identificationIncident monitoring, complaintsDetect emerging risks
EnforcementCorrective measures, penaltiesAddress non-compliance
Market protectionWithdrawal, recallRemove non-compliant AI
Information gatheringSector sweeps, studiesInform policy

Surveillance Triggers

Proactive Surveillance

TriggerDescriptionLikelihood
Random samplingAuthorities select AI systems for reviewModerate
Sector sweepsTargeted examination of high-risk sectorsModerate for priority sectors
New guidance implementationCheck compliance with new requirementsHigh after guidance issued
Scheduled reviewsRegular review programmesVaries by authority
Risk-based targetingFocus on high-risk categoriesHigh for Annex III areas

Reactive Surveillance

TriggerSourceResponse Time
ComplaintsUsers, affected persons, competitorsDays to weeks
Serious incidentsProvider reports, media, authoritiesImmediate to days
WhistleblowersInternal or external disclosureVariable
Media reportsInvestigative journalism, publicityDays
Other authority referralData protection, sector regulatorsWeeks
Post-market monitoring dataProvider's own monitoringDepends on severity
Cross-border alertsOther Member State authoritiesDays

High-Priority Surveillance Areas

AreaWhy PriorityExpected Surveillance
Biometric identificationFundamental rights impactHigh scrutiny
Employment AIWorker protection, discriminationActive surveillance
Credit and insuranceConsumer protectionSector-specific focus
Migration/asylumVulnerable groupsPolitical priority
Law enforcementCivil libertiesEnhanced oversight
Healthcare AIPatient safetyMDR coordination
Education AIChild protectionEmerging focus

Authority Surveillance Powers (Article 74)

Information and Access Powers

PowerScopeLegal Basis
Document requestsTechnical documentation, test reports, logsArticle 74(3)(a)
AI system accessOperating systems for testingArticle 74(3)(b)
Source code accessWhere necessary for assessmentArticle 74(3)(b)
Data accessTraining, validation, test dataArticle 74(3)(c)
Premises accessOffices, data centres, productionArticle 74(3)(e)
Personnel interviewsStaff, management, contractorsArticle 74(3)(f)

Investigation Powers

PowerApplicationConstraints
Unannounced inspectionsOn-site without prior noticeProportionality
Sample collectionAI systems or components for testingTesting purposes
Expert engagementTechnical specialists for assessmentComplex systems
Third-party informationSuppliers, customers, partnersValue chain tracing
Digital evidenceSystem logs, communicationsPrivacy limits

Testing and Evaluation

Test TypePurposeMethodology
Functional testingSystem performs as documentedUse case scenarios
Accuracy testingMeets stated performanceBenchmark datasets
Robustness testingHandles edge cases, adversarial inputsStress testing
Bias testingNon-discrimination verificationDemographic analysis
Safety testingRisk controls effectiveFailure mode analysis
Documentation auditRecords complete and accurateDocument review

Surveillance Process

Stage 1: Initiation

ActivityTimelineYour Response
Surveillance noticeDay 0Acknowledge, identify contact point
Scope clarificationDays 1-3Understand what's being examined
Initial document requestDays 3-7Begin gathering documentation
Inspection schedulingDays 7-14 (if inspection)Arrange logistics, personnel

Stage 2: Investigation

ActivityDescriptionYour Role
Document reviewAuthority reviews provided materialsRespond to follow-up requests
On-site inspectionPhysical visit to premisesFacilitate access, provide support
System testingEvaluation of AI system operationProvide test access, explain operation
Personnel interviewsQuestions to relevant staffMake personnel available, prepare them
Third-party contactAuthority contacts suppliers/customersBe aware, coordinate if needed

Stage 3: Preliminary Findings

Finding TypeAuthority ActionYour Response Options
No issuesClose investigationDocument for records
Minor issuesRequest clarificationProvide explanation
Concerns identifiedPreliminary finding letterRespond with evidence, remediation
Serious issuesFormal notice of non-complianceLegal review, response, corrective action

Stage 4: Outcome

OutcomeDescriptionTimeline
ClosureNo action, compliance confirmedVariable
RecommendationsNon-binding improvement suggestionsImplement voluntarily
Corrective measuresBinding order to address issuesSpecified deadline
Market withdrawalOrder to remove from marketImmediate to 30 days
Product recallRetrieve from deployers/usersSpecified deadline
Administrative fineFinancial penaltyAppeal period

Inspection Preparation

Documentation Readiness

Document CategoryItemsLocation
Technical documentationAnnex IV complete packageAccessible repository
Conformity recordsCE declaration, assessment reportsCompliance files
Testing evidenceValidation reports, benchmark resultsQuality records
Risk managementRisk assessment, mitigation evidenceRisk files
Post-market dataMonitoring reports, incident recordsOperations files
Training recordsStaff training, competency recordsHR files

Personnel Preparation

RolePreparationResponsibilities During Inspection
Inspection coordinatorSingle point of contactManage logistics, coordinate responses
Technical leadUnderstand AI system thoroughlyAnswer technical questions
Compliance officerKnow regulatory requirementsExplain compliance approach
Legal counselUnderstand legal frameworkReview responses, protect rights
Subject matter expertsDetailed knowledge of componentsProvide specialist information

Facility Preparation

AreaPreparation
Meeting roomPrivate space for discussions
System accessDemo environment, credentials ready
Document roomOrganised documentation for review
Secure areasProtocols for sensitive areas
IT supportAvailable for system access needs

Inspection Conduct

DoDon't
Be helpful and responsiveVolunteer excessive information
Answer questions accuratelySpeculate or guess
Provide requested documentsProvide unrequested documents
Take notes of proceedingsRecord without permission
Seek clarification if unclearMake assumptions about requests
Involve legal if neededMake legal admissions

Non-Compliance Responses

Corrective Measures (Article 79)

MeasureWhen AppliedResponse
WarningMinor issues, first instanceAddress and document
Compliance orderSpecific violations identifiedImplement corrections
Withdrawal orderSystem not safe for marketRemove from market
Recall orderDeployed systems pose riskRetrieve from deployers
ProhibitionFundamental non-complianceCease all market activity

Response Strategy

ScenarioRecommended Response
Factual disputeProvide evidence, request reconsideration
Technical disagreementExpert opinion, detailed explanation
Accept findingRemediation plan, timeline, evidence
Procedural challengeLegal review, formal objection if merited
AppealWithin statutory deadline, legal grounds

Appeal Rights

ElementTypical Provision
Right to appealGenerally available
Appeal deadline30-60 days (varies by Member State)
Appeal bodyAdministrative court or tribunal
Suspensive effectVaries—may or may not suspend order
Legal representationAdvisable for formal appeals

Cross-Border Surveillance (Article 75)

Mutual Assistance Mechanisms

MechanismPurposeProcess
Information requestsAuthority A requests info from Authority BFormal request, response obligation
Joint investigationsCoordinated multi-authority investigationAgreed protocol, shared findings
Enforcement requestsRequest action in another territoryWhere operator based elsewhere
Alert notificationsWarn other authorities of risksRapid information sharing

EU-Wide Safeguard Procedure (Article 77)

StageDescriptionTimeline
National actionMember State takes protective measureImmediate
Commission notificationAuthority informs CommissionWithout delay
Commission reviewAssess whether measure justified30 days
Union-wide decisionCommission may extend to all Member StatesFollowing review

Managing Cross-Border Exposure

StrategyImplementation
Consistent complianceSame standards across all markets
Centralised coordinationSingle team handles multi-jurisdiction
Lead authority identificationUnderstand which authority leads
Proactive communicationKeep all relevant authorities informed
Documentation alignmentSame documentation available everywhere

Surveillance Response Checklist

Immediate Response (Days 1-3)

  • Acknowledge surveillance notice
  • Identify internal response team
  • Brief legal counsel
  • Assess scope and urgency
  • Begin gathering requested documentation

Short-Term (Days 3-14)

  • Complete document gathering
  • Prepare inspection logistics
  • Brief personnel involved
  • Identify any gaps or concerns
  • Prepare explanatory materials

During Surveillance

  • Designate single coordinator
  • Track all requests and responses
  • Document all interactions
  • Escalate issues appropriately
  • Maintain constructive relationship

Post-Surveillance

  • Review findings thoroughly
  • Assess response options
  • Implement corrective measures
  • Document remediation
  • Update compliance programme

What You Learned

Key concepts from this chapter

**Market surveillance is ongoing**—initial conformity doesn't guarantee permanent compliance

Surveillance can be triggered by **multiple sources**—complaints, incidents, random sampling, cross-border alerts

Authorities have **extensive powers** including unannounced inspections, source code access, and system testing

**Preparation is essential**—maintain inspection-ready documentation and trained personnel

**Cooperation generally helps**—resistance tends to escalate, cooperation often leads to better outcomes

Chapter Complete

Governance & Penalties

5/8

chapters