When I Work Setup: Day-Zero Path to a Working HR Loop

When I Work 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/when-i-work/. Worked example: Harbor Retail (two recruiters and eight hiring managers) lists everyone who must log in weekly before they invite “the whole company.”

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.

Our snapshot records no trial length for When I Work — 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.

Research lists Slack and Zapier for When I Work. Confirm which are native vs API before go-live.

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

Worked example: Hourly teams that mainly need scheduling and messaging at a low per-user price connects the one integration that prevents double entry before inviting the full team.

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

Worked example: Hourly teams that mainly need scheduling and messaging at a low per-user price runs a 30-minute working session on live data and includes one sceptic who will actually use the tool.

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/when-i-work/ for commercial detail.

Worked example: Hourly teams that mainly need scheduling and messaging at a low per-user price stores a one-page note finance and IT can read without joining another demo.

Research lists Slack and Zapier for When I Work. Confirm which are native vs API before go-live.

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

Worked example: Hourly teams that mainly need scheduling and messaging at a low per-user price connects the one integration that prevents double entry before inviting the full team.

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

Worked example: Hourly teams that mainly need scheduling and messaging at a low per-user price runs a 30-minute working session on live data and includes one sceptic who will actually use the tool.

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/when-i-work/ for commercial detail.

Worked example: Hourly teams that mainly need scheduling and messaging at a low per-user price stores a one-page note finance and IT can read without joining another demo.