EVIDENCE-BASED GOVERNANCE

Evidence Library:

AI Governance in Practice

Completed implementation evidence and platform configurations: registers, assessments,
due diligence, dashboards and Microsoft 365 governance setups, ready to adapt.

01
Programme Evidence
AI Governance Project Implementation

A full 12-month AI governance implementation at a regulated financial organisation, from inventory to EU AI Act conformity, with objectives, timeline, artefacts and audit result.

Open evidence · 6 sections
02
Platform Demo
Microsoft 365 Evidence Vault

A SharePoint + Purview architecture that keeps every AI governance artefact versioned, retained for 10 years and retrievable within hours, including the evidence-drill protocol.

Open evidence · 5 sections
03
Register Evidence
AI Register (Filled Example)

A completed extract from an enterprise AI Register: classification, roles, owners and lifecycle for every system, plus the column standard that makes it audit-ready.

Open evidence · 3 sections
04
Assessment Evidence
Example FRIA (Art. 27)

A completed Fundamental Rights Impact Assessment for a high-risk recruitment screening system: rights risks, mitigations, human oversight and the signed deployment decision.

Open evidence · 6 sections
05
Third-Party Evidence
Vendor Due Diligence Report

A completed AI vendor due diligence for a recruitment-screening supplier: weighted scoring, evidence reviewed, contractual conditions and monitored risks.

Open evidence · 5 sections
06
Reporting Evidence
Board Dashboard (Quarterly)

A board-level quarterly dashboard: portfolio posture, KRIs against risk appetite, EU AI Act deadline tracking, operations metrics and decisions requested.

Open evidence · 5 sections
07
Platform Demo
Purview Configuration

A complete Purview setup protecting AI data and evidence: sensitivity labels, auto-labelling, DLP, 10-year retention, audit and eDiscovery, with PowerShell examples.

Open evidence · 5 sections
08
Workflow Evidence
Copilot Governance Workflow

The six-step approval and operating workflow for Microsoft 365 Copilot and custom agents: intake, classification, controls baseline, approval, monitoring and pilot results.

Open evidence · 5 sections
Evidence 01 · 6 sections
Programme Evidence

AI Governance Project Implementation

A full 12-month AI governance implementation at a regulated financial organisation, from inventory to EU AI Act conformity, with objectives, timeline, artefacts and audit result.

12-month programme47 AI systems9 high-risk to conformityFictional reference case
Section 01 / 06
Project summary

Full implementation of an enterprise AI governance programme at Vondel Finance Group (fictional reference organisation, 2,400 employees, NL/EU, regulated financial services). The programme ran for 12 months, covered the entire AI estate, and reached EU AI Act conformity for all high-risk systems ahead of the August 2026 deadline.

47
AI systems inventoried & classified
9
High-risk systems brought to conformity
0
Prohibited practices found at final screen
96%
Staff AI-literacy completion
12 mo
From kick-off to measured operation
Section 02 / 06
Scope & objectives
ObjectiveTargetResultStatus
Complete AI system inventory, incl. vendor-embedded AI100% of estate47 systems, 12 vendor-embeddedAchieved
AI Act classification with legal sign-offAll systems9 high-risk, 6 limited, 32 minimalAchieved
Prohibited-practice screening (Art. 5)Zero violations1 tool flagged & retired in week 3Achieved
Conformity for high-risk portfolioBefore 2 Aug 2026Completed May 2026Achieved
AI literacy (Art. 4) evidence trail≥ 90% completion96%, records in LMSAchieved
Board reporting rhythmQuarterly4 reports delivered, KPI dashboard liveAchieved
Section 03 / 06
Delivery timeline
Month 1
Mobilise
CAIO appointed, mandate signed; Governance Committee chartered; discovery sweep across procurement, CMDB, SSO and network logs produced inventory v1 (41 systems).
Months 2–3
Foundation
Prohibited-practice screen (one emotion-analytics recruitment add-on retired); AI Policy v1 published; intake gate embedded in procurement & SDLC; literacy layer 1 launched.
Months 4–6
Classification & control build
All 47 systems classified with legal sign-off; 9 high-risk systems gap-assessed against Art. 8–15; risk-management, data-governance and human-oversight controls built; 12 BU champions certified.
Months 7–9
Conformity & evidence
Technical documentation completed (Annex IV); declarations of conformity signed; CE marking & EU-database registration; FRIAs executed for 3 deployer use cases; vendor contracts remediated (top 15).
Months 10–12
Operate & measure
Monitoring dashboards live; incident runbook tested via tabletop; 24-hour evidence drill passed; independent third-line review; maturity re-scan: 1.8 → 3.4.
Section 04 / 06
Governance structure implemented

