How to pilot desk and meeting room booking in a UAE office

    IVOS Technology Solutions · Reviewed

    If colleagues travel to Dubai for a team day and still have to ask reception where to sit, start with one floor. Pick a busy day, give every available desk a name, and ask an employee at another site to reserve one before leaving. Follow that reservation through arrival, a late change and cancellation. That short exercise exposes gaps a software feature list can miss.

    This is a proposed pilot for facilities, reception and IT. The example below uses a Dubai office with visiting Abu Dhabi colleagues, 24 shared desks, two meeting rooms and a boardroom. The quantities illustrate how to run the pilot.

    Decide what employees can actually reserve

    Walk the floor with reception. Check equipment, access routes and what the sign on each door calls the space. Record a room-calendar address for each room that has one. Give desks and rooms stable names employees can match to the physical signs. When an accessible route or an adjustable-height desk matters, let employees find it in a list as well as on the floor plan.

    Space Pilot booking policy Exception to rehearse
    Shared desks Employees can reserve an individual desk before travelling. A dock fails after someone books. Reception finds and confirms a suitable alternative.
    Team neighbourhood A team can see desks in the same zone and coordinate office days. Two visiting departments arrive together and the zone fills up.
    Meeting rooms Employees can reserve a room in the calendar their team already uses. An organiser cancels just one meeting in a recurring series.
    Boardroom A named approver handles requests, with a backup during absences. Two teams request the same time before either request is approved.

    Name one person who can make a desk unavailable and one who can approve an exceptional room booking. Reception should have a way to reach both during the hours the office actually opens. Give IT the site's local time zone and actual working days, including temporary opening hours, before it configures reminders.

    Choose which booking model to test

    If policy exceptions drive the workload, try the rules in Skedda with ordinary employee accounts. For example, set a weekly training-room allowance for a team and check how the next booking behaves when the team reaches its limit. Skedda lets administrators combine restrictions on space, user group and duration with group quotas. A system administrator can bypass some booking conditions, so an administrator-only demonstration can hide what staff will experience. Skedda booking conditions · Group quotas

    If every department already books in Microsoft 365, try a desk pool and a named desk in Microsoft Places. A pool promises capacity in a zone. A named reservation promises a particular workstation. Let one visitor try both, then identify which seats genuinely need individual booking and the associated licence. Microsoft Places desks · Microsoft Places licensing

    If the real question is whether colleagues will travel on the same day, start with a shared weekly plan. Have the team pick a day together in deskbird and then reserve seats. Ask the same group to repeat the exercise when the meeting shifts. This tests whether a schedule change translates into a usable seat when people arrive. deskbird planning and booking workflow

    Run two pilot weeks

    Week one — watch the booking from end to end. Start with one frequent visitor, one local employee, one organiser and one receptionist. Book the last available desk, reserve a room, move a recurring meeting once and cancel it from the organiser's usual calendar. After each change, have a different employee inspect availability and make a new reservation. Verify the organiser, both calendars and reception agree about the same space and time. Try a keyboard-only booking and an alternative check-in method on the first day.

    Set a grace period that suits how people reach your building. Tell employees exactly when the desk will reopen and how to cancel if plans change during the commute. For a Skedda pilot, its check-in rules can initially log what would happen after a missed check-in. Compare those events with reception's observations before choosing automatic cancellation. Make sure your proposed subscription includes check-in. Skedda check-in rules

    Week two — repeat on your busiest team day. Include someone booking a desk from the other office, a team lead approving a room and a late arrival with a dead phone. Ask reception to explain the fallback in the languages your staff use. If a guest is expected, confirm who sends the building access instructions and who alerts the host. A meeting-room reservation and permission to enter the building are two separate steps.

    Count outcomes that can support a decision

    Measure How to calculate it What it tells you
    Successful travel-day reservations Visiting employees who found the suitable seat they booked ÷ visiting employees who attempted that workflow Whether someone can plan the trip with confidence
    Missed check-ins Reservations reaching the deadline without check-in ÷ reservations subject to that deadline Whether to adjust reminders, training or the grace period
    Reuse after release Automatically released reservations later booked by someone else for the overlapping time ÷ automatically released reservations Whether the release rule returns capacity people actually want
    Calendar conflicts Count of overlapping accepted reservations for one room, checked against its calendar Which integration or editing path needs investigation
    Reception interventions Count of manual moves, overrides and duplicate-booking fixes, with one reason per incident Which rules or labels need changing before rollout

    For example, six missed deadlines among 40 eligible reservations is a 15% missed-check-in rate. Ask how many of those six employees were already at their desks. A missed check-in records a booking event. A decision about removing physical desks needs a separate measure of demand and use across peak days. If no reservations were released during the pilot, record reuse as “no released bookings” and repeat during a busier period.

    Decide whether to expand

    Expand once a visiting employee can book the right seat, a calendar edit reaches both systems and reception can resolve a failed check-in or equipment fault without improvising. Keep a named owner and a retest date for each unresolved case. Reuse the pilot rules at the second site only after checking that site's calendar, opening hours and front-desk responsibilities.

    IVOS distributes Skedda in the UAE. To discuss a pilot, share an approximate desk and room count, your calendar platform, a peak office day and the rule that generates the most requests at reception. Discuss your workplace pilot with IVOS · Compare five workplace management platforms