Skip to content

Reviews & Statuses ​

What this is ​

A status shows the condition of a work item. Logs, comments, and Reviews make each status change auditable.

In Modulos, each object type has its own statuses and gets its final status differently:

ObjectStatusesHow the status changes
ControlNot Executed, Executed, Out of Scope, ArchivedThe Control Owner or the owner of a mapped Requirement sets Not Executed, Executed, or Out of Scope directly. Modulos sets Archived after a framework update, Out of Scope from the EU AI Act scoping, and Not Executed after a failed test or an archived Policy. Modulos logs each change. A comment is necessary in one condition only.
RequirementNot Fulfilled, Fulfilled, Out of Scope, ArchivedWhen all mapped Controls have a final status, the Requirement is ready for review. The Requirement Owner then marks it Fulfilled.
AssetIn Progress, In Review, CompletedA status change goes through a Review request, and a selected reviewer (an AI System Owner) selects Approve or Reject.

For the full model, see Governance Operating Model. For the log entries and the notifications that each change makes, see Audit Trail.

Who can do what ​

  • Controls: only the Control Owner or the owner of a mapped Requirement can change the status, whatever their organization role. Other users see the selector or the text, but Modulos rejects their change. For the table, see Controls.
  • Requirements: only the Requirement Owner can change the status.
  • Assets: the selected reviewers, who are AI System Owners, approve or reject a Review request.

How it works ​

Controls ​

A Control has one of four statuses: Not Executed, Executed, Out of Scope, or Archived. Executed, Out of Scope, and Archived are final statuses.

You set the status in the Status field of the Control. The field is a selector for users who can edit Controls. These users are AI System Owners, Editors, and users with access to all AI Systems. Other users see the status as text. The selector has Not Executed, Executed, and Out of Scope. You cannot select Archived.

Modulos saves a status change only from the Control Owner or from the owner of a mapped Requirement. It rejects a change from other users. There is no reviewer approval for Controls. A change applies as follows:

  • Out of Scope: the dialog Mark this control as Out of Scope opens. Select Confirm to apply the change.
  • Executed to Not Executed, while a mapped Requirement is Not Fulfilled and ready for review: the dialog Change Control status to "Not Executed" opens. You must type why you make the change before you can select Confirm. This text becomes a comment on the Control.
  • Executed to Not Executed, in all other conditions where a mapped Requirement is ready for review: Modulos rejects the change with an error. In these conditions, the Requirement that is ready for review is Out of Scope or Archived, and the dialog does not open.
  • All other changes apply immediately.
A Control with the dialog Change Control status to Not Executed open, an empty text box for the reason, and Cancel and Confirm buttons.

When an Executed Control goes back to Not Executed while a mapped Requirement is Not Fulfilled and ready for review, you must type why.

  1. Change Control status to "Not Executed" The dialog opens only when a mapped Requirement is Not Fulfilled and ready for review.
  2. Please provide a reason Type the reason. It becomes a comment on the Control.
  3. Confirm Available after you type the reason.

Modulos records each status change in the Comments and Logs of the Control: who changed the status, when, and from which status to which status. Modulos also sends a Status changed notification.

While a Control has a final status, its content is locked. You cannot edit the report or attach Evidence, and the Owner field is locked. You can remove Evidence from an Out of Scope or Archived Control, but not from an Executed Control. The owner of a mapped Requirement can select a different Control Owner in the Mapped Controls of the Requirement. The Status field stays available.

A Control that is mapped to a Fulfilled Requirement cannot change its status. Modulos shows the error "Cannot update controls of the fulfilled requirement" and the name of the Requirement. To change the Control, the Requirement Owner first sets the Requirement to Not Fulfilled.

Modulos also sets an Executed Control to Not Executed automatically in these conditions:

  • a mapped Metric Test fails or has an error
  • a mapped Agent Test fails
  • a user archives a Policy that is linked to the Control

An Agent Test error does not change the Control.

The log of the Control gives the cause, and each Fulfilled mapped Requirement goes back to Not Fulfilled. For test results, see Results & Remediation. For Policies, see Lifecycle & Approvals.

Requirements ​

A Requirement has the status Not Fulfilled, Fulfilled, or Out of Scope. Modulos can also set Archived.

A Requirement also has a second signal. When all mapped Controls have a final status, the Requirement is ready for review. The Requirement Owner then examines the Controls and their Evidence and selects Mark as Fulfilled. Only the Requirement Owner can change the status of a Requirement. This step is the Review of record for a Requirement. For the procedure, see Requirements.

Assets ​

An Asset has the status In Progress, In Review, or Completed. Assets are the only object type with a formal Review request. Modulos locks the content, the Assigned To field, Edit Info, and the comment editor of an Asset that is In Review or Completed.

To request a status change for an Asset:

  1. Open the Asset and select Request status change.
  2. In Status Change, select the new status.
  3. In Reviewer(s), select one or more AI System Owners.
  4. Optional: type a Comment.
  5. Select Submit.

The Asset then goes to In Review. Each reviewer sees the banner Status Change Request assigned to you. with the button Review Request. On the Comments and Logs tab, the reviewer types the decision in the Review section and selects Approve or Reject. The button Approve applies the new status. The button Reject keeps the previous status. The first decision closes the Review, and the decision goes into the history of the Asset.

An AI System Owner can also select Force Update in the request dialog. This changes the status without a Review.

Change or cancel a Review request ​

While an Asset is In Review, its Asset tab shows the banner This asset is under review by with the names of the reviewers. If a reviewer is not available, two actions change the pending request:

  • Cancel Request, in the banner: an AI System Owner or Editor cancels the request. After you confirm, the Asset gets the status that it had before the request. The log of the Asset records the change, and the reviewers and the requester get a notification.
  • Edit Reviewer(s), in the Review section on Comments and Logs: an AI System Owner selects different reviewers and can type a Comment. The Asset stays In Review with the same requested status. The new reviewers get a notification, and the reviewers that you remove can no longer decide.
Asset Comments and Logs tab with the banner Status Change Request assigned to you, a Review editor, and Approve and Reject buttons.

A reviewer of an Asset types the cause of the decision in the Review section, then selects Approve or Reject.

  1. Status Change Request assigned to you. Shows that you are a reviewer of this request.
  2. Review Type the reason. It becomes a comment on the Asset.
  3. Approve / Reject Approve applies the requested status. Reject keeps the previous status.
  4. Status Shows In Review and the reviewers of the request.

How to use it ​

Changes to a system, a vendor, or an incident can change what a Control must include. Modulos lets you reopen work and keeps the cause on the same trail:

  • To reopen an Executed Control, set it to Not Executed. If a mapped Requirement is Not Fulfilled and ready for review, you must type why.
  • To reopen a Control of a Fulfilled Requirement, the Requirement Owner first sets the Requirement to Not Fulfilled. Then the Control Owner changes the Control.
  • A failed test, a Metric Test error, or an archived Policy reopens the Control automatically and logs the cause.