Bodies & decision rights

  • Board Audit & Risk Committee: risk appetite, quarterly oversight
  • AI Governance Committee (monthly): high-risk approvals, policy, exceptions
  • AI Review Board (weekly): operational assessments, classification challenges
  • 12 BU champions (hub-and-spoke): intake, classification, evidence

Policy architecture

  • 6 board-approved AI principles
  • AI Policy v2 (14 pages, annual review)
  • 6 standards: data, documentation, oversight, vendor, security, literacy
  • 19 procedures & templates in workflow tooling
Section 05 / 06
Evidence artefacts produced
ArtefactCountLocation
Classification records with legal sign-off47GRC platform, AI register module
High-risk assessment reports (2nd-line challenged)9GRC platform + Evidence Vault
Annex IV technical documentation sets9Evidence Vault, per-system folders
Declarations of conformity + CE registrations9Evidence Vault + EU database
FRIA reports (integrated with DPIA)3Evidence Vault, FRIA folder
Committee & review-board minutes31Evidence Vault, governance meetings
Training completion records2,304LMS, quarterly export to Vault
Vendor due-diligence files15Evidence Vault, vendor register
Audit result

Independent third-line review (month 12): no critical findings, 4 improvement recommendations (monitoring thresholds, champion refresh cycle, vendor concentration analysis, tabletop frequency). Supervisory-grade evidence pack for any system reproducible within 24 hours, verified by drill.

Section 06 / 06
Lessons learned
  • Start with the inventory, not the policy. The discovery sweep found 6 unregistered systems, including 3 vendor-embedded; classification followed immediately.
  • SLAs kept governance credible. Minimal-risk clearance in <1 day; high-risk end-to-end in 22 working days against a 25-day SLA. No shadow-AI growth after month 4.
  • Champions made it scale. 12 certified champions absorbed 70% of intake work; the hub focused on the 9 high-risk systems.
  • Evidence drills expose the gaps. The first 24-hour drill failed on training records (LMS export missing); fixed before the real test.
Fictional but representative reference implementation. Figures, organisation and dates are illustrative; structure, artefacts and sequence reflect real EU AI Act programme practice.
Evidence 02 · 5 sections
Platform Demo

Microsoft 365 Evidence Vault

A SharePoint + Purview architecture that keeps every AI governance artefact versioned, retained for 10 years and retrievable within hours, including the evidence-drill protocol.

SharePoint OnlinePurview retentionSensitivity labels24-hour evidence drill
Section 01 / 05
What the Evidence Vault is

A dedicated Microsoft 365 SharePoint architecture that stores every AI governance artefact with immutable versioning, retention labels and audit trails, so that any supervisory request ("show me the file for system X") is answered in hours, not weeks. Built on standard M365: SharePoint Online, Purview retention, sensitivity labels and audit (Standard/Premium).

Section 02 / 05
Site &amp; library structure
 SharePoint · Executive Shield - AI Evidence Vault
