Shiftboard vs Deputy 2026: A Staffing Buyer's Guide

Choose for scheduling rules, then for daily operations

Choose Shiftboard when the difficult part is enforcing assignment policies across complex operations; choose Deputy when the priority is managing schedules, attendance, and routine workforce administration within clearly published subscription tiers. That is a shortlist recommendation based on public product information, not a measured performance ranking. For a staffing agency, the deciding question is whether the scheduler can represent your client assignments and eligibility rules without creating another reconciliation spreadsheet.

The product names need clarification before you compare older reviews. UKG acquired Shiftboard in 2025, according to Recruiter. Shiftboard's main website now redirects to a customer resource page identifying UKG Shiftboard and UKG ScheduleFlex as 2 separate login destinations, according to UKG. Acquisition does not mean both products have disappeared, nor does it establish that their historic packages remain available to new buyers.

Deputy continues under its own brand and is privately held, with Express Employment Professionals among its listed investors; its funding record describes a strategic investment in March 2024, according to Multiples. That older investment record does not disclose the complete current ownership split. Treat investment, product ownership, and an integration relationship as different facts when reviewing procurement documents.

Workforce scheduling software assigns eligible workers to shifts while tracking availability, coverage requirements, and relevant scheduling constraints.

TL;DR: Start with UKG Shiftboard for complex policy enforcement and Deputy for a more standardized scheduling-and-attendance purchase. If your original shortlist specifically meant ScheduleFlex, require UKG to confirm its current offer and scope before comparing it with Deputy. Neither choice should proceed until your client mapping, worker permissions, and payroll handoff pass a practical buyer exercise.

Key Takeaways

• Shiftboard's acquisition changes the buying context: identify the exact UKG product and contract scope rather than treating every historic Shiftboard feature as interchangeable.

• Deputy's published tiers make initial subscription comparison easier, but rotating workers, administrator accounts, billing rules, and add-ons still affect total cost.

• Scheduling eligibility must include the client's requirements, not merely the worker's availability; demonstrate expired credentials and conflicting assignments before signing.

• A payroll integration needs an accurate assignment and pay-code mapping, a reconciliation process, and a named reviewer for exceptions.

• Keep the scheduling system authoritative for assignments; add cross-system orchestration only when the missing handoff has clear inputs, permissions, and review points.

Who this is for: agencies responsible for client coverage

This guide is for a staffing scheduling lead who allocates workers to client locations and needs a defensible purchasing decision. It is especially relevant when recruiters, dispatchers, client supervisors, and payroll staff each hold part of the assignment record. Your agency may need centralized control while clients need restricted visibility into their own schedules.

Weekly staffing workforce: nearly 2.2 million temporary and contract employees worked during an average week in 2024, according to American Staffing Association (2024). That is industry context, not a sizing recommendation for either vendor. For your purchase, the meaningful unit is the assignment: which client requested it, which worker qualifies, who approved it, and how the resulting time reaches payroll.

Red flags: You need a complete applicant tracking and client invoicing system from this purchase; you cannot obtain authorized exports or integration access; you expect software to approve ambiguous employment or scheduling policies without human review.

Those conditions do not automatically disqualify scheduling software. They disqualify a purchasing brief that asks a scheduler to solve undefined responsibilities. Document which existing system owns recruiting, credential evidence, pay rates, and billing. Then evaluate the scheduler against its actual role.

How we evaluated staffing scheduling fit

Our weights emphasize the work that creates staffing exceptions: eligibility, changing coverage, and accountable handoffs. They are editorial priorities, not vendor scores or survey findings. The proof-case counts below are suggested buyer exercises, not published platform limits. Change the weights before reviewing proposals if payroll or client separation is your dominant risk.

Apply the weights only after checking disqualifiers. A polished schedule screen cannot compensate for inadequate client access restrictions or an eligibility rule that cannot be represented. Mark any unproven requirement as unknown rather than awarding partial credit because a brochure mentions compliance.

Use the same anonymized assignment packet for both vendors. Include a client request, worker availability, required training, an absence, a correction, and the intended payroll output. Record whether the demonstrated behavior is native, configurable, integration-dependent, or unavailable. Those labels are more useful than an unsupported overall score.

For a related example of comparing a specialized operating system against surrounding workflow needs, see our platform selection guide for dental membership operations. Its industry requirements differ; the transferable lesson is to define the transaction and its owner before counting features.

Normalize the features around an assignment

The matrix separates documented capabilities from requirements that still need proof. “Confirm” means the public evidence did not establish the precise staffing use case or entitlement. It does not mean the feature is absent. The UKG column refers to UKG Shiftboard's current positioning; do not silently apply it to ScheduleFlex.

The comparison should stop at an evidence boundary. “Payroll integration” does not establish client invoicing, and “training-based scheduling” does not establish a connection to your credential database. Likewise, a permissions feature does not prove that an external client supervisor can be granted exactly the intended access.

Ask each vendor to show what happens when the necessary information is missing. A scheduler should not treat a stale credential export as affirmative eligibility, and an integration should not interpret an unreadable payroll response as success. Your acceptance record should distinguish a rejected assignment from an unknown check requiring review.

