Skip to main content

Create and run an employee journey

Journeys help HR coordinate the tasks and messages involved when an employee joins, leaves or needs structured follow-up during probation.

This feature appears only when Employee journeys is enabled for your organisation and your role allows you to manage journeys. The related employee activities then appear in Workspace → My Tasks automatically; your organisation does not need to enable a separate task feature for journeys.

Employee journeys has one tab for each process your organisation uses: Onboarding, Offboarding and Probation. Each tab starts that process and lists the journeys in progress. Each process is switched on for your organisation on its own. A process that is switched off keeps its tab only while journeys of it exist (for onboarding, also while future starters exist), so you can finish and look them up, but you cannot start new ones or publish its journeys. Journeys, reusable checklists and the step library are set up under Templates.

Create a journey​

  1. Open People, then Employee journeys.
  2. Select the Templates tab, then New template.
  3. Choose Onboarding, Offboarding or Probation follow-up. This choice stays fixed so dates and existing journeys keep the correct meaning.
  4. Give the template a clear name, such as Employee onboarding, Employee offboarding or Probation follow-up: Norway.
  5. Under Do, add each task, acknowledgement, document request, access-closure confirmation or approved email the journey needs.
  6. For a task, choose whether it is completed by the Employee, their Current manager or the Journey starter. The journey starter is normally the HR person who starts the journey.
  7. Choose how many days before or after the first working day for onboarding, the last working day for offboarding or the probation end date for probation follow-up each activity happens, or choose on that date. An offboarding activity can also count from the last day of employment, for example Before last day of employment.
  8. Select Review template and check the journey type, recipient, timing and activities in order.
  9. Select Publish template when the setup is ready to use.

A reusable checklist can also count each task's deadline from the journey date, for example Due 3 days before Last working day. A deadline before the date that falls on a weekend or a public holiday in the employee's working country moves back to the nearest working day. A deadline after the date moves forward. Such a checklist works only in a journey of a type that has that date. Markular will not publish an onboarding journey with a checklist that counts from the last working day. An offboarding checklist can count from the last working day or the Last day of employment, for example the final settlement for pay and holiday on the last day of employment.

If a deadline has already passed when the task is given, for example when an offboarding starts a few days before the last working day, the task is due that same day instead. The original date stays in the task's history, and the first reminder about the deadline comes a week later.

A reusable checklist always runs as an activity in a journey. To use a checklist for one person, start a journey that includes it.

Let a checklist task end in a deviation​

Sometimes a task can't be done, for example when an employee never hands in their phone. May end in a deviation lets the person responsible say so instead of leaving the task open. You find it, and the other settings below, under More settings on the item. It is closed to begin with; when the item differs from the defaults, a dot and a short label under the button say what is switched on. They choose what happened (Not returned, Not done in time, The person did not respond, Could not be done or Other) and can write a note. Tick A note is required if they must always write one. Both are on for a new item. Turn May end in a deviation off for a task that must simply be done. HR following the journey can still record a deviation for them.

When someone records a deviation, the task closes and someone gets a task to follow it up, due in 7 days. The journey stays open until that follow-up is done. Only whoever recorded the deviation, HR following the journey and the person following up can read the note.

Under Who follows up a deviation, choose who gets the follow-up:

  • Checklist starter: the person who started the journey. This is the default.
  • Current manager: the person's manager when the deviation is recorded.
  • Specific people: select Choose people and tick up to 20 people who can sign in to Markular. They share one follow-up, and any one of them can close it.

If no one can be found, for example when the person has no manager, the person who started the journey follows it up. Whoever follows up also sees the note.

Under Reasons for this item you can add reasons of your own, such as Lost on the rig. Select Add reason and write it in your language; one language is enough. Select Add English version or Add Norwegian version to give it in the other language as well, and Remove translation to take that away again. Where a translation is missing, people see the reason as you wrote it. An item can have up to 10 reasons of up to 100 characters each, and the same reason can't be on it twice. Your reasons are offered after the product's reasons and before Other.

Give a checklist task to specific people​

Some work, such as Close IT accounts, can be done by any one of a few named people. In a checklist item, set Responsible to Specific people, select Choose people and tick each person. You can choose up to 20 people, and only people who can sign in to Markular are listed.

