Asynchronous onboarding means a new hire learns the job from recorded walkthroughs, written procedures and searchable answers, on their own schedule, instead of waiting for someone to explain it live. It works only as well as the knowledge behind it. If your documents hold the rules but not the exceptions and the reasoning, new hires will read everything and still have to ask. We built Kept to capture that missing layer in people's own words, so the async material carries the judgment and not just the steps.
This guide is for HR leads, team managers, project managers and owners who need new people productive without burning senior staff's calendars. It covers what asynchronous onboarding is, how to structure the first weeks, what to write down, where live time still belongs, and how to tell whether it is working.
TL;DR
- Asynchronous onboarding replaces default live explanation with self-paced material: documentation, recordings and searchable answers. Live time is kept for questions and relationships.
- It is scalable and repeatable, but new hires often do not know whom to ask, so every async program needs a named buddy and scheduled check-ins.
- The weak point is content. Procedures capture what to do; new hires fail on the exceptions and the reasons, which live in experienced people's heads.
- Measure it by cohort, not by individual: how fast new people get productive, whether they finish the tasks, and what they say at set intervals.
- Capture the expertise through guided interviews first, then structure it into the onboarding path.
Table of Contents
- What asynchronous onboarding actually means
- Why teams move to it
- Where it breaks: the missing layer
- A structure for the first 30 days
- Building the content: what to capture and how
- What still needs to be live
- The visibility problem
- Measuring whether it works
- Our perspective
- Putting this to work with Kept
- FAQ
- Sources
What asynchronous onboarding actually means
Asynchronous communication is communication that does not need an immediate response: the recipient reads, watches or listens, and replies later. Synchronous communication is the opposite: meetings, calls and in-person conversations in real time. Asynchronous onboarding applies that idea to a new hire's first weeks.
In practice, a new person gets a path through written pages, short recorded walkthroughs and self-directed tasks. They work through it when it suits them. They do not sit through back-to-back sessions where a colleague explains the same systems for the tenth time.
GitLab's public handbook is the best-known example. It defines onboarding as the official process of integrating new team members, done in a remote setting through technology rather than face-to-face contact, and it describes onboarding tasks as self-driven and "asynchronous as possible". The same page is candid about the trade-off: because remote onboarding is mostly self-guided, the real-time ability to ask a question does not exist in the same way, so the program relies on documentation.
That last point is the heart of this topic. Asynchronous onboarding is not a scheduling trick. It is a documentation commitment. You are moving the explaining out of conversations and into material that a new hire can use at 7 a.m. or 9 p.m., in any time zone, without interrupting anyone.

Why teams move to it
The pull is practical.
It scales. A live walkthrough costs a senior person's time every time someone joins. A good page or recording costs time once and serves every later hire. GitLab describes documentation-based onboarding as scalable and repeatable.
It respects the new hire's pace. People absorb at different speeds. Slack's guidance on remote onboarding recommends self-paced material such as documentation, recorded walkthroughs and learning modules, with live sessions reserved for questions and clarification. It also warns against front-loading live sessions that overwhelm new hires before they have any context.
It leaves a record. A BBC Worklife feature on asynchronous work, citing a Stanford researcher and GitHub's COO, notes that written communication makes it easier to onboard people, because newcomers can follow the context around past decisions in the written trail rather than relying on someone's memory of why things were done.
For a small or mid-sized business, the first reason is usually the decisive one. When one person is the only one who knows how invoicing exceptions work, a hire's first week can consume a quarter of that person's attention. Asynchronous material gives that time back.
Where it breaks: the missing layer
Most async onboarding programs fail in the same way. The team gathers its existing SOPs, adds a welcome video and a checklist, and calls it done. The new hire completes everything and still stalls on the first real case.
The reason is that standard documents hold what the organization has agreed to write down: the steps, the owners, the tools. They rarely hold what the experienced person actually uses:
| What the document holds | What the person holds |
|---|---|
| The standard sequence of steps | Which steps are load-bearing and which are ceremony |
| The approved threshold or limit | When it is acceptable to bend it, and who must agree |
| The tools and where to find them | The workaround everyone uses when a tool misbehaves |
| The rule | The reason for the rule, and the incident that created it |
| The common case | The three exceptions that account for most of the confusion |
In a live setting, the new hire gets the right column by sitting next to the expert and asking. In an async setting, nobody is there to ask. If the right column never makes it into the material, it simply does not reach the new person, and when that expert leaves, it is gone for good.
This is tribal knowledge, and it is the real risk in asynchronous onboarding. The format is only as good as the judgment it carries. If you want a deeper look at what a written procedure should contain, our guide to onboarding process documentation walks through it.
A structure for the first 30 days
A sequence helps because a new hire with a wall of pages and no order will not know where to start. GitLab's published plan is a useful reference for the shape: day one covers accounts and paperwork, day two remote work and company values, day three security and compliance, day four social topics and benefits, and day five the core tool. Weeks two through four move into exploration, with job-specific tasks beginning around week three, as set out in its onboarding handbook page.
You do not need to copy it. The pattern to take from it is this:
- Week one: access and orientation. Accounts, policies, security basics, benefits. Everything here is stable and easy to record once.
- Week two: how we work. Communication norms, how decisions are made, who owns what. This is where reasoning starts to matter.
- Weeks three and four: the actual job. Guided tasks drawn from real work, with the exceptions explained, not only the happy path.
- Days 30 to 90: widening scope. Harder cases, more independence, regular check-ins.
For a manager building this from scratch, the employee onboarding checklist for managers covers the 90-day arc, and the piece on reducing onboarding time without rushing new hires addresses pacing.
Building the content: what to capture and how
This is the step that decides whether the program works, so it deserves care.
Step 1: Pick the roles and the first ten tasks
Do not document the whole company. Pick one role you hire for repeatedly and list the ten tasks a new person must do in their first month. Those ten are your scope.
Where it goes wrong: teams start with the employee handbook and run out of energy before they reach the job itself.
Step 2: Capture the expert's knowledge, not just the steps
Writing a procedure from scratch is slow, and experts tend to leave out what feels obvious to them. A guided interview works better: someone asks the expert why they do each step, what goes wrong, when they break the rule and what they check before deciding. Investigators and oral historians use the same method, because people describe their judgment far better when asked about specific cases than when asked to write a general rule.

