--- title: "Run skip logic" slug: "bc-run-skip-logic" description: "Optimize quality management with skip logic patterns, allowing relaxed inspections based on item classification and historic performance." tags: ["Task"] updated: 2026-06-25T09:59:00Z published: 2026-06-25T09:59:00Z canonical: "docs.staedean.com/bc-run-skip-logic" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.staedean.com/llms.txt > Use this file to discover all available pages before exploring further. # Run skip logic With Quality Management Skip Logic, companies can set patterns for skipping checks in quality measurement processes. These patterns let non-critical items "earn" a more relaxed inspection regime based on historic performance. Define several **skip patterns** based on the classification of items. The starting point for a pattern is the **ABC classification** of an item, a combination of activity and turnover value. ## Steps To create or update a skip pattern: 1. Choose the ![](https://cdn.document360.io/da662430-6a41-47b1-8c7e-7e4ac37a9756/Images/Documentation/image(150).png) icon (Alt+Q). 2. Type **Skip Pattern** in the search box. 3. Select **New** to create a new skip pattern, or select a line to edit an existing one. 4. On the header, set up the skip pattern identification: | Field | Description | | --- | --- | | Code | Type a code for the skip pattern. | | Description | Describe the skip pattern. | | Activity Class | Select an activity class: **A**, **B**, or **C**. | | Turnover Class | Select a turnover class: **a**, **b**, or **c**. | 5. In the lines, set up one line for each level in the skip pattern | Field | Description | | --- | --- | | Activity Class | Filled automatically (first three fields). | | Turnover Class | Filled automatically. | | Level | Filled automatically. | | Inspection Level | Inspection and quality levels relate to the AQL/Zero Defects methods. The skip pattern level sets the AQL levels to a more relaxed or higher intensity level of inspection. | | Quality Level | See Inspection Level. | | Accepted Receiving Events | The number of receipts to process before a skip is allowed. | | Skip | The number of receiving events to skip. | | Frequency | The number of repeats of the receive and skip events before moving to the next level. | | Reject Level | The level to which the settings return when a rejected receipt occurs. | | Max. Interval | A date formula to set the period in which a frequency must be completed before moving to the next level. When not completed in time, the frequency is set to 0. | ## Skip Progress The progress of an incident in a skip pattern is tracked in the **Incident Entry** to allow manual resets. The following fields track this progress: - **Turnover Class**: copied from the Item Classification Setup. - **Activity Class**: copied from the Item Classification Setup. - **Active**: indicates that this line is part of an active cycle. - **Level**: shows the current level in the skip pattern. - **Quality Control Status**: **Performed** or **Skipped**. Shows whether the pending inspection needs to be completed or skipped. - **Quality Control Result Status**: **Accepted**, **Skipped**, or **Rejected**. Shows the end result of the inspection from the registered measurement. - **Closed by Date Interval**: when checked, the frequency took longer than specified in the max. interval. The "skip status" for an item/vendor is tracked in **Activity Levels**. For each item-vendor combination, the following data is tracked: - **Current Level**: shows the current level in the skip pattern. - **Accepted Events**: the number of accepted events in the current level. - **Skipped Events**: the number of skipped events in the current level. - **Frequency**: the frequency number in the current level. > [!NOTE] > **Note** > > - When the item moves to the next level, the Accepted, Skipped, and Frequency numbers are reset. > - When an item has cycled through the complete pattern and you want it to remain at the highest level, define a high frequency number (for example, 9999). > - When there are receiving events while a measurement is still pending, the measurement for the new events is only created when the pending measurement is completed, to apply the correct skip logic. ## Related - [Quality Management](/bc-quality-management.md)