Library / folderContentRetentionAccess
01_AI-RegisterMaster AI inventory, classification records10 yearsGovernance office (edit), Audit (read)
02_ClassificationsSigned classification records per system10 yearsHub + Legal (edit), Champions (read)
03_Technical-DocumentationAnnex IV sets, model cards, datasheets10 yearsHub + first line (edit)
04_Assessments-FRIA-DPIARisk assessments, FRIA, DPIA, validation reports10 years2nd line (edit), Audit (read)
05_Conformity-CEDeclarations of conformity, CE evidence, EU-db exports10 yearsCompliance (edit), all governance (read)
06_Governance-MeetingsCommittee & review-board minutes, decisions, dissent10 yearsCommittee members (edit)
07_Vendor-Due-DiligenceVDD reports, contract clauses, GPAI evidenceContract + 10 yrsProcurement + Legal (edit)
08_IncidentsIncident reports, regulator notifications, post-mortems10 yearsHub + CISO (edit)
09_Training-LiteracyArt. 4 curricula, completion exports, certifications5 yearsHR/L&D (edit), Hub (read)
10_Board-ReportingQuarterly board packs, KPI dashboards, annual reviews10 yearsCAIO (edit), Board portal (link)
Section 03 / 05
Metadata &amp; content types

Every artefact carries managed metadata, enabling per-system evidence retrieval in seconds:

ColumnTypeExample
AI-System-IDManaged metadata (term set)AI-014 CV Screening Assist
Artefact-TypeChoiceClassification / AnnexIV / FRIA / DoC / Minutes / VDD / Incident
Risk-TierChoiceProhibited-screen / High / Limited / Minimal
Lifecycle-StageChoiceIntake / Approved / Live / Monitoring / Retired
Owner-RolePersonBusiness owner of record
Review-DateDate + flow reminderAnnual re-classification trigger
Section 04 / 05
Purview retention &amp; immutability
# Retention label applied to libraries 01–08 (PowerShell, Purview)
New-RetentionCompliancePolicy -Name "AI-Governance-10Y" `
  -SharePointLocation "https://esp.sharepoint.com/sites/AI-Evidence-Vault" `
  -Enabled $true

New-RetentionComplianceRule -Policy "AI-Governance-10Y" `
  -RetentionDuration 3650 `                      # 10 years, Art. 18 / Annex IV alignment
  -RetentionComplianceAction Keep `
  -ExpirationDateOption ModificationAgeInDays

# Sensitivity label: Highly Confidential, no external sharing, audit on
Set-LabelPolicy -Identity "AI-Vault-HighlyConfidential" `
  -Settings @{BlockSend=$true; AuditEnabled=$true}
Section 05 / 05
Evidence drill: the 24-hour test

Quarterly drill: pick one random system, produce the full supervisory file. Measured result (Q2):

3h 40m
Time to complete evidence pack
14/14
Required artefact types found
1
Missing item in first drill (training export)
0
Missing items in latest drill
Why it matters

Market surveillance authorities may request technical documentation, logs and assessment records on short notice. A working vault converts that request from a crisis into an export. The audit trail in Purview also proves who touched which artefact when, protecting integrity.

Demo configuration. Site names, policies and timings are illustrative; implement retention and access design with your M365/compliance administrators.
Evidence 03 · 3 sections
Register Evidence

AI Register (Filled Example)

A completed extract from an enterprise AI Register: classification, roles, owners and lifecycle for every system, plus the column standard that makes it audit-ready.

47 systems9 high-risk1 prohibited retired24-column standard
Section 01 / 03
Register extract

Extract from the enterprise AI Register (master inventory). Every row is a governed system with its classification, role, owner and lifecycle status. This register is the single source of truth referenced by intake, assessments, monitoring and board reporting.

