<!-- RTOSafe Help — rendered version: https://rtosafe.com.au/help/staff-requirement-sets -->

# Set Up Requirement Sets

Some requirements can be met in more than one way. A trainer might hold the current TAE qualification or an older version that's still accepted for a while. A requirement set lets you list each acceptable **pathway** — staff only need to meet one of them.

***

## When to Use This

* **Different versions are accepted** — for example, `TAE40122` or `TAE40116`
* **A combination is needed** — for example, a First Aid certificate *and* a CPR certificate, each with its own refresh period
* **An older credential is being phased out** — keep accepting it until a set date, then stop

If only one document will do, use a normal document requirement instead — see [Set Up Document Requirements](/help/staff-document-requirements).

***

## Creating a Requirement Set

<div class="help-stepper">

<div class="help-step">
<div class="help-step-number">1</div>
<div class="help-step-content">

Go to [**Settings → Requirement sets**](https://app.rtosafe.com.au/DocumentRequirementGroups) and select **Add requirement set**

</div>
</div>

<div class="help-step">
<div class="help-step-number">2</div>
<div class="help-step-content">

Give it a name, like "Trainer qualification"

</div>
</div>

<div class="help-step">
<div class="help-step-number">3</div>
<div class="help-step-content">

In the first pathway, add the documents or training products that meet it

If a pathway needs more than one credential, add each one — staff need all of them.

</div>
</div>

<div class="help-step">
<div class="help-step-number">4</div>
<div class="help-step-content">

Select **+ Add alternative pathway (OR)** for each other acceptable option, then select **Create requirement set**

</div>
</div>

<div class="help-step">
<div class="help-step-number">5</div>
<div class="help-step-content">

Apply the set to a position in [**Settings → Positions**](https://app.rtosafe.com.au/Positions), or to one staff member through **Manage Requirements**

</div>
</div>

</div>

***

## Refresh Periods and End Dates

Two optional settings change what counts:

* **Must be refreshed every … months** — set on a credential in a pathway. The document must have been issued within that many months, even if it hasn't expired. Useful for things like CPR that you want refreshed more often.
* **Accepted until** — set on a pathway. After that date, the pathway stops counting. From six months out, staff relying on it show as **Upcoming credential sunset**, so you have time to plan.

<div class="help-hint bg-blue-50 border-blue-300 text-blue-800">
<svg class="w-5 h-5 shrink-0" fill="currentColor" viewBox="0 0 20 20"><path fill-rule="evenodd" d="M18 10a8 8 0 11-16 0 8 8 0 0116 0zm-7-4a1 1 0 11-2 0 1 1 0 012 0zM9 9a1 1 0 000 2v3a1 1 0 001 1h1a1 1 0 100-2v-3a1 1 0 00-1-1H9z" clip-rule="evenodd"></path></svg>
<div class="help-hint-content">

Training products in a requirement set match the exact code you add — or, for a unit, a qualification that contains it. Superseded versions aren't matched automatically, so if you accept an older version, add it as its own pathway.

</div>
</div>

***

## What Happens Next

* Staff who don't meet the set yet see it in their requirements, with the pathways that would meet it
* Anyone who doesn't meet any pathway shows as a compliance issue on your dashboard and the [**Staff Document Compliance**](https://app.rtosafe.com.au/Reports/StaffDocumentCompliance) report

***

## Common Issues

<details>

<summary><strong>Trainer holds the qualification but still shows an issue</strong></summary>

Check the document is verified. For a qualification, also check it's the exact code in the pathway, and that it was issued within any refresh period you set.

</details>

<details>

<summary><strong>Staff suddenly showing as not meeting the set</strong></summary>

A pathway may have reached its **Accepted until** date. Staff need to meet one of the remaining pathways.

</details>