Runs a new hire's onboarding as one case: HR, the manager, IT and facilities complete their tasks by day, so the hire arrives to a working laptop, access and badge.
Today the offer letter starts 4 email chains: HR asks IT for a laptop, the manager asks for access to 6 systems, facilities hears about the badge on the Friday before, and the new hire spends the first 3 days waiting. Each team keeps its own list, and the whole picture exists only in the HR coordinator's head.
The hire in the HR system creates an onboarding case in ServiceNow, and the app opens it with the tasks each team owes by day: HR collects documents and the contract, the manager confirms the role profile, the buddy and the first-week plan, IT fulfils the laptop and the access bundle for the role, and facilities issues the badge and the desk. Each task becomes a catalog request or a case task in ServiceNow, so the teams can work in either place and the app shows the same status. The new hire sees a portal screen with the documents to sign, the equipment choice and the first-day checklist. On day 1 the case shows the laptop assigned, the access groups in place and the badge collected, and the manager closes the first-week review on day 5.
| Lane | Does |
|---|---|
| HR coordinator | opens the case, collects documents, sets the start date and the role profile |
| Hiring manager | confirms the role profile, the access bundle, the buddy and the first-week plan |
| IT | fulfils the laptop and access requests; assigns the asset |
| Facilities | issues the badge, the desk and the parking |
| New hire | signs documents, chooses equipment and follows the first-day checklist on the portal screen |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Onboarding queue | grid of hires by start date, department, manager and days to start; tasks done and open per hire; open button |
| S02 Case plan | tasks by team and day with owner, status and the linked request or task number; add task; reassign |
| S03 Manager checklist | role profile, access bundle by role, buddy, first-week plan; confirm |
| S04 New hire portal | portal screen: documents to sign, equipment choice, start-day details, first-day checklist with ticks |
| S05 IT and facilities tasks | laptop request with model and asset tag, access groups requested and granted, badge and desk; complete |
| S06 Onboarding board | hires by start week and readiness, tasks late by team, day-1 readiness rate |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| HR case | the onboarding case and its tasks | ServiceNow |
| Service request | the catalog requests for laptop, access and badge, with approval and state | ServiceNow |
| IT asset | the laptop assigned to the hire, its model and state | ServiceNow |
| Employee | the hire's record with manager, department and groups | ServiceNow |
| Object | What changes |
|---|---|
| Service request | catalog requests created for the laptop, the access bundle and the badge; closed when fulfilled |
| IT asset | laptop assigned to the new hire with the state set to in use |
| HR case | case tasks completed and the case closed after the first-week review |
Start: A new onboarding case appears in ServiceNow, created when the hire is confirmed in the HR system, with a start date within 30 days.
# start criterion, in canonical fields; each system page shows it in that system's fields
{hr_case.type} = 'onboarding' and {hr_case.state} = 'new'| Step | Moves when |
|---|---|
| Case opened | tasks created by team from the role template; the start date sets every due day |
| Manager confirmed | role profile and access bundle confirmed by start minus 10 days; requests created |
| Equipment and access ready | laptop assigned, access groups granted, badge issued by start minus 2 days |
| Day 1 | hire ticks the first-day checklist; open items shown to the coordinator |
| First week closed | manager completes the day-5 review; case closed |
| Component | Trigger → action → outcome |
|---|---|
| btn_confirm_profile | on click → read the access bundle for the role → create the catalog requests for laptop, access and badge, link their numbers to the case |
| chk_requests | on request state change → read the request and the asset → tick the task, update S02 and the hire's portal screen |
| btn_day1_checklist | on tick → record the item with the time → show the coordinator any item still open at 10:00 on day 1 |
| btn_close_case | on click → check that every task is complete → close the case in ServiceNow, store the closure time |
| Step | Time limit and escalation |
|---|---|
| Manager confirmation | start minus 10 working days, then the coordinator is reminded and the manager's manager is copied |
| Equipment and access | start minus 2 working days, then IT's lead sees the hire on the board in red |
| First-week review | start plus 5 working days, then HR is reminded |
Names, places and figures are illustrative; the pattern is the catalogue's.
On 3 March the hire of Amara, a network engineer starting in Nairobi on 24 March, created a case at 09:10, and her manager confirmed the role profile and access bundle by 11:00. IT received the laptop and access requests the same minute, assigned a laptop with its asset tag on 12 March, and the 7 access groups showed as granted on 18 March. Amara signed her documents on the portal screen the week before, collected her badge at 08:30 on day 1, ticked the last checklist item at 09:45, and her manager closed the first-week review on the Friday.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Other systems connect through the same handlers; see how SmartApps connect.
About 30 minutes to a first running screen on your live rows, and 5 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.
Any of ServiceNow, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.
Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.