Shiftboard profile: start with the policy problem

UKG's product material positions UKG Shiftboard around union agreements, fatigue rules, labor laws, and 24/7 operations, according to UKG. That makes it a credible shortlist candidate when scheduling itself is the complex operating problem. Its public positioning is particularly relevant to industrial client assignments where fairness rules and safe coverage matter alongside availability.

Best fit: Your agency needs to explain why a particular worker could or could not receive an assignment, and your client expects scheduling policies to be applied consistently. This is our fit assessment, not a claim that UKG has already modeled your policies. Bring an example involving competing constraints and ask the vendor to explain the order of evaluation.

Limitations: The acquisition creates a scope question for buyers using older SchedulePro or ScheduleFlex comparisons. Current public materials do not establish that every historic package, integration, or commercial arrangement carries forward unchanged. Require the proposal to identify the actual product, implementation services, supported interfaces, and any separate workforce management components.

Implementation should begin with a policy inventory and a data ownership map. Separate hard eligibility rules from preferences, and identify the person allowed to approve an exception. Load anonymized workers and assignments into a candidate environment, then examine the explanation for an excluded worker, a replacement decision, and a corrected schedule.

Choose Shiftboard if that exercise demonstrates the policy depth you need and the commercial scope is clear. Disqualify the proposed configuration if it cannot distinguish client-specific eligibility or cannot produce a reviewable explanation for a disputed assignment. A longer policy setup may be justified; an undefined product boundary is not.

Deputy profile: make the routine operating loop accountable

Deputy's public offering combines scheduling and attendance functions in the Lite, Core, and Pro tiers. Its plan information differentiates basic scheduling from advanced scheduling and forecasting, and places additional access controls in Pro. This creates a more explicit starting point for deciding which capabilities your agency needs to purchase.

Best fit: Your main problem is coordinating availability, open assignments, attendance, and payroll preparation with a consistent operating process. Deputy belongs on the shortlist when dispatchers and workers need a shared schedule and your eligibility policies can be represented without an extensive external decision engine.

Limitations: Tier clarity does not prove staffing-specific completeness. A client location, a scheduling area, and a billable assignment may be different objects in your operating model. Confirm how the proposed configuration distinguishes them. Also confirm whether the required client permissions and integration functions are included in your selected plan.

Implementation should begin with location and area design, worker identity matching, and payroll mapping. Ask an actual dispatcher to perform a cancellation and correction using anonymized data. Have payroll examine the output independently. The exercise should expose whether the proposed structure will create duplicate records or require manual reclassification.

Choose Deputy if the normal scheduling loop is understandable to your team and the exception path is equally clear. Disqualify the configuration if a worker's assignments across client locations cannot be checked together or if your required supervisor access reveals unrelated client data. An easier initial setup is valuable only when the ongoing controls hold.

Pricing and TCO: normalize the roster before the rate

Pricing checked October 10, 2026.

The table reports the vendor's displayed US-dollar subscription rates and separates them from quote-only purchasing questions. Prices exclude applicable taxes. Confirm the selected billing cycle and account-specific terms before using the headline rates in a budget. The grouped Deputy row presents the plans in the same order as their rates so the comparison does not invent a blended subscription price.

No public numeric Shiftboard price was verified. Its former pricing routes were either unreadable or redirected to UKG product information without a numeric subscription rate. “Quote-based” is the purchasing label used here; it is not an estimate, a claim that the service is unavailable, or evidence that it costs more than Deputy.

For Deputy, the pricing page says administrators and supervisors count as users. It also describes full-month billing when users are added, archived, or unarchived during a monthly billing period. For an agency rotating workers between assignments, ask finance to model the billable roster across the cycle rather than budgeting only for workers currently on shift.

Normalize TCO with the same categories for both proposals: subscription, implementation, policy administration, integration maintenance, message charges, support, and exception handling. Keep unknown amounts visible. Do not convert an unquoted implementation fee into a zero-cost assumption.

The lower subscription rate may still be the appropriate purchase if native functions handle your workflow. Conversely, additional setup may be justified when it removes a difficult scheduling-policy gap. Make that judgment from demonstrated behavior and a written scope, not a speculative savings percentage.

The handoff between scheduling, credentials, and payroll

A proposed US Tech Automations workflow could begin when an authorized scheduler export or API response shows an unfilled assignment. It would match the assignment to the agency's worker IDs, consult an authorized credential export, and produce a dispatcher review queue showing eligible candidates and unresolved checks. Prerequisites include supported access to the selected scheduling product, a maintained client-assignment map, current credential evidence, and approved data permissions. The dispatcher reviews exceptions and approves the assignment; the proposal does not assume an automatic booking or an existing deployment.

A separate configurable US Tech Automations workflow could trigger when an approved time record becomes available through a supported API or export. It would compare worker, assignment, hours, and pay-code mappings against the payroll import specification, then produce a reconciled import draft and an exception report. Payroll reviews discrepancies before upload or authorized writeback. This requires accessible approval status, stable identifiers, an agreed payroll schema, and retained processing records. It describes a possible design, not a customer result or a currently connected system.

