Deputy Setup: Day-Zero Path to a Working HR Loop

Set up Deputy for day-zero work — seats, one core loop, required integrations, and non-admin proof — before optional hubs.

By Lee M.Updated Aug 18, 20267 min readFact-checked

Quick answer

Set up Deputy in this order: qualify seats for the people who will actually open it, name one HR/ops owner, configure one hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run, connect the HRIS/payroll/calendar you depend on, then have a non-admin run a hiring manager moves a candidate and leaves feedback without an admin. Confirm core hris (Lite+) and payroll processing (Lite+) are on the package you will actually buy. You’re done when that walkthrough works — not when every optional hub is switched on.

Start on the entry package on the pricing page
Name one HR / ops owner
one hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run
Connect required HRIS / payroll / calendar
Prove a non-admin can run the loop

What matters in your Deputy setup

What Deputy actually is — Deputy is a shift-work platform for scheduling, timekeeping, compliance, comms, and optional HR/payroll add-ons. Published USD per-user: Lite list price Core list price (most popular), Pro list price list price monthly invoice minimum. All users including mana…
Configure these first — Research lists applicant tracking, career site and job boards, core hris, and payroll processing as supported — that is your day-zero surface.
Do not treat it as every HR job — Deputy is applicant tracking / recruiting. It is not a substitute for frontline scheduling or a GPS time clock.
Prove with a real workflow — Worked example: Harbor Retail (two recruiters and eight hiring managers) is done when they can a hiring manager moves a candidate and leaves feedback without an admin — not after a vendor tour.

Deputy day-zero path

Deputy setup walkthrough for applicant tracking / recruiting. — A working Deputy core loop beats a decorated empty workspace.

Deputy must vs nice

Must-have

Core job loop
Plan / hub gates
Integrations

Nice-to-have

AI extras

1. Qualify seats and packaging

Deputy is often sold on seats, hubs, pools, or quote packaging in our snapshot — treat homepage tiles as marketing, not a bill of materials. Confirm live packaging on the pricing page. Never invent list prices here — confirm seats, hubs, and quote terms on /pricing/deputy/. Worked example: Harbor Retail (two recruiters and eight hiring managers) lists everyone who must log in weekly before they invite “the whole company.”

2. Configure one core loop

Configure one hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run. Research-supported surfaces include applicant tracking, career site and job boards, workforce scheduling, and frontline communications. Worked example: Harbor Retail (two recruiters and eight hiring managers) refuses optional modules until a hiring manager moves a candidate and leaves feedback without an admin.

3. Non-admin proof

Our snapshot records no trial length for Deputy — ask for an evaluation window in writing before you commit seats. Success: a hiring manager moves a candidate and leaves feedback without an admin. Worked example: Harbor Retail (two recruiters and eight hiring managers) records a 10-minute loom of the walkthrough for stakeholders who skip hands-on time.

Deputy checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1Name an HR/ops ownerFields, users, and hygiene need a responsible party.
2Configure one core loopone hiring pipeline, one career-site job, and interview scheduling that a hiring manager can run
3Complete non-admin proofa hiring manager moves a candidate and leaves feedback without an admin

4. Connect the integrations Deputy must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.

Research lists Slack, Zapier, and Google Workspace for Deputy. Confirm which are native vs API before go-live.

Pick one identity or SSO path if required.
Connect one operational integration the weekly users touch daily.
Document anything left as manual export.

Worked example: Multi-location hourly operators who need scheduling + time + labor compliance connects the one integration that prevents double entry before inviting the full team.

5. Train weekly users — not a one-time all-hands

Train the people who must open Deputy every week. Cover: login, the core loop (applicant tracking, career site and job boards, and workforce scheduling), and where to log blockers.

Worked example: Multi-location hourly operators who need scheduling + time + labor compliance runs a 30-minute working session on live data and includes one sceptic who will actually use the tool.

6. Write the setup note stakeholders can audit

Document plan tier, admin owner, integrations live, and the non-admin proof (applicant tracking, career site and job boards, and core hris). Link to /pricing/deputy/ for commercial detail.

Worked example: Multi-location hourly operators who need scheduling + time + labor compliance stores a one-page note finance and IT can read without joining another demo.

7. Connect the integrations Deputy must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.