When the journey reaches the item, Markular creates one task that each of them sees in Workspace → My Tasks, marked Shared with the others. One of them completes it for all, and the Tasks table shows everyone it went to and who completed it. The people are fixed when the checklist starts: changing the checklist later does not change tasks that already exist.

Someone without a Markular user, such as an IT contact at another company, can be added as an external contact. Select Add external contact next to Choose people, then search for the contact or select New external contact and enter their name, email, organisation and language. External contacts show with an External label, and the 20-person limit counts them too. Manage them on the External contacts tab of People → Employee journeys, where you can edit or deactivate a contact. A deactivated contact gets no new tasks and can no longer open their tasks.

If the contact is the only one on open tasks or on items in templates, Markular first shows which ones when you select Deactivate. Those tasks will wait for an assignee, and whoever started each journey is told. New journeys give those template items to no one until you choose someone else in the template. You can still deactivate the contact. See Tasks waiting for an assignee.

By default, HR follows up the external contacts on an item: Markular sends them nothing, and you call or email them yourself. The Tasks table shows a Contact line under the responsible, giving the contact's name, organisation and email, and the people on the item see the same contact on their task in My Tasks. If the item has only external contacts, the table shows HR follows up as the responsible and no one gets the task in My Tasks: close it with Mark as done in the journey, and the table shows you as the one who completed it.

To let the contacts do the task themselves, tick External contacts sign in and do it on the item. When the task becomes ready, Markular then emails each contact a link to their own task page. They sign in with a code sent to their email and can complete the task there, or mark it not applicable, with a reason if they like. The Tasks table shows the contact as the one who completed it, with a small building mark on their picture. If you change a contact's email, they are signed out and the new address gets a new link. See Complete tasks as an external contact for what the contact sees.

Give a checklist task to a group​

When a task should go to whoever handles something at the time, such as IT access, give it to a group instead of to named people. Groups are kept on the Groups tab of People → Employee journeys:

  1. Select New group, then enter a name and, if you like, a description.
  2. Select Choose people and tick each member. Only people who can sign in to Markular are listed.
  3. Select Save.

To change the members later, select Edit on the group, remove a member with the × on their name or add people with Choose people, then select Save. The Used by column shows the checklists that give tasks to the group and how many of its tasks are open.

In a checklist item, set Responsible to Group and choose the group. The item shows the current members. When the journey reaches the item, Markular creates one task that every member sees in Workspace → My Tasks, and one of them completes it for all. The Tasks table shows the group as the responsible, as a square with the group's name. Hover over it to see who is in the group.

Membership is followed while the task is open. Someone added to the group sees its open tasks, and someone removed from it no longer sees them. A group that is in use must keep at least one member, and Markular will not publish a checklist whose group has no one who can take the task. The message shows under that item.

A group that a checklist or an open task uses cannot be deactivated. Choose another responsible on those items and finish the open tasks first. A deactivated group can no longer be chosen in a checklist, and you can select Reactivate at any time.

When you add an email, the template picker shows which languages each approved email supports. Choose a template that covers the languages used by the people who will receive that journey. Markular uses the recipient's saved language when the email is prepared. Older approved emails that do not yet have a matching translation use English.

Your organisation must complete every enabled language before a new email template can be published. This keeps HR from starting a journey that later switches unexpectedly between languages. Once an email has been prepared for delivery, its language and wording stay fixed even if the recipient changes their language preference or HR updates the template afterwards.

Publishing creates a fixed version. Employees who already have an active journey keep the version they started with. Later changes apply only to journeys started from a newer published version.

An employee task is assigned to the employee selected when the journey starts. It appears in Workspace → My Tasks, explains why it was assigned and links the employee to their own profile. If that employee does not yet have a usable sign-in identity, the activity is shown as needing attention instead of being assigned to somebody else.

A current-manager task follows the employee's active reporting line when that activity opens. The task then stays with the manager selected at that point, so later organisation changes do not silently transfer work that is already in progress. If Markular cannot find exactly one active manager, the activity is shown as needing attention. Correct the reporting line before resuming the journey.

