Override Shifts(Short Term Schedule Changes)

Purpose

An override is a normal shift that happens to overlap an existing, longer shift on the same group. AlertOps uses an implicit precedence rule: during any overlap, the shift with the shorter duration and earlier end date takes priority. When the shorter shift ends, the longer shift resumes automatically — no manual revert required.

This is how you cover a sick day, a vacation week, a holiday swap, or a training period without editing the base rotation. You add a shorter shift with the right members for that window; it wins for the overlap and then quietly steps aside.

Audience

Relevant for Group Managers and App Admins

Anyone responsible for a group's on-call coverage. The person taking the override must already be a member of the group.

Prerequisites

• A group with at least one active shift (fixed or rotating).
• The replacement user is already a member of the group.
• Familiarity with Scheduling Basics — you will use the same shift editor you already know.
• For multi-day absences that affect every group a user belongs to, consider an Out-of-Office entry on the user's profile instead — it covers every group in one place.

How Override Precedence Works

Relevant for Anyone creating or verifying an override

There is no special "Override" shift template in AlertOps. Overrides are an emergent behavior of a single rule:

A few consequences of this rule that catch people out:

• Both shifts stay visible on the calendar simultaneously. There is no badge, colour change, tooltip, or active indicator anywhere in the Schedule grid or shift list that tells you which one is winning — the precedence is resolved internally at paging time.
• You do not have to delete or end the longer shift. You simply add the shorter one over the window you need to cover.
• When the shorter shift's end time passes, routing falls back to the longer shift on its own. No manual clean-up is required.
• If you want to undo a planned override before it takes effect, delete the shorter shift. The longer shift was never modified.
• Two shifts with exactly the same duration and the same end date are a true tie — paging is effectively random between them. If you need a specific member to cover, make sure the override shift is shorter (by duration or end date, or both) than the shift it overrides.

When to Use an Override vs. Other Tools

Relevant for Group Managers

Pick the lightest-weight tool for the scope of the change:

Create an Override by Adding a Shorter Shift

Relevant for Group Managers and App Admins

Step 1 — Open the group's Schedule tab

1. Go to Configuration → Groups.
2. Click the group whose coverage you want to change.
3. Open the Schedule tab.

Figure 1 — The Schedule tab is where all of a group's shifts live, including the shorter shift you are about to add to create an override.

Step 2 — Add a new shift

1. Click + ADD SHIFT.
2. Pick a shift template that suits your override. For a one-time coverage change the simplest choice is a Fixed template ("Fixed With Selected Users - Business Hours" or similar); for a recurring override pattern use a Rotating or Custom template.
3. The shift editor opens.

Step 3 — Configure the shift so it is shorter than the base shift

Configure the shift's dates, times, and members exactly as you would a normal shift — the precedence rule does the rest. The important constraint is that the new shift's total duration and end date are both shorter/earlier than the shift it is overriding. A few typical setups:

4. Click SAVE. The new shift appears on the schedule grid alongside the base shift. Both remain visible.

Step 4 — Verify by triggering a test alert

1. Wait until the override window is active (or set it to start in a minute or two while you test).
2. Trigger a test alert to the group — from Alerts → + Create Alert or via whichever integration feeds the group.
3. Confirm that the override member, not the base-shift member, is paged.
4. If the wrong person is paged, review Troubleshooting below.

Edit or End an Override Early

Relevant for Group Managers and App Admins

Because an override is just a shorter shift, you edit or delete it like any other shift:

1. Open the group's Schedule tab.
2. In the shift list, click the name of the override shift.
3. Edit any field (to extend, shorten, change the member, or change the role) and click SAVE.
4. To end the override early, set End Date / Time to a moment in the near future and save. When that moment passes, the base shift resumes automatically.
5. To remove the override entirely, delete the shift from the list. The base rotation was never modified and continues as normal.

Common Scenarios

Relevant for Group Managers

Scenario 1 — Single sick day

Scenario 2 — Week-long vacation swap

Scenario 3 — Weekend hand-off

Scenario 4 — Backfill while the Primary is unreachable

Troubleshooting

Relevant for Group Managers and App Admins

The wrong person is being paged during the override window

• Confirm the override shift is actually shorter in total duration than the base shift it is meant to override. If the base shift is itself short, or perpetual, verify the relative durations. The rule is "shorter + earlier end date" — a longer override will not win.
• Confirm the override's time zone. A window that reads 09:00–17:00 in local time but was saved in UTC will fire at a different wall-clock time.
• Confirm the override member is still a group member and still has an active contact method. A removed user will not be paged.
• Trigger a test alert to confirm (see the Verification step above). Visual inspection is not enough — the UI shows both shifts without marking which is active.

Two shifts look like they overlap but both members are being paged

• Check whether the shifts are actually on the same group. Shifts on different groups do not interact.
• Check that one shift is actually shorter than the other by both duration and end date — if the durations are identical or the end dates are not in the order you think, the precedence rule may not pick the one you expected. When in doubt, make the intended override clearly shorter.

The override keeps firing after it should have ended

• Check the End Date / Time on the override shift. Easy to miscount when the window crosses midnight or a DST boundary.
• Confirm the override's time zone matches what you intended.

I can't tell which shift is active right now

• The UI does not surface this — by design, both overlapping shifts remain visible and the precedence is resolved at paging time. The only reliable way to check is to trigger a test alert and confirm who is paged.

Best Practices

Relevant for Group Managers

• Name override shifts descriptively — "Jane vacation Aug 12–15" is far easier to audit than "Override" or "Temp."
• Always set an explicit End Date on an override. A perpetual override (no end date) defeats the precedence rule — the base shift will never resume.
• After saving an override, trigger a test alert during its window. Because the UI does not mark which shift is active, this is the only reliable verification that your override is actually winning.
• Pick the right tool for the scope — Out-of-Office when a person is out across every group they're in, an override shift when only one group needs a coverage change, a base-shift edit for permanent changes.
• Use contrasting shift colours — it does not affect precedence, but it makes it easier to spot the override visually on the grid.
• Delete stale override shifts periodically. Expired overrides are harmless but they clutter the shift list and make future audits harder.