Setting up a persistent virtual office takes less time than most teams expect and more thought than most teams give it. The software part is minutes. The part that decides whether people log in on day two is the floor plan, the norms and the first meeting, and those are what this guide schedules across a single working day.
The plan below assumes a team of five to twenty-five people and a coordinator with a free day. Larger teams should run it for one department first. If you want the reasoning behind why a persistent office rather than more meeting links, start with what a virtual office is and come back.
Before the day starts, have three things ready: a list of everyone who will be invited with their department, a rough idea of who should be able to manage rooms and invite people (usually the coordinator plus one person per department), and a slot in everyone's calendar late in the afternoon for the first meeting. Nothing else needs preparing; the office itself is created in the first ten minutes.
Morning: decide the floor plan
The temptation is to open the tool and start clicking. Resist it for an hour and sketch the office on paper first, because the floor plan is a statement about how the team works and it is much easier to change on paper.
A persistent office is built from six room types, and a good first office uses all of them at least once.
Reception. Where people arrive and where guests wait. One is enough. It is also the room a new hire sees first, so give it a sensible name and, if you brand the office, make sure the branding is on.
Open floor. The default working room. Being here with an available status means "you can talk to me". Small teams need one; teams with distinct departments want one per department so that being in the marketing room says something.
Focus rooms. Small rooms for uninterrupted work. Plan for roughly one per two or three people who do deep work. The norm that goes with them, nobody knocks, is written down in the afternoon.
Meeting rooms. For instant and scheduled meetings. Two is a good start: one for the team's standing meetings, one for ad-hoc conversations that outgrow the open floor.
Client suites. For external guests. Even if you are not hosting clients yet, create one, because the moment you need it you will not want to be designing it. Guest links that open into it are available from the Team plan.
Break room. The room with no purpose. It is the single most important room for a remote team's culture and the one most often left out. Create it.
Now count rooms against your plan. The Free plan allows 1 office with 7 rooms, which fits a compact layout: reception, open floor, two focus rooms, meeting room, client suite, break room. The Team plan allows 3 offices and 20 rooms; the Business plan 10 and 80. If your paper plan has more rooms than your plan allows, merge focus rooms first, then meeting rooms. Never cut the break room.
Before lunch, create the office and the rooms exactly as sketched. On KioskMate the onboarding wizard offers templates for common layouts, which you can use as a starting point and edit, or you can build the rooms from the office manager one at a time. Either way the whole step takes about fifteen minutes once the sketch is done.
Midday: departments, roles and invitations
With rooms in place, decide who is who.
Departments. Create the departments that match your open-floor rooms. Departments are what make the people directory navigable and let a newcomer see that the four people in the design room are, in fact, the design team.
Roles. Keep it simple on day one: a small number of admins who can change the office, managers who can create rooms and invite people, and members who work. Resist the urge to make everyone an admin because it is easier; the audit trail is only useful if changes come from a few accounts.
Invitations. Check the people limit before you send anything: 8 on Free, 25 on Team, 100 on Business. Then send every invitation in one batch with a two-line note that says when the office opens (this afternoon) and what the first meeting is (see below). Staggered invitations produce a half-empty office, and a half-empty office teaches people that nobody is there.
If you are onboarding new hires alongside the rollout, seat them explicitly; the remote onboarding guide covers what they need on day one.
Afternoon: norms, status and the first meeting
This is the part that decides adoption. Do not skip it because the software is done.
Write the norms on one page. Four rules are enough for day one:
- Keep the office open in a tab while you are working. Let your status expire by itself when you stop.
- Available on an open floor means anyone can walk over and talk. No message first.
- Focus rooms and do-not-disturb are not interrupted, for any reason short of an outage.
- Standing meetings happen in the meeting room, not on a meeting link. Arrive early if you like.
Pin this where the team will see it. The etiquette guide has a longer template if you want one, but four rules on day one beats twelve.
Set the status example. Ask managers to spend the afternoon on the open floor with an honest status and a short status message. People copy what they see; if the leads are all in focus rooms with do-not-disturb, the team will follow.
Hold the first meeting in the meeting room. Schedule it for late afternoon with an agenda and every member as an invitee, and export the .ics so it lands in calendars. The agenda is short: here is the floor plan and why, here are the four rules, here is where we meet every week from now on. Fifteen minutes. The point is that everyone has been in the office once, together, and knows where the meeting room is. Meeting length is capped at 30 minutes on the Free plan and 4 hours on Team, which is far more than this needs.
Branding and the details that bring people back on day two
A few small things make the difference between an office people use and one they were told to use.
Branding. Put the company name, logo and colour on the office. It sounds cosmetic. It is the difference between "the tool" and "our office" in how people talk about it.
Room names that mean something. "Focus room 2" is fine; "The quiet car" is better if that is how your team talks. Meeting rooms named after the meetings that happen in them ("Monday planning") tell newcomers the rhythm without a handbook.
A reason to open the tab tomorrow. The first standing meeting of the week should be in the office. If tomorrow is a normal day, ask one manager to take their coffee in the break room at a fixed time and let people find them.
Integrations, later. Calendar export is built in; deeper integrations can wait until the team has used the office for a fortnight and knows what it wants.
Week one review: rename, merge, remove
After five working days, spend thirty minutes on three questions.
What should be renamed? Rooms that people refer to by a different name than the one on the door should be renamed to match. Departments that nobody uses should be folded into the ones people do.
What should be merged? If two focus rooms are always empty and one is always full, you have too many. If two departments always sit together, consider one open floor for both.
What should be removed? Anything that has not been entered in five days, except the client suite and the break room. The client suite will be needed; the break room needs a nudge, not a removal.
Then look at the board at three points in the day and ask whether it tells the truth about who is around. If it does, the office is working. If it does not, the problem is almost always rule one, and the fix is a reminder rather than a redesign.
All of this fits inside the Free plan for a team of up to 8. Open the office, sketch the floor plan, and start the clock.