Choose Request document when the employee must provide one particular document, such as an employment certificate or completed form. Select the People document type before the journey can be reviewed, give the activity a clear name and add any instructions the employee needs. The selected type tells Markular where an approved document belongs; the employee does not have to classify it. The accepted formats and maximum size are shown with the request.

The employee opens the request from Workspace → My Tasks, or from their limited preboarding page before their work account is ready. They can check, replace or remove a private draft before choosing Send to HR. The activity is completed when HR approves the document, not when the employee uploads it.

Publishing fixes the document type for that journey version. Correct a draft template before publishing. Later template changes apply only to new journeys; they do not silently reclassify a document already requested from somebody.

Choose Ask for acknowledgement when the employee should read information and explicitly confirm that they have read and understood it. Write a clear, self-contained statement. The employee reviews that statement in Workspace → My Tasks, selects the confirmation and then chooses Acknowledge. Markular records who acknowledged it and when, and completes the journey activity.

An acknowledgement is not an electronic signature, consent or proof that the employee agrees with the content. Use a signing process when a document requires a legally binding signature. A journey that has already started keeps the published statement it started with; changing the template affects only newer journeys.

For an offboarding journey, choose Confirm access closure when HR or the employee's current manager must verify that agreed access has been closed. Add a clear confirmation statement and select the responsible person. The employee cannot be made responsible for confirming their own access closure.

The responsible person opens the Task in Workspace → My Tasks, reviews the statement and explicitly confirms completion. Markular records who confirmed and when. This records the controlled check; it does not itself deactivate an account in Microsoft Entra ID, an external HR system or another service.

For an offboarding journey, choose Hold exit conversation when someone should hold an exit conversation with the employee. It is offered when your organisation uses employee conversations. Under Who holds the conversation?, choose Journey starter (usually HR), Current manager or Specific person. For a specific person, select Choose person and pick them. The activity is due 5 days before the last working day; change the timing if you need to.

The person who holds the conversation gets the task in Workspace → My Tasks and becomes the conversation host. Only they can create the conversation. They select Create draft on the task. Under Choose a template they pick one of your organisation's conversation templates or No template, then select Create draft again. The template's points are copied into the conversation. It opens as a draft, so they can look it over and prepare before they invite anyone. They add other participants, for example someone from HR, in the conversation itself; see Add and remove participants. Completing the conversation completes the task. If the conversation isn't held, for example because the employee declines, HR closes the task with Mark not applicable and can write why.

Reuse a task in several checklists​

A task such as Return laptop often belongs in several checklists. Write it once in the Step library on the Templates tab of People → Employee journeys and choose it in each checklist instead of typing it again.

  1. Under Step library, select New step.
  2. Write the title and, if needed, an instruction in your language. Select Add English version or Add Norwegian version to add a translation in the other language. People see the title in their language when it is there, otherwise the one you wrote.
  3. Under What the recipient sees about the person, choose the details the person doing the task needs, such as Last working day or Employee number. The name is always shown, and sensitive personal data cannot be chosen. The recipient sees the details only while the task is ready or in progress.
  4. Select Save step.
  5. In a checklist item, under Task, choose From step library and pick the step. Who is responsible and the deadline are still set in each checklist.

Each step shows how many checklists use it. Changing a step does not change a published checklist by itself: a published version keeps the text and details it was published with, so journeys that are already running are not affected. A checklist that uses a changed step is marked Steps updated. Select Edit on it, save the draft and publish it again to take the changed step into use.

A journey uses the newest published version of each checklist it includes, from the moment it reaches that checklist. After you publish a new version of a checklist, every journey that reaches it from then on gets the new version; you do not need to publish the journey template again. A checklist that has already started keeps the version it started with.

Archiving a step removes it from the list you choose from. Checklists that already use it keep its text.

Start a journey for an employee​

  1. Open People, then Employee journeys, and select the tab for the process: Onboarding, Offboarding or Probation.
  2. Select Start onboarding, Start offboarding or Start probation follow-up.
  3. If several journeys are published for that process, choose one under Template.
  4. For onboarding, choose whether you are selecting a Future starter or a Current employee. Offboarding and probation follow-up list only current employees.
  5. Confirm the employing country and choose the employee.
  6. Choose the employee's first working day for onboarding or probation end date for probation follow-up. For offboarding, choose both the Last working day and the Last day of employment. The last day of employment can be the same day or later, for example when holiday is taken before the employment ends. If the employment relationship already has the dates, they are filled in. Markular uses the dates to calculate activity timing.
  7. Review the employee, dates and journey version.
  8. Select Start journey.

