So nothing slips through on someone's first day
Employee onboarding starts from one dialog: pick the person, the date and the template tied to their job position. The checklist builds itself, deadlines and owners included.
The nine item types are not boxes to tick. Training gets assigned, the check-up scheduled with the work category, the contract generated from a template, the task opened with a due date. Completion is read from that record.
For a departing employee the module looks up what is still signed out to them: assets with inventory numbers and protective equipment that never came back.
Enter the reminder cascade as days before the due date and only the most urgent one is sent. The My items tab shows each person just what is waiting on them.
Switch the option on and the application opens onboarding on the hire date and offboarding on the leaving date. The template comes from the job position.
Laptop prepared at -14 days, contract signed on day zero, induction at +7. The real date is worked out per employee.
A specific user, any holder of a job position, the line manager, the new hire, or the process owner. If nobody fits, the owner takes it.
A PDF of the steps with signature fields. Items also print the health check-up request and the protective equipment record sheet.
Mark them Not relevant. It is the one manual change the automatic status recalculation will not overwrite.
Managed onboarding and offboarding means every step around someone's arrival and departure has an owner and a due date: training, the pre-employment medical check-up, the contract to sign, the issue of protective equipment, handing over a laptop. The eIntranet module holds that sequence as a template tied to a job position and runs it for a specific employee.
What sets it apart from a checklist in Word is where the tick mark comes from. A process is built from the template, and eight of the nine item types are never ticked by hand — the module looks into the related record and reads the real state there. Training counts as done once it reaches the Completed or Confirmed state in the Training module. A medical check-up counts once it has an examination date and the assessment concludes fit, or fit with conditions. A contract counts once it is signed. If someone deletes the target record, the item drops back to outstanding and the reason is written into its note.
The other half of the module is the departure, and that half usually gets neglected. The exit sheet lists what the departing employee still has assigned in the asset register — individual items with their inventory numbers — and which issued protective equipment has no return date recorded. That is the list a manager prints and takes to the handover meeting.
The whole cycle has six steps, and two of them run without anyone touching them:
Deadline chasing runs off-screen. A nightly job recalculates running processes, and when an item is overdue or its date is approaching, it sends a reminder to the responsible person and to the process owner. The lead times are configured as a cascade, 7, 3 and 0 days before the due date by default. Move an item's date and the cascade resets, so the reminders for the new date actually arrive.
This is the question we get most often about onboarding software: is it just a list to tick off, or will it do something for me? For the Employee onboarding and offboarding module the answer looks like this.
What it reads as input. The employee and their job position from the Employees module, and for automatic starts also the start date and end date from the personal record. The work category and risk factors for the medical request come from the job position settings in the OHS module — and when someone holds several positions, the stricter variant wins.
What it creates by itself. A training assignment or a document to read, a scheduled occupational medical check-up with the work category pre-filled, a contract to sign generated from a template along with its attachments, and a task with a due date, a main assignee and an approver. The record it creates behaves in the target module exactly like one entered by hand, including that module's own reminder jobs.
What it deliberately does not create. Not the issue of protective equipment, because that needs a size and a stock variant nobody can guess. Not a form, because an empty row would look completed in the Forms module and would skew the completion statistics. Not the asset handover protocol either — the module only links to it with the recipient pre-filled.
What comes out. Three printed PDF outputs: the onboarding or exit sheet with the item table and a signature block, the request for an occupational medical check-up for the provider, and the record sheet of issued protective equipment. You need no hardware at all — no reader, terminal or tag plays any part here; the module works purely with data already held in eIntranet.
Nine item types cover what really happens around an arrival and a departure. Eight of them read their state from the related module, so they cannot be ticked by hand — they can only be marked Not relevant, which the recalculation deliberately skips.
| Item type | What happens on start | Where completion is read from |
|---|---|---|
| Training | Training is assigned to the employee per the template | Assignment state in the Training module |
| Occupational medical check-up | A check-up is scheduled with the work category and risks pre-filled | Examination date and assessment in the OHS module |
| Personal protective equipment | Nothing — issuing needs a size and a stock variant | Items missing against the position norm; on exit, unreturned ones |
| Contract to sign | A contract is generated from a template with attachments | Signature state in the Employees module |
| Asset handover | Nothing — the module links to the handover protocol | On exit: what the employee still has assigned |
| Task | A task is created with a due date, assignee and approver | Completion date in the Tasks module |
| Document to read | Assigned like training, with confirmation and IP address | Assignment state in the Training module |
| Form to fill in | Nothing — an empty row would skew completion statistics | A submitted form dated after the process started |
| Manual item | Nothing | Manual confirmation with a date, note and attachment |
On top of that come six permission levels, from No access through Own only and Own and subordinates up to Delete and recycle bin, assignable to an individual or to a whole job position. Deleted processes, items and templates go to the recycle bin and can be restored; an item disappears from the bin if its parent process has been deleted in the meantime, so that nobody restores a row into a process no one can reach.
Do not start with a complete template for every position. The approach that works has four steps:
That last step comes with a safeguard the module applies on its own. When you enable automatic starts, it notes the day the option took effect and ignores earlier start dates. Without it, the first nightly run at a company with history in its personal records would open a process for every single employee at once and send out hundreds of e-mails.
There is no shortage of onboarding tools, and most of them are really a shared task list with nicer graphics. Three questions tell them apart faster than a demo does:
If a person ticks the checklist, you have two sources of truth: the state in the checklist and the reality in your HR records. Ask what happens when someone deletes or changes the record in the target module. In eIntranet the item returns to outstanding and the reason is written into its note.
The gap between a line saying "assign safety training" and a training actually assigned is the entire value of the module. Check whether the software creates records in the module where the work really gets done, or whether it just e-mails the HR officer.
Everyone sells the arrival; the departure gets skipped. Ask whether the tool lists assigned assets with inventory numbers and unreturned protective equipment as of the leaving date. That is the part you can put a number on.
For a company of under twenty people hiring two or three a year, two things matter: that nothing gets forgotten when HR is the owner squeezing it between other work, and that a laptop does not vanish when someone leaves. One onboarding template, one offboarding template, items of the Task and Manual type, and the exit sheet with assets will do.
In manufacturing and shift operations the centre of gravity moves. An arrival there means a medical check-up matched to the work category, induction and refresher training, a protective equipment norm tied to the position, and often structured on-the-job training as well. You end up with more templates — a welder, a forklift operator and a warehouse worker already differ at the medical check-up, not at the welcome e-mail. That is why the module ties a template to a job position and, at start, offers the one that fits the employee's position best.
Seasonal hiring is a third case. There, automatic starts driven by the start date pay for themselves: fifteen temporary workers arriving in the same week get their processes on their own, including the dates pushed back to fourteen days before the start.
The Employee onboarding and offboarding module has no price of its own. You pay for user seats in eIntranet and every module is included in every plan. Prices per user and month, excluding VAT, look like this:
| Number of users | Basic | Normal | Extra |
|---|---|---|---|
| 1–10 | €2.4 | €2.8 | €3.2 |
| 11–20 | €2.1 | €2.5 | €2.9 |
| 21–50 | €1.7 | €2.1 | €2.5 |
| 51–100 | €1.5 | €1.9 | €2.3 |
| 101 and more | €1.4 | €1.8 | €2.2 |
The question we hear most often about onboarding is this: do I pay for every hire separately? No. The number of processes started, the number of templates and the number of checklist items have no effect on the price. A company of eighty that hires twelve people a year and parts with nine runs twenty-one processes and pays exactly what it would pay without them.
The second question is more practical: a process runs on an employee held in eIntranet, so that person occupies a seat. For temporary and seasonal staff this means counting them into your plan for as long as you keep their records. You need no hardware and the module itself creates no extra fees; the cost of the medical check-up or of buying protective equipment goes to the provider and the supplier, not to us. Current prices and storage sizes are on the pricing page.
Let us be straight about it: an onboarding checklist in a spreadsheet is free, and for a company that hires two people a year and has no protective equipment or medical check-ups to arrange, it genuinely is enough. A shared document with five rows and an owner against each of them does the job, and paying for that makes no sense.
The limit shows up in two places. The first is evidence. A spreadsheet can claim the training happened, but it cannot prove it — and with safety training or a pre-employment medical check-up, the document is the only thing that carries weight during an inspection. The second is re-keying. The moment an item means "create a record in another system", somebody starts typing the same thing in two places, and from then on the two drift apart.
The remaining options deserve an honest word. Dedicated onboarding tools are pleasant to use, but they know nothing about Czech occupational medical check-ups, work categorisation or protective equipment norms. And general task tools such as Trello handle an arrival perfectly well, right up to the point where you need an exit list of assigned assets. You can try it out at no cost: eIntranet comes with a 14-day free trial covering every module.
The Employee onboarding and offboarding module builds on four other eIntranet areas. The Employees module is the source of personal records, job positions and contracts to sign. The Employee training module receives assigned training and documents to read and watches their validity. The OHS module keeps occupational medical check-ups, work categories and the issue of protective equipment. The Asset register supplies the exit sheet with the list of assigned items, and the Tasks module takes on the items that have no agenda of their own.
Yes, it creates them itself. Starting a process produces a training assignment in the Training module, a scheduled occupational medical check-up in the OHS module with the work category pre-filled, a contract to sign generated from a template with its attachments, and a task with a due date and an assignee.
Three item types are deliberately excluded, because creating them automatically would do harm: issuing protective equipment needs a size and a stock variant, an empty form row would skew the completion statistics, and the asset handover protocol is raised by hand. For those, the module only links to the right place.
No. The Employee onboarding and offboarding module has no price of its own and is included in every eIntranet plan. The number of processes started, the number of templates and the number of checklist items have no effect on the price. You pay only for user seats according to the price list.
One practical caveat: a process runs on an employee held in eIntranet, so that person occupies a seat. For temporary and seasonal staff, count them into your plan for as long as you keep their records.
Yes. A template is assigned to one or more job positions, and when a process starts the module offers the one that best matches the employee's position. A template with no position assigned applies to everyone, so a general onboarding and a welder-specific onboarding can exist side by side.
Templates come in two types, onboarding and offboarding, and each can have its own default process owner. Items are ordered within the template, and each carries a date offset in days from the start date or the last working day.
No, not for eight of the nine item types. Their state is read from the related module, so a manual tick would disappear at the next recalculation and look like a bug in the application. Only the Manual item type is confirmed by hand, with a date, a note and an attachment.
For typed items one manual change remains: marking them Not relevant. The recalculation deliberately skips those, which suits a training course a particular employee does not have to take.
The item returns to outstanding and the reason is written into its note. At every recalculation the module checks whether the target record still exists; if someone has deleted it, the stored link is dropped and the state corrected. That way the checklist cannot claim completion for something no longer on file.
The module is equally careful about unfavourable outcomes. A check-up concluding not fit does not count as completed, and a rejected or expired contract stays outstanding along with its status description.
Yes. The exit sheet lists the assets the employee still has signed out according to the register, with the inventory number of each item, plus any issued protective equipment with no return date recorded. The list is compiled as of the print date, so it matches the situation at the handover meeting.
The module does not rely on the handover protocol; it reads the asset register directly. So if nobody ever filled the protocol in, that makes no difference to an unreturned laptop — it still shows up on the exit sheet.
No, it does not generate those documents. It can put them on the offboarding checklist as an item with a due date and an owner so that nobody forgets them, but the document itself is produced elsewhere. The module prints three outputs of its own: the onboarding and exit sheet, the request for an occupational medical check-up, and the record sheet of issued protective equipment.
Contracts and their amendments are a different matter — the module does create those from a template in the Employees module, attachments included, and their signature feeds back into the checklist automatically.
Yes, but the option has to be switched on in the module settings first, because it is off by default. A nightly job then picks up employees whose start date falls inside the chosen window and opens a process from the most suitable template. Offboarding works the same way from the end date.
When you enable it, the module notes the day the option took effect and ignores earlier start dates. Without that safeguard, the first run at a company with history in its personal records would open a process for every employee at once.
No, the module works without them, but you lose part of its value. An item type is only offered when the corresponding module is enabled for the company — so without the OHS module you cannot schedule an occupational medical check-up, and without the Training module you cannot assign training or a document to read.
The module still stands on its own: Task, Manual and Contract items plus the exit list of assigned assets cover an ordinary office arrival and departure. Missing areas can be added later, and the templates do not need rewriting.
Yes. A nightly job goes through the running processes and, for an item whose date is approaching or has passed, sends a reminder to the responsible person and to the process owner. The lead times are configured as a cascade, 7, 3 and 0 days before the due date by default, and a company can change them.
If somebody moves an item's date, the cascade resets and the reminders for the new date really do arrive. Saving an item without changing the date, on the other hand, does not fire already-sent reminders again.
Registration is non-binding and includes a free 14-day trial of the application.