> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/workforce-management-solutions/random-selection.md).

# Random selection

Configure random cardholder selection for screening, access control, competency management, and spot checks.

There are two similarly-named features for randomly selecting cardholders at a door, for example for random screening. The key difference is **where the logic runs**: **Random Cardholder Selection** is **server-based**, while **Random Selection** is **controller-based**. Random Selection is the **current core feature** (`C12824`); Random Cardholder Selection (`C12583`) is the older customisation being migrated away from. **They cannot run on the same door at the same time.**

### Comparison

|                       | Random Cardholder Selection                                                                                               | Random Selection                                                               |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **Main difference**   | Server based. The server **and** controller need to be online to work properly.                                           | Controller based. Works even when the controller is **offline** to the server. |
| **Available version** | v7.01 to v8.30 or later                                                                                                   | v8.30 or later (not available in v8.20)                                        |
| **Licensing string**  | `[Limits]` `Competencies=X`; `[Features]` `RandomCardholderSelection=1`; `[Customisations]` `RandomCardholderSelection=1` | `[Features]` `Random Selection=1`                                              |

### Exception: v8.10 customisation

Random Selection is also available as a **customisation only in v8.10**, with the licence string:

```
[Customisations]
Random Selection=1
```

### Important: not on the same door

Random Cardholder Selection and Random Selection **cannot work on the same door at the same time**. You can have both customisations in v8.10 at the same site, but the two customisations should **not** be configured onto the same door.

### Migration: customisation to core

| Customisation                            | → | Core                          |
| ---------------------------------------- | - | ----------------------------- |
| `C12583` LIC Random Cardholder Selection | → | `C12824` LIC Random Selection |

The migration step for customers currently using the customisation is provided in **v8.30**, as this is the last version in which the customisation is upgraded. From **v8.40**, customers should be using **`C12824`** (the core Random Selection feature).

### Random Selection feature mechanics

Random Selection allows cardholder selection for **drug or alcohol testing, and vehicle or cardholder spot checks**. The **Random Selection Admin viewer** lets operators manage the **percentage-based chance of selection**, the times selection can occur, and the associated access groups of a Random Selection item.

**Main features:**

* Rules created with a defined **access group, schedule, and probability of selection**.
* **Selection messaging** configurable to inform the cardholder via the **T20 reader** after selection.
* Define how many cardholders can be selected over a period (for example only 10 per hour).

**Use case (drug or alcohol testing):** when a cardholder is selected at a nominated door, access is granted and the cardholder's **Competency** (as nominated in configuration) is either **expired or disabled**. Competencies can then be used to deny access to specific areas until the cardholder is tested. This pairs with the [Alcolizer Integration](/knowledge-hub/products/cc-software/configure/workforce-management-solutions/alcolizer-integration.md) breath-testing workflow.

### Version history

* **v8.30:** Random Selection feature introduced.
* **v8.40:** **"Overdue Arrivals"** functionality added to Random Selection.
* The Random Selection feature (`C12824`) replaces the Random Cardholder Selection customisation (`C12583`) from v8.30.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/workforce-management-solutions/random-selection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.