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 Mobile · Flows · Payroll · Edge cases

Punch Clock: Clocking In From Your Pocket

Employees clock in from a widget, checked by location or Wi-Fi. Every punch runs through the business’s wage rules, so payroll gets hours both sides trust.

Context
Planday • iOS, Android
Role
Senior Product Designer
Scope
Widget, flows, edge cases
Status
Shipped Spring 2020

The problem

Hours are where trust breaks down

Hospitality wages depend on exact hours. Punches from a shared terminal or a manager’s memory meant corrections every payroll run.

  • For employees: clock in on their phone, see what will be paid.
  • For managers: punches they can trust, because they happened at the workplace.
  • For payroll: hours that follow the agreement, fewer fixes.
Before any screens: a workshop on time tracking from both sides. Employees fear being watched, managers fear paying for hours nobody worked. It ended with “How might we increase trust through time tracking?”
A SWOT and a value proposition canvas for each side.

The model

Three times for every shift

A punch isn’t a paid hour yet. Each shift keeps three sets of times, so nothing is overwritten.

PunchedWhat the clock recorded
11:24 – 21:22
CalculatedAfter the wage rules
11:30 – 21:15
ApprovedWhat gets paid
11:30 – 21:15
1 Clocking in six minutes early counts from the scheduled start.2 Clocking out rounds to the nearest 15 minutes, which adds 15 minutes of overtime.3 The manager approves, and the approved times go to payroll with the overtime supplement.

The widget

One card, always one next step

On the home screen, the card always shows the shift and the one action that moves it forward.

  • The Punch Clock widget: Ready

    Ready

    At work and on time: one big button.

  • The Punch Clock widget: On shift

    On shift

    A running timer, with break and end side by side.

  • The Punch Clock widget: Something to fix

    Something to fix

    Location blocked? One tap to the right setting.

  • The Punch Clock widget: Not at work

    Not at work

    No dead end: report a problem to the manager instead.

  • The Punch Clock widget: Wi-Fi check

    Wi-Fi check

    For basements and malls, an approved network works too.

The flows

Designing for every “no”

The happy path is one tap. The work was everything else: location off, permission denied, weak GPS. I mapped every check for every action, so nobody hits a dead end.

The complete Punch Clock flows: four actions, each with location and Wi-Fi checks
The full map: start shift, start break, end break and end shift, for both location and Wi-Fi. Click to zoom.

Eight flows, one pattern

Same checks, same order, one fix per failure. Quick to build, predictable to use.

Next idea: when close enough, hide the map and enlarge the button.

Review

Spot a mistake, request a change

Employees see what they punched and what will be paid. If something’s off, they request a change, and the manager approves it before payroll.

My hours Week 46

Mon 1011:30 – 21:15Punched 11:24 – 21:22Approved
Tue 1116:00 – 23:00Punched 15:58 – 23:04Waiting
Thu 1311:30 – ?No clock-outCheck

Request a change

Send request

Looking back

Small card, a lot of trust

Clocking in moved to every employee’s phone, and the path from punch to pay became visible. Lesson: on a feature this small, the edge cases are the product.

Thanks for reading!