Skip to main content

Automate onboarding: from the first day to the end of the probation period

A form starts onboarding. Office, IT and the manager work in parallel, while probation-period feedback meetings are prompted and documented on time.
Industry: HR
Department: HR

Why employee onboarding often fails at the checklist

A new colleague starts on Monday. The workspace is not ready, access to the wiki arrives only on Wednesday, and signed documents are still missing two weeks later. The checklist is just a copy of a template; there is no automated onboarding workflow.

In the months that follow, visibility is often lacking. Nobody is quite sure whether the three-month feedback meeting took place. Every new starter triggers the same coordination by email and informal requests.

The root cause is usually the setup: onboarding is spread across HR, IT, Office and the manager, and no one owns the checklist.

How swoox.io automates onboarding

With swoox.io, onboarding starts with an HR form containing the employee’s name, role, team and start date. This creates an onboarding record that keeps everyone informed of the current status. Before day one, tasks run in parallel: Office confirms the workspace and access equipment, a checklist is created in the wiki, and a welcome message is prepared for the team chat. A person confirms each step owned by a department.

Onboarding continues after the first day. Rules linked to the record trigger reminders for missing documents and probation-period feedback meetings. If a milestone changes, the new rule immediately applies to all ongoing probation periods.

Technically, the workflow is a BPMN 2.0 process with parallel paths and defined confirmation points. Systems such as the wiki, chat or email are connected via REST. Optionally, an agent creates a personal task list based on role and team. If the result does not match the expected format, the team template is used instead. The AI model is your choice.

What is the agent allowed to do?

Platform Level
The tool allowlist and role- and permission system determine which systems and data the agent can access. Anything not approved remains inaccessible.
Process Level
The BPMN process is an explicit graph. The agent works within the modelled path. Control points that require a decision are defined in advance.
Agent Level
Stopping rules and human oversight apply at the point of consequence—where a decision affects systems, colleagues or access rights. A person confirms the action before the process continues.
This keeps every agent decision traceable: what was done, when, on what basis and who approved it. In its analysis of agent governance, Fraunhofer FIT also describes a deterministic process framework as a robust way to introduce AI agents into business processes under control (Gimpel et al., 2026).

The onboarding process, step by step

(Example workflow – each process is unique)

  1. HR reports the new starter using a form, and an onboarding record is created.
  2. The process assigns the person to their team and distributes the tasks.
  3. The wiki checklist and welcome message for the team chat are created in parallel.
  4. Office confirms the workspace and access equipment. A person confirms this because the department is responsible. If confirmation is missing, a reminder is sent after a defined period.
  5. On the first working day, a welcome email and briefing are automatically sent to the manager.
  6. HR confirms receipt of the documents. If anything is missing, a rule triggers a follow-up request.
  7. During the probation period, reminders prompt feedback meetings until the manager marks them as complete.
  8. At the end of the probation period, management receives a final report covering all confirmed steps.

Results: onboarding everyone involved can see

  • The status of every onboarding is visible, eliminating status-chasing emails.
  • The workspace and access are planned and confirmed before day one.
  • Documents and feedback meetings are tracked until completed.
  • Every step is documented, including who confirmed it and when.
  • Master data is entered once and reused throughout the workflow.
  • Responsibilities belong to roles rather than individuals, keeping the checklist current even when staff change.
  • New milestones immediately apply to all ongoing probation periods.

Why swoox.io for SMEs?

swoox.io runs on-premises or as PaaS in the EU, with SSO/MFA and a role- and permission system. During onboarding, each role sees only what it needs: HR sees personnel documents, Office sees workspace tasks, and managers see their feedback meetings. Even a small IT team can manage the permissions.

Onboarding is often the first process connecting several departments. The same foundation can then support leave requests or purchase requisitions. Business teams model workflows with low-code on BPMN 2.0, while IT operates the platform.

For the optional AI step, swoox.io is not tied to a provider. Models such as ChatGPT, Claude or Llama can be integrated without changing the process. REST integrations, forms, templates and email delivery are standard components. Integration with identity management or Active Directory is delivered as project work.

Frequently asked questions about the onboarding workflow

Does swoox.io replace our HR system?
No. Personnel files, contracts and leave management remain in your HR systems. swoox.io coordinates the workflows between them, keeps onboarding up to date throughout the probation period and documents every step.
Can we change milestones later?
Yes. Milestones such as feedback meetings are defined as rules. Any changed or new rule applies immediately to all ongoing onboarding processes.
Who intervenes if something is delayed or goes wrong?
Every confirmation point is assigned to a role. If a step remains open, the process reminds the responsible person, and the process log shows the current status. If an AI step is involved, the process stops at predefined control points and waits for a human decision.
Can onboarding involving employee data be operated in compliance with the GDPR?
Yes. You can run swoox.io on-premises or as PaaS in the EU, depending on your operating model. Access is controlled by the role- and permission system, and personal data remains in your own environment.
How do we start with the first process?
In the demo, we walk through your onboarding workflow and show you how it looks in swoox.io.
Get to know swoox.io

We’d be happy to show you how easy and flexible process automation with swoox.io can be.
Or you can try it out for yourself.