New hires open Workday on day one expecting a clear 1-through-6 checklist, and instead meet a flat My Tasks queue mixing Contact Change, Manage Payment Elections, Complete Federal Withholding Elections, Review Documents, and IT equipment To Do steps in no obvious order. Presenting those exact live Workday business process steps as a grouped, plain-language progress screen inside Microsoft Teams, Slack, or a clean browser tab lets incoming employees finish day-one administration in one sitting without changing your underlying Workday Onboarding business process.
You do not need to rip out your Workday staffing rules or buy a separate enterprise onboarding suite that syncs stale CSV snapshots overnight. Every task, condition rule, and security policy already lives inside Workday—what new hires lack is a calm visual sequence over those APIs.
Why Standard Workday Onboarding Feels Fragmented to a First-Time User
From an HRIS architect’s perspective, the Onboarding business process (Steps: Set Up Onboarding Business Process) is clean and modular. Triggered after the Hire completion step and Create Workday Account (directly following Onboarding Setup), it fans out into specialized subprocesses so Payroll, Benefits, Compliance, and HR Operations each own their own validations and approvals.
To a new employee who has never seen Workday terminology before, that modular fan-out creates four immediate points of friction:
- Unfamiliar Action Labels in My Tasks: Even when administrators populate the
Checklist Labelfield on a Tasks step, subprocesses likeEdit Government IDs,Change Emergency Contacts,Manage Payment Elections, andChange Benefit Electionsland alongside each other with internal HR nouns rather than plain sequence cues (“Step 2 of 5 — Where to send your paycheck”). - Pre-Start vs. Day-One Step Delays: Best-practice Workday configurations use
Business Process -> Maintain Step Delayso pre-hires complete initial forms before day one while holdingComplete Form I-9(or Section 2 verification) andChange Benefit Electionsuntil the start date. Without a visual timeline showing Done before Day 1 vs. Unlocks Monday morning, new hires think steps are missing and email HR. - All-or-Nothing Document Bundles: A single
Review Documentsstep often bundles five PDFs—Employee Handbook, Confidentiality Agreement, Acceptable Use Policy, Safety Acknowledgment, and Arbitration Opt-Out—behind small attachment links and e-signature checkboxes that are awkward to read on a phone or laptop split-screen. - Disconnected Manual To-Dos: Equipment sizing, badge photo uploads, and manager 30-day check-ins frequently sit as bare Workday
To Dosteps whose instructions tell the worker to open another tab, fill out a separate form, and remember to come back to Workday to click Submit.
Mapping Workday Onboarding Subprocesses to a Calm Day-One Checklist
A well-structured onboarding screen keeps Workday as the single system of record while organizing live inboxTasks and completed Onboarding event steps into four clear stages:
| Checklist Stage Seen by New Hire | Underlying Workday Subprocess / Step Type | Workday Security Domain (Employee as Self / Pre-Employee as Self) |
Live API Read & Write Path |
|---|---|---|---|
| Checklist Stage Seen by New Hire1. Confirm Who You Are & Emergency Contact | Underlying Workday Subprocess / Step TypeTasks step (Contact Change / Home Contact Change, Preferred Name Change, Change Emergency Contacts) |
Workday Security Domain ( Employee as Self / Pre-Employee as Self )Self-Service: Home Contact Information, Self-Service: Preferred Name, Self-Service: Emergency Contacts |
Live API Read & Write Pathcommon/v1 /workers/me/inboxTasks, person/v4 /homeContactInformationChanges, Human_Resources SOAP Change_Emergency_Contacts |
| Checklist Stage Seen by New Hire2. Direct Deposit & Tax Withholding | Underlying Workday Subprocess / Step TypeManage Payment Elections, Complete Federal Withholding Elections, state/local tax steps |
Workday Security Domain ( Employee as Self / Pre-Employee as Self )Self-Service: Payment Election, Self-Service: Payroll (My Withholding Elections) - USA (or CAN) |
Live API Read & Write PathLive task state via My Tasks REST and WQL; deep-link or SOAP/REST completion under user token |
| Checklist Stage Seen by New Hire3. Work Eligibility & Company Policies | Underlying Workday Subprocess / Step TypeComplete Form I-9 (Section 1), Edit Government IDs, Review Documents |
Workday Security Domain ( Employee as Self / Pre-Employee as Self )Self-Service: I-9 Forms, Self-Service: Government IDs, segmented Document Categories |
Live API Read & Write PathbusinessProcess/v1 event step details, document attachment retrieval, and step acknowledgment |
| Checklist Stage Seen by New Hire4. Day-One Setup & Benefits Window | Underlying Workday Subprocess / Step TypeTo Do steps (laptop, badge, Slack/Teams intro) and Change Benefit Elections |
Workday Security Domain ( Employee as Self / Pre-Employee as Self )Self-Service: Benefits (plus life-event BP security policy) |
Live API Read & Write PathPOST /businessProcess/v1/eventSteps/{ID}/toDo, remaining enrollment days countdown via WQL |
Because every API call executes under the new hire’s own user-delegated Workday OAuth 2.0 token (Register API Client, Authorization Code Grant with PKCE), Workday enforces the exact same country-specific address and emergency contact validations, step conditions, and downstream approvals as the native Workday browser UI.
Reading Live Onboarding Progress Without Syncing a Shadow Database
Traditional onboarding portals copy worker records into an external database on a 6-hour schedule. That architecture fails on day one: a new hire finishes Change Emergency Contacts at 9:14 AM, refreshes the portal at 9:15 AM, and still sees the step marked incomplete—while their CISO has to audit a second cloud database holding home addresses and government IDs.
A stateless pass-through screen queries Workday live on page load using the signed-in employee’s Bearer token. Two lightweight calls assemble the entire progress bar in milliseconds:
- Open Actions (
common/v1): Retrieve the worker’s active queue (GET /workers/me/inboxTasks) to identify every awaiting Onboarding step ID, step type, assigned date, and due date. - Completed & Delayed Steps (
wql/v1): Query theOnboardingbusiness process event for the worker so the checklist renders green checkmarks for tasks already finished during pre-boarding and shows release dates for delayed day-one steps:
SELECT businessProcessEvent,
eventStatus,
effectiveDate,
completedSteps,
awaitingActionSteps
FROM businessProcessTransactionsForWorker
WHERE worker = currentWorker()
AND businessProcessType in (onboardingBusinessProcessTypes)When the worker checks off an equipment receipt or manager welcome item on the checklist, the screen calls Workday’s businessProcess/v1 step action directly:
POST /ccx/api/businessProcess/v1/{tenant}/eventSteps/{eventStepWid}/toDo HTTP/1.1
Authorization: Bearer <employee_oauth_access_token>
Content-Type: application/json
{
"comment": "Confirmed laptop serial number and badge pickup at Day-1 orientation."
}Workday records the completion in the business process audit trail initiated by the employee themselves, fires the next conditional step in the Onboarding definition immediately, and updates the progress bar on screen from 3 of 6 complete to 4 of 6 complete with zero cached state.
Why Embedding the Checklist in Teams, Slack, or Mobile Changes Completion Rates
New corporate hires live inside Microsoft Teams, Slack, Feishu, or Lark during their first week; retail, hospitality, and warehouse hires live on their phones. Forcing either group to hunt through corporate bookmarks, locate the Workday tile, navigate to My Tasks, and decipher 11 ungrouped rows guarantees stalled steps and manual HR Partner chase emails (Mass Advance Onboarding Setup Events).
Putting the checklist directly inside a pinned Teams tab, a Slack app home view, or a branded phone screen changes three practical behaviors:
- Clear Time Estimates Per Card: Grouping quick actions (Confirm Home Address & Emergency Contact — 2 min) separately from document-heavy steps (Direct Deposit & W-4 — have a voided check handy) stops workers from abandoning a half-finished form mid-orientation.
- Plain-Language Context Beside Live Tasks: When a new hire wonders why a step asks for routing details or how medical benefit deadlines work, pairing visual checklists with live first-week Workday answers resolves questions before they become HR tickets.
- Privacy-Safe Reminders: Instead of emailing sensitive task details to personal inboxes, a short Teams message or mobile push notification says “2 day-one items left before payroll cutoff” and opens straight into the authenticated checklist.
Building Day-One Onboarding Screens with Kiweely Leaf and Bridge
Two upcoming Kiweely products—both coming next—cover the visual and conversational halves of day-one onboarding without requiring a Workday Extend license:
- Kiweely Leaf (coming next) lets HRIS administrators describe an onboarding checklist or employee portal in plain English. AI agents inspect your live Workday tenant’s Onboarding business process steps, security domains, and localized fields, wire the standard Workday OAuth 2.0, REST, WQL, RaaS, and SOAP APIs, and publish the branded screen to any browser, embedded inside Microsoft Teams, Slack, DingTalk, Feishu, or Lark, or inside the Kiweely Leaf iOS and Android phone app—with zero employee HR data stored at rest.
- Kiweely Bridge (coming next) connects Claude, ChatGPT, and Gemini directly to Workday via user-delegated OAuth (
Register API Clientwith PKCE) so new hires can ask natural questions about their own onboarding tasks, pay schedule, and benefit eligibility with read-only defaults and zero stored payloads. (If your team already licenses Workday Extend and builds custom onboarding experiences inside Workday today, Kiweely Vine builds and tests Extend apps on Mac and Windows right now.)
Frequently asked questions
Why do new hires see so many separate items in Workday My Tasks on day one?
Workday models onboarding as an orchestration of independent subprocesses—such as Contact Change, Personal Information Change, Manage Payment Elections, Complete Form I-9, Change Benefit Elections, Review Documents, and To Do steps—each generating its own My Tasks row as parallel or sequenced actions fire.
Can an external onboarding checklist mark Workday To Do and Review Documents steps complete?
Yes. Using Workday's standard businessProcess/v1 REST API and SOAP web services under the signed-in employee's own OAuth 2.0 Bearer token, an external UI can read awaiting inboxTasks and submit valid step completions without bypassing Workday security or audit trails.
Does grouping Workday onboarding tasks in Microsoft Teams or Slack require a Workday Extend license?
No. Standard Workday tenants include Register API Client (OAuth 2.0 Authorization Code Grant with PKCE), REST, WQL, RaaS, and SOAP APIs, allowing external pass-through checklists to run in Teams, Slack, or a browser without a Workday Extend subscription.
Where does sensitive new-hire data like bank routing numbers or National IDs live when submitted through a pass-through screen?
Directly in Workday and nowhere else. A stateless pass-through screen holds zero HR records at rest—inputs transmit in memory under the employee's own Workday OAuth session straight to the governing Workday business process.