Agent

New starter onboarding pack

New starters lose their first fortnight looking for documents and permissions nobody remembered to arrange. This agent builds the onboarding plan for a role from material your organisation already has: the team wiki, the last starter's plan, the access checklist and the induction schedule. The manager approves it before the starter sees it.

How it runs

Step by step

01

Take the role and start date

The agent reads the approved role brief and the start details, then finds the onboarding plan used for the closest comparable role.

02

Assemble the access checklist

Tools, systems and equipment for the role are listed from your own access notes, with the owner named against each item.

03

Draft the first week plan

Sessions, introductions and reading are laid out day by day in the format the People team already uses.

04

Group the reading by week

Handbook pages, team documents and product material are grouped so the starter is not handed everything at once.

05

Flag what is not arranged

Anything with no owner or no date, such as an unordered laptop or an unbooked induction, is listed for the manager.

06

The manager approves the plan

The manager edits and approves. The pack reaches the starter and the IT queue only after that.

The harness

Exactly what this agent can see, touch and change

The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.

Context

What reaches the model

People teams and managers onboarding into several teams at once, where each function has its own tools, induction and reading.

Escalation

When it asks a person

The manager approves the plan before the new starter receives it

Applications & Rights

Which tools it uses, and what it may do in each
NotionRead only
ConfluenceRead only
Google DriveReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.

Verification

How you know it’s right

Every claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.

Who it’s for

People teams and managers onboarding into several teams at once, where each function has its own tools, induction and reading.

What you’ll need

  • A connected wiki or handbook
  • An access checklist per role type
  • An agreed onboarding format
  • A manager to approve each plan

What you get

  • A first week plan
  • An access and equipment checklist
  • A grouped reading list

What it doesn’t do

It drafts the plan and the checklist. It does not raise access requests, order equipment or book sessions, and it cannot confirm that anything on the list was actually done.

How you get it

We build the first one with you

Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.

01

Scope

One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.

02

Co-build

Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.

03

Handover

You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.

What it replaces

Parts of the work currently spread across the categories below. It does not replace any of those products outright.

Copying the last starter's plan by handOnboarding checklists scattered across documentsFirst week questions landing on the manager
Estimated savingNot setNo figure ships until someone at ollo owns it and the method behind it.

Frequently asked

How is this different from an onboarding template?

A template is the same for everyone. This is built from your material for that specific role, names an owner for each item, and marks what has not been arranged. It also follows your wiki as it changes, so last year's tool list does not follow the starter around.

Does the new starter talk to it directly?

They can ask questions about the material it was built from once the manager has approved the plan, and get cited answers from the handbook. Anything personal, such as pay or contract terms, goes to a named People contact instead.

Who keeps it accurate?

The People team owns the source material. Where the agent finds a page that contradicts another, it flags the pair rather than choosing between them, and People decide which is right.

Can it cover contractors and returning staff?

Yes, where you have material for those cases connected. The plan reflects whatever access rules and induction you have written down. Where nothing is written, the agent says so rather than assuming the employee plan applies.

Let's Build

AI is a capability you build. Let's build it together.

30 minutes with our team and you'll leave with a real plan — not a sales pitch.