---
title: Execution Process
slug: execution-process
createdAt: 2026-05-04T09:03:17.350Z
---

Once a list is **Activated**, it can be executed. Mantsu's Checklists module supports **four execution scenarios**.

## Step 1 : Trigger

A list can be triggered in two ways:

| Method        | Description                                                   |
| ------------- | ------------------------------------------------------------- |
| **Manual**    | An operator or supervisor triggers the list directly          |
| **Automatic** | The Order Cockpit triggers the list as part of a routing step |

*See the configured triggers documentation for customer-specific trigger definitions.*

## Step 2: First Execution

The operator opens the list and answers all checks. After answering:

- The system validates that **all checks are answered**
- If not, the operator must complete remaining checks
- If all checks are answered, the system evaluates whether **all answers are within tolerance/expected values**

## Step 3: Checks Successful?

| Result | Scenario                 | Next Step                             |
| ------ | ------------------------ | ------------------------------------- |
| ✅ Yes  | **1-execution scenario** | List is completed                     |
| ✅ Yes  | **2-execution scenario** | System triggers second execution      |
| ✅ Yes  | **Approval scenario**    | System routes to Approver             |
| ❌ No   | Any scenario             | List is closed with **failed** status |

## Step 4: Second Execution (if applicable)

A second operator (different role or same role, per configuration) answers all checks independently. The same success/failure logic applies. On success, approval is triggered if configured.

## Step 5: Approval (if applicable)

The Approver opens the execution record and validates all answers:

- **Approved** → execution is finalized
- **Not approved** → execution loops back to the first execution step