Management Review

Purpose

This procedure sets out the management review of Rygen Technologies’ AI Management System (AIMS), held every four months under ISO/IEC 42001:2023 Clause 9.3.

Scope

This procedure applies to top management’s review of the performance, suitability, adequacy and effectiveness of the AIMS.

Management Review Framework

The review keeps the AIMS aligned with business objectives, addresses emerging risks, and improves the AIMS based on performance data and stakeholder feedback.

AIMS Strategic Themes

Strategic Themes are priorities set by top management that shape AIMS direction but are not formal objectives under ISO 42001 Clause 6.2. A theme is used when a priority needs standing executive attention but cannot yet be measured with KPIs and targets.

A Strategic Theme has a directional statement, a designated owner, and a report-out at every management review.

Themes have no numerical KPI targets. They are reported narratively under the Clause 9.3.2 inputs on changes in internal and external issues and on opportunities for continual improvement. When measurement becomes possible, top management may promote a theme to a formal AIMS objective at an annual objectives review.

A theme is recorded in the minutes of the management review that adopted it. Each later management review report gives its status under the standing input below.

Review Schedule

Management reviews are held every four months, in January, May and September. Attendees:

RoleRequired
CEOYes
CTOYes
Principal AI EngineerYes
Other executivesOptional

Review Process

Preparation (1 week prior)

The Principal AI Engineer prepares:

  • the Management Review Report
  • AIMS objectives performance data
  • risk register updates
  • incident reports and corrective actions
  • a service provider SLA and availability performance summary

Review Meeting Agenda

TopicDurationPurpose
Meeting Overview10 minPurpose and expected outcomes
Status of Previous Actions15 minAction items from the last review
AIMS Implementation Progress20 minImplementation status and certification progress
Context Changes15 minExternal and internal changes affecting the AIMS, and interested party updates
Strategic Themes5 minStatus of active Strategic Themes
AIMS Performance30 minObjectives performance, incidents and corrective actions, and audit results
Opportunities for Improvement15 minStrategic opportunities and process improvements
Decisions and Actions15 minResource decisions, AIMS changes, and next steps

Required Inputs (per ISO 42001 9.3.2)

Each management review shall consider every input below. Where an input has nothing new, the report says so.

Standing items, at every review:

  • status of actions from previous management reviews
  • changes in external and internal issues relevant to the AIMS, including whether climate change is a relevant issue (ISO/IEC 42001:2023/Amd 1:2024)
  • changes in the needs and expectations of interested parties
  • status of AIMS Strategic Themes
  • opportunities for continual improvement
  • a review of the AI policy (AI-001), with its result recorded in the Management Review Report
  • the risk register review (AI-008, Monitoring & Review phase)

Performance information:

  • trends in nonconformities and corrective actions
  • trends in monitoring and measurement results
  • audit findings and observations
  • AI system performance against objectives
  • AI incidents in the period (AI-023, Metrics and Monitoring)
  • monitoring-plan results for each system (AI-017, Integration with Management Review)
  • training effectiveness and further training needs (AI-021)

Periodic items:

  • a SWOT analysis, refreshed every four months in line with the strategic planning cycle
  • confirmation that each impact assessment is current, as often as AI-009 (Assessment Triggers) requires

Required Outputs (per ISO 42001 9.3.3)

Each management review shall record decisions and actions on:

  • continual improvement opportunities and their priority
  • changes to the AIMS, including policy and objective updates, process changes, and risk treatment adjustments
  • resource needs, including personnel, tools, training and budget
  • actions to address identified gaps or weaknesses
  • updates to AI system development or operational practices

Documentation

Meeting Records

The Principal AI Engineer keeps the minutes with the decisions made, the action items with owners, and the attendance record.

Follow-up

  • Distribute the minutes within 3 business days.
  • Update AIMS documents as decided.

Storage

Meeting records are kept in content/meetings/ in the aims-governance repository, one directory per review, and kept permanently (AI-017). The AI Governance team and executives have access.

Emergency Reviews

The CEO, CTO or Principal AI Engineer may call an ad hoc review for a critical incident, a major regulatory change, or a significant business change affecting AI.

Revision History

VersionDateAuthorSummary of Change
1.02025-06-05Field BradleyInitial draft.
1.12025-09-02Field BradleyMigrated to markdown and gitlab
1.22026-01-07Field BradleyAdded external provider performance summary to preparation checklist (NCR-006, CAR-005)
1.32026-01-13Field BradleyEnhanced inputs/outputs per ISO 42001 9.3.2/9.3.3; added trends analysis, SWOT, coverage flexibility (AI-1195)
1.42026-01-16Field BradleyAdded climate change to standing items per ISO/IAF MD 26:2024 (AI-1230)
1.52026-05-06Field BradleyAdded AIMS Strategic Themes concept and standing review item (AI-1495)
1.62026-07-14Field BradleyChanged management review cadence from quarterly to every four months (January / May / September); aligned dependent review cadences (AI-1759)
1.72026-09-15Field BradleyCorrected the meeting-record storage location from Confluence to the aims-governance repository, which is where the records are held (AI-1976)
1.82026-11-04Field BradleyAction items are tracked in Jira; monthly status reports are not done (AI-2173)
1.92026-11-09Field BradleyCut repeated text and lists every input Clause 9.3.2 and the AIMS procedures send to each review, citing their rules instead of repeating them (AI-2173, AI-2131). Removes the standing SoA-exclusions input and the universal action-deadline and Jira-only tracking requirements.
1.102026-11-10Field BradleyRemoved the impact disposition verification input, which AI-009 no longer sets (AI-1976).