This is what Kept's guided interviews are designed for. The expert explains the process in their own words, and the platform helps document the exceptions and the reasoning behind them, then structures the result into a workflow that others can retrieve. Capture is opt-in, and the person can review and delete what they contributed.
Step 3: Choose the right format for each piece
Not everything belongs in the same format.
- Written pages suit anything a new hire will search for later: policies, thresholds, decision rules, naming conventions.
- Short recordings suit anything visual: how to move through a tool, how a report is assembled. Asynchronous video is one-way recorded video that people watch whenever they like. The Association for Talent Development's guidance is that it does not replace video conferencing but sharpens it: when real-time dialogue is needed, it is clearer and more productive. If recording is the bottleneck, AI-generated onboarding videos can reduce production effort.
- Self-directed tasks suit practice. GitLab's approach uses an issue template through which new hires work their way through onboarding tasks, supported by a searchable handbook where they can look up answers. Treat the task as the teaching tool: a new hire who completes a real, scoped task learns more than one who watches three more videos.
Step 4: Make it findable
A new hire in week three will not remember which page held the refund threshold. They need to ask a question and get an answer. GitLab's model is handbook-first, with a central repository as the single source of truth so people become self-sufficient when looking for answers.
Kept's search is context-aware and returns citation-backed answers, so a new hire can see which captured procedure an answer came from. That matters for trust: a new person who can check where an answer originated is more likely to act on it.
Step 5: Control access and ownership
Onboarding material often mixes the general with the sensitive. Kept business workspaces have workspace-level access controls, so a new hire sees what their role requires, and the organization keeps clear control over who owns and can delete captured knowledge.
For teams that want to start small, the post on piloting onboarding documentation in four to eight weeks lays out a scoped approach, and the onboarding playbook guide shows how to assemble the pieces into one document.
What still needs to be live
Async does not mean alone. The research on remote and distributed onboarding is consistent on one point: the human side needs deliberate design.
GitLab notes that a documentation-based approach carries a risk, which is that new hires may not know whom to ask for help. Its recommended remedy is to assign a buddy and check in regularly. Slack's guidance gives concrete rhythms: weekly manager one-on-ones in the first 30 days, then every two weeks, a dedicated direct-message thread for async questions, a clear message that questions are welcome, and a buddy for informal guidance, all in its remote onboarding guide for managers.
A workable live layer looks like this:
- A first-day call with the manager, short and personal, before the new hire opens a single page.
- A weekly one-on-one for the first month, focused on what confused them, not on status.
- A buddy who answers the small questions that nobody would write a page about.
- A live Q&A slot once or twice a week where the new hire brings the questions the material did not answer.
- Team introductions that are social, not informational.
The principle is simple: use live time for relationships and clarification, and use async material for transmission. When live sessions are used to read information aloud, they waste the one thing a live conversation does better than a page.
The visibility problem
One risk deserves its own mention. Microsoft Research studied onboarding in newly virtual teams and found that reduced informal interaction and reduced newcomer visibility can inhibit onboarding. In an office, a newcomer picks up norms by overhearing and being seen. Remotely, that does not happen by itself.
The design response is to build in the visibility that offices provide by accident: ask new hires to share early work in a team channel, have the manager respond publicly to good questions, and make the buddy relationship explicit. The async material gives the knowledge. These practices give the belonging.
Measuring whether it works
An async program that nobody measures drifts. You do not need a complex dashboard. Track a small set of signals:
- Time to productivity: how long until a new hire handles the core tasks of the role without help. Define it per role before you start.
- Task completion: whether the self-directed onboarding tasks actually get finished, and where people stop.
- Early retention: whether new hires are still with you at 90 days.
- New-hire feedback at intervals: a short pulse survey after the first couple of days, at 30 days and at 90 days, asking about clarity and confidence.
- Questions asked: the questions new hires raise repeatedly are your documentation gaps, listed for you.
Read the results by cohort, not by person. One slow starter tells you little. If a whole cohort stalls at the same task, the material is the issue, not the people. That last signal, repeated questions, is the most useful for the content: each one points to an exception or a reason that never made it onto a page.
Our perspective
Most onboarding problems we hear about are described as training problems. We think they are knowledge problems. The new hire is not slow; the material is missing the part that experienced people carry.
A procedure is a record of what the organization decided to write down. The person who runs the process every day knows more: which steps are load-bearing, which are ceremony, where the threshold really sits, and why. If you go async without capturing that, you have only made the gap quieter. Nobody is in the room to notice it.
That is why we built Kept around conversation. People explain how they work far better when someone asks them good questions about real cases than when they are told to write a document. Guided interaction brings out the exceptions and the reasoning, in their own words, and keeps each person's context intact. The result is documentation a new hire can search, cite and trust.
We also think capture should be the expert's choice. Opt-in, reviewable, deletable. People share judgment more freely when they stay in control of it.
If you take one thing from this guide: before you record the next welcome video, sit one expert down and ask them what they would tell a new hire about the three cases that always go wrong.
Anthony
Putting this to work with Kept
Kept is a conversational AI platform for documenting and managing workflows. Your people describe their processes in their own words, guided interviews draw out the exceptions and the reasoning, and the platform structures it all into workflows your team can search, with answers that cite where they came from. Business workspaces have access controls at the workspace level, so onboarding material reaches the right people.

