This is the multi-page printable view of this section. Click here to print.
An effective on-call schedule must be flexible and ensure that on-call shifts fit around other commitments in each team members life.
On-Call Optimizer takes the hassle out of maintaining flexible on-call schedules and provides a foundation for teams to experience an on-call environment that delivers growth in expertise.
The core object in On-Call Optimizer.
The main role of the schedule is to contain a list of shifts which describe which member(s) are expected to be on-call at a particular point in time.
To achieve this goal each schedule contains a set of configuration details in addition to the list of shifts. These configuration details are used by On-Call Optimizer to regularly extend the list of shifts into the future to maintain a desired horizon.
Each set of new shifts generated by On-Call Optimizer is referred to as an assignment, described further below. The collection of assignments associated with a schedule collectively describe the history and future shifts for the schedule.
Advanced configurations of On-Call Optimizer make use of inter-schedule relationships to achieve more complex scheduling outcomes than are possible within a single schedule.
Schedules can be configured with source and destination integrations in order to keep their configuration and assignments synchronized with external systems (e.g. On-Call Products such as PagerDuty or Ops Genie).
Maintaining a balance of shifts between members of a schedule is one of the primary objectives that On-Call Optimizer targets. On-Call Optimizer considers a schedule to be balanced when each member has fair share of the total number of shifts.
See the Schedule Balance page for detailed information on how balance and fairness is calculated and reported in On-Call Optimizer.
An on-call shift is a contiguous period with defined start and end times associated with one or more assignees. The start and end time of an on-call shift are measured to the minute only (no seconds component) and must be fully specified including a time zone.
The maximum length of a single on-call shift is one week.
On-Call Optimizer supports up to 2 assignees per shift referred to as the primary and secondary respectively.
Each schedule contains a list of shift configurations which describe how future shifts in the schedule are to be assigned. A shift configuration is made up of the time at which a shift in the schedule should start and who the desired assignee(s) for the shift should be.
On-Call Optimizer uses the shift configuration to generate the list of specific shifts with explicit start and end times when extending the schedule.
On-Call Optimizer can support almost any rotation configuration using a combination of basic and nested schedules:
nested schedule.On-Call Optimizer supports up to 3 levels of nesting.
Nesting provides an intuitive and straightforward method to configure rotations whenever there are two or more different groups of people or configurations to manage. Common examples of this would be rotating between two halves of a team on different sides of the world, or having only a subset of a team provide after-hours coverage for a schedule.
The configuration library contains multiple examples demonstrating how these simple combinations enable many diverse schedule structures to be created while remaining simple to undersatnd and configure.
A collection of shifts associated in some way with a schedule. The shifts in an assignment may not overlap at any point, and typically would represent a contiguous block of time, but under certain configurations (e.g. business hours only) there may be gaps where no shift or assignment is present.
On-Call Optimizer continually generates new assignments to maintain the schedule according to its configuration.
Assignments can exist in a number of states with defined roles, purposes and processes for moving between states. Please refer to the full assignment documentation for further details.
The quality of each assignment is evaluated by On-Call Optimizer based on how close to perfectly meeting every goal and constraint it reaches. When a perfect assignment is not able to be made, as set of penalties are reported to help explain the factors that impacted on the quality of the assignment.
Further details of how quality is evaluated and calculated can be found on the Assignments page.
The horizon of a schedule is counted in days and describes the level of visibiltiy into future assignments that is or should be provided by the schedule.
desired horizon, it describes how far in advance shifts
should be assigned, and therefore the minimum number of days of notice that members should receive prior to a shift
they are assigned to.current horizon, it describes how many days exist between a point
in time (typically the current date) and the end of the final shift that has been assigned in the scheduleThe schedule lifecycle documentation describes how On-Call Optimizer triggers assignment
of new shifts when the current horizon is about to fall below the desired horizon.
Horizon is a property of a schedule, not any particular member, and is calculated based on calendar days in the configured time zone of the schedule itself. A current horizon of zero indicates that the schedule’s assigned
shifts will end (or already ended before) today, while a current horizon of 1 day indicates that the final shift
in the currently assigned schedule ends tomorrow and so on.
The schedule window describes how many days of future shifts should be assigned at once when assigning new shifts during the lifecycle of the schedule. The configured window is also used as the default size for a new custom assignment.
By default the schedule window extends on from the final shift in the current schedule, but can be changed to start from a different date (so long as it is not in the future) when generating a custom assignment.
The history window describes how many past shifts are included when calculating the balance of the schedule.
On-Call Optimizer uses a 6-month history window, counting backwards from the start of the first shift in the new assignment.
The availability information for a schedule consists of the combination of both:
A schedule is composed of one or more assignments, which allocate members to shifts covering specific time periods.
The assignments for a schedule can be accessed in several locations:
The quality of an individual assignment describes how close to optimal the assignment algorithm was able to reach given the constraints of the schedule configuration and availability of the members.
The quality of an assignment is reported at the top of the assignment page where you will find a summary line containing details on the balance of the schedule and the quality of the assignment. The following icons and colours are used to provide a quick visual overview of the quality of the assignment:
When an optimal assignment cannot be found, a set of penalties are reported to describe each of the compromises that On-Call Optimizer had to make to find an viable assignment. These penalties are listed in the “Assignment Penalties” section of the assignment details page found either to the right of the assignment itself, or below the assignment when the screen is narrow.
For details on the types of penalties that can be reported, refer to the algorithm reference page.
The assignment concept is used throughout the lifecycle of a schedule leading to several different types of assignments.
The current assignment for a schedule is synonymous with the schedule itself and represents the canonical list of shifts describing which member is assigned at each point in time. There only ever exists a single current assignment per schedule and the current assignment is only ever modified through the assignment confirmation process.
On-Call Optimizer regularly generates new assignments to ensure the current assignment is extended into the future according to configuration of the schedule.
A pending assignment represents a list of shifts that are not yet confirmed but are being considered for addition to the schedule using one of the supported actions.
Pending assignments (if present, often there will not be any) are listed in the right-hand side bar of the schedule view underneath the details of the next planned assignment.
Pending assignments originate from several sources.
An automatic assignment is regularly generated by On-Call Optimizer during the lifecycle of the schedule to extend the current assignment based on the configured assignment parameters.
Automatic assignments are only able to use the Add Shifts action to confirm new shifts onto the end of the current assignment.
A custom assignment is created directly by a user. The starting date, number of shifts and the action that is used to confirm the custom assignment into the current assignment for the schedule are all able to be customized by the user.
An imported assignment holds shifts that originated and were assigned in an external system such as the on-call product linked to a schedule. When a link is created, On-Call Optimizer will import the history of prior shifts from the on-call product so they are available to help the assignment algorithm create assignments that balance across all members of the schedule.
Saved assignments record the history of how the schedule was built and has evolved over time. In simple cases each historical assignment can be matched directly to a subset of the schedule (more specifically to a subset of the current assignment of the schedule), however in more complex cases where the schedule has been re-assigned or individual shift swaps have occurred it is possible that none of the shifts from a saved assignment remain in the current schedule.
A pending assignment must select one of the following actions to determine how the current assignment is updated when the assignment is confirmed.
The pending shifts are added directly to the existing list of shifts in the current assignment. The combined list is sorted by start time. This action will fail if any of pending shifts overlap with or attempt to re-assign any of the existing shifts in the schedule.
The Add Shifts action is the only action used for any assignment initiated by On-Call Optimizer, such as extending the schedule with new shifts or importing shifts from an external source. Authorized users may also use the Add Shifts action when confirming a Custom Assignment.
The action will not modify the end time of any existing shifts and will therefore create a gap in the schedule if the start time of the earliest pending shift does not exactly match the end time of an existing shift.
This action is useful when the desire is to re-assigning all shifts after a particular date/time. This action will not be used by any assignment created by On-Call Optimizer, but may be specified by authorized users when confirming a Custom Assignment.
The action will not modify the start or end time of any existing shifts and will therefore create a gap in the schedule if the start and/or end times of the pending shifts do not exactly match the start/end times of any surrounding existing shifts.
This action is useful when the desire is to re-assign a small set of shifts (including just a single shift), such as in the case of taking-over or swapping shifts. This action will not be used by any assignment created by On-Call Optimizer, but may be specified by authorized users when confirming a Custom Assignment.
The process of confirming an assignment involves the following steps, which are guaranteed to occur transactionally:
Time and tide wait for no one - On-Call Optimizer continuously monitors and assigns upcoming shifts to the best available members and ensures that any external destinations configured for the schedule remain synchronized with the assigned shifts.
How this occurs is easily understood as two processes that operate continuously, each checking the current state and taking any necessary actions to move towards the desired state at any time where a difference between two two states (current and desired) is detected.
The automatic assignment process is responsible for ensuring the number of future shifts assigned for the schedule always remains above the desired horizon.
During typical conditions, the current horizon (the end time of the final shift assigned in the schedule) is compared to the desired horizon and a new assignment is triggered whenever the current horizon is about to fall below the desired value.
The date the next automated assignment will fall due and the shifts that will be assigned at that time are visible in the Schedule Details side-bar on the right-hand side of each schedule.
The action taken once a new automatic assignment has been generated depend on the configuration of the Require manual confirmation? configuration setting for the schedule:
A newly created schedule may not have any existing shifts from which the current horizon and therefore the due date for the next assignment can be calculated! To address this, all schedules are created with a configured start date in the future.
Prior to the start date no shifts are eligble for auto-assignment, and the start date itself is used instead of the the end time of the latest assigned shift when calculating the current horizon of the schedule.
This means that the first assignment for new schedules will occur N days prior to the configured start date, where N matches the desired horizon configuration of the schedule.
No further automatic assignment actions are undertaken while a previous automatic assignment is awaiting review. If this review does not happen promptly the schedule becomes at risk of members not receiving the desired horizon window of notification before their newly assigned shifts, or in the worst case, the schedule could run out of shifts entirely.
Setting the start date to a future date at any time after the schedule has been created will result in the first assignment logic described above being triggered again - while the start date is in the future, it will be used as the basis for calculating the horizon when no other shifts exists. This can be used to cause On-Call Optimizer to skip assignment of shifts for a period of time if desired.
The external synchronization process is responsible for importing and exporting information about a schedule from configured external systems.
For schedules configured with a link to an external On-Call Product, the following configuration details for the schedule will be regularly updated with the external values:
All other configuration details including the shift configuration, cross-schedule availability, destinations and automatic assignment configuration are not changed by this process.
Each configured destination is provided with new information whenever a new assignment is confirmed. Refer to the destinations documentation for further details.
The availability information for each member of the schedule is refreshed every hour and cached ready for use in any future assignments.
The balance of shifts between members of a schedule is one of the primary objectives that On-Call Optimizer targets.
On-Call Optimizer considers a schedule to be balanced when each member has a share of the total number of shifts that is proportional to the time at which they were added to the schedule.
This means that the target number of shifts for each member in the schedule will often differ - members who joined the schedule around the same time will have similar targets, but the target will vary between members who have joined the schedule at a later date.
Statistics describing the balance of the schedule are available for the current assignment - showing the live state of the schedule, and can also be viewed when creating new custom assignments or examining the history of a particular assignment - showing a snapshot view of how that assignment altered, or will alter the balance of the schedule when it is or was confirmed.
At the top of each assignment page you will find a summary line containing details on the balance of the schedule and the quality of the assignment. The following icons and colours are used to provide a quick visual overview of the status of the schedule balance:
The live balance of a schedule will be displayed when viewing the current assignment for a schedule using a table similar to the one shown here. For each member the following information is shown:
Completed - the number of shifts already completed by the member (any shift currently in progress is counted as completed in this table).Upcoming - the number of shifts that have been confirmed for the member in future assignments.Total - the total number of completed and upcoming shifts assigned to the member.Target - the number of shifts that the member should be assigned, based on the the number of assignable members in the schedule and when they joined.Excess - the number of shifts that the member’s total is in excess of their target.The impact of an individual assignment on the balance of a schedule can be seen on the assignment details page both before the assignment is confirmed and afterwards.
The balance table shown for an individual assignment is very similar to the example for the live balance above, except that the the Completed and Upcoming columns
are replaced with Previous and New columns instead:
Previous - the number of shifts already assigned to the member (may be completed or upcoming) which are not changing in the assignment.New - the number of additional shifts that will be assigned to the member when the assignment is confirmed.Total - the total number of previous and new shifts that will be assigned to the member when the assignment is confirmed.Target - the number of shifts that the member should be assigned at the time when the assignment is confirmed.Excess - the number of shifts that the member’s total is in excess of their target.Unlike the live balance shown for the current assignment, the balance statistics shown for an individual assignment are a snapshot of the balance of the schedule at the point in time when the assignment was generated or confirmed.
The balance for a schedule is calculated and tracked individually for each type of shift in the schedule. Shift types follow directly from the Shift Configuration of the schedule and are described by the day and time at which the shift starts, combined with its duration. The role (primary, secondary, etc) assigned forms the final component of a shift type, to ensure members are assigned a proportionate number of shifts for each role.
The numbers reported in the balance tables count the number of shifts of each type assigned to a member and will therefore represent different lengths of time. In the balance table for a daily shift, a value of 1.0 would represent 24 hours, while in the table for a weekly shift a value of 1.0 would represent 168 hours.
Fractional shift numbers will arise in a number of situations, commonly including:
The balance for a schedule is calculated from the earliest shift contained within the history window (6 months in the past) until the final future shift that has been assigned.
Even when displayed in the context of an individual assignment that may only be covering a few days of time, the balance reported is for the schedule over the entire window.
The configuration of a schedule controls how On-Call Optimizer will behaviour throughout its lifecycle and is broken into several sections as described below.
The basic configuration includes the following details:
For schedules linked to a external On-Call Product the basic configuration is not editable and will be automatically synchronized from the external schedule. However you can still modify whether or not each individual member is invited to share their calendar with the schedule.
For schedules not linked to an external product up to 20 members can be added. The name of a member must be an email address in order to invite the member to share and for the schedule to subsequently receive availability information from the member.
When adding a member by email address, On-Call Optimizer will by default to sending an invitation to join the schedule and share their calendar availabilty
data. To prevent an invitation being sent, uncheck the box for the member’s row before clicking the Create or Update button at the bottom of the page.
The first and second columns of the members table will show the invitation and calendar availability state for each previously invited member of the schedule. A description of each state can be shown by hovering over the icon(s) for any particular member.
The shift configuration describes how On-Call Optimizer will generate future shifts for the schedule. Up to 10 shifts may be configured on a schedule. The available configuration fields for each shift are:
Daily, Weekdays, Weekends.Valid values for the assignee fields are either a static member of the schedule or one of the following keywords:
BEST_MEMBER to request automatic assignment.LAST_PRIMARY to request assignment of the member who was primary in the last shift.[Not assigned] to request that no member be assigned to this role in the shift.The Day, Hour and Minute fields describe when each new shift will start. The Primary/Secondary Assignee fields describe who, or how On-Call Optimizer will choose to, assign to each shift.
The [Not assigned] keyword is typically used in the secondary field when only a single assignee is required for the shift, however it can also be used in the primary
field when you wish to configure a schedule with non-continuous assignments (e.g. only create shifts for business hours Monday to Friday). The only restriction is that at
least one of the shift configurations must contain an assignee - there’s no point asking On-Call Optimizer to manage a schedule to which no-one is every assigned!
Use to the example configs to further understand how shift configurations can be combined to achieve a variety of different schedule types and configurations, or for detailed information consult the extension logic, and assignment algorithm reference.
The auto assignment configuration (located in the right side-bar) controls how On-Call Optimizer will maintain and extend the schedule with new assigments through the following parameters:
New schedules are created with manual confirmation enabled, but it is recommended to disable manual confirmation once the schedule has reached steady state and members are comfortable with how On-Call Optimizer is operating.
The rationale for this choice is that when first adopting dynamic scheduling it is not uncommon for members to need a few iterations of assignments to establish the patterns and habits of providing availability information, and therefore the ability to review (and potentially re-generate) each automatic assignment before it is confirmed can be useful.
However, once team members are comfortable with the generated assignments and a pattern of usage with On-Call Optimizer has been established, the effort of reviewing each new assignment is harder to justify and delayed, or forgotten approval of an assignment risks reducing the horizon of the schedule below the desired value, or in the worst case causing the schedule to run out of assigned shifts!
The schedule window should usally be kept above 20 days to ensure sufficient shifts to optimize over are present in each assignment.
It is also important not set the schedule window too large either to ensure availability information is available for all members for the time period covered by the window. Large schedule windows risk scheduling shifts beyond the date where where members are comfortable maintaining their calendar availability details in advance.
The default values for the horizon and schedule window are both 30 days which has been found to work well for many schedules in practice. This provides at lesat 1 month notice for each new shift that is assigned to a member and results in the available horizon for the schedule following a sawtooth pattern between 60 days immediately following each new assignment, and then gradually reducing to 30 days over time until the configured horizon is reached and the next assignment is triggered.
The horizon can be lowered as far as the team members are comfortable with without any adverse impact on the quality of assignments - the only impact of a low horizon is less notification for each member before a shift.
The cross-schedule availability configuration can be used to automatically generate availability information for a schedule based on the assignments that are present in another schedule.
The availabilty information generated by cross-schedule availability configuration will be used with the same weight and purposes as availability information that has been individually supplied by members from their calendars.
Configuring cross-schedule availability requires 3 pieces of information:
Configuring cross-schedule availability creates a dependency on the source schedule which requires that it has been assigned prior to the schedule that is depending on it. Attempts to assign new shifts for a schedule which has a cross-schedule availability dependency on a source schedule which does not yet have assignments covering the dates of the requested assignment will fail as the source shifts needed to generate the availability entries required by the configuration do not exist.
Therefore when configuring cross-schedule availability you need to double-check that the horizon and schedule window settings for the source schedule are appropriately set to ensure it is always assigned before the schedule depending on it.
The destination configuration describes the set of integrations that should be updated with the assignments for the schedule. The available configuration parameters for a destination are:
See the destinations topic for further details.
On-Call Optimizer supports the export of schedule information (assigned shifts) to external integrations which are referred to as the destinations of a schedule.
Currently On-Call Optimizer can be configured with any of the supported On-Call Products as a destination for a schedule. Support for other destination types (e.g. calendars) will be added in due course.
On-Call Optimizer provides a list of shifts, each consisting of a single assignee to each destination. In order to export a schedule containing both primary and secondary assignees, two destinations will need to be configured, one sourced from the primary assignee, the other sourced from the secondary assignee.
For each destination On-Call Optimizer tracks the timestamp until which the schedule has been exported (e.g. the end time of the latest shift that was successfull sent to the destination).
When configured for automatic export, the destination will be updated with new shifts after each new assignment is confirmed to the schedule. When automatic export is disabled, the destination will only be updated when an export is explicitly triggered via the user interface.
To trigger a destination export, click the “Export Now” button in the bottom of the Schedule Details sidebar for a schedule.
A status is reported for each destination as one of the following states:
Any destination reporting an Error or Warning status will cause the schedule to be reported in the corresponding state also.
On-Call Optimizer does not yet perform any ongoing synchronization or monitoring of the exported shifts, nor will changed shifts prior to the timestamp previously exported to the destination be re-exported if a future assignment modifies them in On-Call Optimizer.
Both the export timestamp and the reported status are affected by this limitation.
Unexpected changes in member availability are an inevitable fact of life. On-Call Optimizer assists schedule members to handle these events by co-ordinating the process of reassigning a future shift that the requesting member is no longer able to perform.
Members simply specify the shift they are unable to perform and then get back to other work.
In the background On-Call Optimizer takes care of notifying and checking with each other member of the schedule to determine whether they are willing and able to take the shift, and then when a willing member is found the schedule is automatically updated.
Eliminates significant time that would previously have been needed to manually arrange and configure the swap.
The members most likely to be able to accept the swap request are notified first as On-Call Optimizer is able to integrate the information already held for each member, including their blocks, preferences and the overall balance of the schedule, into the planning of the swap request.
Members can choose to simply take the requested shift without needing to swap one of their existing shifts in return, providing greater choice and flexibilty in how requests are resolved.
On-Call Optimizer ensures balance across the schedule is maintained by assigning fewer shifts to any member who has performed more than the expected share of shifts in future assignments.
The end result is simple, straightforward shift swaps with minimal time or hassle required from any member.
To initiate a request to swap a future shift, click the swap icon shown to the right of the shift when viewing the assignments for a schedule.
Before confirming the request you will have the opportunity to supply a short note which you can use to describe any information or details that will help other members determine whether they are able to accept the request as well as a deadline by which you would like to receive an answer to the swap request by.
Once you confirm the details of your swap request On-Call Optimizer will begin assembling an ordered list of members who are candidates for the swap.
When determining the ordering of members, On-Call Optimizer considers the same set of factors and weights as used in the automatic assignment algorithm including member availability, schedule balance and the distance between shifts for a member.
Members will be given a time window within which they can respond to the request. The length of time given to each member defaults to 8 working hours, but will be reduced as necessary in order to ensure that all remaining candidates can be given an opportunity to respond prior to the specified deadline.
When reducing the available response time window, On-Call Optimizer will not reduce the window below 4 working hours, but will instead increase the number of members allowed to have outstanding notifications to achieve the goal of giving all members an opportunity to respond prior to the specified deadline.
If no response has been received at the end of the time window allocated to a member, On-Call Optimizer will move on and notify further members of the schedule to request their response. Members who did not respond within their original time window are still able to respond at any point up until the request has been completed.
Once a response that causes the request to enter the accepted state is received (e.g. a Swap or Take action) no further members are notified. In cases where all members defer their response, or no response has been received and the deadline is approaching the request will enter a last chance state (described further below) in which all members are re-notified.
To respond to a swap request, the responding member must choose one of four available actions:
Take the shift, without swapping an existing shift. The requested shift will be reassigned to the member accepting the request. If this results in any imbalance between members in the schedule, it will be addressed by On-Call Optimizer assigning more/fewer shifts to the appropriate members in subsequent assignments.
Swap an existing shift. The responding member will be able to choose from a subset of their assigned future shifts that match the availability information of the requesting member (e.g. any assigned shifts that fall within a blocked time period will be unavailable as a swap target).
This option may be unavailable when the responding member has no assigned future shifts, all their assigned future shifts conflict with the requesting members availability, or none of their assigned shifts are considered equivalent to the partial shift being swapped.
Defer their response until all other members have responded. Indicating that they may consider taking the shift as a last resort, but would prefer another solution to be found if possible. On-Call Optimizer will re-notify members who deferred their response when the request enters into the last chance state. This option cannot be selected once the last chance state itself has been reached.
On-Call Optimizer will automatically select this option for any member whose availability information contains a block matching the requested shift. In this case, the member will not be notified of the request until it enters the last chance state in the case that all other members respond with a decline or defer response.
Decline the request. Indicating that they are unable to take the requested shift.
After selecting the desired action, an optional note to explain the response can also be provided.
Once you are happy with your selection and any note, click the Confirm Response button.
The first member to respond with a “Take” or “Swap” action will cause the request to be marked as accepted.
On-Call Optimizer supports swapping part of a larger shift. To use this functionality click on the
Edit start/end time button to the right of the Shift to Swap line when creating or editing a swap request
and select the desired start/end time (which must be within the original shift selected) for the swap request.
Responders will Other than the selection of candidate shifts for responders to swap described below, all other processing of partial swap requests is unchanged.
When responding to a swap request for a partial shift members will be presented with a list of equivalent partial shifts assigned to them that could be swapped with the requesting member. Depending on the details of the partial swap requested only a subset of the shifts assigned to the responding member may be considered equivalent and able to be swapped based on the criteria below.
If none of the member’s assigned shifts are considered equivalent
to the the partial swap request the Swap response will be unavailable, however the responding member can still
choose to Take the shift without a swap.
An assigned shift for a member is considered to be equivalent for a partial swap if it starts at the same shift configuration day and time and has the same duration as the base shift which the partial swap request originates from.
If the duration of the partial swap is less than 24 hours, weekdays are considered equivalent to each other when matching the start day between the requested partial swap and each potential equivalent shift assigned to the responder.
On-Call Optimizer supports swap requests that change the shift that is currently occuring which can arise in two ways:
When swapping the current shift On-Call Optimizer will immediately enter the last chance mode of processing and request an immediate response from all members of the schedule. When a member accepts the request the swap will begin from the next minute to allow time for synchronization with any configured destinations.
Each swap request passes through the following states
The request has been received and is being processed by On-Call Optimizer. Notifications to each candidate member will be sent in turn and all response actions are available to be chosen by any candidate member (including those who have not yet been notified, who may notice the request in the UI, etc).
Either a swap or an agreement to take the shift has been found and On-Call Optimizer is currently processing the required update(s) to the assignments of the schedule. Once a request has moved into the accepted state it cannot be changed. Other members are unable to respond in any way and the action cannot be reversed unless a subsequent swap request for the same shift is made after the current request reaches the completed state.
The requested shift (and the shift being swapped to if present) have been successfully reassigned in the current assignment of the schedule. The request and the swap are final. If future changes to the shift are required they must be made via further swap requests or custom assignments of the schedule.
The last chance state is entered when any of the following conditions are met:
When the last chance state is entered all members who have not explicitly declined the shift will be re-notified with the information that no-one has yet accepted the shift and their further response is now required.
If no responses are received during the last chance state, the request will become overdue once the deadline has passed. In this state, all members will have received at least one prior notification, but no member has accepted the request, and at least one member has not yet provided a response.
The request will remain in this state until it expires with On-Call Optimizer periodically reminding any members have not yet responded (including those that initially deferred their response) that the requesting member is still awaiting an answer.
These terminal states indicate that the request was unable to be completed, either because all candidate members explicitly declined the shift (Infeasible), or the start time of the shift was reached before any member accepted the shift (Expired).
Each member of a schedule in On-Call Optimizer has configurable properties and an associated role which determines the level of permissions with which they can interact with the schedule.
The boolean assignable property is configurable on each member of a schedule, regardless of role, and determines whether the member will be included in the assignment
of future shifts for the schedule. A typical use case for this property is to allow a user to manage a schedule without participating in the schedule themselves.
Schedule admins have full access to the schedule and can perform all actions available to members. The user who creates the schedule becomes the first schedule admin and can add further members as required. It is recommended to configure at least 2 admins per schedule.
Organization owned schedules are only deletable by a schedule admin when the Manage Schedules permission has been granted
to organization members. If this permission is not granted, the schedule will only be deleteable by organization admins.
Member is the default role for newly added members of a schedule. Members are able to make changes to the configuration and assignments of the schedule, but cannot remove or delete the schedule.
Members in the viewer role can participate fully in the schedule (including being assigned shifts), but are not able to make any changes to the schedule’s configuration or assignments.