For a concrete illustrative coverage check, Deputy documents a default roster window covering Forward look: 36 hours and the previous 12 hours, and its sample roster response includes the metadata object _DPMetaData and the nested break object Slots.mixedActivity, according to Deputy. The documented window totals 36 + 12 = 48 hours. Assume a fictional client needs continuous coverage in 8-hour blocks: 48 ÷ 8 = 6 blocks. Those block counts are arithmetic assumptions, not actual bookings or vendor performance. A dispatcher would still review each assignment's eligibility and local times, while the integration must request an explicit range when the required planning horizon exceeds the default.

This example also separates metadata from business approval. The presence of an API object does not prove that a client accepted a worker or that payroll should pay a particular rate. Maintain those decisions in their designated systems and carry their identifiers into the reconciliation evidence.

For an adjacent example of the trigger, calculation, and review pattern, our campaign pacing exception recipe shows the general structure. Staffing needs different rules and authorization, but the ownership question is similar: who reviews an exception before it changes an operational commitment?

DIY automation versus a configured operating design

Zapier, Make, n8n, or an in-house service can be a reasonable way to connect exports and APIs. Those tools can support run histories, retries, error branches, and audit evidence when configured. A staffing agency with an accountable technical owner may prefer that approach for a narrow handoff whose inputs and failure modes are well understood.

The buyer must still design and own observability, idempotency, escalation, access controls, and maintenance. Idempotency means a repeated input should not create a duplicate operational action. Decide how the workflow recognizes a corrected timesheet, distinguishes it from a replay, and alerts the owner when a credential source is unavailable.

A proposed orchestration design could configure persistent assignment-to-worker mappings, separate unknown eligibility from rejection, retain review decisions, and route payroll exceptions to a named owner. The prerequisites are the same authorized interfaces and reliable source data required by DIY. Human review remains necessary for policy exceptions and disputed time; adding another service does not supply missing authority.

Our agency software evaluation guide offers a related purchasing pattern: judge the surrounding review process as well as the software interface. For scheduling, the practical question is whether your team can diagnose and recover a failed handoff without reconstructing it from scattered messages.

A shortlist exercise that exposes the expensive failures

Use the following buyer-authored pilot packet in a copy or candidate environment. Every count is a suggested exercise target, not a published limit or a measured result. An unresolved check should remain visible as unknown rather than being recorded as a successful rejection or approval.

First, freeze the proposed product and plan. Write down which features are native, which require configuration, and which depend on another system. This prevents a successful demonstration from quietly relying on an unquoted component.

Next, run the pilot packet with your dispatcher and payroll reviewer present. Include a correction after the first processing attempt. Ask what the operator sees when an upstream system fails, how recovery proceeds, and whether the recovery preserves the original decision evidence.

Finally, compare the exception records alongside the commercial proposal. Select the configuration that satisfies the disqualifiers and gives your team a maintainable operating process. Keep unresolved requirements in the decision record rather than burying them in a favorable average score.

Questions staffing buyers ask before signing

Is Shiftboard still available after the UKG acquisition?

UKG identifies current customer access for UKG Shiftboard and UKG ScheduleFlex, but new-buyer scope needs confirmation. Specify the product in your request and avoid assuming that a historic ScheduleFlex package is the current commercial offer.

Is Deputy automatically the cheaper choice?

No, a public subscription rate does not establish a lower total cost. Compare billable roster behavior, implementation, interfaces, add-ons, and the effort required to handle exceptions before making a cost claim.

Which product should handle complex union or fatigue rules?

UKG Shiftboard is the more directly positioned shortlist candidate for those scheduling requirements. Require a demonstration using your actual policy structure, including conflicting rules and the person authorized to review an exception.

Can either product replace our entire staffing software stack?

This comparison does not establish a complete replacement for an agency's recruiting, credential, payroll, and client billing systems. Keep those responsibilities explicit and prove the handoffs that the proposed scheduler actually supports.

When NOT to use US Tech Automations?

Keep the simpler existing tool when native scheduling and payroll functions already cover the process, when a narrow DIY workflow has a capable owner, or when source access and reliable identifiers are unavailable. A proposed US Tech Automations design could reconcile approved records and route exceptions, but it should not add another system to a process that already has adequate controls.

What should we settle before committing to a plan?

Settle product identity, client separation, worker eligibility, billable-user rules, and the payroll acceptance process. An unresolved requirement should have an owner and a proof task before it becomes a contractual assumption.

Choose the scheduler, then close the demonstrated gap

Shortlist Shiftboard for difficult scheduling-policy enforcement and Deputy for a clearly tiered scheduling-and-attendance workflow. If ScheduleFlex is the actual candidate, obtain its current scope separately. Let your anonymized assignment exercise decide the purchase, with unknown requirements left visible.

Once the scheduler is selected, see how US Tech Automations could configure the reconciliation handoff around authorized APIs or exports, stable assignment identifiers, and human approval points. Add orchestration where the exercise demonstrated a missing step, and keep the chosen scheduler responsible for its scheduling decisions.