Skip to content

Register an AI System ​

The registration of an AI System sets the scope of the governance work. The wizard records what the system is, what your organization uses it for, and who uses it. It also records if the EU AI Act applies and which frameworks apply. An AI System with a narrow scope stays stable and keeps its Evidence comparable. Then your team does not have to do the work again before an audit.

What this is ​

Registration gives:

  • an AI System record in the AI Registry with a name, Owners, an intended purpose, and a description
  • its Current State, Run Scope, and Geographic Scope
  • the EU AI Act classification, when you answer Yes to the EU AI Act question
  • the frameworks that apply, with their Requirements and Controls scoped from that classification
  • the Sources and Evidence that you add during registration
  • a registration status (Draft, Pending, Approved, or Rejected) and an Overview page with the registration record

Where in Modulos ​

  • AI Registry → AI Systems → New AI System opens the create dialog and then the registration wizard.
  • AI Registry → AI Systems shows the AI Systems that you can see. Each Draft has a Draft badge. Click a Draft to open it in the wizard.
  • AI Registry → My Submissions shows the AI Systems that you made, with the Drafts.
  • AI System → Overview shows the registration record and the registration decision.
  • AI System → Settings changes the registration details, frameworks, roles, and Sources after registration.

Who can do what ​

Permissions

  • All users of the organization can register AI Systems. The New AI System button shows for all users.
  • An Organization Admin or an Organization Registration Manager approves or rejects a Pending AI System. See User Management for these roles.
  • The user who made an AI System can delete it while it is Draft, Pending, or Rejected. An Organization Registration Manager can delete a Draft. Owners and the users with full access to all AI Systems can delete it in all statuses.

In the AI System:

  • Owners configure settings and give AI System roles.
  • Editors do the work on Controls and attach Evidence.
  • Viewers read the AI System and add comments for assurance. They cannot change items.

How it works ​

Registration starts with a short dialog and continues in the steps of a wizard:

  1. Create dialog Name the AI System and select its Owners. Modulos saves it as a Draft.
  2. AI System & Details Describe the system and what your organization uses it for.
  3. Use & Documents Record who uses the system. Add Sources. When governance is on, record if the EU AI Act applies, and add Evidence.
  4. Frameworks When governance is on: select the frameworks, then send the AI System for approval.

Each step saves its data before you go to the next step. You can stop and continue at a different time.

Create dialog ​

New AI System opens the Create New AI System dialog. The dialog has two fields: the AI System name (2 to 100 characters) and the Owner field. You are an Owner from the start, and you stay an Owner during registration. After registration, you can give ownership to a different user in Settings. Add more Owners from the activated users of your organization. Create saves the AI System as a Draft and opens the wizard with the name filled in.

A Draft does not count against the AI Systems limit of your plan. The limit applies when you send the AI System for approval. See Plan limit for AI Systems.

Step 1: AI System & Details ​

Basic information:

FieldRequiredWhat to enter
AI SystemYesThe name. Use the name of the tool and how you use it, for example "Claude for Customer Support" and not only "Claude". Make one entry for each different use. For one tool with two purposes, two entries can be necessary, because the risk class changes with the use of the system.
OwnerYesMinimum one Owner. The creator stays in the field during registration. You can change this field only if you have the right to give and remove AI System roles.
Intended PurposeYesWhat your organization uses the system for, or will use it for, with a minimum of 10 characters. Name the task, the business procedure, the persons that its outputs have an effect on, and the domain. "Answers employee questions about HR policies" and "screens job applications" are two HR chatbots with very different risk classes. This entry sets the legal class of the system.
DescriptionNoWhat the system is and how it operates. Give the type of technology, for example a chatbot on a large language model or a scoring model. Also give the data that goes in, the output, and the users. Write about your deployment, not the marketing text of the vendor. Maximum 5,000 characters.

Scout uses the description

Modulos puts the AI System description into the system prompt of Scout (up to 5,000 characters). Write the architecture, the data Sources, and the deployment context. Then the answers of Scout are about your system. See First Steps for help with the description.

AI System details:

FieldRequiredWhat to enter
Current StateYesProposed: an idea or a request, not tested. Pilot: a small trial with actual users or actual data. With Already in use, persons use the system at this time, also without a formal approval. Write what is there, not what has approval.
Target Go-Live DateNoThe date when you plan to start productive use. An estimate is sufficient. For a system that is Already in use, the field name is Go-Live Date: enter the date when the system went live.
AI Lifecycle StageNoWhere the system is in the AI life cycle, from the first concept to retirement. The values come from the AI System Lifecycle tag of your organization. This field shows when governance is on for your organization.
AI System LanguageNoThe default language of the AI System. Modulos fills in the organization language.
AI System Annual Economic ValueNoThe value that the AI System gives in one year, for example more revenue, lower costs, or losses that it prevents. Modulos compares it with the risk value in the Value and Risk view. With the Economic Value-Based Allocation method, it also sets the risk limit of the AI System. An estimate is sufficient: you can start with 0 and change it after registration. With 0, the Value and Risk view shows Incomplete data for the AI System. This field shows when risk management is on for your organization.
Geographic ScopeNoWhere persons will use the system: EU, UK, US, APAC, LATAM, MEA, or Global. You can select more than one value. Scout uses this value as context in conversations and in risk quantification.
Registration wizard step AI System & Details with the Basic Information and AI System Details cards and a guidance panel for the Intended Purpose field.

