Hej! Let's talk.

Product Design Lead in Copenhagen. Happy to chat about work, design or a good coffee spot.

Stefan Cioroiu's resume: Product Design Lead with over 10 years of experience, based in Copenhagen. Senior Product Designer at Veo Technologies, earlier Senior Product Designer at Novo Nordisk, Senior then Lead Product Designer at Planday, and Product Designer at Tradeshift, Founders and Zigna, starting as a UI and graphic designer at Me-Mover. Studied at KEA, Copenhagen School of Design and Technology.

3 min read B2B · Workflow · Rules · Web app

Shift Requests: Swaps and Handovers Without the Guesswork

One inbox where managers handle open shifts, handovers and swaps the same way, with conflicts flagged before they approve.

Context
Planday • Web / Schedule
Role
Lead Product Designer
Scope
Request inbox, rules, conflicts
Status
Shipped

The problem

Every request was its own detour

Each request type lived somewhere else. Approving safely meant checking the schedule, counting hours and remembering preferences.

Most skipped the checks, causing double bookings and unplanned overtime.

3

different flows for what is really one decision: who works this shift?

0

warnings about overlaps, rest time or weekly limits before approving

?

for employees, no way to see a request’s status

One inbox

One list, one panel, one decision

One filterable list. Each request opens the same panel: the shift, who’s involved, conflicts, and what approving will do.

The Requests page: a filterable list of requests on the left and the selected request's details on the right

Request types

Same pattern, every kind of request

Once a manager has handled one type, they know them all.

A shift handover request from Alex Smith to John Doe

A handover to a colleague

The employee picks who takes it. The manager sees both sides before approving.

A shift swap request between John Doe and Jessica Cobe

A swap between two people

Both shifts are shown together, so the manager checks one decision, not two.

Four requests for three open shifts with three employees selected and a summary line

Fill several shifts at once

For several identical shifts, pick that many people. The summary says what happens.

Four requests for one open shift, ranked first to fourth, with conflicts per employee

Many people, one open shift

First come, preselected. A fair decision is one click.

A handover request with three colleagues who asked to take the shift

A handover to anyone

Shifts up for grabs work like open shifts.

The deny shift request dialog with an optional note and an SMS option

Saying no, kindly

Denying is as quick as approving, with an optional reason.

Conflicts

Problems flagged before you approve

Every requester is checked for overlaps, rest time, hour limits and preferences.

Conflicts inform, they don’t block. Sometimes the overtime is worth it.

A handover request with a warning: conflicting shifts for John Doe, 2

JD John Doe 2 conflicts

  • Overlapping shift Bar, Tue 13 June, 16:00 – 20:45
  • Weekly limit 51 of 48 hours this week
  • Note Prefers not to work Tuesdays

Try it

You are the manager

Three colleagues offered to take Lukas’s shift. Pick one.

InteractivePick a colleague, then approve or decline.

Handover request

Kitchen · Tue 13 June · 17:00 – 23:00

LK Lukas can’t make it and offered the shift to the team.

2 conflicts for John

  • Overlapping shift Bar, Tue 13 June, 16:00 – 20:45
  • Weekly limit 51 of 48 hours this week

You can still approve. Sometimes the overtime is worth it.

What we heard

Faster for managers, fairer for teams

Managers in testing mentioned the conflict count most, then the first-come ranking.

I used to approve swaps from my phone without knowing if the person was already working that day. Now I can see it before I click.
Restaurant manager, beta feedback

Looking back

Design the decision, not the screen

Three features were one question: who works this shift, and is that okay? Once the decision had one shape, every request fit.

Next: auto-approve conflict-free swaps.

Thanks for reading!