IDSystem & purposeProvider / buildRoleRisk tierLifecycleOwnerNext review
AI-003Fraud Signal Detection; transaction anomaly scoringInternal build (ML platform)ProviderMinimalLiveHead of PaymentsMar 2027
AI-007Customer Service Copilot; agent-assist drafting in contact centreVendor SaaS (GPAI-based)DeployerLimitedLiveDir. Customer OpsSep 2026
AI-014CV Screening Assist; candidate ranking for recruitmentVendor SaaSDeployerHighLive · conformCHROMay 2027
AI-019Credit Decisioning Support; affordability & risk scoringInternal build + vendor modelProviderHighLive · conformCRO RetailMay 2027
AI-022Workplace Analytics; meeting & focus-time patternsM365 integrated vendorDeployerLimitedLiveCHRODec 2026
AI-025Marketing Content Generator; campaign copy draftsGPAI API (enterprise)DeployerLimitedLiveCMONov 2026
AI-031KYC Document Check; identity document authenticityVendor SaaSDeployerHighLive · conformHead of ComplianceJun 2027
AI-036Attrition Prediction; flight-risk scoring of employeesHR-suite embeddedDeployerHighRemediatingCHROAug 2026
AI-040Emotion Insights add-on; interview sentiment analysisVendor add-onDeployerProhibited (Art. 5)Retired W3n/aClosed
AI-044Energy Optimisation; HVAC setpoint learning in officesInternal buildProviderMinimalLiveFacilities Dir.Jan 2027

Register extract: 10 of 47 rows shown. Fields abbreviated; production register carries 24 columns incl. data categories, affected persons, oversight owner, model version, and links to all evidence artefacts.

Section 02 / 03
Portfolio summary
47
Systems in register
9
High-risk (8 conform, 1 remediating)
6
Limited-risk (transparency)
32
Minimal-risk
1
Prohibited practice retired
Section 03 / 03
Register column standard

Identity & classification

  • ID, name, purpose, affected persons
  • Risk tier + classification rationale + legal sign-off
  • Provider / deployer / importer role determination
  • Annex III domain (where applicable)

Operation & evidence

  • Business owner, oversight owner, monitoring owner
  • Lifecycle stage + change history + re-trigger flags
  • Links: classification record, assessments, Annex IV, DoC, FRIA
  • Vendor + contract reference, next review date
Supervisory answer

"Which AI systems do you operate and how are they classified?" is answered by this register in one export. Every classification links to its signed rationale; every high-risk row links to its conformity evidence in the Vault.

Fictional register extract. System names, counts and dates are illustrative; the column standard and tier logic follow EU AI Act classification practice.
Evidence 04 · 6 sections
Assessment Evidence

Example FRIA (Art. 27)

A completed Fundamental Rights Impact Assessment for a high-risk recruitment screening system: rights risks, mitigations, human oversight and the signed deployment decision.

AI Act Art. 27Annex III employmentIntegrated with DPIAApproved with conditions
Section 01 / 06
Assessment header
FieldValue
SystemAI-014 · CV Screening Assist (vendor SaaS, candidate ranking for vacancies)
DeployerVondel Finance Group · Human Resources
Legal basisEU AI Act Art. 27 (deployer FRIA duty: Annex III employment use case); complements DPIA-2025-041 (GDPR Art. 35)
AssessorsAI Compliance Mgr (lead), DPO, HR Director, Worker Council observer
Date / version14 May 2026 · v1.0 · approved by AI Governance Committee 21 May 2026
Review cycleAnnual, or upon substantial modification / vendor model change
Section 02 / 06
Deployment context &amp; affected persons

The system ranks external job applicants for corporate vacancies (approx. 6,500 applications/year) based on CV-text similarity to role criteria, producing a ranked shortlist for recruiter review. No automated rejection: all decisions are taken by human recruiters; the ranking is advisory input. Affected persons are job applicants (external natural persons), including potentially vulnerable groups (career starters, career switchers, international applicants with non-NL CV conventions).

