Stacking & Blocking

Stacking is the decision of which functions occupy which floors in a multi-level building. It is usually the first spatial move after the area schedule, and it is done with a stacking diagram - a simple vertical bar chart of the building, one band per floor, each band coloured and labelled with the department or use assigned to it, with headcounts and areas noted. The diagram in this lesson shows the idea: public and shared functions low, working floors in the middle, quieter or leadership functions high, and a vertical connection running through.

Several forces pull on a stack at once, and good stacking is the art of balancing them. Floor area and fit come first - a department of sixty people cannot go on a floor that holds forty, so you tessellate teams against floor plates, sometimes splitting a large team across floors or combining small ones. Ground-floor logic matters: reception, security, the cafe and anything the public or visitors reach belongs low and near the entrance, while functions that need no footfall can go high. Adjacency between floors is central - teams that work together should be stacked on adjacent levels so a stair connects them, not divided by many floors. And special needs override convenience: a function with heavy floor loading, a data centre, a double-height studio or a client-facing floor may be fixed to a particular level by the building itself.

Stacking is also where you spend the building's best assets deliberately. The floors with the finest views, the roof terrace, the double-height volume or the most daylight are limited and valuable; deciding whether they go to leadership, to the staff cafe and social heart, or to the teams who most need daylight is a real cultural choice, not a neutral one. Many modern organisations deliberately put the shared, social 'heart' on a prime floor rather than reserving the penthouse for executives - a decision that says something about the organisation and that stacking is the moment to make. Throughout, remember that the stack must also satisfy egress and occupant-load logic floor by floor; those limits are verified with the code and the life-safety specialist, not assumed.

Once a floor's occupants are decided, blocking arranges them across it. A blocking diagram divides the floor plate into zones - blocks - for each team, function or setting, placed in relation to the core, the windows and the circulation. It is still coarse: you are working with areas and relationships, not individual desks, deciding that sales sits along the north windows, engineering takes the deep west end, meeting rooms cluster by the lift lobby, and the social space anchors a corner with a view. The fine layout of furniture comes later; blocking sets the zones it will fill. The diagram shows a single floor blocked around its core.

The logic of blocking turns on a few reliable principles. The core and perimeter have opposite characters: the zone around the building core is deep, daylight-poor and naturally suited to things that do not need windows - copy and store, internal meeting rooms, server and support rooms, some circulation - while the perimeter carries the daylight and views and should generally go to the spaces where people spend the most time, or to shared settings everyone can enjoy. Spending precious window-line on enclosed manager offices while the open floor sits in gloom is one of the most common and most regretted blocking mistakes. Arrival and sequence matter too: what you meet as you step off the lift - a welcoming social zone, or a wall of meeting-room doors, or a dead corridor - sets the tone of the floor.

Blocking is also where acoustic and activity zoning begins (developed in Lesson 2.3 and Module 4). Loud, busy functions - a buzzing sales team, a collaboration zone, the pantry - should be blocked away from those needing quiet, so the floor has a gradient rather than a collision. And blocking must keep circulation honest: a clear primary route that reaches every block without forcing people to cut through teams that need calm. A good blocking diagram can be read in seconds - you can see where you would arrive, where the noise is, where the quiet is, and how you would move - and that legibility is the sign the floor will work before a single desk is drawn.

In a single-floor office, everyone shares one plane and adjacency is purely horizontal. The moment an organisation occupies more than one floor, a new and underestimated problem appears: vertical separation is felt much more strongly than horizontal distance. People will happily walk the length of a floor to a colleague but hesitate to take a lift one level up for the same conversation, because the lift introduces waiting, enclosure and a psychological break. A stack that ignores this produces floors that behave like separate companies, however well each is laid out.

The designer's job is therefore to connect the floors deliberately, and the most powerful tool is an interconnecting stair - an open, inviting feature stair (distinct from the fire stairs, which are for egress and verified with the code) that links adjacent occupied floors directly. A well-placed, generous stair, ideally near the social heart, makes two or three floors feel like one community: people use it without thinking, casual encounters happen on it, and teams stacked across it stay genuinely connected. An atrium or a void does the same at a larger scale, giving visual connection and daylight between levels and letting people sense the life of the floors above and below. Where a stair is not possible, even aligning the lift lobbies, the social spaces and the 'you-arrive-here' moments vertically helps the floors read as one place.

This is why stacking and connection must be designed together, not in sequence. If you know two teams must collaborate, you do not merely stack them on adjacent floors and hope - you stack them around a shared stair and put a common setting at its landings, so the vertical move becomes easy and even pleasant. The reach of a feature stair is limited - it comfortably binds two or three adjacent floors, not a whole tower - so in taller occupancies you plan in vertical neighbourhoods: clusters of a few floors tied by a stair and a shared amenity, with the clusters themselves arranged up the building by how much they interact. Get this right and a multi-floor office feels like one organisation; get it wrong and it feels like a filing cabinet of strangers.

An organisation is not a fixed thing, and a plan that fits it perfectly on move-in day can be strangling within two years. Teams grow and shrink, new functions appear, projects reshuffle people. Stacking and blocking are where you build in the capacity to absorb that change - and where you must resist the opposite temptation to over-build for a speculative future that may never arrive. The craft is planning honestly for the change you can foresee without paying, in money or empty floor, for change you cannot.

Several techniques help. Leave deliberate slack: rather than filling every floor to the last desk, keep a planned margin - a partly open floor, a zone held for expansion - so a growing team has somewhere to go without a disruptive reshuffle. Plan expansion adjacently: if you can foresee which teams will grow, block them next to soft, easily-reassigned space (open desks, a flexible project area) rather than boxing them between fixed walls, so they can spread sideways. Favour standardisation and a universal plan: desks, meeting rooms and settings built to a consistent kit of parts mean a team can move or grow by reassigning space rather than rebuilding it, and a floor can be re-blocked by changing labels, not demolishing partitions. This universal-plan thinking - where most of the floor is a flexible, shared field rather than bespoke fixed rooms - is one of the strongest enablers of long-term flexibility.

Flexibility also lives in the base-build: demountable partitions, a raised floor or accessible services, a regular grid and generous floor-to-floor height let a space be reconfigured cheaply for years, which is why the architect's early decisions (Lesson 2.4) matter so much to flexibility. But hold the honest balance the whole course insists on: flexibility has a cost, and infinite flexibility is a trap. Over-sized floors held empty 'for growth', or everything built demountable at a premium, waste money and can make a space feel provisional and unloved. The goal is a plan calibrated to realistic change - enough slack and standardisation to absorb the growth you can actually foresee, committed enough to feel settled and cared-for - and, as ever, calibrated to the specific organisation rather than to a generic ideal of endless adaptability.