A clearer path to a shift swap

A shared swap workflow lets controllers propose an exchange and follow its status while planners review the scheduling effect. The request, checks and decision stay connected.

The exchange still needs to meet qualification, availability, coverage and working-time requirements.

Request the exchange

An employee proposes a swap with an eligible colleague. The other employee can review the request, and the exchange follows the configured approval process.

Staff can follow the request status in the platform. Mobile access supports the available workflows when an internet connection is available.

Review the effect

Planners review the proposed assignments and the relevant rule checks. A swap may change rest between duties or accumulated working time, so review the surrounding period as well as the two shifts.

Matching qualifications is a starting point. Suitability and approval also depend on the other checks.

Share the approved change

Once the required approvals are complete, the approved change can be reflected in the roster. Keeping the request and assignment information together helps reduce duplicate entry and uncertainty about the current plan.

The organisation should define who approves requests and how staff are informed of approved changes.

See what the workflow changes

Compare the time needed to propose, review and complete swaps with the current process. Review rejected requests and recurring conflicts to identify whether configuration, communication or staffing needs attention.

Shift swaps give staff more scheduling options within the coverage and approval requirements of the operation.

See SkyRoster’s shift-swap workflow for an illustrative example.