Section 03 / 06
Fundamental-rights risk assessment
RiskRights potentially affected (EU Charter)LikelihoodImpactMitigations in placeResidual
Discriminatory ranking (gender, age, ethnicity, origin)Art. 21 non-discrimination; Art. 23 equalityMediumHighBias testing per cohort on protected-attribute proxies; vendor fairness reports reviewed quarterly; threshold alerts; annual independent auditMedium-Low
Opacity of ranking rationale to candidatesArt. 41/47 good administration & remedyMediumMediumCandidate notice at application (Art. 26(7) style disclosure); explanation of system's role on request; human review of any contested outcomeLow
Automation bias by recruiters (over-reliance on rank)Art. 21; human dignity Art. 1MediumMediumRecruiter training on advisory nature; ranking hidden until own shortlist drafted (blind-first workflow); override logging & reviewLow
Privacy intrusion via CV enrichment/scrapingArt. 7–8 privacy & data protectionLowHighContractual ban on enrichment/social-media scraping; DPIA data-minimisation; vendor data-flow audit rights exercisedLow
Non-NL CV format disadvantageArt. 21 non-discriminationMediumMediumRepresentativeness test incl. international CV samples; ranking calibration checked across CV-format groupsLow-Medium
Section 04 / 06
Human oversight measures (Art. 14 / 26)
  • Oversight owner: Head of Talent Acquisition (named, certified); deputy: HR Ops Lead.
  • Intervention rights: recruiters may re-rank, discard or override any suggestion; overrides logged with reason codes and reviewed monthly.
  • Competence: all 14 recruiters completed practitioner training incl. bias awareness; refresh annually.
  • Monitoring: override rate, cohort fairness metrics, and rank-outcome correlation reviewed monthly by HR + quarterly by 2nd line.
Section 05 / 06
Incident &amp; materialisation plan
  • Fairness alert > threshold → system throttled to "advisory-hidden" mode within 24h; hiring continues manually.
  • Suspected discriminatory impact → incident runbook AI-IR-01; DPO + Compliance notified same day; candidate remediation path (re-review by independent recruiter).
  • Serious incident determination → provider notification and regulatory reporting clocks as per AI Act Art. 73 (2/10/15 days).
Section 06 / 06
Conclusion &amp; sign-off
DecisionCondition
Deployment approvedAdvisory-only mode; blind-first recruiter workflow; quarterly fairness reporting to Governance Committee; FRIA review May 2027 or upon vendor model change

Signed: AI Compliance Manager · DPO · CHRO, countersigned by CAIO, 21 May 2026. Evidence filed: Vault / 04_Assessments-FRIA-DPIA / AI-014-FRIA-v1.0.

Fictional example FRIA, condensed for readability. Production FRIAs include methodology annexes, dataset descriptions, vendor evidence references and works-council consultation records.
Evidence 05 · 5 sections
Third-Party Evidence

Vendor Due Diligence Report

A completed AI vendor due diligence for a recruitment-screening supplier: weighted scoring, evidence reviewed, contractual conditions and monitored risks.

6 domainsWeighted score 3.8/56 contract conditionsApproved with conditions
Section 01 / 05
Engagement summary
FieldValue
VendorNimbus Talent AI B.V. (fictional) · supplier of "AI-014 CV Screening Assist"
Assessment typeInitial AI Vendor Due Diligence (pre-contract) + annual re-assessment
ScopeAI Act conformity, GPAI dependencies, data protection, security, financial/operational resilience, exit
Assessed byProcurement (lead), AI Compliance, Legal, DPO, CISO office
ResultApproved with conditions · 6 conditions, 2 monitored risks
Section 02 / 05
Scoring overview
DomainWeightScore (1–5)Finding
AI Act conformity readiness25%4.0Strong Annex IV docs provided; DoC for v3.2 signed; EU-db registration verified
GPAI & third-party model chain15%3.0Monitor built on external GPAI; training-data summary received; change-notification clause required
Data protection (GDPR)20%4.5Strong EU processing only; no enrichment/scraping; DPA audited; deletion API tested
Security & resilience15%4.0Strong ISO 27001 certified; pen-test summary 2026; incident SLA 24h agreed
Fairness & model governance15%3.5Monitor quarterly fairness reports promised; first independent audit pending
Financial & operational health5%4.0Strong 8 yrs operating, profitable FY25, 60+ enterprise clients
Exit & continuity5%2.5Gap no escrow initially; data-export format proprietary; remediation agreed

Weighted result: 3.8 / 5 · approve with conditions

Section 03 / 05
Key evidence reviewed
  • Annex IV technical documentation package for CV Screening Assist v3.2, incl. data-governance and human-oversight sections
  • EU declaration of conformity + EU-database registration extract
  • GPAI provider documentation and training-data summary (per AI Act Art. 53)
  • DPA + subprocessor list (all EU); ISO 27001 certificate; penetration-test executive summary
  • Quarterly fairness report sample (cohort bias metrics); model-change release notes history
  • Financial statements FY2024–FY2025; reference calls with 2 existing clients