If the start button cannot be selected, no journey is published for that process yet. Publish one under Templates first.

If no one can take some of the checklist tasks, for example because the employee has no position and so no current manager, the review says how many will start blocked and why. You can still start the journey. The other tasks start as usual, and those wait for an assignee. See Tasks waiting for an assignee.

If some tasks were due before today, for example because the journey starts close to the last working day, the review says how many. Those tasks will be due today instead. You can change each due date in the task list after starting. See Give one task its own due date.

Add someone who has not started yet under Future starters on the Onboarding tab. This lets HR prepare onboarding while keeping the person out of the ordinary Directory and operational workforce views. See Add and follow a future starter.

The selected dates are saved with the journey. If an offboarding's dates change, open the offboarding and select Change dates. Both dates are filled in, and you can change either or both. Open tasks that are counted from a changed date get new due dates, with the same rule for weekends and holidays. You see which due dates change before you confirm. Completed tasks keep their dates, and so do due dates you set by hand. You can choose a date in the past, and the tasks then show as overdue. Planned emails whose new time has passed are sent right away, and the dialog lists them under Sent right away before you confirm. The new dates are saved on the employment relationship too. An offboarding started before Markular had the last day of employment opens with that field empty; fill it in to save.

Starting onboarding or probation follow-up does not change the employee's dates in People. Starting offboarding saves the last working day and the last day of employment on the employment relationship, where the profile shows them. Keep externally mastered employment dates in their authoritative system.

An employee can have only one offboarding in progress per employment relationship. An employee without an employment relationship can have only one in progress in total. If one is already in progress, the panel says so instead of showing the dates, with a link to Open offboarding. A completed or cancelled offboarding does not stop a new one.

If the employee already has a completed journey of the same kind, the panel says so under the person, with the date it was completed and a link to open it. You can still start a new one, for example when someone is rehired. If the earlier journey was completed by mistake, open it and mark it as cancelled first. The panel leaves out cancelled journeys.

Starting offboarding does not automatically disable accounts or delete employee data. Add clear return, handover and Confirm access closure activities to the journey. Account closure and data retention remain separate controlled processes until your organisation has configured the responsible integrations and policies.

Prepare access before the first working day​

If the future employee does not have a work account yet, open the active journey and find Preboarding access.

  1. Select Prepare invitation.
  2. Enter the employee's private email address.
  3. Choose the invitation language and how long it should remain valid.
  4. Select Prepare invitation.

The journey then shows Ready to send, the masked recipient and the expiry date. Preparing an invitation does not send it. This gives HR a separate review step before external access is issued and keeps the private address separate from the employee's future work account.

When the details are correct:

  1. Select Send invitation.
  2. Review the masked recipient, language and expiry date.
  3. Select Send invitation again to confirm.

The status first changes to Sending while Markular delivers the branded email, then to Sent when the email service accepts it. Do not prepare a new invitation while delivery is in progress. The link is private, expires on the shown date and grants only the limited preboarding access connected to this employee journey.

The future employee opens the link, checks the organisation and masked private email address, and asks Markular to send a one-time code. The six-digit code is valid for 10 minutes and can only be used once. After verification, Markular opens a separate preboarding page that cannot be used as ordinary People or Workspace access.

Preparing the invitation also makes employee activities that were waiting for a sign-in method available in the employee's limited preboarding page. The future employee sees only their own tasks, progress and controlled completion actions. Document requests cannot be marked complete without the required submission.

Review preboarding documents​

Open the active employee journey and find Preboarding documents. Only documents for employees within your area of responsibility are shown.

  1. Select Review and check the file against the document type and instructions shown beside it.
  2. Select Approve and file in Documents when it is correct. The same file is placed in the employee's protected Documents area and the activity is completed.
  3. Select Request changes when the candidate must replace it. Write a short, actionable explanation containing only information the candidate should see, then send the request.

The candidate receives an email that an update is needed, but the explanation itself is shown only after they verify their identity in preboarding. They must replace the file and explicitly send it back to HR. The earlier submission is kept in the process history.

