In a medical setting, care is rarely confined to a single eight-hour window. Clusters are designed to mirror this reality by allowing you to group a series of related shifts and assign them to a single associate as a unified block. This ensures that the same clinician remains on a specific service for a set duration, which is vital for maintaining continuity of care and reducing hand-off risks.
Strategic Template Integration
When defining your team’s recurring rotations within a Mesh AI Template, you can designate specific shifts as a "cluster" over defined intervals. For example, if your department requires the same resident to cover a Friday-Saturday-Sunday "Weekend Block," clustering these shifts ensures they are never split between different people.
How the Autoscheduler Prioritizes Clusters
Once these groupings are established, the Mesh AI Autoscheduler treats them as high-priority constraints. Rather than viewing each shift as an isolated slot to fill, the system views the entire cluster as a single commitment. This significantly reduces manual adjustments and ensures the resulting schedule respects the logical flow of your medical team's workload.
To effectively implement shift clustering within your department, you must define three core parameters that dictate how the rotation logic will function. These elements ensure that the bundle of shifts aligns with your specific clinical cycle and hand-off requirements.
The Cluster Interval: Defining the Duration of Service
The interval represents the length of time a clinician remains responsible for the bundled shifts before the assignment rotates to a new member. This setting determines both the date range of the individual's commitment and the frequency at which the "baton" is passed. In many hospital settings, this is set to a seven-day interval to mirror weekly rotations, but it can be customized to fit any recurring block, such as a four-day "short-call" cycle or a monthly service rotation.
2. The Start Date: Anchoring the Rotation Cycle
To ensure the system assigns these blocks accurately, you must establish an anchor point known as the "Most Recent Start Date." This date tells the logic exactly when the hand-off occurs. For example, if your weekly service block always begins on a Monday morning, you would set the start date to the most recent Monday. This allows the system to calculate the correct timing for every subsequent interval, ensuring that the rotation always triggers on the intended day of the week regardless of the total interval length.
3. Included Shifts: Defining the Scope of Coverage
The final step is identifying the specific shifts from your template that constitute the cluster. Every shift included in this group is effectively "locked" to a single associate for the duration of the interval. This ensures that if a clinician is assigned to the primary service shift, they are also automatically assigned to the secondary or associated tasks (such as rounding or post-call documentation) within that same block. While these clusters automate the process, administrators always retain the ability to manually override or adjust individual shifts as needed for last-minute departmental changes.
Examples:
The same team member is on-call for an entire week (7-day cluster).
The member who is on-call on Fridays should also be on-call on Sundays (7-day cluster).
There is a nurse shift every day, and members who are assigned these shifts must work in three-day rotations (3-day cluster).