Section 04 / 05
Conditions imposed (contractual)
  1. Substantial-modification notification ≥ 30 days before deployment of model changes, with regression evidence;
  2. Serious-incident reporting to deployer within 24 hours, aligned with Art. 73 clocks;
  3. Quarterly fairness reports + annual independent bias audit shared in full;
  4. No CV enrichment or external data scraping; audit right exercised annually;
  5. Source-code/model escrow + standardised data export (CSV/JSON) within 30 days of exit;
  6. EU data residency maintained; new subprocessors require prior written consent.
Section 05 / 05
Monitored risks &amp; review
RiskMonitorTriggerOwner
GPAI upstream model change alters ranking behaviourChange-notice log + quarterly regression testAny un-notified behaviour changeAI Compliance
Vendor concentration: 3 HR systems on same GPAI backendAnnual concentration analysis> 3 critical processes on one backendCAIO office

Next full re-assessment: April 2027, or upon any major model version, ownership change, or serious incident.

Fictional VDD report, condensed. Production reports append the questionnaire (86 items), evidence index and contract clause mapping.
Evidence 06 · 5 sections
Reporting Evidence

Board Dashboard (Quarterly)

A board-level quarterly dashboard: portfolio posture, KRIs against risk appetite, EU AI Act deadline tracking, operations metrics and decisions requested.

Q2 20265 KRIs vs appetiteAug 2026 on track3 board decisions
Section 01 / 05
Quarter summary

Board Audit & Risk Committee · AI governance report Q2 2026. Traffic-light view across portfolio, risk, compliance and operations.

47
AI systems in register
+3 vs Q1
9
High-risk systems
8 conform · 1 remediating
2
AI incidents (0 serious)
−1 vs Q1
96%
AI-literacy completion
+4pt
100%
Systems with named owner
target met
Section 02 / 05
Risk posture vs appetite
KRIAppetiteActualStatus
Serious AI incidents (Art. 73 reportable)00Within
High-risk systems without current conformity0 after Aug 20261 (AI-036, remediation on plan)Watch
Unregistered AI discovered in shadow scans≤ 1/quarter1 (marketing GenAI tool, since registered)Within
Override monitoring: high-risk systems with zero logged human interventions01 (coaching action taken)Watch
Critical processes concentrated on single GPAI backend≤ 33At limit
Section 03 / 05
Compliance programme vs EU AI Act deadlines
MilestoneDeadlineProgressStatus
Prohibited-practice screen & AI literacy (Art. 4–5)Feb 2025
Done
GPAI vendor evidence in contractsAug 2025
Done
High-risk conformity (Annex III portfolio)Aug 2026
On track
Transparency measures (limited-risk tier)Aug 2026
Done
Regulatory sandbox participation (innovation)optional
Exploring
Section 04 / 05
Governance operations

Throughput Q2

  • Intakes processed: 14 (12 minimal, 2 high-risk)
  • Median decision time: minimal <1 day · high-risk 19 days (SLA 25)
  • Approvals with conditions: 2 · rejections: 1 (facial-emotion feature)
  • Evidence drill: passed, 3h 40m, 0 missing artefacts

Incidents & lessons

  • INC-2026-011: drift alert on credit model; retrained, root cause: input schema change
  • INC-2026-014: chatbot disclosed incorrect fee text; guardrail + knowledge-source fix
  • Lessons fed into release-gate checklist v3 and vendor change-notice SLA
Section 05 / 05
Decisions requested from the board
  1. Approve updated AI risk appetite (concentration threshold lowered from 4 to 3 critical processes per GPAI backend);
  2. Approve budget for independent fairness audits of 2 high-risk systems (annual);
  3. Note the AI-036 remediation plan and the August 2026 conformity trajectory.
