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 Payroll Officer
Turns the worked month into DATEV and answers for every surcharge. Cares about night, Sunday and holiday supplements from the Tarifvertrag, Minijob limits caught before the month closes, and corrections after the close. Treats "CSV export" as an admission that the handoff was never designed.
Deputy
When I Work
This judge calls it a tie.
Criterion by criterion
Roster building & demand planning
Deputy
Demand-based planning runs off named sources — forecasted sales, delivery orders and foot traffic — into one-click auto-scheduling that weighs availability, training and cost, with hour and wage budgets and real-time variance tracked while planning; that is most of the way up this ladder. We found no public information on sharing staff across locations, and the forecasting is sold as AI rather than a documented method.
When I Work
One-click auto-scheduling fills shifts from availability and qualifications, templates cover weekday, weekend and holiday staffing, open shifts surface the gaps, and labour is shared between departments and locations. What the pages do not show is demand-based planning from a named source: forecasting is described as scheduled versus budgeted hours, and we found no public information tying it to POS revenue, footfall or bookings.
Working-time law & collective agreements
Deputy
The planner gets named guardrails — minimum rest between shifts and maximum weekly hours — plus a serious break regime with templates, overlap prevention, missed-break flags and attestation, which clears the middle of the range. But every compliance artefact is framed for US state and fair-workweek law; we found no public information on ArbZG rest rules, Minijob earnings ceilings, or night, Sunday and holiday surcharges from a Tarifvertrag.
When I Work
Configurable rules cover minimum hours between shifts (1 to 18), maximum days in a row and per week, a concern summary before publishing, and weekly, daily and double overtime at 1.5 and 2 times the rate, with concern-raising shifts hidden from open-shift claiming. But the checks are configurable numbers rather than modelled law: we found no public information on ArbZG, Minijob earnings ceilings, or night, Sunday and holiday surcharges from a collective agreement, and the terms state the service is designed for the United States.
Mobile self-service for deskless staff
Deputy
The mobile app delivers the roster with automatic reminders, leave and availability requests, employee-initiated swaps, open-shift alerts, app clock-in with location verification, in-app messaging and a news feed — and pay stubs visible in the app, which I welcome. We found no public information on offline handling, multilingual coverage, or swaps being explicitly re-checked against qualifications and rest periods before approval.
When I Work
iOS and Android apps deliver the roster, shift swaps, drops, releases and open-shift bidding, with clock-in from the phone or a shared terminal app and built-in team messaging; swap partners whose pickup would raise a concern are filtered out of the selection. We found no public information on offline handling, language coverage or accessibility statements, which keeps it below the top band.
Works council & employee data
Deputy
Custom access levels, a self-serve data processing agreement, a published sub-processor list and deletion on termination give an operator the basics for a works-council conversation. We found no public information on an audit log of who viewed an individual's data, configurable deletion periods, GPS tracking being off by default, or materials for works-council approval under BetrVG § 87 — and the app's clock-in records when and where someone worked.
When I Work
Role permissions are genuinely granular — wage view off by default for new supervisors, supervisors limited to employees they supervise, object-level toggles — timesheet edits carry a history of who changed what, GPS collection is permission-based, and deletion is available on request. We found no public information on a data processing agreement, documentation for works-council approval, an audit of who viewed an individual's data, or configurable retention and deletion periods.
Payroll handoff & integrations
Deputy
Approved timesheets, pay rates and leave go to Paycor in one click with an approval step before transmission, the POS feeds the forecasting, and a documented API exists — a designed handoff, not a CSV apology. But the payroll engine is stated as US-only, and we found no public information on DATEV or Lohn und Gehalt, wage types mapped per surcharge, an HR master-data sync, or retro corrections after the month closes.
When I Work
Named payroll processors receive the pay-period hours directly, the period closes as a lock that only an admin or manager can reopen, rounded entries can be transmitted, and a documented API with webhooks exists. But every named payroll target is North American — we found no public information on DATEV or any German payroll system — surcharge mapping stops at overtime multipliers, and the documented fallback is a generated spreadsheet, which to me says the handoff was never designed for a Lohn office.
European sovereignty
Deputy
The contracting entities are named — Deputechnologies Pty Ltd in Australia, with Deputy Corporation in San Francisco for the Americas — and a self-serve data processing agreement and a published sub-processor list exist. We found no public information on where employee data is hosted, on any EU hosting claim, or on a European entity or transfer safeguards.
When I Work
Primary data centers are in the United States, the contracting entity is When I Work, Inc. of Minneapolis, and non-US storage appears only as a "may be stored and processed in your region" without a named provider. Transfers out of restricting jurisdictions rest on approved standard contractual clauses or consent, which is the stated safeguard that keeps this above the bottom, but no hosting option, subprocessor list or certification is documented.
Pricing transparency
Deputy
Lite, Core and Pro carry public per-user prices with annual and monthly figures, taxes stated as excluded, and the Analytics+, Messaging+ and HR add-ons priced per user per month. The payroll add-on is unpriced on the public pages — the stated basis is a monthly base and per-employee fee that varies by business size — the Flexi and charity plans carry no number, and we found no public information on how inactive or seasonal staff are counted, so the real annual invoice is not computable from the pages alone.
When I Work
Both self-serve price points are public — "$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, no setup fees, no contracts, and scheduling, time tracking and messaging included in every plan. Enterprise pricing is a sales conversation, and we found no public information on VAT treatment or how inactive or seasonal staff are counted, so the annual invoice is not fully computable.
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.