Build an onboarding plan for a new hire

Creates a dated task list, welcome email, first-week schedule and draft 30/60/90 for one new hire from your documented onboarding process.

This skill applies your documented onboarding process to one person. It produces a dated task list with one owner per task, a welcome email, a first-week schedule and a draft 30/60/90, then pushes them to your tools once you approve. It invents no steps: every task comes from your own documents.

When to use it

  • Someone starts in two weeks and the plan has to be built by hand again.
  • Onboarding tasks keep falling between HR, the manager and IT because nobody was named.
  • Each manager runs onboarding differently and new hires notice.
  • You hire in more than one country and the steps differ.
  • You documented your onboarding process and want to put it to work on every hire.

What you get

One review pack, in this order:

  • Hire details: only the ones your process depends on.
  • Task list: every task in the words of the source document, with exactly one owner, an actual due date plus its offset from the start date, and the document it came from.
  • Needs an owner: tasks your documents leave unassigned, as questions for you.
  • Welcome email: in your voice, covering what your documents say it should.
  • First-week schedule: each meeting, who's in it, how long, and roughly when.
  • 30/60/90 draft: learning, contributing, owning. Marked DRAFT, because the manager owns it.
  • Documents to duplicate: links to each master.

It ends with two lists: the gaps to close before anything is pushed, and what your documents don't cover for this hire.

How it works

  1. It gets your onboarding process document. It asks where it is and searches Effy AI knowledge, connected folders, drives and wikis. It identifies the document by content, not by file name. If no documented process exists, it stops and offers to create one with the "Document your onboarding process" skill first.
  2. It works out which hire details matter. A detail matters if your process branches on it or counts dates from it. It asks for the missing ones in one message and says why each is needed.
  3. It looks for role-specific material. A meeting list, a 30/60/90 outline, or documents to copy for this role or department. If there is none, those sections stay visibly thin.
  4. It builds the pack and shows it. Nothing is created in other tools at this point.
  5. It pushes, once you say so. Tasks go to the tool your process names, with assignees matched to real accounts and calculated due dates. First-week meetings are placed around attendees' availability and the hire's public holidays. It checks what already exists first, so a re-run updates and doesn't duplicate.

What it never does. It doesn't build a plan from general knowledge of how onboarding usually works. It doesn't guess an owner or a due date: unassigned tasks are flagged and are not pushed. It doesn't pick a tool for you. It doesn't invite the new hire before their work account exists, and nothing goes to the new hire or the manager unless you ask for that specifically.

How to run it

Install the Effy AI plugin for Claude or ChatGPT. One install adds every Effy AI skill, this one included. Then connect the tools you want the skill to read from, such as email, calendar, your drive or your meeting notetaker, and ask for what you need in plain words: the assistant picks the right skill.

Before you start: you need your onboarding process document. Connect your task tracker and calendars if you want the plan pushed; otherwise it gives you output you can paste or import.

  1. Ask, for example: "Effy, build an onboarding plan for [name], starting [date]."
  2. Point it to your process document and give the hire's details.
  3. Review the pack and close the gaps.
  4. Tell it to push.

It can also save the approved 30/60/90 as a draft growth plan for the hire in Effy AI.

Click. Try. Use.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.