Ecosystem
Leadership view
Modules
HR Partner
HR School HR knowledge base
The first week
HU EN DE
Plan your start

The first live process can start within a week.

It grows later without starting over. An employee list and the first content are all it takes.

See how it starts

How deep shall we go?

Same start. Two depths.

Brief Espresso If you only have a few minutes. Overview The essentials, with practical examples.
surface. If you only have a few minutes mid-depth. The essentials, with practical examples
Why it doesn't take months

We don't turn the system start into a months-long project.

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 start as early as the first week.

1A ready base modelWe don't redesign the system from scratch for every client.
2Import, not manual entryWe start from the existing employee list.
3Existing content can be enough to startFrom a PDF, the first online course and exam can be launched in a short time.

The rollout is not a corporate project in its own right. Its purpose is to get the system into use as soon as possible.

The first week

What happens in the first week?

  1. Day 1–3 Your own environment and the basics Your own system environment, the organisational basics, the permissions and the company look are set up. Logo, colours, background and basic branding: a matter of minutes to hours, not a separate development project.
  2. Day 3–5 Import, job roles, first content Employees come from the existing list. Job roles and permissions are set, the first content is loaded.
  3. Week 1 First live use The first assignment goes out: the first training or process runs live. From here the system is in your hands.
  4. After that Growth at your own pace New modules, sites, processes – when they are needed.

The pace is usually set not by the system, but by how soon the starting data is available.

The pace depends on the data available and on what we start with.

To start

What do you need to start?

Less than you'd think.

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

We build the rest on this, together.

An example from oneLearning

Prepare an Excel file with your employee data and a PDF.We hand you a working e-learning system.

With two PDF courses and an employee list, the first online training and exam can be launched in a short time.

Existing content can be edited, extended and enriched with exams or media later, if needed.

What stays

What stays with you later?

The foundations stay the same later – even when new modules, sites or processes come in.

The base dataNo need to enter it again.
The job-role modelNo need to rebuild it.
The organisational structureCarries on being used.
New modulesPlug into the same foundation.

What has been built once can be built on.

Growth

Not everything has to be switched on from day one.

Let's get started first. Fine-tuning can happen while it runs.

There is no need to model the whole organisation's next five years before go-live.

It can start with a first part you can already use, and then, on the same foundation, come:

  • new modules
  • new sites
  • new processes
  • new job roles
  1. Base model
  2. Import
  3. First modules
  4. Go live
  5. Growth
  • Performance
  • Documents
  • Working time
  • Onboarding
  • Reports

on the same foundation, without starting over

Low entry risk

No need to commit blindly for the long term.

We launch a first part you can already use, you see it working, and you build on from there.

30-day notice period.
In more detail: data model, job roles, import, 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.
The first stepDeliberately 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.
Where it belongs

Where does oneStart fit in?

oneSolutionHR ecosystem oneLoopThe operating model oneStartThe start model

oneSolution is the system. oneLoop is the operating model. oneStart is how we get going with it. Not a separate product, module or licence – the One system's standardised start model.

Let's agree what to start with.

We look at which data and content are available and what the first live process could be.

Plan your start