Lifecycle surveys

Lifecycle surveys are sent automatically at key moments in an employee’s tenure, based on their hire date and termination date. The feature is off by default and is enabled per organisation.

There are three lifecycle types, each with a ready-made, bilingual template:

Onboarding – sent a number of days after the hire date (default 30 days) to capture how the introduction went.
Stay – a recurring engagement check-in a number of days after the hire date (default 365 days).
Exit – sent a number of days before the termination date (default 14 days), including a structured reason code for why the employee is leaving.

How to configure. First create a survey from the desired lifecycle template (via “Start from template”) and note its survey ID. Then go to Surveys → Overview, where the lifecycle card appears when the feature is enabled. Enable the types you want, set the day offset, and paste in the survey ID to send. A catch-up window ensures a survey still goes out if the scheduled job misses a day. Saving checks that every survey ID you enter actually exists in your organisation, and is rejected immediately with an error if it’s mistyped, belongs to a different organisation, or hasn’t been created yet.

How enrolment works. A scheduled job runs once a day, finds the employees who have just crossed their offset, and creates a single-recipient invite through the same invite/response flow every other survey uses. Each employee is enrolled only once per lifecycle (a marker prevents duplicates), and the exit survey is never sent to anyone whose termination date has already passed.

Anonymity. Onboarding and exit cohorts are often small. Results are therefore shown through the same reporting view as other surveys and protected by the same threshold (minimum group size): answers are only aggregated once enough people have responded, so an individual employee’s answers can never be singled out.

Custom triggers. Beyond the three fixed types, you can create your own triggers under the “Custom triggers” heading on the same page. A custom trigger is based on any date field on the employee (e.g. Probation end, Birth date, Last workday) and a number of days before or after that date, and can point at any survey in your library. Click “Create custom trigger”, fill in a name, the date field, whether it should send days before or after, the catch-up window, and which survey to send, then switch it to “Active”. Existing triggers are listed as cards with edit and delete buttons; deleting asks for confirmation since it’s permanent. Just like the three fixed types, the survey ID is checked against your library before saving, and a disabled trigger never sends anything.