My Availability

When you know ahead of time that you cannot serve, My Availability lets you declare the window yourself. The platform removes you from your own overlapping future duty and reopens those posts so leadership can find coverage — no swap request needed.

What This Is

N4 Safety supports two operating models for handling a member who cannot make an assignment, and your organization runs one of them at a time:

Find-your-own-coverage — you use Swapping Shifts to trade your assignment with another safety team member.
Self-declared unavailability — you use this page to declare a window you cannot serve, and the platform removes you from your own affected duty.

This page covers the second model. If your organization has enabled it, My Availability appears in your sidebar.

🛡️

Admin Only: Which model your organization uses is set by your Organization Admin or Oversight leaders. See Unavailability Settings for the admin side of this feature.

Declaring a Time You Cannot Serve

Open My Availability

Click My Availability in the sidebar.

Set Your Window

Enter Unavailable from and Until using the two date-and-time fields.

Declare It

Click Declare unavailability.

Times are entered in your organization’s time zone, shown just below the fields. If you are travelling and your phone’s clock is set to a different zone, go by the label on the page, not your device.

What Happens When You Declare

Declaring a window does three things, and the confirmation message tells you exactly what happened:

Overlapping posts reopen. Any future, not-yet-started duty you were assigned to within the window — including leader- and rotation-assigned posts — is removed from you, and those posts reopen for someone else to claim.
Duty already in progress is left alone. If one of your assignments has already started, the platform does not touch it. You will see a note telling you to contact leadership directly about that duty.
No overlapping duty found. If nothing in your schedule fell inside the window, you will simply see a confirmation that no duty was affected.

Only your own future, not-yet-started duty is ever affected. If you are already checked in or an assignment has started, declaring unavailable will not remove it or “undo” your check-in — that duty is left exactly as it is. This is by design: the platform never rewrites duty that is already happening.

Declaring a window also automatically cancels any pending swap requests you made for duty inside that window, and any direct swap requests sent to you where you were the intended recipient. See Swapping Shifts if you want to understand how those requests normally work.

You cannot have two overlapping active declarations at the same time — declare one window, cancel it if your plans change, then declare a new one.

Viewing Your Declarations

Your Active declarations list shows every window you currently have in effect, each marked with an amber Active badge. Under each declaration, a “Duty removed from” list names the specific events and posts that were reopened.

Below your active declarations, a Recently Cancelled section shows declarations you cancelled in roughly the last 30 days, so you have a short history without an unbounded list to scroll through.

Cancelling a Declaration

Changed your mind, or your plans shifted? You can cancel an active declaration at any time.

Find the Declaration

Locate it in your Active declarations list.

Cancel It

Click Cancel declaration, then confirm.

Review the Outcome

The result tells you exactly what came back — read it carefully, since a cancel does not always mean full restoration.

Cancelling a declaration can result in three different outcomes, and the platform shows you which one applied to each affected event:

Restored as floating support. You are added back to the event, but as floating/support — never back into the exact post someone else has since claimed. This appears in green.
Not restored — no longer schedulable. If something changed since you declared off (for example, a compliance requirement lapsed), you are not put back on that event’s duty. This is called out in amber, and the page tells you to contact leadership to be re-placed.
Already started — left unchanged. If the event has since started, cancelling your declaration does not touch it. It stays exactly as it was.

A confirmation that your declaration was cancelled does not guarantee you were restored to every event. Always check the outcome list — “not restored” and “already started” mean the platform deliberately left that duty alone.

Don’t See This Page?

If My Availability is not in your sidebar, your organization has not turned on self-declared unavailability. Your organization instead uses the find-your-own-coverage model — see Swapping Shifts to trade your assignment with a teammate. If you believe your organization should be using this feature, talk to your Organization Admin.