Workday’s Sana entry point highlights the handoffs behind employee onboarding

Public developments and original analysis · Announcement date: 2026-10-13 · Sources

Workday’s move to place Sana at the work entry point highlights AI’s growing role in coordinating requests. Employee onboarding still spans personal records, equipment, account access and owner confirmation. Mokyun’s relevant application is to organise those tasks around one onboarding case so employees and managers can see actual readiness.

This week’s development: distinct availability stages

On October 13, 2026, Workday announced Sana as the new Workday Home and introduced HR and IT service agent Sana Concierge. Home was available with administrator-controlled enablement. Concierge was available to early adopters, with general availability expected in the first quarter of 2027.

This October 17 analysis keeps those announcement stages separate. The event is older than 72 hours; the new contribution is an onboarding handoff analysis within this week’s work-entry developments. The following process is an illustrative scenario, not a report of a deployed customer workflow.

The onboarding problem: one start date and several completion standards

Imagine a new employee starting next week. HR holds the start date and role; IT needs account scope and equipment requirements; facilities prepares building access; the manager confirms initial assignments. Departmental forms may each be complete while the employee still needs to ask whether everything is ready.

A common entry point makes the right channel easier to find. Cross-department work also needs shared identifiers, dependencies and results. The enterprise wants progress after one submission while each owner confirms work within their responsibilities and permissions. Completion in one department can leave other prerequisites unresolved.

The deliverable: a readiness record that exposes open items

Organise the case around an employee identifier, start date, role and approved role requirements. The preparation record separates information checks, equipment handover, account requests and building access, each with an owner, supporting information, status and open items. Agreed completion rules determine overall readiness.

An item without system confirmation remains awaiting confirmation and goes to its owner. Approved access, created accounts and usable access represent different stages. Personal information is restricted by responsibility. A first pilot can use redacted samples and only the fields necessary to prepare the work.

Mokyun’s approach: coordinate preparation around the case

Mokyun’s published platform direction includes enterprise knowledge, task orchestration, system connections and process execution. Applied to onboarding, a proposed design retrieves role-specific rules, coordinates preparation by HR, IT, facilities and the manager, and associates existing requests with their results.

Digital employees check materials, prepare task lists, assemble progress and remind owners of handoffs. Authorised people decide access scope and exceptions. HR, workflow, ticketing and identity interfaces require validation in the target environment. No Mokyun connection to Sana is assumed, and the model does not independently expand account permissions.

The first deliverable can be a readiness record and task drafts through existing approval channels. Once handoffs work consistently, application initiation and authorised record updates can be assessed individually. Employee information, owners and system results then stay associated with the same case.

Scenario: a role change before the start date

Suppose the employee’s role changes before joining. The digital employee identifies a revised requirement, assembles affected equipment and application-access items, and routes them for confirmation. HR and the manager confirm the new requirements before task owners update their work. Previously completed items retain their handling history.

The employee sees current information requests and readiness status; the manager sees remaining gaps. The handoff includes the revised preparation record, approved requirements, system request identifiers and owners for open items. Those materials support the next person taking over the case.

Business value: fewer repeated enquiries and better first-day readiness

Start with one role category and the same onboarding standard. Compare resubmissions, repeated enquiries, waiting between roles and first-day readiness. Include the time spent by the employee, HR, IT and facilities. Entry-point response speed alone leaves out much of the work; completion needs actual handover or system confirmation.

The scenario fits enterprises with defined onboarding responsibilities and basic source records. A redacted onboarding form and role requirements can anchor a Mokyun assessment of preparation steps and cross-department deliverables, followed by a decision on the order of system connections.

• Mokyun digital employees
• Mokyun enterprise system integration
• Mokyun task and agent approach
• Discuss an onboarding workflow

Mokyun Editorial · neo@mokyun.com