Remote Onboarding: How to Make New Hires Feel Present

The first week of a remote job is a strange kind of quiet. Your laptop arrives, your accounts work, your calendar fills with introductions, and between the introductions there is nothing: no desk neighbour to ask a small question, no sense of who is around, no way to tell whether the silence in the chat app means everyone is heads-down or everyone has gone to lunch.

Most remote onboarding guides focus on paperwork and tooling. Those matter, but they are not what new hires remember. They remember whether they felt present, whether they could see the team and be seen by it. This guide is about the first thirty days from that angle, with a checklist at the end.

The first-week problem

In an office, a new hire absorbs an enormous amount without anyone teaching it. Who sits with whom. Who arrives early. Which manager has an open door and which one you book. Where the coffee is and who else is usually there. All of it comes free from being in the space.

Remotely, none of it arrives on its own, and two problems follow. The first is that new hires do not know who is around. They have a list of names and a directory of faces, but no live sense of who is working right now and who could be interrupted. The second is that they do not know who to ask. Every question feels like it might be going to the wrong person, so it gets saved up for the next scheduled check-in, and the check-in becomes a list of small blockers that should each have taken two minutes on the day they arose.

The fix for both is the same: give the new hire a place, not just a schedule.

Before day one: reception, seating and a buddy

Three things should be true before the new hire logs in for the first time.

There is a reception desk. A persistent office has a reception room for a reason: it is where people arrive. Have the new hire land there, and have a real person (their manager or buddy) waiting. That first minute sets the tone. Arriving into an empty space and hunting for the right channel sets the opposite tone. Reception is also where guests and interview candidates arrive, so it is worth keeping tidy anyway.

Their team has a visible home. Set up the office so departments are legible: engineering works from these rooms, sales from those, design over there. Seat the new hire in their team's open floor from the start. Simply seeing that four colleagues are in the same room, two of them available, changes the calculation on every small question.

They have a named buddy who is not their manager. The buddy's job is to be interruptible for the first two weeks. Ask the buddy to keep their status honest, sit in the same room as the new hire and expect drop-ins. A buddy who is always in a focus room is not a buddy.

If you are setting the office up from scratch for this, our guide to setting up a persistent virtual office in a day walks through the floor plan.

Days 1 to 5: a schedule built on drop-ins

The standard remote onboarding week is back-to-back calls: HR, IT, each team lead, each system walkthrough. New hires end it exhausted and no more connected than when they started, because every conversation had a purpose and none of it was theirs.

Re-shape the week around drop-ins instead.

Monday. Arrival at reception, a short welcome, then an hour with the buddy in the team's room. Not a walkthrough: a working hour where the buddy does their own job and the new hire watches who comes and goes. Afternoon: the mandatory account and security setup, done in a meeting room with someone present to answer questions.

Tuesday. Two short scheduled introductions, then a standing instruction: for the rest of the day, if anyone on the team is available on the open floor, walk over and ask them what they are working on. The team knows to expect it.

Wednesday. The new hire attends the team's regular meeting in the team's meeting room, arriving ten minutes early. The minutes before a meeting are where a lot of belonging happens; in a persistent room they happen naturally, on a meeting link they do not exist.

Thursday. A first real task, small and finishable, worked on from the open floor with the buddy nearby. The point is to have a reason to ask two or three questions and discover that asking is easy.

Friday. Break room lunch with whoever is there, and a fifteen-minute check-in with the manager that asks one question: who have you not talked to yet that you think you should have?

Notice that the number of scheduled calls is about a third of the usual week. The rest is presence.

Weeks 2 to 4: status, focus rooms and rhythm

Once the new hire knows the floor, three habits carry them through the first month.

Status messages. Encourage a short status message that says what they are on: "reading the billing service" or "drafting the launch email". It is a low-cost way for colleagues to spot when a newcomer is working on something they know about and wander over. Veterans rarely bother with status messages; for new hires they are a conversation magnet.

Focus rooms, used correctly. New hires often feel they should be visible all the time. Tell them explicitly that focus rooms are for everyone, that using one is not hiding, and that the team's norm is that nobody knocks on a focus room door. Then also tell them the flip side: when they come out, they come back to the open floor, not to offline.

Learning the rhythm. By week three the new hire should be able to say when the team tends to be around, when the break room fills up, and who prefers a drop-in over a message. This knowledge is what an office used to supply automatically. A persistent office supplies it again, provided the new hire spends time on the floor rather than in scheduled calls.

Roles and permissions, briefly

Give new hires the least access they need on day one and add to it deliberately. Most teams onboard people as members and promote them later; managers get a role that lets them create rooms and invite others. Keep an eye on the plan's people limit as you invite: the Free plan seats 8, the Team plan 25 and the Business plan 100, so a hiring burst sometimes needs a plan change before the invitations go out. Our FAQ covers roles and invitations if you want the specifics.

The 20-point remote onboarding checklist

Copy this into your handbook and tick it off per hire.

Before day one

1. Accounts created and tested by someone other than IT.
2. New hire invited to the office and seated in their team's room.
3. Buddy named, briefed and asked to be interruptible for two weeks.
4. Manager or buddy scheduled to be waiting at reception on Monday morning.
5. Team told when the new hire starts and asked to keep status honest that week.

Week one

1. Welcome at reception by a real person.
2. One working hour beside the buddy, no agenda.
3. Mandatory setup done with someone present, not from a document.
4. Standing permission to approach anyone who is available on the open floor.
5. Attends the team's regular meeting in the team's room, arriving early.
6. First small, finishable task, worked from the open floor.
7. Friday check-in: who have you not talked to yet?

Weeks two to four

1. Status message habit introduced.
2. Focus-room norms explained explicitly, in both directions.
3. Introduced to one adjacent team by walking into their room, not by a call.
4. Has been in the break room with colleagues at least three times.
5. Knows the team's daily rhythm and can describe it.
6. Has run one small meeting in a meeting room, with agenda and invitees.
7. Manager check-in at day 30 with the same question as day 5.
8. Buddy relationship formally ended, with an explicit "you can still drop in".

The items that matter most are the ones about place: 2, 6, 7, 9, 10, 15 and 16. Get those right and the paperwork looks after itself.