DesignationISO/IEC/IEEE DIS 42703
Stage40.99, DIS approved for FDIS
Planning date, an estimate13 Sep 2027
Published source todayIEEE Std 7003-2024
9.3.2Clause
Evaluation

Ongoing evaluation: inputs

IEEE Std 7003-2024, Clause 9.3.2Carried into ISO/IEC/IEEE DIS 42703Retrieved 20 October 2026

The inputs are the requirements and design documentation, the stakeholder, data and risk sections of the profile, and the records of the design and output evaluation.

What clause 9.3.2 asks

The ongoing evaluation takes the documentation of the system requirements and design, the stakeholder identification, data representation and risk and impact assessment sections of the bias profile, and the records of the design and output evaluation. The records of the earlier evaluation are the baseline against which the ongoing results are read.

Why it matters

The baseline is what makes a drift finding meaningful. A metric that is 0.8 today says little without the value at the last evaluation and the reference value. The input list also keeps the ongoing work connected to the stakeholder set and the data map, which can change while the model stays the same. A monitoring team that receives only the production metrics is missing the context that tells it what a change means.

What good looks like

Assemble the ongoing input pack at the start of operations and refresh it at every evaluation. Keep the baseline results, the reference values and the interpretation rules. Confirm that the stakeholder and data versions are current. Record any change to the inputs as a trigger for a review, because a new stakeholder set can change what counts as drift.

Evidence an assessor asks for

The assessor will ask what the baseline was and when it was set. A monitoring result without a baseline is an observation, not a finding.

  • Baseline pack The last evaluation results, reference values and interpretation rules
  • Profile extracts The current stakeholder, data and risk sections
  • Requirements and design The current versions of both
  • Input change log Each change to an input and the review it triggered

Where it commonly fails

  • The baseline is the first production month, not an evaluation
  • The stakeholder and data versions are not refreshed
  • A change to the requirements does not trigger a review

What to do before publication

Set the baseline from the design and output evaluation, not from production.

Read across

← 9.3.1 Ongoing evaluation: purpose9.3.3 Ongoing evaluation: outputs →

Full register / The dates / Free scope check