Use Internal notes on the journey to coordinate with authorised colleagues. Each note shows its author and time. These notes are separate from the candidate-facing explanation and are never visible to the candidate. Do not copy sensitive document contents into a note.

End preboarding access​

Open the employee journey and find Preboarding access when the private sign-in should no longer be used.

If the employee's managed Markular sign-in is ready, select Move to Markular access. Review the exact work sign-in, sign-in method and access role, then confirm the move. The private sign-in and its active sessions stop immediately. The employee continues with the same tasks and journey history through the managed work identity; Markular does not create a second employee record, copy the journey or send another welcome.

If the offer is withdrawn or access should simply stop, select Revoke preboarding access. Revoking closes the private sign-in immediately but does not delete the employee journey, tasks or audit history. Only authorised People administrators can still review that retained history.

Move to Markular access appears only after the private preboarding identity is verified and the same active People record has a managed work identity with active minimum access. If it is not available, give or adopt Markular access from the person's profile first. A UPN, UPN2 or matching email address by itself is never sufficient proof; Markular binds the reviewed managed identity to the existing People record and rejects confirmation if either side changed after review.

Follow progress​

The Onboarding and Offboarding tabs list their journeys under Started journeys. The list has five columns: Employee with organisation context, Journey, the key date, Progress and Status. The key date is Last working day on offboarding and Start date on onboarding. Progress shows how many of the journey's tasks are done, with a bar and a percentage. Journeys still under way come first: those that need attention at the top, then those in progress, each with the soonest key date first. Completed and cancelled journeys follow, the most recently started first. Select a column heading to sort by it, select it again to reverse the order, and a third time to go back to the usual order. On a narrow screen, such as a phone, the list keeps the usual order. Search by employee or journey, or filter the list by status. The list opens on Remaining: journeys that need attention or are in progress. All statuses adds completed and cancelled journeys, or you can tick the statuses you want. Each status shows how many of the journeys your search finds have it. Needs attention includes journeys where a step failed. The list opens on Remaining again the next time you open the tab. When no journey is left, the list says Nothing left to do. When the search or filter finds none, it says No employee journeys found. Show all clears the search and lists every journey. Probation follow-up journeys are listed on the Probation tab.

Open a journey to see its progress: how many of its tasks are done, planned tasks included. A task marked Not applicable, or no longer needed, counts as done. A Deviation counts as done once its follow-up task is done. A cancelled task isn't counted. Under Steps, the journey lists the steps that have no tasks of their own, such as an email or a wait, with when they happen.

Needs attention means a step could not continue, for example because a required recipient was unavailable. The step is shown under Steps with an explanation. Correct the cause and select Resume onboarding (or offboarding or probation follow-up).

The journey shows a Tasks table with the tasks it has created so far, including each task in a checklist. For each task you see who is responsible, the due date and the status. A task that hasn't started shows no status. A line under the status says who started it, who completed it, who marked it Not applicable and why, if they said, who recorded a Deviation and why, with their note, The required tasks were done for an optional activity that was no longer needed, or why it was cancelled, each with the date. Tasks from steps that haven't started yet are listed too, with the status Planned and the due date when it's already known. They become real tasks when their step starts.

Under Responsible, each person shows with their picture, or their initials when they have none. A group shows as a square, and hovering over it lists its members. An external contact shows with a small building mark on their picture and External · company under their name. When several people share a task, their pictures are stacked with the first name and how many more; hover over them to see everyone. Hover over a person to see their contact card, if you may open their profile. The one who completed a task, marked it Not applicable or recorded a Deviation shows the same way, with their picture, in the line under the status.

The table opens on Remaining: tasks that are Not started or In progress, and each Deviation whose follow-up isn't done. To see other tasks, open the Status filter above the table. It has five statuses: Not started, In progress, Deviation, Completed and Not applicable. A deviation whose follow-up is done counts as Completed. Select All statuses to see every task, or tick the statuses you want, such as Completed. Each status shows how many tasks have it. The table opens on Remaining again the next time you open the journey. When you mark a task done or not applicable while the table hides that status, it leaves the table, and a message at the top of the page confirms it. When no task is left, the table says Nothing left to do., and Show all lists every task.

