Assessment amendments and version history keep completed AI Impact Assessments current through new, reviewable versions instead of in-place edits, with every superseded version kept on the record.
An AI Impact Assessment describes a system at a point in time. Systems change: models are swapped, scope widens, regulations move, and incidents happen. When the assessment is a static document, teams face a bad choice. Edit it in place and lose the history, or leave it stale and let a signed approval drift away from the system actually running.
PulseAI now treats amendment as a first-class part of the assessment lifecycle. A completed assessment is never edited in place. Amending it opens a new version with the content carried forward, so teams update what changed instead of re-entering what did not.
Each amendment starts with a structured reason for change: an incident, a model change, a scope change, a regulatory change, a scheduled review, or a correction, alongside a written explanation.
Reasons that can invalidate the existing assessment (an incident, a model change, a scope change, or a regulatory change) force an explicit governance decision rather than letting it happen by default. Either the current version keeps governing while the amendment is under review, which requires a recorded acknowledgment of that choice, or governance is suspended until the new version is approved.
The evaluation is frozen when an assessment is submitted for review: the catalog versions used, the category ratings, the overall rating, and the framework compliance position. Approvers countersign exactly that frozen evaluation. It is never recomputed after the fact, so a later change to scoring thresholds cannot silently restate an assessment somebody already signed.
Before signing, an approver sees what moved since the previous version, with the changes that deserve a second look called out by name: an overall rating that decreased, a category rating that fell without any answer changing, mitigations that were removed, a dependency footprint that grew, a system purpose that changed.
Each use case now has a single authoritative record of which assessment version governs certification, and every attestation and certification check reads it. When governance is suspended pending re-assessment, that is reflected there too, so certification stops being enforced against a version nobody currently stands behind, while the version history stays intact.
Superseded versions are archived in full and stay visible in version history, labeled by what happened to them: superseded by an approved successor, or discarded before approval. The record is append-only.
At a glance
partnerships@pulseai.now