Restricting Scheduling based on keywords

Keyword-based load matching allows you to set resource requirements on orders so that when planning on the live scheduler, only loads with suitably qualified drivers, vehicles, and trailers are available.

How It Works

When you drag an order onto the scheduler, any loads that don't meet the order's keyword requirements are greyed out, preventing accidental allocation to unqualified resources.

Keywords are added to orders using the existing keyword/tag input during order creation or editing.

Keyword Prefixes

Use a prefix to specify which resource type the requirement applies to:

Keywords are case-insensitive — D:adr  and D:ADR  are treated the same way.

What Counts as a Match

A resource satisfies a keyword requirement if either of the following is true:

1. Tag/keyword match - The resource has the key in its tags or keywords (e.g. a vehicle tagged HIAB , a trailer with keyword TASCC , etc.)
2. Valid custom date - The resource has a custom date with that code and the date has not expired. For drivers, the built-in dates (HGV, Tacho, CPC) are also checked.

If a custom date has expired, it will not satisfy the requirement. This ensures only currently qualified resources are matched.

Multiple Keywords

You can add multiple prefixed keywords to a single order. All requirements must be met for a load to be considered compatible.

For example, an order with keywords D:ADR  and V:HIAB  requires:

• The driver to have ADR qualification and
• The vehicle to have a HIAB tag

If either is missing, the load is greyed out during drag.

Subcontractors

Subcontract loads are never restricted by keyword matching. Resource compliance is the subcontractor's responsibility, so their loads always remain available for allocation regardless of order keywords.

Existing Keywords

Plain keywords without a prefix (e.g. TASCC , ADR , WTN ) continue to work as before for their own purposes (TASCC trailer filtering, display badges, etc.). They are not checked by the new load matching system — only prefixed keywords (D: , V: , T: ) trigger compatibility checks.

Examples

Scenario 1: ADR Delivery

A chemical plant requires full ADR compliance — the driver, vehicle, and trailer must all be ADR certified.

1. Add keywords D:ADR , V:ADR , and T:ADR  to the order
2. On the scheduler, only loads where the driver, vehicle, and trailer all have valid ADR certification are available
3. This is additional to the global ADR  tag which only notifies you that the order is ADR

Scenario 2: Specialist Vehicle

An order requires a vehicle with a specific capability (e.g. HIAB crane).

1. Add the keyword V:HIAB  to the order during creation
2. On the scheduler, only loads with a vehicle tagged HIAB  are available

Scenario 3: Multiple Requirements

An order needs a TASCC-assured trailer and a vehicle with a HIAB crane.

1. Add keywords T:TASCC  and V:HIAB  to the order

2. On the scheduler, only loads meeting both requirements are available — the trailer must have TASCC  and the vehicle must have HIAB

Scenario 4: Custom Date Compliance

Your company tracks a custom driver date called ALLMI .

1. Set up ALLMI  as a custom driver date in company settings

2. Ensure drivers have their ALLMI expiry dates recorded

3. Add D:ALLMI  to orders that require it

4. Only loads with drivers whose ALLMI certification is still valid will be available