Step 1 of the registration wizard. The guidance panel shows help for the field that you edit.

  1. Steps The three steps of the wizard. Select a step name to go to that step.
  2. Intended Purpose Required, minimum 10 characters. This entry sets the legal class of the system.
  3. Guidance panel Shows help for the field that you edit.

A guidance panel next to the fields shows help for the field that you edit. The panel shows on screens that are 1024 px wide or wider.

Continue saves the step. To continue a Draft at a different time, open it from AI Registry → AI Systems or AI Registry → My Submissions. The step names at the top of the wizard also move you between the steps. A step name moves you back to an earlier step, or forward to the next step after Modulos saves the current step. If you go away from the wizard with changes on step 1 or step 2 that are not saved, Modulos shows a confirmation dialog.

Step 2: Use & Documents ​

Where will this AI System run? is required. Select all user groups that use the system:

  • Internal: "Used by staff in a controlled context"
  • Employee-facing: "Available to employees broadly"
  • Customer-facing: "Interacts with external customers"
  • Embedded in product: "Part of a product you ship"

Does the EU AI Act apply to this AI System? has three answers: Yes, No, and Not sure. The classification fields show only for Yes. With Yes, Product Category and Role are required. Use Case is available when you set these two fields, and its values include Minimal Risk.

With No or Not sure, the wizard saves no EU AI Act classification and does not keep the answer. When you open the Draft again, the question has no answer.

The button Add full EU AI Act details shows five more fields. They are Organization Establishment, Model Property, AI System Requirements, Prohibited AI Practices (Article 5), and Model Supply Terms. After registration, you can change the classification in AI System → Settings → EU AI Act, with the scoping questionnaire. See AI System Settings. A Yes answer with a classification selects the EU AI Act framework on the next step, and you cannot clear it there.

Registration wizard step Use & Documents with run scope chips, the EU AI Act question answered Yes with Product Category and Role, one connected Source, and one Evidence file.

Step 2 of the registration wizard records who uses the system, the EU AI Act classification, and the first Sources and Evidence.

  1. Where will this AI System run? Required. Select all user groups that use the system.
  2. EU AI Act With Yes, Product Category and Role are required. Step 3 then selects the EU AI Act framework.
  3. Connect Sources, Evidence Modulos saves each Source and each file on the Draft immediately.

Connect Sources adds the Sources that Runtime Inspection tests and Scout use. Add Source opens the same dialog as AI System → Settings → Sources, with Check connection. Modulos saves each Source on the Draft immediately. The Source types that your organization did not turn on show in a different group. An Organization Admin turns them on in Organization → Source & Connectors. See Sources.

Evidence lets you upload documents that you have (policies, assessments, architecture notes) with Add Evidence. The files become Evidence of the AI System immediately, and you can remove them. If you do not have Sources or Evidence at this time, add them after registration.

Scout during registration ​

The Scout button in the page header opens Scout in registration mode. Scout reads the data that you typed, also in fields that you did not save. It can read the Sources that you select in the chat. It can compare your entry with the other AI Systems of your organization that you can see, to make names and text agree. Scout can tell you what to enter, or if the EU AI Act possibly applies. In this mode, you cannot save answers as Evidence.

Scout can also propose AI Systems in a chat. When you accept, Scout adds them to My Submissions as Drafts, with you as Owner. See Scout.

Step 3: Frameworks ​

This step shows when governance is on for your organization.

The wizard selects the EU AI Act framework when you answered Yes and set a classification on step 2. You cannot clear it while that classification stays. Select the other frameworks that apply. Each card shows the number of Requirements and Controls of the framework. The Reset to suggested button sets the selection back to the suggestion.

The wizard shows only frameworks for AI applications. Organization-scope frameworks (OFF-x) attach to the organization AI System. See The organization AI System.

Create AI System sends the AI System for approval: its registration status changes from Draft to Pending. Then the wizard attaches the selected frameworks. It runs the EU AI Act scoping one time, to make the Requirements agree with the classification. Then it opens the Overview. You can add or change frameworks in AI System → Settings → Frameworks. Before an audit, an Organization Admin can freeze framework updates there.

