Neighbourhood (in ABW)
In Activity-Based Working, a neighbourhood is a loosely defined zone of the floor plate that is home territory for a specific team or business unit. Neighbourhoods solve the belonging problem of pure hot-desking: even though no desk is permanently assigned, employees from a team are expected to locate within their neighbourhood, which typically includes a mix of open desks, a collaboration table, a phone pod, and team storage.
Neighbourhoods are typically sized for 15–30 people and differentiated through subtle design cues. Colour accents, dedicated storage, team name on a low-height panel. Rather than hard partitions. In a well-designed ABW floor for a 300-person Pune GCC, six to eight neighbourhoods might be distributed across the floor, with shared amenity spaces in the centre or at the core.
Related terms
Learn more
Activity-Based Working: Why Static Desks Are Obsolete
How Neighbourhood (in ABW) fits into an office project
Neighbourhood (in ABW) matters when a workplace moves from a broad design idea to a coordinated brief. The team should define what the term means for this project, where it appears in the drawings or specifications, and who approves it. That prevents a familiar word from hiding a gap in scope, procurement, installation, or handover.
Questions to settle early
- What outcome should Neighbourhood (in ABW) support for the people using the workplace?
- Which drawings, schedules, samples, or calculations will confirm the requirement?
- What needs to be coordinated with architecture, interiors, MEP, technology, or building management?
What to record in the project brief
Record the selected approach, responsible owner, approval point, relevant exclusions, and the evidence required at installation or handover. If the requirement affects cost, lead time, maintenance, safety, comfort, or future flexibility, state that connection plainly. The definition is a starting point. The project brief turns it into a checkable decision.
A practical checklist for Neighbourhood (in ABW)
When Neighbourhood (in ABW) appears in a workplace brief, avoid treating it as a standalone line item. Connect the requirement to the people, spaces, services, and operating routines it is meant to support. A short definition is useful for orientation. A good brief also explains the project context, the expected performance, and the evidence needed before approval.
Before design sign-off
Confirm the existing site condition and any landlord or building-management rules that affect the decision. Mark the requirement on the relevant plans and schedules. Check interfaces with adjacent trades, access for installation, maintenance access, replacement cycles, and the effect on the programme. If alternatives are possible, compare them on whole-life suitability rather than headline purchase price alone.
At procurement and handover
Keep the approved specification, supplier information, samples or calculations, and agreed exclusions together with the project record. At handover, verify that the installed result matches the approved design and that the client receives the information needed to operate and maintain it. This makes Neighbourhood (in ABW) a useful control in delivery, not just a glossary phrase.
For a project-specific discussion, start with the Vektor Spaces services, review the delivery process, and bring the relevant questions to a project enquiry.
Get a fixed-price estimate from Vektor Spaces. Design, build, and handover in one contract.
Get a fixed-price estimate →