It is built for the onboarding situation described above: expertise that lives with a few people, new hires who need answers without waiting, and managers who want less repetition. Our plans, kept for you and kept for business, start with a consultation and onboarding. You can see how the approach applies to new-hire programs on the onboarding use case page and find the plans on our pricing page.
FAQ
What does it mean if a job or onboarding process is asynchronous?
It means work and communication do not depend on everyone being online at the same moment. In onboarding, the new hire works through documents, recordings and tasks on their own schedule, and colleagues reply when they can rather than instantly.
Is asynchronous onboarding better than live onboarding?
The strongest programs combine both. Self-paced material carries the information, and live time is kept for questions, feedback and relationships. Front-loading live sessions before a new hire has context tends to overwhelm them, as Slack's guidance on remote onboarding notes.
How long does it take to set up?
Start with one role and its first ten tasks rather than the whole company. A scoped pilot can run in a matter of weeks, and you can widen it role by role as the material proves itself.
Who should own the onboarding content?
The people who do the work should supply the knowledge, and one person, often in HR or the team lead, should own the structure and keep it current. Guided interviews let experts contribute without having to write documents themselves.
How do we keep new hires from feeling isolated?
Assign a buddy, hold weekly one-on-ones in the first month, give new hires a dedicated place to ask questions, and make early work visible to the team. These steps replace the informal contact an office provides automatically.
Sources
- The complete guide to remote onboarding for new-hires, GitLab Handbook
- Remote Onboarding: A Complete Guide for Managers, Slack
- How asynchronous communication could change your workday, BBC Worklife
- Not Seen and Not Heard: Onboarding Challenges in Newly Virtual Teams, Microsoft Research
- Asynchronous Video vs. Video Conferencing, ATD
