App catalogue People and compliance

Employee onboarding

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.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 Onboarding queuescreenS02 Case planscreenS03 Manager checklistscreenS04 New hire portalscreenS05 IT and facilities tasksscreendh_hr_caseHR casedh_requestService requestdh_assetIT assetdh_employeeEmployeeServiceNowsn_hr_core_case · sn_hr_core_taskServiceNowsc_request · sc_req_item · sc_taskServiceNowalm_asset · alm_hardwareServiceNowsys_user · sys_user_grmember · s…rows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on ServiceNow. Other systems have their own page.
5 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
4
data handlers, read in place
catalogue
1
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

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.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
HR coordinatoropens the case, collects documents, sets the start date and the role profile
Hiring managerconfirms the role profile, the access bundle, the buddy and the first-week plan
ITfulfils the laptop and access requests; assigns the asset
Facilitiesissues the badge, the desk and the parking
New hiresigns documents, chooses equipment and follows the first-day checklist on the portal screen
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Onboarding queuegrid of hires by start date, department, manager and days to start; tasks done and open per hire; open button
S02 Case plantasks by team and day with owner, status and the linked request or task number; add task; reassign
S03 Manager checklistrole profile, access bundle by role, buddy, first-week plan; confirm
S04 New hire portalportal screen: documents to sign, equipment choice, start-day details, first-day checklist with ticks
S05 IT and facilities taskslaptop request with model and asset tag, access groups requested and granted, badge and desk; complete
S06 Onboarding boardhires by start week and readiness, tasks late by team, day-1 readiness rate
Data handlers

4 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
HR casethe onboarding case and its tasksServiceNow
Service requestthe catalog requests for laptop, access and badge, with approval and stateServiceNow
IT assetthe laptop assigned to the hire, its model and stateServiceNow
Employeethe hire's record with manager, department and groupsServiceNow

Written back

ObjectWhat changes
Service requestcatalog requests created for the laptop, the access bundle and the badge; closed when fulfilled
IT assetlaptop assigned to the new hire with the state set to in use
HR casecase tasks completed and the case closed after the first-week review
The flow

From the trigger to the last write

THE FLOW · EMPLOYEE ONBOARDING1Case openedtasks created by team fromthe role template; thestart date sets every dueday2Manager confirmedrole profile and accessbundle confirmed by startminus 10 days; requestscreated3Equipment and accessreadylaptop assigned, accessgroups granted, badgeissued by start minus 2days4Day 1hire ticks the first-daychecklist; open items shownto the coordinator5First week closedmanager completes the day-5review; case closed
Each step and the criterion that moves it.

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'

StepMoves when
Case openedtasks created by team from the role template; the start date sets every due day
Manager confirmedrole profile and access bundle confirmed by start minus 10 days; requests created
Equipment and access readylaptop assigned, access groups granted, badge issued by start minus 2 days
Day 1hire ticks the first-day checklist; open items shown to the coordinator
First week closedmanager completes the day-5 review; case closed
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
btn_confirm_profileon click → read the access bundle for the role → create the catalog requests for laptop, access and badge, link their numbers to the case
chk_requestson request state change → read the request and the asset → tick the task, update S02 and the hire's portal screen
btn_day1_checkliston tick → record the item with the time → show the coordinator any item still open at 10:00 on day 1
btn_close_caseon click → check that every task is complete → close the case in ServiceNow, store the closure time

Clocks

StepTime limit and escalation
Manager confirmationstart minus 10 working days, then the coordinator is reminded and the manager's manager is copied
Equipment and accessstart minus 2 working days, then IT's lead sees the hire on the board in red
First-week reviewstart plus 5 working days, then HR is reminded

Measures

hires with laptop, access and badge on day 1tasks late by teamdays from hire confirmed to case closednew hire checklist completion
A day with the app

Illustrative

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.

illustrative scenario · Employee onboarding
On your systems

One page per system

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.

Terms on this page

Onboarding caseThe HR case in ServiceNow that holds every task for one new hire.
Access bundleThe set of groups and applications a role needs, granted together from one request.
Catalog requestA request for an item from the ServiceNow service catalog, such as a laptop, with its own approval and fulfilment.
Questions

How long does it take to have this running?

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.

Which system does it run on?

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.

Who takes part from outside the company?

Roles on portal screens see only the rows the access policy allows, and their steps are logged like everyone else's.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

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.