Drift attestation — the quarterly signature

The short answer. A drift attestation is the recorded act of checking: on this date, this owner compared the model's current performance against its locked baseline and threshold, and signed the result. One attestation is a data point; a year of them is the monitoring history that separates organisations with a monitoring plan from organisations with a monitoring practice.

A monitoring plan says checks will happen. An attestation is proof one did: the metric value on the date, the baseline it was compared to, the verdict, and a name.

Its power is entirely in the date column. Plans can be written the week before a survey; a quarterly attestation history can only have been produced quarterly. That makes attestations the purest example of accumulating evidence — and the reason preparation guides say to start this clock before the standards manual even publishes.

In HAI-OS, the attestation is generated by the drift engine’s scheduled evaluation and lands on the hash-chained audit trail, so the history assembles itself and its integrity is verifiable inside the survey binder.

Where do you actually stand? The free RUAIH readiness score maps your organisation against the five focus areas in about eight minutes, and the published crosswalk shows how each control lands across RUAIH, CHAI and the NIST AI RMF.

Drift attestation — the quarterly signature

Keep reading