Scheduling
Publishing Shifts
Understand the draft vs. published workflow, how to publish shifts, and how email notifications work.
ClinicShifts uses a draft-first workflow — all newly created shifts start as drafts, giving you time to build and review the schedule before making it visible to your team.
Draft vs. Published
| Aspect | Draft | Published |
|---|---|---|
| Visual | Striped left border | Solid left border |
| Visibility | Admins only | Everyone (admins, providers, facility managers) |
| Notifications | None | Triggers email notifications when changes are made |
| Calendar sync | Not included | Appears in synced calendars and shared location links |
Publishing Shifts
There are two ways to publish shifts:
Publish Selected Shifts
- Select one or more draft shifts on the schedule
- Click the Publish button in the top-right operations panel
- The button will show the count — e.g., Publish (3) — indicating how many selected shifts will be published
Publish All Visible Shifts
- Make sure no shifts are selected (use Deselect All if needed)
- Click the Publish button
- All draft shifts currently visible on the schedule will be published
Email Notifications
When Send shift email notifications is enabled in Organization Settings, the following actions trigger automatic emails:
- Publishing a shift — the assigned provider receives a notification about their new shift
- Editing a published shift — the assigned provider is notified of the change
- Deleting a published shift — the previously assigned provider is notified of the cancellation
- Location calendar changes — subscribers to shared location calendars receive updates
Draft shifts do not trigger any notifications. This gives you the freedom to build, rearrange, and finalize the schedule without generating unnecessary emails.
Recommended Workflow
- Create shifts as drafts — build out the entire week or month
- Review and adjust — move shifts around, fill gaps, resolve warnings
- Publish all at once — publish the finalized schedule so everyone is notified simultaneously
This approach prevents providers from receiving multiple notification emails as you make iterative changes.