Appearance
Requirements
Requirements are the "what" of a framework: the obligations that come directly from the regulation or standard.
What this is
Requirements are the compliance "contract" for the scope of an AI System. They are:
- from the framework: they keep the structure of the source document
- mapped to Controls: you do the work one time and use it for more than one Requirement
- fulfilled on purpose: the Requirement Owner records the decision that the obligation is satisfied
For the end-to-end model, see Governance Operating Model.
Where in Modulos
AI System → Requirementsto see the obligations, filter them by framework (Filter → Framework), and monitor fulfillment. The address of the page keeps the filters. A copied link opens the same filtered Requirements.- Open a Requirement to see the tabs Requirement and Comments and Logs. The Requirement tab shows the Description, the Details, and the Mapped Controls. The right panel shows Status, Owner, and Mapped Frameworks.
Who can do what
Permissions
- All members of an AI System can see its Requirements and the mapped Controls.
- Only an AI System Owner can select the Requirement Owner. The Requirement Owner must be an AI System Owner or an Editor.
- Only the Requirement Owner can change the status of a Requirement.
- The Requirement Owner selects the Control Owners of the mapped Controls.

A Requirement keeps the framework obligation and shows the Controls that map to it.
- Requirement The header shows the code and the name of the Requirement.
- Status Only the Requirement Owner can change the status.
- Executed Control(s) Shows how many mapped Controls are Executed or Out of Scope. Archived Controls do not count.
- Mapped Controls Select Controls to change their Owner or status together.
How it works
Requirements are framework-derived
When you add a framework to an AI System, Modulos makes Requirements that keep the structure of the framework. Each Requirement has its own code, for example MRF-213. Most Requirements give the article or clause of the source in their name or in Details. This lets auditors see which obligation a Control and an Evidence item are for.
Requirements map to Controls
Requirements do not hold the work. They map to Controls, and the Controls do the work:
- many Requirements can map to one Control
- one Requirement can map to more than one Control, when the obligation has more than one measure
When an AI System Owner selects a Requirement Owner, Modulos also makes that user the Owner of each mapped Control that has no Owner.
In Mapped Controls, the Requirement Owner can change more than one Control at the same time. Select the Controls, then set Assign To or Change Status, and select Apply Changes.
Change Status has no comment field. As a result, Modulos rejects a change from Executed to Not Executed when a mapped Requirement of the Control is ready for review. Make this change on the page of the Control, where you can type why.
Status and readiness are different
A Requirement has a status:
- Not Fulfilled or Fulfilled
- Out of Scope for an item that does not apply
A Requirement also has a different signal: ready for review.
This is an important difference: in Modulos, fulfillment is a decision that the Requirement Owner records. Modulos does not set Fulfilled automatically.
What "ready for review" means
A Requirement is ready for review when all its mapped Controls have a final status: Executed, Out of Scope, or Archived. The Requirement Owner then gets a notification and these tasks:
- examine the mapped Controls and their Evidence
- make sure that the obligation is satisfied for the scope of this AI System
- mark the Requirement as Fulfilled
While the Requirement is ready for review and Not Fulfilled, the page shows the banner "Requirement is ready to be reviewed. If all related controls are correctly executed mark this requirement as Fulfilled." with the button Mark as Fulfilled.

When all mapped Controls have a final status, the Requirement Owner can mark the Requirement as Fulfilled.
- Requirement is ready to be reviewed. Shows that all mapped Controls have a final status.
- Mark as Fulfilled Records the fulfillment decision of the Requirement Owner.
- Comments and Logs Shows when the Requirement became ready for review.
- Status Stays Not Fulfilled until the Requirement Owner marks it as Fulfilled.
Marking a Requirement as fulfilled
Only the Requirement Owner can mark a Requirement as Fulfilled, and only when all its mapped Controls have a final status. Modulos records the decision in Comments and Logs.
The mapped Controls set the ready-for-review signal, and the Requirement Owner sets the status to Fulfilled:
- Not Fulfilled A mapped Control is Not Executed
- all Controls have a final status
- a Control reopens
- Not Fulfilled, ready for review A signal, not a status
- Mark as Fulfilled
- set to Not Fulfilled
- Fulfilled The decision of its Owner
While a Requirement is Fulfilled, its mapped Controls cannot change their status. To reopen the work, the Requirement Owner sets the Requirement to Not Fulfilled. A failed test, a Metric Test error, or an archived Policy can set a mapped Control back to Not Executed while the Requirement is Fulfilled. The Requirement then goes back to Not Fulfilled and is no longer ready for review. For the Control rules, see Reviews & Statuses.
How to use it
- Start from frameworks Add the frameworks that agree with the scope of your audit.
- Select a Requirement Owner An AI System Owner selects the user who records the fulfillment decision.
- Complete the mapped Controls The Control Owners do the work and attach Evidence.
- Examine when ready for review Make sure that the Evidence and the reports satisfy the obligation.
- Mark as Fulfilled Record the decision when all mapped Controls have a final status.
Important considerations
- Requirements are obligations, not tasks. Use Controls for the work.
- Mark a Requirement as Fulfilled only when Evidence shows it. If you cannot show it to an auditor, the Requirement is not fulfilled.
- Use Out of Scope only when necessary, and make it agree with the scope statement of the AI System. Then auditors can examine each exclusion.