Deputy vs When I Work

Deputy

Auto-scheduling, demand forecasting, micro-scheduling and multi-location hierarchies are all named features, but the captured pages never name the data source the forecast draws on, and I found no public information showing staffing requirements per shift, qualifications or coverage gaps before publication. The engine is branded "Deputy AI included in every plan" rather than documented as a method. That sits above a plain weekly grid yet well short of demonstrated demand-based planning.

When I Work

Shift templates, skills and certification management, OpenShifts, labor sharing across unlimited locations and an auto-scheduler matching shifts by eligibility, availability and preferences are all evidenced, which carries this well past a plain weekly grid. The forecasting story compares scheduled hours against future demand, but the pages never name the demand data source and the auto-scheduler is said to use "workforce management app data", so I found no public information on what the forecast actually consumes; coverage gaps before publication are also not shown.

Deputy

Every captured page repeats "Labor Law Compliance", with "Break planning compliance" and "Fair workweek compliance" — the latter a US predictive-scheduling regime — but no page names the ArbZG daily maximum, the 11-hour rest period or a Minijob earnings limit, and nothing states whether a violation blocks publication, warns the planner or merely exports. This is precisely the compliance-is-"supported" claim with no rule behind it that I keep hoping a vendor will finally cash out.

When I Work

The pages describe "overtime and break tracking" and paid-break tracking, which is a record of hours, not a check: nothing says a rule warns the planner or blocks publication, and no specific rule is ever named. The terms state the service is designed for use in the United States, and I found no public information on the ArbZG daily maximum, the 11-hour rest period, youth or maternity protection, Minijob limits or collective-agreement surcharges.

Deputy

The lite tier's own list gives the shop floor a mobile app with availability, leave, shift swap and "Find Replacement", plus a time clock app — most of a real self-service set. I found no public information on whether swaps are checked against qualifications or rest periods before approval, on offline clock-in, on multilingual coverage, or on push notification of changes, so it reads as mid-level with the rule-checking question unanswered.

When I Work

The floor worker gets real substance: mobile apps with availability entry, time-off approval, swap review, open-shift claiming, instant notifications, GPS clock-in and built-in messaging that spares personal phone numbers. I found no public information on swaps being checked against qualifications or rest periods before approval, offline handling, a multilingual interface, or employees seeing and exporting the data held about them.

Deputy

There is a privacy centre with GDPR resources, sub-processor change notifications and configurable access levels — though those access levels sit in the top tier, and "additional audit reporting" is sold as an add-on rather than shown as a per-employee view log. I found no public information on retention or deletion periods for availability and absence data, on whether biometric time clocking can be switched off, or on any documentation a works council would need for approval.

When I Work

Admin, Supervisor, Manager and Employee roles with custom role permissions and "Advanced privacy and data controls" are the only visibility configuration shown, and nothing says who can see absence reasons. GPS and geofencing clock-in is marketed as a feature, the privacy policy describes location collection "where you grant this permission", and I found no public information on whether monitoring can be switched off, on an audit log of views and changes, on retention or deletion periods for employee records, or on any documentation a works agreement would need.

Deputy

A public API is listed and a payroll module is "available on annual Core and Pro plans in the US" with a base and per-employee fee that "varies by business size" — unpriced and US-only, while "Payroll & HR Integrations" names no system. I found no public information on a DATEV or Lohn-und-Gehalt handoff, no named POS integration, and surcharges are never mentioned, so the month's export remains a claim rather than a documented path.

When I Work

Named payroll sync with Rippling, ADP, QuickBooks and Gusto covering attendance and labor data, a POS integration and a documented API are genuinely more than a CSV. I found no public information on surcharge or wage-type mapping, on a lock step before transmission, on a German payroll path such as DATEV Lohn und Gehalt, or on which tier the time clock sits in beyond a reference to licensing the Time & Attendance feature.

Deputy

The contracting entity on the captured pages is Deputy Corporation of San Francisco, the parent is Australian, and I found no public information on an EU entity, on where employee data is hosted, or on any named subprocessor chain — the privacy centre confirms only that other sub-processors exist with locations unstated. A scheduling tool holding availability and absence data with no evidenced EU residence or processor transparency sits at the bottom of this scale.

When I Work

The contracting entity is When I Work, Inc. of Minneapolis, primary data centers are in the United States, and the terms are governed by Minnesota law. I found no public information on EU hosting, an EU entity, or a published subprocessor list; the only named third-party processor is Clair for on-demand pay.

Deputy

Three tiers carry public per-user prices — Lite "$5 per user per month", Core "$6.50 per user per month", Pro "$9 per user per month (USD excl. all applicable taxes)" — with a stated 10% annual discount and billing options, but the payroll add-on's fee "varies by business size", the AI is "introductory free" with no after-price, the Flexi plan carries no number, and I found no public information on how inactive or seasonal staff are counted or on any minimum term. The main tiers are computable; the real annual invoice is not.

When I Work

The pricing page publishes "Single location or schedule $2.50 /user/month" and "Multiple locations or schedules $5 /user/month" with monthly or annual billing, no setup fees and no contracts, so the main per-head maths is computable. Enterprise pricing is a sales conversation, the single-sign-on and API question points the same way, and I found no public information on how inactive or seasonal staff are counted or on VAT treatment.