Remote onboarding is generally well organised for the first two weeks and thin afterwards. The failure point sits in the second month, once the formal programme has ended.
The first fortnight covers the easy material
Accounts, tools, policies and the org chart are all explicit, documented and easy to schedule. They are also the part of onboarding that everyone remembers to build.
A new starter finishes that programme feeling equipped, because they have completed everything that was set in front of them and nothing has yet gone wrong.
What they have acquired is the part of the job that could be written down, which in most roles is a small fraction of what the job requires.
The difficult material is informal and undocumented
Knowing which decisions are actually reversible, whose approval is real, and which parts of the codebase or the client list are fragile is not written anywhere.
In an office this transfers through overheard conversation and casual proximity, at no scheduled cost to anyone. Remotely there is no equivalent ambient channel.
So the second month is when the new hire begins hitting questions that the documentation cannot answer and that they do not yet know how to ask.
Support is withdrawn exactly when it becomes necessary
Buddy schemes, daily check-ins and structured introductions are usually scoped to the first two weeks, because that is when a new person visibly needs help.
By week five the new hire looks settled, so the scaffolding comes down. Their questions at that point are harder and less obviously legitimate to ask.
Many hires respond by guessing rather than asking, which produces work that has to be redone and a growing reluctance to raise the next question.
Nobody observes the struggle
A colocated manager notices a new person sitting still, looking uncertain or asking the desk next to them. None of those signals exist remotely.
What the manager sees instead is output, which lags the difficulty by several weeks. By the time the output is visibly weak the pattern is established.
This delay is why remote onboarding problems frequently surface as a performance concern in month three rather than as a support gap in month two.
Extending the scaffolding is the cheap intervention
Keeping a named person available through the first full quarter, with a standing slot rather than an open invitation, removes the need for the new hire to judge whether asking is acceptable.
Pairing them on real work during that period transfers the informal material directly, because the tacit knowledge surfaces at the moment it is being used.
The cost is a few hours a week from one experienced person, set against the cost of a hire who takes twice as long to become useful.