---
sourceDocument: Xanadu Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/employee-service-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Document the lifecycle event process

# Document the lifecycle event process {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Define and document the lifecycle event process. Lifecycle events are generally
cross-departmental and require action from different departments.

It is thus critical that everyone agrees on the flow and their areas of responsibility. As
you map out a lifecycle event, consider who is responsible for owning the activity, what the
activity type is, and if there is a targeted audience for that activity.

## Defining the lifecycle event {#define-lifecycle-event-process__section_az2_gnl_hhb}

As you map out and define your lifecycle event, consider the following.

* What is the lifecycle event type? Examples of lifecycle events include employee onboarding, offboarding, and parental leave.
* What are the different stages of the lifecycle event? These stages are represented as activity sets, which act as containers for the associated activities. Each activity set is triggered based on specified conditions.
* What are the different activities for each activity set? For each activity, determine the appropriate owning group, activity type, and audience.
  * Who owns the activity? Lifecycle events generally span multiple departments. Each activity must be owned by the relevant group that is responsible for overseeing and maintaining that activity, such as HR, IT, or Facilities.
  * What is the activity type? Is it a task for an employee or fulfiller? An approval or notification?
    * Approvals
    * Tasks for employees
    * Activities for fulfillers, which can be configured as order guides, catalog items, HR services, HR tasks, incidents, and more
    * Notifications
    {#define-lifecycle-event-process__ul_f3l_cc5_dhb}
  * Is there a targeted audience for the activity? Some activities are not required for all employees, and you can use audience records to target the activity to the appropriate user types.
  {#define-lifecycle-event-process__ul_orm_l15_dhb}
{#define-lifecycle-event-process__ul_ejw_1xn_dhb}  

## New hire onboarding

New hire onboarding is a lifecycle event that is included as demo data with the Lifecycle
Events for Enterprise \[com.sn_hr_lifecycle_ent\] plugin. The event is organized into activity
sets, such as pre-hire, pre-boarding, and day one, which represent different stages in the
lifecycle event process. Each activity set contains one or more activities, such as a task
for the employee to enroll in medical benefits or a request for an IT fulfiller to set up a
new hire's phone and voicemail.

**Previous topic:** [Building a lifecycle event](https://www.servicenow.com/docs/iDETeCN1tSxhn5uV_cu9Yg "Lifecycle events enable you to automate the fulfillment of HR cases such as new hire onboarding.")  
**Next topic:** [Configure the supporting components for a lifecycle event](https://www.servicenow.com/docs/MkNtrflriL7oMGjfVjjtlw "Configure the supporting components for a lifecycle event. Lifecycle events are a collection of activities. For each activity, you must identify and configure the underlying components that support it, such as HR task templates, order guides, catalog items, and HR services. You must also identify and configure the relevant owning groups, activity types, and audience records.")