How long does it take to roll out desk booking software?

Yes, pilot one office first. In deskbird you set up and publish the pilot office while every other office stays hidden as a draft. We don't promise a standard rollout time. The setup follows a fixed order of steps, some of them need your IT team, and a few changes take hours to reach every user.

How long does it take to roll out desk booking software?

There is no standard rollout time we can promise. The setup follows a fixed order: offices, floors and spaces, floor plans, users and groups, access rules, meeting rooms, then publishing. Some steps need your IT team, and a few changes take hours to reach every user. We suggest a pilot in one office first, then expanding.

Before you start, have these ready:

• The Global Admin role in deskbird for the person doing the setup.
• Office details: the name, address and opening hours of each office.
• Floor plan images: one per floor.
• Your team structure: the departments or teams you want as groups.
• A decision on meeting rooms: synced with Microsoft 365 or Google Workspace calendars, or kept only in deskbird.

Where the software itself adds a wait:

• SAML single sign-on (User & Data Management Plus add-on): you send your identity provider's metadata to our support team. We configure the connection and confirm when it is ready.
• SCIM provisioning (same add-on): the first sync can take 1 to 2 hours.
• Microsoft Teams: pinning the deskbird app for everyone can take up to 24 hours to reach all users.

Should you pilot desk booking in one office first?

Yes. A small pilot group gets first experience with the tool, finds problems and helps fix them before everyone else starts booking. In deskbird you set up the pilot office and publish it, while other offices stay saved as drafts. Drafts stay hidden from users until you publish them.

How to set up the pilot in deskbird:

• Build the office before anyone sees it. Save the office as a draft, then add floors, areas, desks and the floor plan. When it is ready, publish the office, its floors and areas, and the floor plan. Publishing an area can't be undone.
• Limit who can book. Set the pilot office to Restricted so only selected groups can book there.
• Test as a normal user. Global Admins, Office Admins and Managers can book any area regardless of access rules. To check a restricted area, ask a colleague without an admin role to try to book it.

Pick pilot users from different teams, departments and roles. People from the pilot can later act as tool champions who answer colleagues' questions when you expand.

Planning a pilot? More than 250,000 users in 80+ countries already book with deskbird. Get a demo tailored to your offices, starting with your locations and current tools.

What does a pilot-to-full-rollout plan look like?

We suggest 3 phases: a pilot in one office, an expansion to further offices, and a full rollout to everyone. Agree success criteria before the pilot starts and plan a decision point at its end: scale, adjust or stop. The table shows what happens in each phase and who is usually involved.

Put the milestones in a calendar: training, pilot start and end, the deadline for feedback, and the decision point.

What do you need to set up in deskbird?

You need offices, floors and areas, users and groups, access rules and meeting rooms, set up in that order. Decide how people sign in and where user accounts come from first. Set both up before you invite users, so nobody creates a separate email and password account. Global Admins can follow an in-app setup checklist.

• Offices and floors. Each office needs a name, address and opening hours. Upload one floor plan image per floor (.svg recommended, .pdf, .jpg, .jpeg, .png and .webp also work, up to 15 MB) and place areas and desks in a drag-and-drop editor.
• Sign-in. Sign-in with Microsoft or Google works on every plan. SAML single sign-on is part of the User & Data Management Plus add-on.
• User accounts. Invite people by email or upload them in a CSV file. By default, colleagues with your company email domain can also register themselves. SCIM provisioning and HRIS sync are part of the User & Data Management Plus add-on.
• Meeting rooms. Decide per room whether it syncs with Microsoft 365 or Google Workspace calendars or lives only in deskbird. A room created only in deskbird can't be converted to a synced room later.
• Microsoft Teams. Your Microsoft 365 admin allows the deskbird app in the Teams admin center and can install and pin it for everyone.

Our Basic setup guide in the Help Center walks through each step in order.

What should you measure during a desk booking pilot?

Measure whether people use the tool and how the office is used. Track the adoption rate, meaning the share of pilot users who book regularly, plus desk occupancy and no-shows. Add support questions and a short survey. Agree the targets before the pilot starts, so you can judge the pilot against them at the decision point.

Combine the numbers with feedback from interviews or a short workshop with pilot users.

Who needs to be involved in a desk booking rollout?

HR and workplace managers lead the rollout together. HR focuses on the people side: communication, training and policy. The workplace manager owns the technical and organizational setup. Your IT team handles sign-in, user provisioning, calendar sync and the Teams app. Managers who book themselves motivate their teams to follow.

• Workplace or facility manager: offices, floor plans, booking rules, access rules.
• IT: sign-in method, user provisioning, meeting room calendars, Teams and Outlook.
• HR: policy, communication, training.
• Tool champions: early users in each team who help colleagues.
• Executive sponsor and managers: back the project and set the example by booking themselves.

Our free guide, 6 strategies for successfully implementing desk-sharing software, covers the role of HR and workplace managers, tool champions and managers, and how to plan the communication.

What slows a desk booking rollout down?

The most common mistakes are skipping a review of current space use, having no written booking policy, and choosing hard-to-use software. A fourth is treating launch day as the finish line. Without monitoring and adjustments, even a well-planned rollout drifts away from how teams actually work.

A few setup details also cost time if you find them late:

• Restricting an office too early. Before you restrict an office, add everyone with an assigned desk or parking spot there to an allowed group. Otherwise their assignments are removed.
• Creating rooms before deciding on calendar sync. A room created only in deskbird has to be created again to sync it later.
• Inviting users before single sign-on and provisioning are set up. People then create separate email and password accounts.

For the workplace side of the rollout, from policy to office layout, see our hot desking implementation guide. To compare tools before you start, see the best desk booking software, or see how desk booking in deskbird works.