# Resource Optimiser

## **What is the Resource Optimiser?**

The **Resource Optimiser** is a tool within the Maica Planner used to identify and fill unfilled Appointments or Shifts using Maica's Optimisation Engine using either an [Optimisation Run](/maica-knowledge-base/the-planner/resource-optimiser/running-the-optimiser.md) or [Broadcast](/maica-knowledge-base/the-planner/resource-optimiser/broadcasting-overview.md). 

{% hint style="info" %}
Please note, you can also access the Resource Optimiser from the [Schedule Manager](/maica-knowledge-base/schedule-manager/schedule-manager-overview.md). 
{% endhint %}

It consolidates all Appointment and Shift records requiring Optimisation/Filling into a single screen, allowing users to review, run, and confirm Resource allocations efficiently. 

{% hint style="success" %}
To learn more about how to Maica classifies a record as requiring optimisation, please [click here](#what-gets-pulled-into-the-optimiser). 
{% endhint %}

The Optimisation logic evaluates each Appointment or Shift based on a range of customisable inputs such as Resource Availability, Attributes, Workload, Skills, and Participant Preferences and then fills or Broadcasts each one with the most suitable Resource. 

{% hint style="info" %}
To learn more about the logic behind Maica's Optimisation Engine, please [click here](/maica-knowledge-base/maica-administration-guide/system-processes/maicas-optimisation-engine.md). 
{% endhint %}

## Where do I find the Resource Optimiser? 

The Resource Optimiser can be accessed directly from the **Planner Toolbar**, as shown below. 

<figure><img src="/files/L8cul3UTNVttzxig0VEd" alt=""><figcaption></figcaption></figure>

To find it, simply:&#x20;

1. Open the **Planner**.
2. Select the **Optimiser** icon from the toolbar at the top of the screen.
3. The Optimiser panel will open, displaying a list of all unfilled Appointments or Shifts within the date range currently shown in the Planner.

## What gets pulled into the Optimiser?&#x20;

When the Optimiser is opened, it retrieves all records where the required number of Resources does not meet the defined ratio and the Status is Scheduled or Planned. These records are considered *unfilled* and are therefore eligible for optimisation or broadcasting.

Additionally, the Optimiser will also only consolidate records from the defined Period currently displayed in the Planner at the time it is opened.&#x20;

In summary,&#x20;

**Included Records:**

* Appointments or Shifts where **Status** is *Scheduled* or *Planned*.
* Records where the number of **Resources** does not meet the **Ratio**.
* Appointments or Shifts visible within the **current Planner date range**.

{% hint style="info" %}
For example, a Shift requiring two staff members but currently assigned only one will appear in the Optimiser until the second Resource is confirmed.
{% endhint %}

**Excluded Records**

* Appointments or Shifts marked as *Completed* or *Cancelled*.
* Records that already meet the required Resource or Participant Ratio.
* Records outside of the visible Planner date range.

{% hint style="info" %}
For example, if you have an unfilled Appointment in the following week to the one set in your Planner, that Appointment will not display in the Optimiser.&#x20;
{% endhint %}

## Optimiser Parts&#x20;

The Optimiser is made up of a range of different parts, each are described in the table below:&#x20;

{% hint style="info" %}
Please note, key parts of the Optimiser are described in further detail below. Please click the Part name to learn more.&#x20;
{% endhint %}

<figure><img src="/files/NXQ38oDqxxOZy7qJNV9U" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="73.931640625" align="center">No.</th><th width="204.734375">Part</th><th>Description</th></tr></thead><tbody><tr><td align="center"><strong>1</strong></td><td><a href="#resource-pool"><strong>Resource Pool</strong></a></td><td>Used to create filters to define a smaller, more relevant group of Resources for Optimisation. Only Resources matching the selected pool criteria will be considered when running the Optimiser. <em>(Described further below)</em></td></tr><tr><td align="center"><strong>2</strong></td><td><a href="#ranking-criteria"><strong>Ranking Criteria</strong></a></td><td>Criteria you add adjust Resource scoring. <em>(Described further below)</em></td></tr><tr><td align="center"><strong>3</strong></td><td><a href="#optimiser-settings"><strong>Settings</strong></a></td><td>Provides configuration options for Optimisation behaviour on a per run basis. <em>(Described further below)</em></td></tr><tr><td align="center"><strong>4</strong></td><td><strong>Status Filters</strong></td><td>Allows filtering of Appointments or Shifts within the Optimiser by status, for example showing only <em>Filled</em> or <em>Partially Filled</em> records.</td></tr><tr><td align="center"><strong>5</strong></td><td><strong>Progress Indicator</strong></td><td>Shows the number of filled versus total unfilled records (e.g. <em>0 of 51 filled</em>). Updates automatically during optimisation and provides the ability to pause your run at any stage.</td></tr><tr><td align="center"><strong>6</strong></td><td><a href="/pages/ELBnmUjm4Efgcg2i9JvR"><strong>Broadcast Trigger</strong></a></td><td>Triggers the modal for the Broadcasting process for selected records based on the current Ranking Criteria, Resource Pool and Settings.<br><br>To learn more about Broadcasting, <a href="/pages/ELBnmUjm4Efgcg2i9JvR">click here</a>. </td></tr><tr><td align="center"><strong>7</strong></td><td><strong>Optimisation Trigger</strong></td><td>Executes the Optimisation process for selected records based on the current Ranking Criteria, Resource Pool and Settings.</td></tr><tr><td align="center"><strong>8</strong></td><td><strong>Select All</strong></td><td>Selects or deselects all records within the list for batch Optimisation or Confirmation.</td></tr><tr><td align="center"><strong>9</strong></td><td><strong>Status Column</strong></td><td>Displays the current Status of each Appointment or Shift (e.g. Unfilled, Filled, Partially Filled, or Error).</td></tr><tr><td align="center"><strong>10</strong></td><td><strong>Appointment Column</strong></td><td>Shows the Appointment or Shift identifier, including the date and time. Please note, this information is configurable and based on your Appointment Text Format in the<a href="/spaces/9selzjEx6KX7RYEawAVr/pages/8vqQUcucFQBxsh5UTl9H#text-format"> Planner Management Settings</a>.</td></tr><tr><td align="center"><strong>11</strong></td><td><strong>Configurable Column</strong></td><td>Allows custom configuration to display additional fields such as Location or Participants.</td></tr><tr><td align="center"><strong>12</strong></td><td><a href="#resource-column"><strong>Resource Column</strong></a></td><td>Displays current Resources. <em>(Statuses and Resource Pills described further below)</em></td></tr><tr><td align="center"><strong>13</strong></td><td><strong>Required Badge</strong></td><td>Displays the number of Resources required for the Appointment or Shift based on the defined Ratio. </td></tr><tr><td align="center"><strong>14</strong></td><td><strong>Pending Badge</strong></td><td>Displays the number of Resources who have been Broadcast too but have not yet responded. </td></tr><tr><td align="center"><strong>15</strong></td><td><strong>Accepted Badge</strong></td><td>Displays the number of Resources who have Accepted the Appointment or Shift but are not yet confirmed.</td></tr><tr><td align="center"><strong>16</strong></td><td><strong>Confirmed Badge</strong></td><td>Displays the number of confirmed Resources currently allocated to the Appointment or Shift.</td></tr><tr><td align="center"><strong>17</strong></td><td><a href="#appointment-insights"><strong>Appointment Insights</strong></a></td><td>Provides further and more detailed matching information for each Resource, including matched and unmatched criteria. It also displays all Pending Resources related to the Appointment or Shift. <em>(Described further below)</em></td></tr><tr><td align="center"><strong>18</strong></td><td><a href="#manually-assign-resources"><strong>Manual Assignment</strong></a></td><td>Allows manual selection or replacement of Resources from the Appointment or Shift using Maica's Find Resource modal. <em>(Described further below)</em></td></tr><tr><td align="center"><strong>19</strong></td><td><strong>Undo</strong></td><td>Reverts to the last Optimisation for the selected Appointment or Shift.</td></tr><tr><td align="center"><strong>20</strong></td><td><strong>Cancel</strong></td><td>Exits the Optimiser without saving any changes made during the current session. A confirmation modal will appear before closing.</td></tr><tr><td align="center"><strong>21</strong></td><td><strong>Confirm</strong></td><td>Saves all Optimisation results and applies them to the selected Appointments or Shifts. Once confirmed, a summary screen will display all changes made during the session.<br><br><em>Please note, while using the Optimiser, no records are updated in Maica until <strong>Confirm</strong> is selected. Any changes made prior to confirmation exist only within the Optimiser session.</em></td></tr></tbody></table>

Please refer to the sections below for further detail on the above described Optimiser parts:&#x20;

{% hint style="info" %}
Please note: The Resource Pool, Ranking Criteria and Optimiser Settings are respected by both Optimisation Runs and Broadcasting Runs.
{% endhint %}

### Resource Pool&#x20;

The **Resource Pool** is used to define a smaller, more relevant group of Resources for optimisation or broadcasting.\
Only Resources matching the criteria added to the pool will be considered when running either of the above mentioned methods.

To configure the Resource Pool:

1. Click **Add Criteria**.
2. A new filter row will appear where you can specify the **Field**, **Operator**, and **Value**.
3. Multiple criteria can be added to refine the pool further.
4. Each added criterion is combined with an **AND** condition, meaning all must be met for a Resource to be included.

**Understanding Filter Components**

Each criterion is made up of three components:

<table><thead><tr><th width="140.259765625">Component</th><th>Description</th></tr></thead><tbody><tr><td><strong>Field</strong></td><td>Defines which field the Optimiser will evaluate. Fields are grouped under <strong>Resource</strong> or <strong>Skill</strong> objects. <br><br>Examples include <em>Resource → Work Type</em>, <em>Resource → Gender</em>, or <em>Skill → Certificate</em>.</td></tr><tr><td><strong>Operator</strong></td><td>Determines how the value is compared to the field. Common operators include <em>equals</em>, <em>not equal to</em>, <em>contains</em>, and <em>does not contain</em>. The Operator value is refined depending on the selected Field. </td></tr><tr><td><strong>Value</strong></td><td>The specific value being matched against the field. This may be a picklist option, text entry, or date, depending on the selected field. For example, if <em>Resource → Gender</em> is chosen, available values might be <em>Man</em> or <em>Woman</em>.</td></tr></tbody></table>

**Example:** Adding the criterion *Resource → Work Type equals Full-Time* limits the pool to only full-time staff. Adding an additional rule such as *Skill → Certificate IV in Disability* will further narrow the pool so that only full-time staff who hold that qualification are considered.

{% hint style="success" %}
The **Current Pool** count shows how many Resources meet all applied criteria.
{% endhint %}

{% hint style="info" %}
The Resource Pool does not impact the order of Resource ranking — only which Resources are included for evaluation.
{% endhint %}

### Ranking Criteria&#x20;

Unlike the Resource Pool, the **Ranking Criteria** controls how Resources are scored and prioritised when compared against Appointments or Shifts. It uses the same **Add Criteria** process as described in the **Resource Pool** section above, but serves a different function.

{% hint style="success" %}
While the **Resource Pool** determines *who* is eligible to be considered, the **Ranking Criteria** determines *how well* those Resources match the Appointment or Shift once they are included.
{% endhint %}

When Ranking Criteria is applied:

* A Resource must meet **at least one** of the criteria to be included in the Optimiser run.
* If a Resource meets **none** of the criteria, they are **excluded** entirely.
* Resources who meet **one or more** criteria are included and then **ranked** based on the number of criteria they satisfy.
* A Resource who meets more criteria will rank higher than a Resource who meets fewer.

Ranking Criteria therefore acts as both:

1. An *inclusion rule* (must meet at least one), and
2. A *prioritisation rule* (more matches = stronger candidate).

#### Example 1:&#x20;

**Criterion:** `Resource → Gender equals Woman`

* Any Resource who identifies as a Woman will be included and receive scoring contribution for this rule.
* Any Resource who does *not* match this rule receives **zero** for this criterion and is **excluded** from automated selection.

#### **Example 2: Two Different Criteria**

**Criteria added:**

1. `Resource → Region equals East Metro`
2. `Resource → Language contains Mandarin`

Here is how Resources are treated:

| Resource | Matches Region? | Matches Language? | Included? | Relative Ranking       |
| -------- | --------------- | ----------------- | --------- | ---------------------- |
| Worker A | ✔               | ✔                 | ✔         | Highest (matches both) |
| Worker B | ✔               | ✖                 | ✔         | Medium (matches one)   |
| Worker C | ✖               | ✔                 | ✔         | Medium (matches one)   |
| Worker D | ✖               | ✖                 | **✖**     | **Excluded**           |

**Key behaviour:**

* Worker A ranks highest because they meet **two** criteria.
* Workers B and C rank below Worker A because they meet **only one**.
* Worker D is **excluded** because they meet none.

{% hint style="info" %}
Removing or changing Ranking Criteria only affects optimisation runs with that criteria applied, it has no impact on previously optimised records.
{% endhint %}

### Optimiser Settings&#x20;

#### Matching Score Importance Level&#x20;

The **Matching Score Importance Level** determines how much influence each category has on the Resource’s overall matching score. The total of all categories must equal **100%**, and each category’s weight can be adjusted manually to prioritise what matters most to your organisation.

The categories are defined below:&#x20;

<table><thead><tr><th width="125.71875">Category</th><th>Description</th></tr></thead><tbody><tr><td><strong>Skills</strong></td><td>Measures how many of the required Skills a Resource has compared with the total Skills needed. </td></tr><tr><td><strong>Availability</strong></td><td>Checks whether the Resource has enough Available hours on the relevant day to cover the Appointment or Shift. Any existing usage or unavailability is subtracted from the daily limit, and the remaining time is compared against the requirement. The resulting score is weighted by the Availability percentage.</td></tr><tr><td><strong>Workload</strong></td><td>Evaluates weekly capacity by comparing the required minutes for the Appointment or Shift plus the Resource’s current scheduled hours against their fortnightly limit. The result is scaled by the Workload importance percentage.</td></tr><tr><td><strong>Attributes</strong></td><td>Counts how many requested Attributes a Resource satisfies (for example, gender, language, or experience).</td></tr><tr><td><strong>Travel</strong></td><td>Scores proximity by comparing the Resource’s distance to the Appointment location against the closest candidate. Resources co-located or nearest to the site receive the highest score, weighted by the Travel importance percentage.</td></tr></tbody></table>

{% hint style="info" %}
For example, if *Attributes* and *Skills* are set to 40% each, and *Travel* is set to 0%, the Optimiser will focus almost entirely on matching qualities and skill requirements, ignoring distance as a factor.
{% endhint %}

{% hint style="warning" %}
Please note, weighting does not filter Resources — it influences *how strongly* each matching criterion affects the total score.
{% endhint %}

#### Only use allocated Resources&#x20;

This Setting restricts Optimisation to Resources who already have a defined relationship with the Participant. Meaning, only Resources who are a [Participant Resource](/maica-knowledge-base/participants/participant-profile.md#participant-resources) to the allocated Participants on the Appointment or Shift will be considered.&#x20;

#### How Travel Scoring Works

The **Travel** category within the Matching Score evaluates how close each Resource is to the Appointment location. It is one of the most valued scoring categories for organisations with mobile workforces, as it directly impacts travel time, cost, and scheduling efficiency.

This section explains the full mechanics of the Travel score, including prerequisites, how each Resource's origin location is determined, and how the final score is calculated.

#### Prerequisites

For Travel scoring to be active, the following must be true:

{% stepper %}
{% step %}
**The Appointment must have a Location set**

This can be a Location record, a Participant Location, or a Manual Entry address. Without a destination address, the system has no reference point to measure distance and **all Resources will receive a Travel score of 0%**.
{% endstep %}

{% step %}
**A valid Google API Key must be configured**

This must be configured in Settings > Maps Management. The system geocodes the Appointment address using Google to obtain latitude and longitude coordinates.
{% endstep %}

{% step %}
**The Travel importance percentage must be greater than 0%**

This must be set in the Matching Score Importance Level settings. If set to 0%, Travel is excluded from the overall score entirely.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
If you open the Resource Finder or Optimiser before setting a Location on the Appointment, the Travel score will not be calculated. Always set the Location first, then proceed to Resource selection.
{% endhint %}

#### How the Appointment Location is Resolved

The system resolves the Appointment's destination address based on its **Location Type**:

| Location Type            | Address Source                                                                                                                                           |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Location**             | The address from the linked Location record. If the Location record has no address stored, Maica queries the record directly for its `Location Address`. |
| **Participant Location** | The `Participant Location` field on the Appointment.                                                                                                     |
| **Manual Entry**         | A concatenation of the `Street`, `City`, `State`, and `Postal Code` fields on the Appointment.                                                           |

Once resolved, the address is sent to Google's geocoding service to obtain precise latitude and longitude coordinates. If this geocoding call fails or the address cannot be resolved, Travel scoring is skipped for the entire run.

#### How Each Resource's Origin Location is Determined

Each Resource's starting location is determined by the **Default Origin/Destination Order** setting, found in **Settings > Maps Management**. This setting defines a prioritised list of location sources. The system tries each option in order and uses the **first one that resolves to a valid geolocation** for that Resource.

The configurable options are:

<table><thead><tr><th width="70.92578125" align="center">Priority</th><th width="221.095703125">Option</th><th width="146.650390625">Label</th><th>Description</th></tr></thead><tbody><tr><td align="center">1</td><td><code>appointmentAddress</code></td><td><strong>Previous/Next Appointment</strong></td><td>The location of the Resource's most recent Appointment <em>earlier on the same day</em> as the new Appointment. This reflects where the Resource will actually be coming from in a back-to-back scheduling scenario. The system queries the Resource's Appointment Resources for the closest prior appointment on that calendar day.</td></tr><tr><td align="center">2</td><td><code>primaryLocationAddress</code></td><td><strong>Primary Location</strong></td><td>The geolocation of the Resource's linked Primary Location record (e.g. their usual office, hub, or base).</td></tr><tr><td align="center">3</td><td><code>homeAddress</code></td><td><strong>Home Address</strong></td><td>The geolocation stored directly on the Resource record (sourced from their address fields).</td></tr><tr><td align="center">4</td><td><code>currentLocation</code></td><td><strong>Current Location</strong></td><td>The Resource's live browser-based GPS location. <strong>Note:</strong> This option is only available in the client-side Travel Management modal and is <strong>not used</strong> in server-side scoring within the Resource Finder or Optimiser.</td></tr></tbody></table>

The **default priority order** is: `appointmentAddress > primaryLocationAddress > homeAddress > currentLocation`.

{% hint style="info" %}
The priority order is fully configurable. For example, if your organisation always wants to measure distance from the Resource's Primary Location regardless of their daily schedule, you can reorder the list in Maps Management to place `primaryLocationAddress` first.
{% endhint %}

{% hint style="warning" %}
If none of the configured options resolve to a valid geolocation for a given Resource (e.g. no same-day prior appointment, no Primary Location, and no Home Address on record), that Resource will display **"Location not found"** and will not receive a Travel score.
{% endhint %}

**Example:** A Resource has a confirmed Appointment at "SIL - Armadale" earlier in the day, and their Primary Location is "Senses Hub - Burswood". Using the default origin order, the system will use the Armadale appointment location as their origin (since `appointmentAddress` is first in priority), rather than the Burswood hub. If there were no same-day prior appointment, it would fall back to the Burswood hub location instead.

#### How the Travel Score is Calculated

The Travel score uses a **relative scoring model**. Rather than scoring Resources against a fixed distance threshold, it compares all Resources against each other:

{% stepper %}
{% step %}
**Calculate distance**

The system calculates the **straight-line distance in kilometres** between each Resource's resolved origin and the Appointment's geocoded location.
{% endstep %}

{% step %}
**Identify the closest Resource**

It identifies the **minimum distance** (the closest Resource).
{% endstep %}

{% step %}
**Calculate the score**

Each Resource is scored as a ratio: `Score = Minimum Distance / Resource Distance`.
{% endstep %}
{% endstepper %}

This means:

* The **closest Resource** always receives **100%** for Travel.
* A Resource **twice as far** as the closest receives **50%**.
* A Resource **co-located** with the Appointment (distance = 0) receives **100%**.
* A Resource with no resolvable location receives **no score** and displays "Location not found".

The resulting percentage is then multiplied by the **Travel importance weighting** to determine its contribution to the overall matching score.

**Example:**

<table><thead><tr><th width="145.3330078125">Resource</th><th align="center">Distance to Appointment</th><th align="center">Travel Score</th></tr></thead><tbody><tr><td>Worker A</td><td align="center">5 km (closest)</td><td align="center">100%</td></tr><tr><td>Worker B</td><td align="center">10 km</td><td align="center">50%</td></tr><tr><td>Worker C</td><td align="center">25 km</td><td align="center">20%</td></tr><tr><td>Worker D</td><td align="center">Location not found</td><td align="center">No score</td></tr></tbody></table>

If the Travel importance is set to **20%**, Worker A contributes 20% to their overall score from Travel, Worker B contributes 10%, and Worker C contributes 4%.

{% hint style="info" %}
The Travel score is especially useful when combined with other criteria. For example, setting Skills to 40%, Availability to 30%, Workload to 10%, and Travel to 20% gives a balanced view where proximity is considered but does not override qualifications and availability.
{% endhint %}

### Resource Column&#x20;

The **Resources** column displays all Resources linked to each Appointment or Shift within the Optimiser. Each Resource is represented by a status indicator (colour and outline) showing their current state in the optimisation or confirmation process. From this column, users can view, update, or manage Resource statuses using the available actions.

#### Resource Statuses

Each Resource is displayed as a pill with a distinct border colour and style to indicate its current status.

<table><thead><tr><th width="141.373046875">Status </th><th width="149.8603515625">Visual Indicator </th><th>Description </th></tr></thead><tbody><tr><td><strong>Confirmed</strong></td><td>Black outline</td><td>Indicates that the Resource has been confirmed for the Appointment or Shift. Confirmed Resources will be applied to the record once the Optimiser session is confirmed.</td></tr><tr><td><strong>Accepted</strong></td><td>Yellow outline</td><td>Indicates that the Resource has accepted an allocation but is not yet confirmed. These Resources are awaiting user confirmation. </td></tr><tr><td><strong>Pending</strong></td><td>Blue outline</td><td>Shows that a Resource has been requested but has not yet responded. Pending Resources may later accept or decline. </td></tr><tr><td><strong>Declined</strong></td><td>Red outline</td><td>Indicates that the Resource declined the allocation. The Resource remains visible until manually removed or withdrawn.</td></tr><tr><td><strong>Withdrawn</strong></td><td>Greyed out</td><td>Represents a Resource that has been withdrawn from the Appointment or Shift. </td></tr></tbody></table>

#### Available Actions&#x20;

Each Resource pill includes a dropdown menu providing context-sensitive actions. The available actions depend on the Resource’s current status.

| Action       | Description                                                                                                              | Available When                                                                         |
| ------------ | ------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- |
| **Confirm**  | Marks the Resource as confirmed for the Appointment or Shift. Once confirmed, the outline changes to black.              | Available for Resources with *Pending, Withdrawn, Declined* or *Accepted* status.      |
| **Decline**  | Marks the Resource as having declined the allocation. The outline changes to red.                                        | Available for Resources with *Pending, Withdrawn, Confirmed* or *Accepted* status.     |
| **Withdraw** | Withdraws a previously confirmed or accepted Resource. The pill becomes greyed out.                                      | Available for Resources with *Confirmed*, *Accepted*, *Pending*, or *Declined* status. |
| **Remove**   | Removes the Resource from the Appointment or Shift entirely. This deletes the pill from the record within the Optimiser. | Available for all statuses.                                                            |

#### Example Scenarios&#x20;

| Scenario                                             | Starting Status   | Action Taken               | Result                                                         |
| ---------------------------------------------------- | ----------------- | -------------------------- | -------------------------------------------------------------- |
| A previously confirmed Resource becomes unavailable. | Confirmed (black) | User selects **Withdraw**. | Resource becomes *Withdrawn* (greyed out).                     |
| A declined Resource is no longer relevant.           | Declined (red)    | User selects **Remove**.   | Resource pill is removed from the Appointment.                 |
| A previously unavailable Resource becomes available. | Declined (red)    | User selects **Confirm**.  | Resource becomes *Confirmed* and allocated to the Appointment. |

### Appointment Insights&#x20;

The Appointment Insights modal is available for each Appointment or Shift, and is better used after the Optimiser has been run. It can be accessed by expanding the record and selecting the **Insights** icon.

The table below details the fields on each Insight:

<table><thead><tr><th width="222.232421875">Field </th><th>Description </th></tr></thead><tbody><tr><td><strong>Appointment ID and Time</strong></td><td>Displays the unique Appointment or Shift identifier and its scheduled start and end time.</td></tr><tr><td><strong>Location</strong></td><td>Shows the Appointment or Shift location or Note (e.g. <em>The Appointment is happening online</em>).</td></tr><tr><td><strong>Pending Resources</strong></td><td><em>This is a Broadcasting function, coming to Maica shortly.</em> </td></tr><tr><td><strong>Overall Matching Score</strong></td><td>Displays a percentage score showing how closely the Resource matches the Appointment or Shift. The score combines all weighted categories (Availability, Workload, Skills, Attributes, and Travel). <br><br>Note, you can click the score to see a further breakdown of each category, as well as switch between any Resources allocated to the Appointment or Shift. </td></tr><tr><td><strong>Matched Criteria</strong></td><td>Lists all conditions where the Resource met the Optimiser’s requirements. Each entry includes a short description explaining the match, for example: <em>Available for scheduled time</em> or <em>Within weekly limit</em>.</td></tr><tr><td><strong>Unmatched Criteria</strong></td><td>Lists any conditions not met by the Resource, preventing a full match. For example: <em>Skill missing – Certificate IV in Disability</em> or <em>Travel distance exceeds defined range</em>.</td></tr></tbody></table>

### Manually Assign Resources&#x20;

The **Manual Assignment** function allows users to select or replace Resources for an Appointment or Shift directly within the Optimiser. It provides full control over Resource allocation without rerunning the optimisation process.

{% hint style="info" %}
You can also launch Broadcasting from within the Find Resource modal. Doing so, will pre populate the selected Resource in the Manual Selection field of the Broadcast run and ensure they are one of, or the only, Resource to receive an offer.&#x20;
{% endhint %}

Manual Assignment uses the [**Find Resource**](/maica-knowledge-base/appointments/create-an-appointment/smart-selection-filter.md) modal to display all eligible Resources that meet the Optimiser’s current configuration. Each Resource is shown with a corresponding **Overall Matching Score**, allowing users to make informed selections based on the same scoring logic used by automated optimisation.

{% hint style="info" %}
To learn more about the Find Resource modal, please [click here](/maica-knowledge-base/appointments/create-an-appointment/smart-selection-filter.md).&#x20;
{% endhint %}

{% hint style="success" %}
Please note, opening the Find Resource respects the defined Resource Pool in the Optimiser. Meaning, if you set *Resource → Work Type equals Full-Time,* then opening the Find Resource modal will only show Full-Time staff.
{% endhint %}

#### **How Manual Assignment Works**

1. Click the **Resource Column** in the Optimiser to open the **Find Resource** modal.
2. Review the list of available Resources and their matching scores. These will be ordered by the assigned Resources, followed by the most suitable remaining Resources.&#x20;
3. Use the **Search Bar** or **Sort By** options to locate preferred Resources.
4. Tick the checkbox beside each Resource you wish to assign.
5. Click **Confirm** to save your selection within the Optimiser session.
6. The Appointment or Shift will display the newly assigned Resource(s) once the modal closes.

#### Manual Assignment Scenarios&#x20;

<table><thead><tr><th width="138.748046875">Scenario</th><th>Configuration</th><th>Action</th><th>Outcome</th></tr></thead><tbody><tr><td><strong>1. Add extra Resource to a fully filled Appointment</strong></td><td>Appointment requires <strong>2 Resources</strong> and already has <strong>2 confirmed</strong>.</td><td>You manually select and add an additional Resource.</td><td>The new Resource is added as an <strong>extra allocation</strong> and displayed in the Optimiser. Maica allows you to do so if desired. </td></tr><tr><td><strong>2. Replace a confirmed Resource</strong></td><td>Appointment has <strong>1 confirmed Resource</strong> who is no longer available.</td><td>You open Manual Assignment, deselect the current Resource, and select another.</td><td>The new Resource replaces the previous one in the Optimiser view. Changes are not applied to the Appointment record until <strong>Confirm</strong> is selected.</td></tr><tr><td><strong>3. Add Resource to a partially filled Appointment</strong></td><td>Appointment requires <strong>2 Resources</strong> but currently has <strong>1 confirmed</strong>.</td><td>You select an additional Resource manually.</td><td>The Appointment now shows <strong>2 confirmed</strong> Resources and the record will be considered <strong>fully filled</strong> once confirmed.</td></tr><tr><td><strong>4. Assign multiple Resources at once</strong></td><td>Appointment has <strong>no Resources assigned</strong> and requires <strong>3</strong>.</td><td>You manually select three Resources from the list and confirm.</td><td>All three Resources are added simultaneously. The record will show as <strong>filled</strong> once confirmed on the main Optimiser screen.</td></tr><tr><td><strong>5. Add Resource who does not meet all criteria</strong></td><td>Appointment requires <strong>1 Resource</strong>; you select a Resource with a <strong>lower Matching Score</strong> (e.g. 40%).</td><td>The selected Resource is manually confirmed.</td><td>The Resource is still accepted. The Optimiser does not prevent manual overrides, allowing assignment even if some criteria are unmet.</td></tr><tr><td><strong>6. Cancel without confirming</strong></td><td>You open Manual Assignment and select Resources but then choose <strong>Cancel</strong>.</td><td>You cancel the selection.</td><td>No changes are saved. The Appointment or Shift remains in its previous state.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://knowledge.maica.com.au/maica-knowledge-base/the-planner/resource-optimiser.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.