Ecosystem
Leadership view
Modules
HR Partner
HR School HR knowledge base
HU EN DE
Agree the starting scope

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

Agree the starting scope →

The first week

What happens in the first week?

  1. Day 1–3 Your own environment and the basics The company's own environment, the organisational basics and the base settings are set up.
  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 depends on the data available and the starting scope.

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

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.

It can start with training only. Performance reviews, document handling, working time, onboarding or management reports can come later.

  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

With an employee list and one or two pieces of starting content at hand, the first live use can start within a week.

The pace depends on the data available and the starting scope.

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.
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.
Where it belongs

Where does oneStart fit in?

oneSolution·oneLoop·oneStart

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 the starting scope.

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

Agree the starting scope