home / use cases / back-office operations / employee-onboarding-offboarding

Onboarding and offboarding, without the dropped steps

When HR announces a joiner or a leaver, your Aivell runs the whole checklist — notifies IT about accounts and equipment, books the first-day sessions, sends the welcome pack, tracks every step in a sheet and escalates whatever is still open near the start date. Leavers get the same rigor, in reverse.

Watch the demo

starts when: HR announces a new joiner — or a leaver — by email

The problem

A first day tells the new hire everything. Laptop ready, badge working, someone waiting at the door — or a folding chair, an IT ticket “in progress”, and a manager improvising a tour. The difference is never effort; it is whether the eleven-step checklist was actually run, by someone who also had a normal job to do that week.

Offboarding fails more quietly and costs more: accounts that stay alive for months after the goodbye cake, equipment nobody logged, payroll surprised at the end of the month. All of it is coordination overhead — the sort of invisible work that adds up to an estimated $17k per employee per year in admin burden.

How your Aivell does it

  1. One email starts the machine. HR announces a name and a start date. The chore opens the tracker and instantly knows every task, owner and deadline between now and day one.
  2. The requests go out early. IT gets the account and equipment list two weeks ahead — not the Friday before. Payroll gets its paperwork request. The buddy Davide assigned gets a heads-up.
  3. The calendar fills itself. Welcome tour, payroll session, safety briefing — booked with the right people, meeting rooms included, before anyone has to remember to do it.
  4. Progress is visible, not assumed. Every step lives in the tracker with a status. Silence is not success: unticked items get chased, and three days out, whatever is still open escalates to HR by name.
  5. Leavers get the mirror image. Handover reminders, equipment return, and an access-removal request prepared in advance — but held until a human approves it on the day, because timing is the whole point.

The chore reads like the checklist you already have in a drawer, because that is what it is — finally executed the same way every time, by a colleague who never has a busier week. And the guardrails ensure it can nudge, book and track, but never touch a calendar, an address or a row you didn’t hand it.

The chore, as you'd write it.

No flowcharts, no code — a chore is just a message to your Aivell, in your own words. It shapes it into a solid, guarded procedure and follows it to the letter. This one:

Giulia Aivell · run the joiner checklist ● active

when HR announces a start date, open a new row per task in the joiner tracker

email IT the account list — badge, laptop, mailbox — two weeks ahead

book the first-day sessions — welcome tour, payroll paperwork, safety briefing

send the newcomer the welcome pack, in their own language

the day before the start, confirm with the buddy — Davide assigns buddies

anything still unticked three days before the start, escalate to HR

leavers run the list backwards — access removal goes out on the last day, not before

keep each step's status in the tracker until HR and IT have both ticked done

You
Got it — I'll start right away, and check with you whenever something needs a human.
Giulia Aivell

The tools it uses.

Connected with single-click passkeys — no copied tokens, no OAuth hell.

Email notifies IT, payroll and the newcomer
Calendar books first-day sessions and reviews
Spreadsheets tracks every checklist step to done

Sensible guardrails.

Every tool can be limited to exactly what this chore needs. For this one, you might set:

Email May write to internal addresses and to the one personal address HR provided for the newcomer. Nowhere else.
Calendar Creates events only in the onboarding calendar and the named attendees' invites. Other people's meetings are untouchable.
Spreadsheets Updates status cells in the joiner tracker; it cannot delete rows or rewrite the checklist template.

Questions, answered.

Every role needs a different checklist. Can it cope? +

Yes — the checklist is plain language in the chore, and it can branch like you would when briefing someone. Warehouse joiners get the safety briefing and boots order; office joiners get the laptop and the payroll session. One chore, your variants.

Employee records include contracts, salaries and bank details. Where do they go? +

Nowhere. Everything the Aivell reads and writes — announcement emails, the tracker, the welcome pack — is processed onboard the box, behind your firewall. Personnel data never transits a cloud AI service.

Offboarding is security-sensitive. Does the AI cut access by itself? +

No. It prepares the access-removal request with the full account list, and the message sits waiting until HR taps approve — from a phone, if the last day is a Saturday. The Aivell drafts; a human pulls the trigger.

What if IT simply doesn't answer? +

The tracker stays honest. Unticked items get chased, and three days before the start date anything still open lands on HR's desk with a name attached. The point is that nothing can be silently forgotten.

Related.

What is an Aivell?

An Aivell is an on-premise AI colleague: a small box that plugs into your network, runs its own AI onboard and takes the repetitive work off your desk. Prompts, documents, data — nothing ever leaves your office. Unplug the internet: it keeps working.

You describe each task as a chore, in plain language. Your Aivell turns it into a solid, guarded procedure and runs it in the background — with guardrails on every tool, a complete audit trail, and approvals in your hand when you want them. One-time setup, fixed monthly fee. No tokens, no overages.

Watch the demo

onboard inference · air-gapped · fixed monthly fee