To find tasks in a long journey, type part of a task's name or of who is responsible in Search tasks. Anyone responsible narrows the table to the tasks one or more people have, and Any due date to tasks that are Overdue, Due in the next 7 days or have No due date. The numbers in Anyone responsible and Status count the tasks the other filters show, so with Remaining you see how many tasks each person has left. Select Task, Responsible, Due or Status at the top of a column to sort by it, select it again to reverse the order, and a third time to go back to the journey's own order. Tasks without a due date come last. When the search and filters leave no task, the table says No tasks match these filters., and Show all clears them. The table opens with no search and every person and due date the next time you open the journey.

After a deviation, the task that follows it up shows in the list too, and the journey isn't completed until it is done. You can't mark a follow-up not applicable, but you can mark it done for the person who has it.

Tasks waiting for an assignee​

A checklist task waits for an assignee when no one can take it. This happens, for example, when the employee has no position and so no current manager, when the position above theirs is vacant, when a group has no one who can sign in, or when the person named on the task can't sign in. The journey still starts, and its other tasks reach their owners as usual.

A task that is already open waits for an assignee too when everyone who had it drops out, for example when its only external contact is deactivated, or when no one in the group or the person named on it can sign in any more. Markular checks open tasks for this about every 15 minutes, and whoever started the journey gets a notification. When someone can take the task again, it can be done again and keeps its due date, comments and history.

  • Tasks shows whom the task is meant for, such as Current manager, and under its title Waiting for an assignee with the reason.
  • The journey says how many tasks are waiting, and so does its row under Started journeys.
  • Whoever started the journey gets one notification about the waiting tasks, and one more if the earliest due date among them passes while they still wait. It arrives as they have chosen under Notifications on My Tasks.

Fix the reason, for example by giving the employee a position under a manager or by reactivating the external contact. Markular checks waiting tasks again about every 15 minutes and gives each one to its assignee as soon as there is one, with the usual notification. To check right away, select Try again under the task. You see Try again on the tasks whose due date you can change.

A waiting task keeps its due date, and you can change the date or mark the task not applicable. No one can mark it done until it has an assignee.

Give one task its own due date​

Sometimes one task needs more time than the template gives, for example when IT needs two more days to return equipment. In Tasks, select the task's due date, or open the menu (⋮) on the task and select Change due date…. Choose the new date and, if you like, write why. Select Save. The task keeps its time of day.

The table then shows Set by hand under the due date. Point at the info icon to see who changed it, when, the date it had before and the reason. A due date set by hand stays put when the journey's dates change, and Change dates lists the task as Kept, set by hand.

You can change the due date of any task that isn't closed, including one that waits for an earlier task. You can choose a date in the past, and the task then shows as overdue. You can change the due date of a planned task once its activity starts.

Read and answer comments from external contacts​

A task with an external contact has a comments button in Tasks: a speech bubble with the number of comments. Select it to open a panel at the side with the task's comments. A comment from a contact shows their name with an External label. Write your answer in Add a comment and select Post comment. The contact sees your answer, with your name, the next time they open their tasks. Markular does not send an email about new comments, so check the button when you are waiting for an answer. When the contact does the task themselves, the comments say External contacts on this task can read these comments. When HR follows up the contact, the contact does not see the comments.

You can answer when you can mark the journey's tasks done. Tasks without an external contact have no comments button here. Their comments stay between the people who got the task.

Add notes to a task​

You can keep notes on a task, for example what you agreed with the employee or why the task takes longer. Only the people who follow the journey can read them. The person responsible for the task and external contacts can't. In Tasks:

  1. Open the menu (⋮) on the task and select Add note…. A panel opens at the side.
  2. Write your note in Add a note.
  3. Select Save note.

The note shows with your name and the time. A task can have several notes, oldest first. The panel says Only those who follow this journey can read these notes. When the task has an external contact, its comments are in the same panel, under the notes.

A task with notes has a notes button next to its comments: a notepad with the number of notes. Select it to read them. You can add notes to open and closed tasks.

You can change or delete your own notes. Open the menu (⋮) on the note:

  • Edit lets you change the text. Select Save. The note then shows Edited after the time.
  • Delete… asks Delete this note? Select Delete note. The note is removed for good.