Plan limit for AI Systems ​

When your organization has no more AI Systems in its plan, the wizard shows a banner: No more AI Systems can be created on your current plan. You can continue to edit the Draft and use Scout. On the last step, View Usage replaces Create AI System and opens Organization → Usage in a new browser tab. AI Systems in Pending, Approved, and Rejected count against the limit, and Drafts do not. See Usage.

Registration approval ​

An Organization Admin or an Organization Registration Manager makes the decision on each Pending AI System. These users see all AI Systems of the organization in the AI Registry, also the AI Systems where they have no role. To find the Pending AI Systems, use the Registration Status filter in AI Registry → AI Systems.

Overview of a Pending AI System with the AI System Registration decision required banner, Reject and Approve buttons, and the Status Pending in the side panel.

An Organization Registration Manager approves or rejects a Pending AI System on its Overview.

  1. AI System Registration decision required Shows on a Pending AI System for an Organization Admin or an Organization Registration Manager.
  2. Reject, Approve Reject asks for a cause of minimum 5 characters. Approve sets the status to Approved.
  3. Status The registration status of the AI System.

On the Overview of a Pending AI System, these users see the banner AI System Registration decision required with Reject and Approve:

  • The Approve button shows a confirmation dialog and sets the status to Approved. The creator of the AI System gets a notification. Approved is the last status: it does not change again.
  • The Reject button shows a dialog for the cause, with a minimum of 5 characters, and sets the status to Rejected. The cause becomes a comment on the Overview, and the creator gets a notification with the cause.

The creator gets no notification for a decision that the creator makes. A Rejected AI System shows the banner AI System Registration was rejected with Submit for review. An Owner, an Organization Admin, or an Organization Registration Manager sees it. The button sends the AI System for approval again, and the status changes to Pending. A Rejected AI System does not go back to Draft. Each status change makes an entry in the log of the AI System.

The registration status has an effect on risk limits. A Draft or a Rejected AI System gets no part of the risk appetite of the organization, and its risk limit shows No risk limit. A Pending or an Approved AI System gets a risk limit. See Risk limits.

Delete a Draft ​

To delete a Draft, open it in the wizard and select Delete Draft in the menu at the top right. The creator, the Owners, Organization Registration Managers, and the users with full access to all AI Systems see this menu item.

In AI Registry → My Submissions, the menu of each card has Delete. It shows for the AI Systems that you made while they are Draft, Pending, or Rejected. If you are an Owner or have full access to all AI Systems, it also shows for an Approved AI System.

An Owner can delete a Pending, Approved, or Rejected AI System in AI System → Settings → Danger Zone. A Draft opens in the wizard and has no Settings. The users with full access to all AI Systems can do this too: Organization Admins, Organization Risk Managers, and Organization Policy Managers.

When a user deletes an AI System that is not Approved, the creator and the Owners get a notification. Modulos sends no notification when the creator or an Owner deletes it.

After registration: the Overview ​

AI System → Overview is the first item in the sidebar of the AI System. It opens when you select a Pending, Approved, or Rejected AI System in the AI Registry. The Overview shows the registration record:

  • System Information: the intended purpose (with the name Intended Use) and the description. Edit opens Settings → General Settings.
  • EU AI Act Assessment: the recorded classification and the EU AI Act Questionnaire button.
  • A side panel with Status (the registration status), Owner, and Submitted (the date when the AI System was made). It also shows Current State, Target Go-Live Date, AI Lifecycle Stage, Geographic Scope, and Run Scope.

The Comments and Logs tab holds the comments about the AI System and its log, with each registration status change. See The log of an AI System.

You can edit all registration details of a Pending, Approved, or Rejected AI System in AI System → Settings → General Settings. You edit a Draft in the wizard. Current State and run scope are required there. For an older AI System without these fields, you must fill in the two fields before you can save its settings.

How to use it ​

  1. Name the system by its use Give the name of the tool and how you use it. Make one entry for each use, and add a second Owner.
  2. Write the intended purpose Task, business procedure, affected persons, and domain: this sets the legal class.
  3. Record state and scope Current state, go-live date, who uses the system, and geographic scope.
  4. Answer the EU AI Act question For Yes, set Product Category and Role. The wizard then selects the EU AI Act framework.
  5. Select frameworks and send Keep the suggestion or add frameworks, then send the AI System for approval.

Important considerations ​

  • Keep each AI System narrow. One deployed system or one use case for each AI System keeps Evidence and risk quantification defensible.
  • The intended purpose and the description are a record for your team and your auditors. Text that is not clear makes classification and audits slow.
  • Add a second Owner in the create dialog or in AI System → Settings → User Access. See Multiple Owners for the rules.
  • Give AI System roles and Requirement Owners at the start. This makes separation of duties easier to keep.