---
title: List Creation Process
slug: list-creation-process
createdAt: 2026-05-04T09:03:17.337Z
---

In Mantsu's Checklists module, the full list creation lifecycle follows a structured review and approval workflow.

## Step 1: Create New Version

The creator creates a new list version and fills in:

- The **trigger**
- The **ID** of the checklist
- The **description**

The system auto-generates a version number. The creator can link the checklist to an **Equipment Class**, an **Equipment** or a **Location**. Once saved, the system sets the status to **Draft** and stamps the date and author.

## Step 2: Fill In Version Details

The creator adds metadata and content:

- **Delay between questions** (optional)
- **Sequential execution** toggle (whether checks must be done in order)
- **Attached documents**
- **Execution mode**: one of 4 execution possibilities (see [Execution Process](docId\:cuFuMwQq_BELX9T0wOxmE))
- **Individual checks**: unlimited checks can be added, each with:
  - Different answer types
  - An optional barcode link (for scanner use)
  - Optional text and picture fields in the answer
  - At least one valid answer per check is required

## Step 3: Save & Version Check

On save, the system validates completeness:

- If **incomplete** → status remains **Draft** and the system shows what is missing
- If **complete** → status moves to **For Review**

## Step 4: Validator Review

The validator opens the Checklists module and reviews pending actions. Two outcomes are possible:

| Outcome     | Status Change | Action                           |
| ----------- | ------------- | -------------------------------- |
| **Approve** | → Reviewed    | Creator is notified              |
| **Reject**  | → Draft       | Creator receives rejection notes |

## Step 5: Activation

The approver (or authorised user) requests activation. The system:

1. Checks whether a previous active version exists
2. If so, asks for confirmation to deactivate it
3. On confirmation, moves status to **Activated** and the previous version to **Deactivated**

## Step 6: Post-Activation Change

If an Activated list must be changed:

- A **new draft version** is created
- The active version **remains available for execution** until the new version is Activated

Only \*one active version\* per checklist ID is allowed at any time.