Activity-based working fails most often not because the design is wrong, but because the timeline compresses the change-management work into a fraction of what it actually needs. A floor plan can be built in months. Getting people to actually use it the way it was designed takes longer.
This is a realistic phase-by-phase timeline, built from what actually happens on Indian office rollouts rather than a vendor's best-case slide.
Phase one: space utilisation audit (4-6 weeks)
Before any layout is drawn, a proper space utilisation audit measures how the current space is actually used, not how the org chart assumes it is used. This typically runs 4-6 weeks and covers desk occupancy sampling across different times of day and week, meeting room booking versus actual usage, and structured interviews with team leads about work patterns that a simple headcount will miss.
Skipping this phase to save time is the single most common cause of an ABW rollout that gets the desk-to-seat ratio wrong on day one.
Phase two: design, pilot zone, and stakeholder walkthrough (6-10 weeks)
Rather than designing the whole floor at once, a pilot zone, one department or one wing, lets the design get tested with real usage before the full rollout commits to it. This phase includes the zoning design itself, a physical or high-fidelity mockup of the pilot zone, and a structured walkthrough with the actual occupants who will use it, not just leadership.
| Phase | Typical duration | What gets skipped when rushed |
|---|---|---|
| Utilisation audit | 4-6 weeks | Real occupancy data, replaced by assumption |
| Design and pilot | 6-10 weeks | Real-world testing before full commitment |
| Construction and fit-out | 10-16 weeks | Rarely skipped, but often starts before design is validated |
| Change management and training | 8-12 weeks, overlapping construction | Compressed into a single all-hands email |
| Post-occupancy review | 8-12 weeks after move-in | Skipped entirely on most rollouts |
Phase three: construction and fit-out (10-16 weeks)
This phase follows the standard turnkey design-build delivery timeline, but ABW-specific elements, booking system integration, locker allocation, and the technology behind hot-desking, need their own commissioning window before move-in, not a last-minute addition during snagging.
Phase four: change management, running in parallel with construction (8-12 weeks)
This is the phase most commonly compressed to almost nothing, and it is the one change management for ABW transitions actually needs the most lead time for. Booking-system training, desk-etiquette guidelines, and clear communication about what is changing and why should run throughout construction, finishing before move-in day rather than starting on it.
Phase five: post-occupancy review (8-12 weeks after move-in)
Most rollouts stop the moment the team moves in, which means nobody ever measures whether the zoning ratios actually match real usage. A structured post-occupancy evaluation at 8-12 weeks catches desk-ratio mismatches, underused zones, and booking-system friction while they are still cheap to adjust, rather than discovering them a year later when the space feels wrong but nobody can say exactly why.
What actually happens when a phase gets compressed
Compressing the utilisation audit into a two-week desk count usually produces a desk-to-seat ratio based on headcount rather than real behaviour, which then gets discovered wrong only after move-in when either desks sit empty or people cannot find a seat during peak hours. Compressing change management into a single announcement email typically produces low adoption of the booking system in the first month, with people reverting to informal desk claiming that undermines the entire ABW model. Both failures are avoidable, and both cost more in post-launch firefighting than the time saved by rushing the original phase.
Frequently asked questions
Realistically 7-10 months end to end, including the utilisation audit, design and pilot, construction, change management running in parallel, and post-occupancy review. Compressing this significantly usually means skipping the audit or the review, not actually saving time.
The utilisation audit before design starts and the post-occupancy review after move-in. Both are the easiest to skip on a tight timeline and the most likely to cause a mismatch between the design and real usage.
No. Change management should run in parallel with construction, finishing before move-in day, so people already understand booking systems and desk etiquette by the time they occupy the new space.
A pilot zone lets the design get tested with real usage and stakeholder feedback before the full rollout commits to a zoning ratio and layout that may need adjustment.