AI Onboarding Workflows: Replacing the 90-Day Plan with Just-in-Time Knowledge
Keep the 30-60-90 plan for what it does well, agreeing outcomes between a manager and a new hire, and delete the reading list inside it, because the reading list is the part that goes stale and gets forgotten while the agreement is the part that needs people. Move the "how do I" knowledge into just-in-time answers from a company brain, but keep three groups of items out of that move: anything that must be proven, anything that is costly to learn late, and anything that depends on judgment.
Two jobs in one spreadsheet
A 30-60-90 plan does two jobs. It agrees what the new hire should have achieved by each checkpoint, and it schedules what they read, whom they meet and which systems they learn. The second job is where plans fail. A static schedule cannot fit a senior engineer who breezes through the architecture documents but is stuck on the company's deployment pipeline, so they spend time on material they already know and get no help where they are blocked. Dozens of wiki pages read in week one are often forgotten by the week they apply, and the hire interrupts a colleague. The plan itself also rots, because managers rarely have time to update every link, and new hires end up pointed to deprecated systems.
Just-in-time answers fix that second job. Instead of a twenty-page manual on expense reporting in week one, the hire gets a short, actionable guide the first time they submit an expense report. The first job, agreeing outcomes, stays with the manager.
Sort every item in the old plan
We recommend sorting each item in your current plan three ways:
- Front-load what is costly to learn late or must be proven: security and safety rules, legal and policy acknowledgments, and access that blocks day one.
- Make just-in-time what is cheap to get wrong once and findable at the moment of need: procedures, tool how-tos, who owns what, acronyms and location-specific benefits information.
- Keep with a person what depends on judgment: priorities, feedback, working relationships and career conversations.
The claim that completion rates become irrelevant holds only for the second group. For the first, a completion record is the requirement, and a just-in-time answer is not proof that anyone read it. Keep those items as required tasks with evidence, as described in the audit trail guide, and let everything else leave the schedule.
The plan after the sort
This example is for a knowledge-work role. Adapt the outcomes to yours. The 30-60-90 day plan template covers the outcome side in more detail.
| Period | The plan keeps | The assistant answers | Check |
|---|---|---|---|
| Week 1 | Accounts working, required training done with proof, first small task assigned | Where things live, how to request access, how to set up tools | Questions that still needed a person |
| Days 8 to 30 | One supervised task finished to the manager's standard | How a process works, who owns what, what a term means | Time to the first finished task |
| Days 31 to 60 | One task owned from start to finish | Exceptions, escalation routes, the reasons behind a process | Questions the same hire asks twice |
| Days 61 to 90 | A defined area of responsibility and a review of the first quarter | Policy and planning questions as they come up | Manager time spent on repeat questions |
People keep what only people can do: introductions, feedback on the first task, judgment calls and the career conversation. The mentor's one-on-one should not review a checklist of completed tasks. Start it from the topics the hire asked the assistant about most, which the assistant can summarize as counts, and let the hire choose which questions to bring. A cluster of questions on one topic can point to a deeper misunderstanding, and that is the conversation worth having.
Make just-in-time answers trustworthy
You cannot point a language model at a messy shared drive and expect accurate onboarding support. Audit the wikis, handbooks and policy documents first, and keep tasks, role templates and linked knowledge in one structure. The public GitLab onboarding handbook is a good example of that organization.
AWS describes retrieval-augmented generation as redirecting the model to retrieve relevant information from authoritative, pre-determined knowledge sources. That makes cited answers possible. It does not make them correct, so the sources have to be.
Put the assistant in the chat tool the hire already uses, such as Slack or Microsoft Teams, and not in a separate portal. A nudge can arrive when the plan says the need begins, for example a short guide on the code review process when the first pull request is opened. Trigger it from a milestone in the plan and not from watching the hire's activity.
The assistant must respect existing access controls. Tag every document with an access control list and filter the results by the user's identity, through your identity provider, before anything goes to the model. A new marketing coordinator who asks about financial projections should not get data from a restricted executive dashboard.
When it cannot answer
When the knowledge base has no definitive answer, the assistant should say so and route the question to a named expert, found through the org chart or document authorship. The expert then writes the answer into the governing page, and the assistant reads that page next time. The answer goes into a reviewed page, not into the assistant's memory, so the next change to the policy is made in one place.
Treat the AI tooling around your HR data as part of the security review. TechCrunch reported that Mercor, an AI recruiting startup, confirmed a security incident linked to a supply chain attack involving the open source project LiteLLM, and that it was one of thousands of companies affected. Ask any vendor which open-source components handle your data and how quickly it patches them.
What to measure
- Time to first value: how long a hire takes to finish a meaningful task, such as closing a support ticket, shipping a pull request or launching a campaign.
- Resolution rate: the share of onboarding questions the assistant settles without a person. Count a question as resolved only when the hire does not come back with it or ask a colleague afterwards.
- Completion evidence for the required items, which stays on the books.
- Manager time: whether managers spend less time on repetitive questions and more on coaching.
Review the questions the assistant could not answer. If several hires ask about the remote work policy and get unhelpful responses, you know which document to fix.
Start with the old plan
Open your current 30-60-90 plan and sort every item into the three groups. For the just-in-time group, list the twenty questions hires asked in their first month, make sure each has a current answer with an owner, and launch to one team before the whole company.
-p-1080.jpg)
%20you%20need%20to%20know%20about_cover.png)