A desk booking policy decides whether an activity-based office actually runs the way it was designed to, or slowly drifts back into people camping at the same desk every day. Pune and Mumbai offices that skip the policy and only buy the booking software tend to see one of two failures: desks that look booked but sit empty, or a scramble every Monday morning because everyone tried to book the same row.
The fix is not a better app. It is a short, specific policy that the booking tool then enforces. Most successful activity-based offices get this down to one page that anyone can read in two minutes.
Why the policy matters more than the app
Booking platforms are largely interchangeable on features: a calendar view, a floor map, a mobile app, some analytics. What differs between offices that succeed and offices that quietly abandon the system within six months is whether anyone decided, in writing, how far in advance people can book, what happens to a no-show, and whether teams get priority over their usual neighbourhood.
Skip that decision and the informal rules people invent themselves. Squatting, blocking desks for absent colleagues, booking a whole row and cancelling later. Fill the gap, usually badly.
The core rules a working policy needs
A workable policy answers a short list of questions plainly, in language anyone on the floor can follow without asking facilities.
| Policy question | Typical answer that works |
|---|---|
| How far ahead can I book? | 7 to 14 days, not open-ended |
| Can I book the same desk every day? | No, or only for a defined accessibility need |
| What happens if I don't show up? | Desk auto-releases after 15 to 30 minutes |
| Can I book for a colleague? | Only for approved visitor or onboarding cases |
| Do teams get a home zone? | Yes, a neighbourhood, not fixed seats |
Booking windows and advance-booking limits
A two-week booking window is the most common working range in Pune and Mumbai activity-based offices. Long enough that people can plan around client visits and in-office collaboration days, short enough that desks don't get locked up months in advance by whoever books first.
Same-day booking should stay open right up to arrival, since a meaningful share of desk use is still walk-in on any given day. A policy that only allows advance booking and blocks same-day booking frustrates the exact flexibility activity-based working is meant to deliver.
Handling no-shows without punishing people
No-show handling is where policies tend to over-engineer. The goal is simply to release a booked desk back into the pool if nobody checks in, not to track and penalise individuals. An automatic release window of 15 to 30 minutes after the booked start time, tied to a badge tap or app check-in, does this without needing a manager to chase anyone.
Avoid building a "three strikes" disciplinary system around no-shows. It adds friction for a problem that auto-release already solves, and it tends to make people over-book "just in case," which defeats the purpose.
Team zones versus free-for-all booking
Pure free-for-all booking, where any desk in the building is fair game for anyone, looks flexible on paper but tends to scatter teams across the floor and undercut the informal collaboration activity-based working is supposed to protect. Most offices land on a hybrid: a defined neighbourhood per team where bookings are prioritised for that team, with a smaller pool of genuinely open desks for cross-team work, quiet focus, or visiting colleagues from another office.
This is a workplace strategy decision as much as a booking-tool setting, because it depends on how the team adjacency and zoning were planned during design, not just what the software allows.
Visitor and cross-office desks
Multi-city organisations with both a Pune and a Mumbai office need a small, clearly signed pool of visitor desks that colleagues from the other city, or external guests working on-site for the day, can book without needing a host to release a desk manually. Two to four desks per 50 headcount is a reasonable starting allocation, reviewed against actual cross-office travel patterns after the first quarter.
Getting the policy live
Write the policy in one page, pilot it with one floor or one team for two to three weeks, and adjust the booking window and no-show timing based on real usage before rolling it out building-wide. A policy that is right on paper but never tested against a real Monday morning is guessing.
Frequently asked questions
Seven to fourteen days works for most Pune and Mumbai offices. Long enough to plan around client visits, short enough that desks are not locked up for months by early bookers.
A hybrid works best in practice: a home neighbourhood per team for priority booking, plus a smaller open pool for cross-team work and visitors. Pure free-for-all tends to scatter teams and hurt collaboration.
Auto-release the desk back into the pool 15 to 30 minutes after the booked start time, tied to a badge tap or app check-in. This avoids a disciplinary system while keeping utilisation honest.
Two to four desks per 50 headcount is a reasonable starting point for staff visiting from another office or external guests, reviewed after a quarter of real usage data.