Deputy does schedule inside a shift. Micro-scheduling, included on the Core plan, splits one shift into back-to-back segments across different locations and areas, then feeds those segments into timesheets. If someone told you Deputy has no within-shift scheduling, they were working from old information.
The distinction that matters is the axis. Micro-scheduling answers where a person works during a shift. It does not answer what they are doing against demand at 14:30, and by Deputy's own documentation it cannot leave a gap, which is precisely what a break is.
Every limitation on this page links to Deputy's own help or developer documentation. Prices are published list prices, checked 25 August 2026.
A retail or hospitality worker who spends two hours on the floor, three on the till and one in the stockroom is one shift and three areas. Deputy models that cleanly, and because the segments flow into the timesheet, the hours land in payroll attributed to the right place. For that job it is the better tool, and it is on a cheaper plan than ours.
Deputy Core also carries auto-scheduling and demand forecasting at $6.50 per user per month. That is real capability at a real price, and any comparison that pretends otherwise is not worth reading.
These are not complaints from reviews. They are constraints Deputy publishes, linked so you can check each one.
Deputy documents that you cannot leave any gaps of time between areas. The segments of a micro-scheduled shift have to run back to back. That is the right model for tracking where someone stood, and the wrong one for a break, which is defined by being time nobody is covering.
Deputy documentation: Micro-scheduling FAQsMicro-scheduling supports a single pay rate applied to every part of the shift. If a person moves between work that pays differently inside one shift, that has to be handled outside the feature.
Deputy documentation: Micro-scheduling FAQsThe cap is thirty areas per shift, which is generous. The constraint that bites is conceptual: an area is a location you can be assigned to, so the axis is where a person is, not which of several concurrent workloads they are serving.
Deputy documentation: Work a shift with micro-schedulingGeofencing is available only for single-area shifts, and no geofencing applies to a micro-scheduled timesheet. Teams that adopted Deputy partly for location-verified clock-in give that up on exactly the shifts they most want to subdivide.
Deputy documentation: Managing micro-scheduled shifts and timesheetsOne question separates these two tools. Answer it honestly and the choice is usually clear.
Multi-site retail, hospitality and venue teams where one person legitimately works the floor, then the till, then the stockroom. Micro-scheduling was built for this, it feeds timesheets correctly, and Deputy Core is cheaper than the Soon plan that carries intraday.
Contact centres, service desks and operations teams where everyone sits in one place all day and the planning problem is which of four or five concurrent workloads each person is on, and whether the queue is covered at 14:30.
Soon Scale, the plan carrying intraday coverage, lists at $16 per user per month billed yearly, against $6.50 for Deputy Core. We are the more expensive option, and that only pays back if coverage inside the shift is a problem you have. The full feature-by-feature view is on our Soon versus Deputy page, including the rows Deputy wins.
Partly, and the honest answer depends on what you mean. Deputy ships micro-scheduling on its Core plan, which splits one shift into contiguous segments across different locations and areas. That is genuine within-shift scheduling on the dimension of where someone works. It is not interval-level coverage planning against forecast demand, and because Deputy documents that no gaps are allowed between areas, breaks are not represented as first-class blocks.
Micro-scheduling lets one employee work multiple segments across different locations and areas within a single shift. By default the shift length is divided evenly across the areas you add, and you can then adjust each segment start and finish time. Deputy supports up to thirty areas per shift. It is documented as feeding timesheets, so its primary job is accurate time and pay attribution.
Deputy handles breaks through its break planning and award compliance features rather than through micro-scheduling. Micro-scheduling itself cannot express a break as a segment, because Deputy documents that gaps of time between areas are not allowed and every segment must run back to back.
No. Deputy Core, the plan that includes micro-scheduling, auto-scheduling and demand forecasting, lists at 6.50 US dollars per user per month. Soon Scale, the plan that includes intraday coverage tracking, the AI assistant and forecasting, lists at 16 US dollars per user per month billed yearly. Soon costs more per user. The comparison only makes sense if interval-level coverage is a problem you actually have.
Some teams do, keeping Deputy for time clock, award interpretation and payroll export while planning coverage in Soon. It is not the cheapest arrangement and it means two systems, so it is usually worth deciding which tool owns the schedule rather than running both indefinitely.
Import your team, set your rules, hit auto-fill. Most teams are live the same day.
30 days free ยท No credit card required
Already have an account?Sign in
