Basic Details
Learn about capturing basic details for a new Shift
What does the Basic Details stage include?
The Basic Details tab captures the basic details of the Shift, as described in the below table:
This allows for the selection of Resource(s) by simply typing a name of a Resource (or multiple) or by clicking on the Filter icon which allows for Smart Selection of Resource(s).
This allows for the selection of Asset(s) by simply typing a name of a Asset (or multiple) or by clicking on the Filter icon which allows for Smart Selection of Asset(s).
Date & Time Details
The date and time details are pre-populated from the Planner so there is nothing to do for the user.
Shift Service
This allows for the selection of Shift Service(s). You can add an Shift Service by typing the name of the service, or by using any key words configured within the service. For example: If you were adding Support Coordination, you could type Support Coordination, or, advice.
Claim Type
This allows for the selection of a Claim Type by selecting one from the provided dropdown list.
Time Zone
When creating a new Shift, the timezone is automatically set & displayed based on the Salesforce user’s current browser timezone. This occurs before a Location is selected.
Auto Check-In for Appointments Within a Shift
In addition to the details capture above, when a Shift, Maica allows you to determine how Appointments within that Shift should be checked in. This is especially useful when working with Shifts that contain multiple Appointments, Maica allows the option for those Appointments to be checked in automatically when the Shift itself is checked in via the Desktop & Mobile Care Worker App.
This behaviour is controlled by a toggle at the Shift level and is designed to simplify the mobile check-in experience for long or continuous Shifts while still allowing appointment-level control where required. To learn more, see below.
Configuring Auto Check-In on a Shift
When creating or editing a Shift, you can determine how Appointments within that Shift should be checked in via the toggle within the Basic Details stage.
If Auto Check-In for Appointments is enabled:
Appointments linked to the Shift will be checked in automatically when the Shift is checked in on the Mobile Care Worker App.
If the setting is disabled:
Appointments must be checked in individually, even if the Shift itself is checked in.
This setting is applied per Shift, allowing flexibility based on how services are delivered.
How Check-In Works for Appointments
Auto Check-In Enabled
When a care worker checks in to the Shift on the Mobile Care Worker App:
All Appointments linked to the Shift are automatically checked in
Appointment check-in times use the scheduled Appointment check-in and check-out times
No additional action is required by the care worker at the Appointment level
Auto Check-In Disabled
When auto check-in is not enabled:
Checking in to the Shift does not check in linked Appointments
Care workers must check in to each Appointment individually
This behaviour matches standard Appointment-level check-in requirements
This approach reduces repeated actions for care workers when:
A Shift contains multiple Appointments
Appointments are delivered continuously across a single Shift period
At the same time, it maintains full control for scenarios where Appointment-level check-ins are still required for compliance or operational reasons.
Example Scenarios
A Shift is scheduled from 9:00am–3:00pm with three linked Appointments and auto check-in enabled. The care worker checks in once to the Shift, and all three Appointments are checked in automatically.
A Shift contains multiple Appointments but auto check-in is not enabled. The care worker must check in to each Appointment individually, even after checking in to the Shift.
Things to look out for: Basic Details
1. Resource(s) have a Roster Mode conflict
This alert will show in the instance where the selected Resource(s) have a Roster Mode conflict and hence cannot be allocated to the proposed Shift. This is the only restriction that Maica enforces where the user cannot continue to create the Shift.
Roster Mode in Maica is used to define the behaviour and validation applied when scheduling Shifts for a Resource. When selecting a Roster Mode for a Resource, there are two selectable options. These are:
Appointment: This means Appointments can be scheduled at any time for a Resource provided it is within any active Availability record(s) if these exist. If no Availability record(s) exist, Appointments can be created at any time.Shift: This means Appointments can only be scheduled within a Shift that a Resource is part of and it is within any active Availability record(s) if these exist. If no Availability record(s) exist, Appointments still must fall within a Shift that the Resource is assigned to.
In order to resolve this alert, you must select Resource(s) that are set to a Roster Mode of Shift during the time of the proposed Shift.
You can set a Resource(s) Roster Mode on their Resource Profile, Availability Records, or by using a Global Setting in your Maica organisation for all Resource(s). To learn more, click the links.
It is important to note that if a Resource has a Roster Mode set on their Resource Record that is different to the Roster Mode set for a specific Availability Record, the Availability Record Mode will take precedent during the Availability period.
If No Availability Records are found and the Roster Mode is not set on the Resource Record: the Roster Mode for the Resource will be defined by the Global Roster Mode setting. This is configurable in the Maica Rostering Management settings.
2. Shift Allocation Incomplete
This alert will show in the instance where you have a different number of Resource(s) allocated compared to the specified Required number for the Shift. This will result in an incomplete Shift.
For example, if you have an incorrect required number of Resource(s), Maica will alert you with the following warning:
The Shift does not have the required number of Resources allocated.
In this instance, Maica will still allow you to continue to the next stage of creating your Shift. However, as mentioned, it will result in an unfulfilled Shift.
In order to resolve the Incomplete allocation alert, ensure that the number of selected Resource(s) match the specified required number. For example: If you only require 1 Resource for your Shift, ensure 1 is allocated, as shown below.
Last updated
Was this helpful?