As of 18 Nov 2026, the panel rates Deputy 3/5 and When I Work 3/5 in Employee Scheduling. Weighted by what each judge cares about, 1 of the 6 judges picks Deputy and 4 pick When I Work, 1 calls it a tie. Deputy scores higher on 3 of 7 criteria (Pricing transparency, Roster building & demand planning and European sovereignty). When I Work scores higher on 4 of 7 criteria (Working-time law & collective agreements, Mobile self-service for deskless staff, Payroll handoff & integrations, plus 1 more). Provenance — Deputy: Rest of world, Australia; When I Work: Rest of world. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
Deputy and When I Work split the bench with no overall winner. The table puts Deputy ahead on roster planning (7.3 vs 6.8), pricing transparency (6.8 vs 6.2; 4 judges lean Deputy, 2 tie) and sovereignty (2.8 vs 2.5); Deputy publishes Lite $5, Core $6.50, Pro $9 per user per month, USD excl. all applicable taxes. When I Work is ahead on working time rules (5.3 vs 4.3; 4 judges lean its way), staff self service (7.0 vs 6.5), payroll and integrations (6.5 vs 6.2) and codetermination and privacy (5.0 vs 4.8); it publishes $2.50 per user per month for single-location teams and $5 per user per month for multi-location businesses. Weighted totals split by judge: When I Work leads for the shift manager, works council and skeptic; Deputy for the frontline employee; the payroll officer ties at 5.5; the table shows no totals for the operations director.
Choose Deputy if
You build rosters from forecasted sales, delivery orders and foot traffic, with hour and wage budgets tracked in real time; roster planning scores 7.3 for Deputy vs 6.8 for When I Work, with 2 judges leaning Deputy and 4 tying.
You need published prices before purchase: Deputy lists Lite $5, Core $6.50, Pro $9 per user per month, USD excl. all applicable taxes, and pricing transparency leans Deputy 4 judges to 0 with 2 ties.
You weight the frontline employee's perspective: that judge's weighted total is 5.9 for Deputy vs 5.6 for When I Work.
You want a data processing agreement you can take self-serve: Deputy's sovereignty attributes list the data processing agreement as self-serve.
You compare sovereignty as the bench scored it: 3 judges lean Deputy vs 1 for When I Work (means 2.8 vs 2.5), though both verdicts place the category at 2-3.
Choose When I Work if
You need configurable working-time guardrails: 4 judges lean When I Work on working time rules (5.3 vs 4.3); Deputy's documented guardrails are framed for US state break law and fair workweek.
Your staff handle swaps, drops and open shifts from iOS and Android apps: staff self service scores 7.0 vs 6.5, with 3 judges leaning When I Work and 3 tying.
You close a locked pay period and send hours to named North American processors: payroll and integrations scores 6.5 vs 6.2, with 2 judges leaning When I Work and 4 tying.
You rely on granular role permissions and timesheet edit history: codetermination and privacy leans When I Work 2 judges to 1 (5.0 vs 4.8), with 3 judges tying.
Your panel gives weight to the skeptic: that judge's weighted total is 5.7 for When I Work vs 5.2 for Deputy.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Shift Manager
Builds next week's roster for a restaurant or store on Thursday night and fields the sick calls on Saturday morning. Wants templates, qualifications that stop the wrong person landing on the till, open shifts staff can claim, and a rest period warning before publication rather than after the inspection.
Deputy
When I Work
This judge's pick
Criterion by criterion
Roster building & demand planning
Deputy
Auto-scheduling builds the week in a few clicks, weighing availability, training and cost, and demand comes from named sources — POS sales, delivery orders, foot traffic — with minimum-coverage rules and hour and wage budgets tracked in real time while I schedule, plus forecast-versus-actual sales graphs for correcting afterwards. What I could not find on the captured pages is cross-location staff sharing, so a multi-site chain should ask before assuming.
When I Work
This is a real rostering tool: shift templates, positions and skills on shifts, unlimited job sites with labor sharing between locations, open shifts, and one-click auto-assign that fills shifts based on availability and qualifications while honouring the scheduling rules, with a concern summary shown before I publish. What the pages do not show is where the labour forecast gets its numbers — no sales, footfall or occupancy source is named — so demand-based planning stays generic.
Working-time law & collective agreements
Deputy
The planner gets named guardrails — minimum rest between shifts, maximum work hours per week, and break timing enforced with missed breaks flagged and employee attestation requested — which is the rest-period warning before publication I want. The compliance story is built around US strict break-law states and fair-workweek rules; I found no public information on German working-time law, Minijob earnings limits, collective-agreement surcharges, or tracking of contract hours per employee.
When I Work
The scheduler knows configurable rules: maximum days in a row and per week, minimum hours between shifts (up to 18 hours, so an 11-hour rest is configurable), and weekly, daily and double overtime with multipliers, all surfaced as concerns before publishing and even hiding rule-breaking shifts from open-shift claiming. But these are generic numbers the operator sets; we found no public information on ArbZG, Minijob earnings limits, youth protection or Tarifvertrag surcharges.
Mobile self-service for deskless staff
Deputy
The mobile app covers my Saturday-morning reality: staff see their shifts with automatic reminders, swap with suitable teammates, claim open shifts via mobile alerts, request time off and unavailable days, clock in with location verification, and keep shift talk in a news feed instead of private messengers. I found no public information on swap approvals checked against qualifications or rest periods, offline clock-in, or a multilingual interface.
When I Work
Proper iOS and Android apps where staff see their shifts, request time off, swap, drop and release shifts, bid on open shifts, report an absence themselves, and clock in from their phone or a shared terminal — with built-in team messaging so shift talk stays out of private messengers. Swap targets are filtered so nobody picks up a shift that would break a rule, which is exactly what I want before approving on a Saturday morning; we found no public information on offline clock-in handling or interface languages.
Works council & employee data
Deputy
Pro plans offer custom access levels to limit who sees whose data, a data processing addendum is incorporated into the subscription terms, a sub-processor list is published in the Privacy Centre, and customer data can be exported within 30 days before termination and is otherwise deleted. For a works council I would still be short: no audit log of who viewed an individual's data, no works-agreement documentation for co-determination, and the default setting for location capture at clock-in is not stated.
When I Work
Role permissions are genuinely granular — supervisors see only the employees they supervise, wage visibility for new supervisors is off by default, GPS location collection is permission-based, and timesheet edits are tracked with who made each change. We found no public information on a data processing agreement, configurable deletion periods, or any documentation a works council would need under BetrVG § 87.
Payroll handoff & integrations
Deputy
Approved timesheets, pay rates and leave go to a named payroll partner, Paycor, in one click, with an approval step before sending, a documented API, and payroll, point-of-sale and HR integration categories — POS sales data even feeds the schedule forecast. The named payroll handoff is US-only; I found no public information on DATEV or German payroll systems, wage-type mapping per surcharge, or retro corrections after the close.
When I Work
Named payroll integrations (Rippling, ADP, Gusto, Paychex, QuickBooks Online, Square Payroll and more) with hours sent directly to the processor or exported as a spreadsheet, a pay period that gets closed and locked before transmission, configurable overtime multipliers and rounding, plus a documented API with webhooks and named HR partners. We found no public information on DATEV or Lohn und Gehalt connectivity, or on POS data feeding the forecast.
European sovereignty
Deputy
The contracting entity is named — Deputechnologies Pty Ltd, with Deputy Corporation of San Francisco shown for the Americas — and a data processing addendum plus a sub-processor list are published. The hosting location for employee data is not stated on any page I read, and no EU hosting is claimed anywhere.
When I Work
The contracting entity is When I Work, Inc. of Minneapolis and the primary data centers are stated to be in the United States, with standard contractual clauses or consent named for international transfers; the same section says data "may be stored and processed in your region", so where European employees' data actually sits is not pinned down. We found no published subprocessor list and no certifications stated.
Pricing transparency
Deputy
Every main tier is priced publicly per user per month — Lite at $5, Core at $6.50, Pro at $9 (USD excl. all applicable taxes, billed upfront or in monthly installments) — with monthly rates, a 10% annual saving, and priced add-ons in Analytics+ $1.50, HR $2, Messaging+ $1.95. The payroll add-on's fee varies by business size and the Flexi and charity options carry no number, so the full annual invoice including payroll is not computable from the public pages.
When I Work
Two public prices — $2.50 per user per month for single-location teams and $5 per user per month for multi-location businesses — with monthly or annual billing stated, no long-term contracts, no setup fees, and scheduling, time tracking and messaging included in every plan, so the per-head maths is easy to do. We found no public information on VAT treatment, how inactive or seasonal staff are counted, or enterprise pricing beyond a contact-sales conversation.
Sovereignty, side by side
Dimension
Deputy
When I Work
Legal entity
Incorporated in AU
Not determined
Hosting location
Not determined
Outside the EU
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Published, self-serve
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 18 Nov 2026, the panel rates both 3/5. Weighted by what each judge cares about, 1 of the 6 judges picks Deputy and 4 pick When I Work, 1 calls it a tie. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is Deputy or When I Work European?
Deputy is not European by provenance (Rest of world, Australia). When I Work is not European by provenance (Rest of world). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do Deputy and When I Work store customer data?
Per the vendors’ own pages as captured — Deputy: its pages as captured do not say. When I Work: Outside the EU by default.
Do Deputy and When I Work have a free plan?
As of 18 Nov 2026, Deputy’s own pages state a free plan; When I Work’s pages as captured do not. Each product page links the pricing page it was read from.