Ecosystem
Leadership view
Modules
HR Partner
HR School HR knowledge base
The first week
HU EN DE
Agree the starting scopeAgree scope
Fast, but not temporary

The first working process.In the first week.

With an employee list and the first content at hand, we put the technical foundation together in a few working days, and the first live use can begin.

Watch it in 30 seconds Agree the starting scope

In 30 seconds

What the first week looks like

Once the employee list and the starting content are ready: Excel and PDF in, working training out.

  1. 1 The question
  2. 2 Day 1–3
  3. 3 Day 3–5
  4. 4 Week 1
  5. 5 After that
  6. 6 Same foundation
The first week step by step ↓ Or let’s talk about your start

How deep shall we go?

Brief Overview
If you only have five minutes. The essentials, with practical examples.
The first week

Four steps to the first live use.

  1. Day 1–3 Base model and own environment The organisational base, the roles and the company look are set up.
  2. Day 3–5 Import and first content Employees, job roles and the starting processes or courses come in.
  3. Week 1 First live use The first assignment goes out and the system starts working in a real process.
  4. After that Growth at your own pace New modules, sites and processes can connect to the same foundation.

The actual pace depends mainly on how soon the starting data is available and on the chosen scope.

To start

It takes less than you'd think.

  • An employee list.
  • A few job roles.
  • One or two starting processes or courses.

There is no need to model the whole organisation's next five years before you start.

An example from oneLearning

You prepare an Excel file and a PDF.We turn them into a working e-learning system.

From the existing employee list and course material, the first online training and exam can be launched in a short time.

Not a one-off speed-up

What has been built once can be built on.

The fast start is not a throwaway prototype. The same foundation serves the modules and processes switched on later.

Base dataNo need to enter it again.
Job-role modelNo need to rebuild it.
Organisational structureLater modules use it too.
PermissionsSet once, valid in every connected module.
Later, on the same foundation:
  • Performance
  • Documents
  • Working time
  • Onboarding
  • Reports
Low entry risk

No need to commit blindly for the long term.

We launch the first usable scope, you see it working, and you build on from there.

30-day notice period

First we look at what can become a real, usable process fastest.

Technical details: data model, import and growth
Data modelA ready-made master-data structure: people, organisational units, sites, positions. Every module uses it.
Job-role modelReady-made job roles (e.g. HR, manager, employee) that are tailored to the company at the start.
ImportEmployees and organisational data come from an existing list, following an import template.
PermissionsJob-role-bound access: who sees what and who can edit what – set once, valid in every module.
Starting scopeDeliberately narrow: one or two processes or courses that let the first live use begin.
Integration templatesReady patterns for the usual data connections, so the first link-up does not begin as custom development.
MigrationTaking over existing data and content when it is needed – not a precondition of the start.
Modular growthSwitching on a new module does not mean a new system: the same interface, the same employees and job roles.
No re-entry of dataWhat was entered at the start is used by the later modules too.