{"id":1134,"date":"2026-10-27T12:17:15","date_gmt":"2026-10-27T15:17:15","guid":{"rendered":"https:\/\/www.smartservices.com.ar\/casos-de-uso\/employee-onboarding\/"},"modified":"2026-10-27T12:21:10","modified_gmt":"2026-10-27T15:21:10","slug":"employee-onboarding","status":"publish","type":"use_case","link":"https:\/\/www.smartservices.com.ar\/en\/use-cases\/employee-onboarding\/","title":{"rendered":"Employee Onboarding Automation"},"content":{"rendered":"
\n

In brief.<\/strong> This use case consists of assessing how to: create a role-based checklist, request documents, open cross-team tasks, and show what remains before start day.<\/p>\n

\n

How it works today<\/h2>\n

HR coordinates documents, access, equipment, and tasks with IT and finance. Each hire depends on individual reminders.<\/p>\n<\/section>\n

\n

Where time is lost<\/h2>\n

HR asks each team whether its part is done, and the new hire starts with access or equipment still pending.<\/p>\n<\/section>\n

\n

What can be automated<\/h2>\n

Create a role-based checklist, request documents, open cross-team tasks, and show what remains before start day.<\/p>\n<\/section>\n

\"Possible<\/picture>
Illustrative workflow; exceptions still need review.<\/figcaption><\/figure>\n
\n

How a workflow could work<\/h2>\n

A practical flow takes inputs from the relevant sources, checks them against agreed rules, performs routine actions, and sends uncertain cases to a person.<\/p>\n<\/section>\n

\n

What still needs a person<\/h2>\n

HR validates sensitive information and owners authorize access.<\/p>\n<\/section>\n

\n

Systems that may be involved<\/h2>\n

HRIS, ITSM, identity, email, and repository.<\/p>\n<\/section>\n

\n

When it is worth assessing<\/h2>\n

When each hire requires several teams and progress is not visible.<\/p>\n<\/section>\n

\n

What not to assume<\/h2>\n

Access rights should not be granted from an automatic event without approval.<\/p>\n<\/section>\n

\n

How Smartservices approaches it<\/h2>\n

We map the existing process, verify data and system access, define controls and a human review point, then scope an integration or automation around the actual workflow.<\/p>\n<\/section>\n