Onboarding touches more teams than any other process. IT creates accounts. Someone orders a laptop. The manager plans the first week. HR collects paperwork. When it lives in a checklist in someone’s head, a step gets missed, and the new person spends their first morning without a login.
Here is how to put the whole thing in Jira, once, and apply it for every new hire.
Map the work first
Before you open Jira, list every step and who owns it. Group the steps by team. For most companies it looks like this:
- IT: create accounts, set up the laptop, add the person to groups
- Manager: plan the first week, pick a buddy, set first goals
- HR: send paperwork, book the welcome session
- Facilities: desk, badge and equipment, if you have an office
Each group becomes a work item. Each step becomes a subtask or a checklist item.
Build the template set
In AppsDelivered Templates, create a template set with an epic at the top:
- Name the epic
Onboard $NewEmployee.$NewEmployeeis a custom variable. The app asks for the person’s name when you apply the set. - Add one work item per team under the epic, such as
Create accounts for $NewEmployee. - Set each work item’s Assignee to the team’s owner.
- Add the steps as subtasks or checklist items.
- Add a user variable for the hiring manager to the manager’s work items, so they go to the right person every time.
When you apply the set, you type the name once. Every work item and subtask that uses $NewEmployee fills it in.
Do the same for offboarding
Offboarding is the mirror image, and it matters more for security. Build a second set: remove access, collect equipment, transfer ownership of documents and work items. Apply it the day someone gives notice.
Keep it current
Your onboarding will change. A new tool means a new account to create. Change the template set, not the work items, and every new hire from then on gets the update. The app’s History page shows who changed the set and when, so you can see what changed between two hires.



