Remote onboarding: joining a company you cannot walk into

Remote onboarding is bringing somebody into a team they will not sit with. The administrative half is the same as anywhere — accounts, equipment, paperwork, covered in employee onboarding checklist — and the half that breaks is the one nobody plans, because in an office it happens by itself.

What happens by itself is substantial: learning who is approachable, overhearing how a problem gets solved, noticing that everybody breaks a rule that turned out not to be a rule, and calibrating whether your first week was slow or normal. A remote joiner gets none of that unless somebody arranges it.

What to make explicit

• Who to ask about what, by name, with an explicit invitation to interrupt them. This is the single most valuable thing you can give a remote joiner.
• How work actually flows through the business, written down once — the artefact that pays for itself repeatedly, discussed in induction training.
• Working norms: expected response times, whether cameras are on, what gets escalated, when people are typically offline. In an office these are absorbed; remotely they are guessed at, usually wrongly and anxiously.
• What the first week and first month should look like, so they can tell whether they are behind. Without a stated expectation, most people assume they are.
• Permission to say they are stuck, given explicitly and early. Remote joiners hide confusion for far longer, because asking costs a deliberate message rather than turning a chair.

Equipment and accounts must work on day one, and remotely this is harder and matters more. In an office, a missing login is a mild irritation somebody fixes at your desk; remotely it is a person sitting alone unable to start, forming their first impression of how the company operates. Ship the hardware early and test the accounts before the start date.

The first weeks

1. A scheduled first call with the manager on day one, and one with a named buddy who is not the manager.
2. Short daily check-ins for the first week — ten minutes, not a status meeting — then twice weekly, then normal. Frequent and short beats one long weekly session.
3. Real work in the first week, small and low-risk, with the outcome reviewed. Nothing else establishes whether the person understands the job.
4. Introductions with a purpose. Meet six people because you will work with them on this, not a parade of names they will never place.
5. A written thirty-day plan they can check themselves against, which removes the low-grade anxiety of not knowing whether they are doing enough.
6. A month-three conversation asking what still confuses them — the answers are the best available critique of the process.

The isolation problem

It is real and it is not solved by virtual social events, which most people endure rather than enjoy. What works better is structural: pairing on actual work, a buddy who checks in unprompted, and small-group calls rather than large ones where a new person cannot find a gap to speak. The measure of success is not whether they attended anything; it is whether, by week three, they are asking questions in a channel without hesitating.

Where it lives

Ettex Teams holds who the person is, their team and their access, with the plan and the how-work-flows page in Ettex Docs and the day-one administration in employee onboarding checklist. The communication norms they need spelling out are the ground covered in asynchronous communication and remote work policy.

To be clear: no onboarding automation, no sequenced task assignments, no provisioning integration. Remote onboarding fails on attention rather than on tooling — the missing piece is almost always a named person whose job it was to check in.