You can't change or delete notes others have written.

Mark tasks done for someone​

Sometimes the responsible person has done a task but not ticked it off, for example an employee who has left after handing in their laptop. You can mark it done for them in Tasks:

Select the circle (Mark as done) at the end of the task's row. The task closes right away, also when it asks for a confirmation: marking it done is your confirmation on behalf of the responsible person. Each circle closes one task, so repeat it for every task that was done.

The task closes as if the responsible person had done it, and the journey moves on. The next tasks reach their owners with the usual notifications. The line under the status shows who did it and for whom, for example Kari Normann for Ola Normann. The responsible person gets no email.

A checklist finishes when all its tasks are closed: each open task waits until someone does it or marks it not applicable.

A task that needs a document shows Attach document instead of the circle. Choose a document of the requested type from the person's documents, and add a note if it helps, for example how you checked. The note shows under the status. If the person has sent a document that waits for review, review it instead. A probation or exit conversation task is closed from the conversation itself.

You can mark tasks done when you can start journeys for the person. Don't mark a task done that wasn't done, for example when equipment never came back. Record a deviation instead.

Send a reminder about a task​

When a task is late, or nothing seems to happen with it, you can remind whoever has it. In Tasks:

  1. Open the menu (⋮) on the task and select Send reminder….
  2. Check who the reminder goes to: the people who have the task, a group with how many people are in it, and external contacts who do the task.
  3. Select Send reminder.

People get the reminder in Markular and by email right away, also those who have chosen a daily summary. Someone who has turned task email off gets it in Markular only. External contacts get an email with a link to their tasks. The task then shows Reminded today, and the dialog says when the last reminder was sent and by whom.

You can send one reminder a day for each task. Until a day has passed, Send reminder… can't be selected and says who sent the last one and when. You can't remind anyone about a task that is closed or waits for an earlier task. When no one has the task, the reminder window says so and you can only close it. The reminder doesn't change the automatic due date reminders.

Change who has a task​

Sometimes a task is with the wrong people, for example when someone in the group is away and a colleague should take it. You can give it to others in Tasks:

  1. Open the menu (⋮) on the task and select Change who has it….
  2. The dialog shows the task, its due date and who has it now. Remove people, or select Choose people or Add external contact to add others. If you add external contacts who should do the task themselves, tick External contacts sign in and do it.
  3. Select Save. You see Responsible changed.

The task keeps its due date, comments and history. If it followed a group, a function or the employee's manager, it no longer does, and the dialog says so. Only the people you added are told about the task. The people you removed no longer see it. If you remove the person who started the task, it is no longer In progress, and the dialog says so. A line under the responsible shows who changed it, when, and who had it before, for example Changed by Kari Normann, 20.10.2026. Was Ola Normann.

A task needs at least one person and can go to at most 20 people, so for a big group you choose up to 20 who should have it. If you remove everyone, the dialog says Choose at least one person. Some tasks go to one person only, such as tasks from Confirm access closure and conversations, for example a probation or exit conversation. There you choose one person and no external contacts. You can't change who has a task the employee does themselves, such as sending a document, or a task a new hire does before their first day. Closed tasks can't be changed either.

You can change who has a task when you can start journeys for the person.

Record a deviation for someone​

Sometimes a task wasn't done and the person responsible won't say so, for example an employee who left on their last day without handing in their phone. You can record the deviation for them in Tasks:

  1. Open the menu (⋮) on the task and select Record deviation….
  2. Choose What happened?, and write a note. The note is required where the task asks for one. The checklist's own reasons for the task are offered before Other.
  3. Select Record deviation.

The task closes for everyone who shares it, and whoever the checklist names follows it up, as when the person responsible records it. The dialog names them, for example Lise Leder and 2 others get a task to follow it up. The line under the status shows why, who did it and for whom, for example Not returned · Kari Normann for Ola Normann. Only you, HR following the journey and the person following up can read the note.

You can do this on any open checklist task that has started, also where the task doesn't let the person responsible record a deviation. You can't on a follow-up, on a probation or exit conversation, or while a document the person sent waits for review. If an exit conversation isn't held, mark the task not applicable instead. If the person who started the journey can no longer follow it up, the task stays open and the dialog says so.