Fictional board dashboard. Structure mirrors the quarterly pack: posture, risk vs appetite, compliance trajectory, operations, decisions requested.
Evidence 07 · 5 sections
Platform Demo

Purview Configuration

A complete Purview setup protecting AI data and evidence: sensitivity labels, auto-labelling, DLP, 10-year retention, audit and eDiscovery, with PowerShell examples.

4 sensitivity labelsDLP egress block10-year retentionAudit + eDiscovery
Section 01 / 05
Objective

Microsoft Purview configuration that protects data used by AI systems and AI governance evidence: discover sensitive data, apply sensitivity labels automatically, enforce retention on governance artefacts, and keep a defensible audit trail. Mapped to EU AI Act Art. 10 (data governance) and GDPR.

Section 02 / 05
Configuration overview
Purview capabilityConfigurationAI governance purposeStatus
Information Protection (sensitivity labels)4 labels: Public / Internal / Confidential / Highly Confidential-AITraining data & governance artefacts classified; encryption + no-external-share on HC-AIActive
Auto-labelling policiesSIT-based: IBAN, BSN, passport, salary, health termsPrevents unlabelled sensitive data entering AI pipelinesActive
Data Loss PreventionPolicies on SharePoint, OneDrive, Exchange, Teams + endpointBlocks sensitive datasets leaving approved AI workspacesActive
Retention labels & policiesAI-Governance-10Y on Vault; 5Y on training exportsArt. 18 / Annex IV record-keeping dutiesActive
Audit (Standard + Premium)Unified audit log, 1-yr retention (Premium: 10-yr add-on)Who accessed/changed which artefact, whenActive
eDiscovery (Standard)Case templates for supervisory requests24-hour evidence-pack assemblyActive
Insider Risk ManagementPolicy: mass-export from AI Vault & model reposDetects evidence tampering / IP exfiltrationPilot
Data Map & CatalogAI datasets registered as assets w/ lineageProvenance documentation (Art. 10)In progress
Section 03 / 05
Sensitivity label taxonomy
LabelProtectionApplied to
PublicNonePublished policies, approved marketing outputs
InternalWatermark, no auto-forward externalWorking documents, committee drafts
ConfidentialEncryption, internal groups onlyAssessments, validation reports, VDD files
Highly Confidential - AIEncryption, named roles, no download on unmanaged devices, usage auditedTraining datasets with personal data, Annex IV sets, incident files
Section 04 / 05
Auto-labelling &amp; DLP policy (PowerShell)
# Auto-apply "Highly Confidential - AI" on sensitive info types in AI workspaces
New-AutoSensitivityLabelPolicy -Name "AI-HC-AutoLabel" `
  -ApplySensitivityLabel "Highly Confidential - AI" `
  -SharePointLocation "https://esp.sharepoint.com/sites/AI-Evidence-Vault", `
                      "https://esp.sharepoint.com/sites/AI-TrainingData" `
  -Mode Enable

# DLP: block egress of labelled training data outside approved locations
New-DlpCompliancePolicy -Name "AI-Data-Egress-Block" `
  -SharePointLocation All -OneDriveLocation All -ExchangeLocation All -TeamsLocation All

New-DlpComplianceRule -Name "Block HC-AI external" -Policy "AI-Data-Egress-Block" `
  -ContentContainsSensitiveInformation @{Name="Highly Confidential - AI"} `
  -BlockAccess $true -NotifyUser $true `
  -GenerateAlert @("AICompliance@esp.example","DPO@esp.example")
Section 05 / 05
Audit &amp; evidence queries
# Who accessed Annex IV documentation for AI-014 in the last 90 days?
Search-UnifiedAuditLog -StartDate (Get-Date).AddDays(-90) -EndDate (Get-Date) `
  -Operations FileAccessed,FileModified,FileDownloaded `
  -ObjectIds "*AI-Evidence-Vault/03_Technical-Documentation/AI-014*"

