When transitions depend on emails and memory, tasks are easy to miss.
I build onboarding and offboarding workflows in Jira Service Management that connect the request, approvals, assigned work, and agreed systems, so your teams can see what needs to happen and who owns it.
The workflow, in one line.
Request. A joiner or leaver is raised by HR or the manager, with the information needed to start.
Approvals. Agreed approvers confirm role, access level, and any exceptions before work starts.
Tasks. IT, facilities, finance and the manager each see their own tasks and due dates.
Systems. Identity, email, and access provisioning or removal run where in scope.
Record. What was done, by whom, and what is still open.
A failed integration or an unanswered task becomes a visible item with an owner, instead of disappearing into email.
Less chasing. Clearer responsibility. A record of the work.
Give IT, HR, managers, and other participating teams a shared view of the process.
Define the information and approvals needed to start work.
Assign tasks and surface exceptions before they disappear into email.
Record completion and unresolved items in the agreed workflow.
Built around your people and systems.
The project can include request forms, approval paths, role-based task sets, automation, agreed provisioning or deprovisioning integrations, reporting, and operational documentation.
We define which employee scenarios and systems are covered, how exceptions are handled, and which actions still require a person. Where another platform or supplier is responsible for an action, that dependency is explicit.
Map it, agree it, build it, hand it over.
Map the current process. Identify the participants, systems, delays, and exceptions.
Agree the target workflow. Define ownership, approvals, completion criteria, and integration boundaries.
Build and test. Validate the agreed scenarios, including failed integrations and manual follow-up.
Launch and hand over. Provide instructions and an agreed transition into normal operation.
We review the available integration options during scoping. The proposal identifies what can be automated, what remains manual, and any licensing or supplier dependencies.
Coverage depends on the systems and access paths included in the project. We define those boundaries and how incomplete actions are identified and followed up.
We can discuss improving an existing setup or including a new implementation in the project scope.
Give your teams a process they can rely on.