Centralized Data: Holds all scheduling logic and organizational information specific to the clinician.

Flexible Access: Associates do not require a registered user account to be managed. Profiles can remain unlinked, allowing administrators to maintain full schedules for staff members who do not personally log in to Mesh AI.

Automation: When a block schedule is published, it automatically generates "Tours of Duty" in the corresponding clinical teams.

Precision: These tours carry specific characteristics, such as job qualifications or positions required for that specific rotation.

Scalability: Organizations can run multiple overlapping block schedules simultaneously to manage different cohorts (e.g., PGY-1s vs. PGY-3s).

Logic & Compliance: Each rotation carries predefined job qualifications and positions (e.g., Senior Resident or Trauma Qualified) for one or more teams.

Automation: When you publish a Block Schedule, the rotation automatically generates a Tour of Duty for the clinician. This tour matches the exact start and end dates of the block and applies the correct qualifications to the relevant teams.

Purpose: It ensures that as residents move between specialties, they are automatically granted the correct permissions and scheduling rules for their current clinical environment.

Template Integration: Template rows can be clustered together during the initial setup.

Draft Efficiency: In a draft schedule, selecting one shift in a cluster automatically selects all linked shifts, saving time on manual adjustments.

Autoscheduler Logic: The system ensures the same associate is assigned to every shift within a single cluster to maintain provider consistency.

Visual Identifiers: Clustered shifts are marked with a 'chain link' icon in draft schedules. Matching colors across these icons indicate which shifts belong to the same group.

Direct: A one-to-one transfer from one clinician (or an unassigned slot) to a specific associate.

Open: A single shift offered to the entire team. Depending on settings, these are either first-come-first-served or allow for multiple applicants, with an administrator selecting the recipient.

Proposed: A specific swap or transfer involving one or more shifts between multiple associates.

Open: A clinician offers up their shifts, allowing others to propose "takes" or "trades." You can limit this to one offer or allow multiple bids depending on your team's configuration.

Operational Unity: Groups allow administrators to plan and view multiple related teams (e.g., all Critical Care units) as a single cohesive unit.

Structural Flexibility: A team is not limited to one Group; it can belong to multiple groups simultaneously to accommodate complex organizational hierarchies.

Group-Level Planning: Each group can maintain its own specific block schedules.

Cascading Permissions: Administrative or associate permissions granted at the Group level cascade down to every team within that group, simplifying access management.

Definition: The specific task or role assigned (e.g., Consults, On-Call, Surgical First Assist, Ward Rounding, or Triage).

Eligibility: To ensure safety and proper scope of practice, associates must have matching job qualifications defined within their Tour of Duty to be assigned to these roles.

Definition: The set of verified skills (e.g., Intubation, ER Lead, or Senior Resident) attached to an associate’s profile.

Mesh AI Logic: These act as mandatory filters. The system—and the Autoscheduler—will only allow an associate to be assigned to a Job if they possess the matching qualification.

Usage: They prevent scheduling errors, such as assigning a junior trainee to a senior-only role or placing a clinician in a specialized unit (e.g., NICU) without the required certification.

Delivery Channels: Alerts can be received via mobile push notifications, SMS (text messages), and/or email.

Trigger Events: These are sent for critical scheduling actions, such as a published schedule, a newly approved deal, or a last-minute shift change.

User Control: Individual users have full autonomy to customize which types of alerts they receive and through which methods by visiting their User Settings page.

Scale: This may represent a single hospital, an independent clinic, or an entire cross-hospital health network.

Function: It serves as the master environment where global settings, such as job titles and organizational-wide policies, are established and managed.

Viewer: Grants the associate the ability to see the entity and its published schedules. Viewers cannot modify settings or manage schedules.

Admin: Provides full administrative control over the entity, including the ability to edit rosters and change configurations.

Job Qualifications: It can automatically convey specific qualifications to an associate for a set period, ensuring they are eligible for the correct shifts.

Visual Indicators: Positions display as badges on shifts and requests, making it easy to identify staff roles (e.g., "Chief Resident" or "Consultant") at a glance.

System Logic: These tags are used to filter calendars, generate specific report graphs, or apply targeted scheduling rules to a team (e.g., ensuring a specific number of "Seniors" are on a shift).

Live Data: On the Reports page, you see data for published shifts only.

Draft Data: In the Quick Analytics sidebar, you can see reports for unpublished draft schedules to check for errors before publishing.

All Teams: The request automatically covers every team you belong to. If you are added to a new team, the request follows you.

Some Teams: You choose exactly which teams the request applies to. It won't affect any other teams you work on.

Status: Requests usually only impact the schedule once an administrator approves them.

Separate Approvals: Each team manages its own approval. You might be approved for time off in "Emergency" but still be pending in "Internal Medicine".

Automatic Removal: If your contract or "Tour of Duty" ends for a specific team, any requests for that team are automatically canceled.

Function: Rules set goals or limits, such as fairness (giving everyone equal shifts), personal preferences, or workload limits (e.g., no more than 80 hours a week).

Enforcement Levels:

Draft State: Every schedule begins as an unpublished draft. In this state, shifts are invisible to regular members, cannot be traded, and any changes made do not trigger notifications or appear in reports.

Published State: Once published, the shifts become active on the team calendar, allowing associates to view their assignments and initiate deals.

Overlapping Schedules: Mesh AI allows for multiple schedules to exist for the same time period. This is useful for managing different groups of staff or distinct departmental needs simultaneously.

Core Components: Every shift is assigned a Job that describes exactly what the associate is doing during that time (e.g., On-Call or Triage).

Detailed Information: Shifts can include additional context, such as specific notes about the work period or configurable extra data tailored to your team's needs.

Assignment: Only one associate can be assigned to a specific shift at a time, ensuring clear accountability.

Interdependence: Unlike a department, which is based on hierarchy, a team is defined by scheduling inter-relation. These are people who work the same sets of shifts or whose coverage must be coordinated as a single unit.

Flexible Alignment: A team may not perfectly align with your organization’s structural units. You might create a team specifically for "Night Shift Coverage" or "Weekend Call," even if those members belong to different departments.

Organization Membership: Every team is housed within a specific Organization, where it shares global resources like Job types and Qualifications.

Automation: Templates govern how shifts are automatically populated when you create a new schedule period.

Consistency: They ensure that recurring roles, times, and requirements are applied identically across different weeks or months, reducing manual data entry.

Definition: It defines "when" an associate belongs to a team and "how" they can be scheduled.

Scheduling Characteristics: Each tour includes specific parameters for that associate, such as their job qualifications, positions, or preferred days of the week.

Flexibility & Duration:

Account Ownership: Users maintain full control over their own accounts. They are responsible for managing their personal User Settings, including contact details and how they interact with the platform.

Organizational Links: A single user can be connected to one or more Organizations through an Associate record. This allows a clinician to use one login even if they work across multiple independent hospitals or networks.

Preference Management: Users decide their own notification triggers and delivery methods (SMS, email, or push), ensuring they stay informed on their own terms.