# eDiscovery case: supervisory request, full file for AI-014
New-ComplianceCase -Name "MSA-Request-AI-014" -CaseType eDiscovery
New-ComplianceSearch -Name "AI-014-FullFile" -Case "MSA-Request-AI-014" `
  -SharePointLocation "https://esp.sharepoint.com/sites/AI-Evidence-Vault" `
  -ContentMatchQuery "AI-System-ID:'AI-014'"
Result

Sensitive AI data is discoverable and labelled automatically; governance evidence is retained 10 years with immutability; every access is audited; a supervisory evidence pack is a search-and-export, not a fire drill.

Demo configuration. Cmdlets are illustrative for design review; validate in a test tenant and align retention/legal-hold settings with counsel before production rollout.
Evidence 08 · 5 sections
Workflow Evidence

Copilot Governance Workflow

The six-step approval and operating workflow for Microsoft 365 Copilot and custom agents: intake, classification, controls baseline, approval, monitoring and pilot results.

6-step workflow8-control baselinePilot: 60 users0 exposure incidents
Section 01 / 05
What this workflow governs

The end-to-end approval and operating workflow for Microsoft 365 Copilot and custom Copilot agents across the organisation: who may request one, how it is classified and approved, which controls are switched on, and how usage is monitored. Copilot deployments are registered as AI systems in the AI Register (role: deployer) with transparency measures and workspace-level data controls.

Section 02 / 05
The workflow at a glance
STEP 1
Request
Business unit submits Copilot/agent request via intake form: purpose, users, data sources, expected benefit
STEP 2
Classify
Champion runs classification tree: prohibited screen, tier, role (deployer), GDPR/DPIA trigger
STEP 3
Review
2nd line: data-access scope (semantic index), sensitivity-label coverage, DPIA where personal data
STEP 4
Approve
Decision per rights matrix: minimal auto, limited champion, high-risk Review Board
STEP 5
Configure
Tenant controls applied (see §3), pilot group enabled, training delivered
STEP 6
Monitor
Usage, oversharing findings, incident signals; quarterly review; decommission path
Section 03 / 05
Control baseline per approval
ControlSettingWhy
License & access scopeAssigned per approved group only; no tenant-wide defaultProportionality; cost + risk containment
Data access boundaryCopilot honours M365 permissions; oversharing remediated first (Purview DSPM report)Prevents permission-inherited data exposure
Sensitivity labelsAuto-labelling live before enablement; labelled content excluded where requiredArt. 10 data governance; GDPR minimisation
Commercial data protectionEnterprise data protection confirmed; no prompts/responses used for trainingConfidentiality; vendor terms check
Web-groundingOff for Confidential workspaces; on for approved research groupsSource-control of outputs
Agent publishingCustom agents (Copilot Studio) pass same intake; no public-channel agents without Review BoardShadow-agent prevention
Transparency to usersAcceptable-use notice + "AI output must be verified" banner in onboardingArt. 50-style transparency; calibrated trust
Logging & auditAudit (Premium) on; interactions auditable; eDiscovery scope includes Copilot dataEvidence; incident investigation
Section 04 / 05
Example: approved deployment record
FieldValue
Register IDAI-052 · M365 Copilot for Legal & Compliance (pilot, 60 users)
ClassificationLimited risk · deployer · transparency measures mandatory
DecisionApproved with conditions · Champion + 2nd line · 9 June 2026
ConditionsOversharing remediation completed pre-pilot (412 overshared items fixed); web-grounding off; DPIA-2026-018 filed; user onboarding incl. verification duty
MonitoringMonthly usage + oversharing re-scan; quarterly champion review; first 90-day evaluation gate
Section 05 / 05
Operating metrics (first quarter of pilot)
60/60
Users onboarded & trained
412
Overshared items fixed before go-live
0
Data-exposure incidents
87%
Outputs verified per user survey
4.1h
Est. weekly time saved per user
Design principle

Copilot governance is data governance first: the model respects existing permissions, so the workflow front-loads permission and labelling hygiene. Approve the data estate, then enable the assistant.

Fictional workflow and pilot figures. Control names reference standard Microsoft 365 / Purview capabilities; adapt the baseline to your tenant and licensing.