Mark a task not applicable for someone​

Sometimes a task doesn't apply to the person, for example returning a parking card someone never had, and it's for you to decide, not the person responsible. You can mark it not applicable for them in Tasks:

  1. Open the menu (⋮) on the task and select Not applicable….
  2. If you like, write why under Reason (optional).
  3. Select Mark not applicable.

The task closes for everyone who shares it, and this can't be undone. It counts as done, and a task that waited for it starts. The line under the status shows who did it and for whom, for example Kari Normann for Ola Normann, with your reason if you gave one. The person responsible isn't told.

You can do this on any open task, also one that still waits for an earlier task or for someone to take it, and also where the checklist doesn't let the person responsible mark it not applicable. You can't on a follow-up, or while a document the person sent waits for review.

Add a task for this person​

Now and then a person needs a task the template doesn't have, for example returning special equipment. Add it to their journey instead of following it up somewhere else:

  1. In Tasks, select Add task.
  2. If the journey runs more than one checklist, choose the one the task belongs to in Checklist.
  3. Under Task, choose From step library and pick a step, or choose Write here and write the title in your language. You can add a translation in the other language with Add English version or Add Norwegian version. People see the title in their language when it is there, otherwise the one you wrote.
  4. Choose who is Responsible, the same way as in a checklist.
  5. If you like, set Due: a number of days after Today, or before or after one of the journey's dates, such as Last working day. An offboarding also offers Last day of employment.
  6. Select More settings. Tick May be not applicable if the person responsible may close it as not applicable, with or without a reason. HR following the journey can always do it for them.
  7. Select Add task.

The task starts at once, and whoever gets it is told as for any other task. It shows Added in the list. Point at the info icon to see who added it and when. A deadline counted from a journey date moves when that date changes. A task you add here may always end in a deviation, with a note.

Every task in a checklist has to be done or marked not applicable before the checklist finishes, including a task you add here.

You can add tasks while a checklist in the journey is still running, when you can start journeys for the person.

Open tasks in an offboarding stay with their assigned owners and continue to use the normal Task reminders. Reaching the last working day never marks them complete or cancels them automatically. Cancel the journey only when the offboarding process itself should stop.

While a journey is under way, the person's profile shows a short line such as Offboarding in progress with the key date and how many of its tasks are done. Select Open offboarding (or onboarding or probation follow-up) to follow it. Only people who can manage journeys see this line. Journeys are started and followed under People → Employee journeys, not from the profile.

Cancelling a journey stops open and later activities, but keeps the history. Use cancellation only when the employee journey should no longer continue. If a journey shows as Completed by mistake, you can mark it as cancelled: select More actions, then Mark as cancelled. It then shows as Cancelled, and its tasks and history stay as they are.

When you cancel an offboarding, the dialog asks what should happen to the last working day and end date the offboarding set on the employment. Choose Keep last working day … and end date … when the person is still leaving, for example when you cancel an extra offboarding next to the one that counts. Choose Put back last working day … and end date … when the offboarding was started on the wrong person. It shows the dates the employment had before the offboarding, or none. You can put the dates back only when the earlier dates are saved, the employment still has the dates this offboarding set, and no other offboarding is in progress for it. Otherwise the dialog says why, and you can only keep the dates. Change them on the employment afterwards if needed.

Cancelling an onboarding also ends the person's preboarding access if it is still active or waiting to be used.

Delete a journey started by mistake​

If a journey was started on the wrong person, or is an extra one next to the journey that counts, cancel it first. A cancelled journey shows Delete journey. Deleting removes the journey with its tasks, checklists and notifications for everyone. The audit log keeps a record that the journey existed. Deleting cannot be undone.

A journey cannot be deleted when it left something on the person: a recorded probation outcome, documents from preboarding filed in the person's Documents, or a document the person submitted in one of its tasks. The dialog says which. If the journey is still sending an email, try again in a few minutes.

If you need help​

If an employee cannot be selected, check that you chose the correct population, that they belong to the expected employing country and that they are included in your area of responsibility. Offboarding accepts only current employees.

If an email activity needs attention, confirm that the intended recipient has a usable email address before resuming the journey.

For guidance on probation checkpoints, privacy and responsibilities, see Follow an employee through probation.