π Automates the entire employee onboarding and offboarding lifecycle β from catalog request submission to manager approval and departmental task creation β using Service Catalog, Flow Designer, Approval Engine, and Task Management.
π Overview Β· β¨ Features Β· ποΈ Database Design Β· π Workflow Β· β Flow Designer Β· π Manager Approval Β· π Task Automation Β· πΉ Demo
Coordinating employee onboarding and offboarding manually across multiple departments (HR, IT, Facilities, and Security) often results in delays, security risks, and administrative overhead.
The Employee Lifecycle Management System solves these challenges by providing a centralized ServiceNow-based solution that automates request submission, routes approvals, tracks status changes, and auto-generates department-specific tasks.
| π« Manual Process Issues | β Automated ServiceNow Solution |
|---|---|
| Disconnected department coordination | Centralized Service Portal for request creation |
| Manual request tracking in sheets | Custom Employee Lifecycle Table (u_employee_lifecycle) |
| Delayed hardware, email, and access setup | Automated IT tasks upon manager approval |
| No verification or authorization audit trail | Integrated ServiceNow Approval Engine for line managers |
| Risk of access leaks during offboarding | Automatic task creation for Security and Access revocation |
|
|
|
|
The core data model u_employee_lifecycle stores all employee state and request details:
| Field | DB Name | Type | Description |
|---|---|---|---|
| Employee ID | u_employee_id |
String | Unique ID of the employee |
| Employee Name | u_employee_name |
String | Full name of the employee |
| Employee Email | u_employee_email |
Contact email address | |
| Department | u_department |
Choice | IT, HR, Finance, Operations, Sales |
| Manager | u_manager |
Reference β sys_user |
Line manager (Approver) |
| Joining Date | u_joining_date |
Date | Target start date (Onboarding only) |
| Exit Date | u_exit_date |
Date | Target departure date (Offboarding only) |
| Lifecycle Type | u_lifecycle_type |
Choice | Onboarding / Offboarding |
| Status | u_status |
Choice | New, Pending Approval, In Progress, Closed Complete, Rejected |
| Manager Approval Status | u_manager_approval_status |
Choice | requested / Approved / Rejected |
| Laptop Required | u_laptop_required |
True/False | Onboarding equipment trigger |
| Email Account Required | u_email_required |
True/False | IT mailbox provisioning trigger |
| System Access Required | u_system_access_required |
True/False | Application access credential trigger |
| Asset Return Required | u_asset_return_required |
True/False | Offboarding hardware collection trigger |
| Access Revocation Required | u_access_revocation_required |
True/False | Offboarding credential cancellation trigger |
β Complete project architecture showing catalog variables mapping to custom tables, approvals, and tasks
| Step | Participant | Action | System Outcome |
|---|---|---|---|
| 1 | User / HR | Opens Service Portal | Accesses the catalog item |
| 2 | User / HR | Fills and Submits Request | Service Catalog triggers the Flow Designer |
| 3 | Flow Designer | Retrieves Variables | Creates a record in the custom u_employee_lifecycle table |
| 4 | Approval Engine | Requests Manager Approval | Manager receives Approval record (requested state) |
| 5 | Manager | Reviews Request | Approves or Rejects the request |
| 6a | Flow (Approved) | updates fields | Status β In Progress, Approval Status β Approved. Creates 4 Departmental Tasks |
| 6b | Flow (Rejected) | updates fields | Status β Rejected, Approval Status β Rejected. Workflow ends. |
The flow automates data collection, approval routing, and task generation:
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β TRIGGER β
β ββββββββ β
β π Catalog Item: Onboard / Offboard Employee β
ββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββ
β
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β ACTION 1: Get Catalog Variables β
ββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββ
β
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β ACTION 2: Create Employee Lifecycle Record β
β State: Pending Approval β
ββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββ
β
βΌ
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β ACTION 3: Ask For Approval β
β Approver: u_manager β
ββββββββββββββββββββββββββ¬ββββββββββββββββββββββββββββββββββ
β
ββββββββββββ΄βββββββββββ
β β
β
APPROVED β REJECTED
β β
βΌ βΌ
βββββββββββββββββββββββ βββββββββββββββββββββββ
β π’ Update Record β β π΄ Update Record β
β Status β β β Status β β
β "In Progress" β β "Rejected" β
β β βββββββββββββββββββββββ
β π¦ Create Tasks: β
β β’ HR Task β
β β’ IT Task β
β β’ Facilities Task β
β β’ Security Task β
βββββββββββββββββββββββ
Managers receive approval requests via the ServiceNow Approvals table:
- Dynamic Approver Mapping: Flow retrieves the employee's manager from user records and assigns the approval task.
- Workflow Interlocking: Downstream tasks remain locked until the approval action changes from
requestedtoApproved. - Audit Trails: Approval and rejection timestamps are persisted on the lifecycle record.
Once approved, 4 departmental tasks are generated under the ServiceNow Tasks table:
| Department | Task Type | Description |
|---|---|---|
| HR | Onboarding Paperwork | Handle contracts, verify ID, and initiate onboarding orientation. |
| IT | Equipment & Access | Provision laptop/workstation, create email account, and configure system permissions. |
| Facilities | Workspace Setup | Allocate desk space, issue building access badges, and prepare workspace. |
| Security | Access & Credentials | Activate access permissions, set up security profiles, and configure security parameters. |
β Catalog Submission: Form values map correctly to flow inputs.
β Record Creation: u_employee_lifecycle entry generated in Pending Approval.
β Approval Routing: Approvals generated and routed to the assigned manager.
β Status Transition: Approval updates status to In Progress.
β Task Generation: 4 distinct tasks created for IT, HR, Facilities, and Security.
β Catalog Submission: Exit details populated.
β Manager Approval: Approval routes correctly to the manager.
β Status Transition: On rejection, status transitions to Rejected and exits.
β Task Generation: Tasks successfully created for access revocation and asset return.
- β±οΈ SLA Management: Track completion time for HR and IT tasks to ensure timely onboarding.
- π§ ServiceNow Email Notifications: Automated emails on onboarding initiation, approval, and task completion.
- π Dashboards & KPIs: Central portal reporting charts for managers showing onboarding pipeline.
- π Role-Based ACL Security: Read-only restrictions for employees, edit permissions for managers/fulfillment groups.
- π₯ Department Assignment Groups: Route IT/HR tasks directly to ServiceNow group queues rather than individuals.
Through this project, I gained hands-on experience with:
- ServiceNow Application Development: Database table design, choice list creation, and reference fields.
- Service Catalog Design: Building Record Producers, catalog variables, and form organization.
- Flow Designer Automation: Creating complex workflows, mapping variables, and conditional branching.
- Approval Engine Integration: Setting up manager approval rules and routing.
- Fulfillment Task Management: Auto-generation of tasks for multiple departments.
Chappa Bharath Kumar
- B.Tech Information Technology
- Aditya College of Engineering & Technology
- ServiceNow Developer | Backend Developer | AI Enthusiast
Made with β€οΈ using ServiceNow




