Start with outcomes, not departments
A useful onboarding parent represents one new starter. Its subtasks should describe completed outcomes: accounts created, hardware assigned, induction booked, buddy introduced, and first-week review completed. Keep sensitive HR data out of task summaries.
Example template
Define two run-time values:
starter_name = New starter
start_date = Start date
Then define the reusable subtask outline:
Create accounts for {{starter_name}} | due=+0 | assign=me
Assign hardware to {{starter_name}} | due=+1
Book induction sessions for {{starter_name}} | due=+2
Pair {{starter_name}} with a buddy | due=+3
Week one review with {{starter_name}} | due=+5
Run the checklist
- Create the onboarding parent issue.
- Open Add subtasks from template on that issue.
- Select the onboarding template and enter the starter's details.
- Review the generated summaries, then run the preflight.
- Use the receipt to confirm every subtask and parent link.
Start with the packaged onboarding template
TreeGuard includes this starter so a project administrator can adapt it and save the first reusable process in minutes.
Try it free