Skip to content
English
  • There are no suggestions because the search field is empty.

Setting due dates and prerequisites for onboarding tasks

How a task's due date is worked out from the start date on the accepted offer, and how a prerequisite locks and unlocks a task.

How a task's due date is worked out from the start date on the accepted offer, and how a prerequisite locks and unlocks a task.

This is for System Admins and HR users building onboarding templates under Settings, then Onboarding templates, and for anyone following a live onboarding who wants to know why a task has the date it has. Both settings are chosen per task in the template builder. The rest of the task fields are covered in "Choosing task types in an onboarding template".

The due offset

Due Offset (days) is a whole number of days from -3650 to 3650. It is counted from the employment start date on the candidate's accepted offer. It is not the day onboarding was started. The box hint reads “Days after start date”.

  • An offset of 7 gives a due date one week after the start date.
  • A negative number such as -3 gives a date before the start date, for example a pre-start task due three days before they arrive.
  • To remove the date, clear the box or use the clear control beside it (Clear due date for the task). The task then shows No due date. A task with no due date is never reminded and never shows as overdue.

Only an offer the candidate has accepted counts. Recruit works out each due date when onboarding starts and rechecks it against the accepted offer every night.

Waiting for start date

A task that has an offset but no start date to count from yet has no due date. Instead of a date, the task row on the candidate's Onboarding tab shows Waiting for start date, and so does the Due Date column on the My Tasks tab of the Onboarding hub. The task cannot be overdue and gets no reminder while it waits.

This usually means the candidate has no accepted offer with a start date yet. It happens when onboarding is started by hand before an offer is accepted. The date appears once the offer is accepted and carries a start date.

Overdue tasks

A task is overdue once its due date has passed and it is not Complete or Skipped. Overdue tasks are shown in red in My Tasks and counted as Overdue on the Onboarding hub. Reminder emails to new starters follow the due dates on their Content and Form tasks. See "Reminder settings for onboarding tasks".

An Email Trigger task that has an offset is sent on its due date rather than when it unlocks. See "How email trigger tasks send".

Prerequisites and locked tasks

In the template, the Dependency list on a task picks the one task that must be finished first. It defaults to None. A task with a dependency starts out Locked. The portal shows it greyed out with “Waiting on: [task name]”. Nobody can act on a locked task, including staff, and its buttons are hidden.

The prerequisite can sit in any phase. The list shows tasks by title, so give tasks different titles. A task can have only one prerequisite, and a template cannot be saved if dependencies loop back on themselves (“Task dependencies contain a cycle”).

When a task unlocks

The task unlocks and becomes Not Started as soon as its prerequisite is Complete or Skipped, whoever does it. A prerequisite that is only Under review does not release anything waiting on it until it is approved.

  • A Content or Form task emails the new starter that a new task is available, unless Send to candidate email is off for that task. It is on by default.
  • An Email Trigger task with no due offset sends its email straight away. With an offset it waits for its due date.
  • An Internal task appears for its assignee, with no email.

If a finished prerequisite is reset, the tasks waiting on it that have not been started go back to Locked. Tasks already In Progress stay as they are.

Problems you may hit

  • A task is stuck on Locked: its prerequisite is not Complete or Skipped yet. A prerequisite that is Under review needs approving.
  • A task shows Waiting for start date: the candidate has no accepted offer with a start date yet.
  • A task has no date at all: its offset box is empty, so it never goes overdue.