> For the complete documentation index, see [llms.txt](https://compassly.gitbook.io/compassly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://compassly.gitbook.io/compassly-docs/core-modules/shifts/shift-management/manage-shifts-in-batch.md). # Manage Shifts in Bulk **Page type:** Task Guide\ **Status:** Draft\ **Owner:** Compassly Documentation Team\ **Last verified:** 2026-07-08\ **Audience:** Super Admin, Admin, Supervisor, Clinician, Basic ## What This Section Covers This material covers how to select multiple shifts at once and publish, unpublish, edit, or delete them together, including what happens when some of your selected shifts aren't eligible for the action. ## Before You Start * You must have permission "Manage shifts and notes". * A shift in **Published (Note Signed)** status is excluded from every bulk action below — it has to be unlocked first. See [Unlock and Edit a Signed Progress Note](/compassly-docs/core-modules/shifts/shift-management/unlock-signed-progress-note.md). * Bulk actions work the same way in ***Day***, ***Week***, ***Month***, and ***Table*** view. ## Where To Start 1. Sign in to Compassly. 2. In the left navigation menu, select ***Shifts***. 3. In the left navigation menu, select ***Shift Management*** from the dropdown menu under ***Shifts***. 4. Select shifts using the checkboxes on individual shift snippets (calendar views) or shift rows (***Table*** view), a day-column header checkbox to select everything in that day, or the ***Select all*** checkbox. ## Available Actions 1. **Check the selected-items counter before acting.** * Once you select at least one shift, a bulk action bar appears with buttons for the actions available and a running count. Each button's counter only includes shifts that are actually eligible for that action — for example, if you select 10 shifts but only 2 are eligible to be published, the Publish button shows `2`, not `10`. Always check the counter matches what you expect before clicking through. 2. **Delete shifts in bulk.** * Click ***Delete***, then confirm. Only shifts that can be deleted are removed — the confirmation tells you how many. 3. **Publish shifts in bulk.** * Click ***Publish***, then confirm. Only shifts that aren't already published are affected. 4. **Unpublish shifts in bulk.** * Click ***Unpublish***, then confirm. Only shifts currently in **Published (Note Unsigned)** status are eligible — Template, Unpublished, and signed shifts are excluded from the count. Progress Note content on unpublished shifts is preserved, not reset. 5. **Edit shifts in bulk.** * Click ***Edit*** to open the Bulk Edit window. Only shifts in **Template**, **Unpublished**, or **Published (Note Unsigned)** status are eligible — signed shifts are excluded. * The window has three toggles — ***Time***, ***Team Member & Service***, and ***Clients*** — each collapsed and off by default. Turn on only the ones you want to change; anything left off is untouched on every selected shift. At least one toggle must be on to continue. * Turning on ***Team Member & Service*** requires both a Team Member and a Service — you can't set one without the other in this block. * If any selected shift is in **Template** status with no Client attached, and you enable ***Team Member & Service*** without also enabling ***Clients***, you'll see a warning explaining that those specific shifts will only get the Team Member applied — no Service, and they'll stay in Template status, since a Template shift can't hold a Service without a Client. Enabling ***Clients*** alongside ***Team Member & Service*** avoids this by giving those shifts everything they need to be promoted to Unpublished. * Changing the Team Member, Service, or Clients on any shift through bulk edit resets that shift's Progress Note (Brief Summary and all Individual Notes). * Click ***Update***, then confirm. If any of the changes would create a scheduling conflict, you'll see a **Shift overlap detected** message before anything is saved — see [Understand Shift Overlap Validation](/compassly-docs/core-modules/shifts/shift-management/understand-shift-overlap-validation.md). ## Role Differences * ***Super Admin / Admin / Supervisor:*** Can bulk-manage any shifts they have access to. * ***Clinician / Basic:*** Can bulk-manage shifts assigned to themselves. ## Summary Of Section **Upon reviewing this material, you should be able to:** * Select multiple shifts and understand why a bulk action's counter might be lower than your selection * Delete, publish, or unpublish shifts in bulk * Use the Bulk Edit toggles to change only the fields you intend to * Recognize when a Template-status shift without a Client needs special attention during bulk edit ## Related Guides * [Publish a Shift](/compassly-docs/core-modules/shifts/shift-management/publish-shift.md) * [Delete a Shift](/compassly-docs/core-modules/shifts/shift-management/delete-shift.md) * [Edit Shift Details](/compassly-docs/core-modules/shifts/shift-management/edit-shift.md) * [Understand Shift Overlap Validation](/compassly-docs/core-modules/shifts/shift-management/understand-shift-overlap-validation.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://compassly.gitbook.io/compassly-docs/core-modules/shifts/shift-management/manage-shifts-in-batch.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.