Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Shearing Layers (Six S’s)

Concept

Vocabulary that names a phenomenon.

Read a building as layers with different rates of change, so fast work can move without damaging slower parts worth retaining.

Also known as: Six S’s; pace layers; layers of longevity; Site, Structure, Skin, Services, Space Plan, and Stuff

Frank Duffy named the timing problem. Stewart Brand made it memorable as the six S’s: Site, Structure, Skin, Services, Space Plan, and Stuff. “Shearing” is the useful word. Layers don’t age together. They rub when a fast-changing layer is trapped inside a slower one.

Understand This First

Scope

This entry describes a conceptual frame used in design, adaptation, and disassembly planning. It isn’t structural, fire-safety, code, cost, or planning advice. A qualified professional has to evaluate layer boundaries and performance duties for a specific project.

What It Is

Shearing layers are building parts grouped by expected rate of change. Brand’s six-layer version is the common shorthand:

LayerWhat it coversTypical circular question
SiteLand, access, orientation, utilities, urban settingWhat should remain available across many building lives?
StructureFoundations, frame, slabs, cores, primary load pathHow can the long-life load-bearing system avoid being damaged by shorter-life work?
SkinFaçade, roof, weathering envelope, shadingCan the envelope be repaired or replaced without gutting the building?
ServicesMEP systems, risers, distribution, controlsCan systems be reached, upgraded, isolated, and removed without structural or fit-out demolition?
Space PlanPartitions, ceilings, floor finishes, internal layoutCan the occupied plan change without attacking structure, skin, or primary services?
StuffFurniture, equipment, loose fittings, appliances, tenant goodsCan loose products return to use, repair, resale, or product stewardship instead of becoming churn waste?

The labels are a starting point, not a law. Laboratories often split services into base-building plant, lab gases, containment systems, and user equipment; housing distinguishes support, infill, finishes, and appliances.

The test is whether one layer can end its service life without forcing an earlier end on the layer behind it. A good layer strategy lets fast layers slip past slow ones. A bad one ties them together, so every change becomes a small demolition.

Why It Matters

Buildings are handed over once and changed for decades. Handover economics reward completion, not later change. Tenants move, services age, façades fail, programs shift, and loose equipment churns while structure and site should remain useful.

Shearing layers show where value is trapped. A service run cast into a slab injures the structure when it changes. A fit-out that blocks façade access captures the skin. Bonded finishes turn recoverable products into strip-out waste. The vocabulary changes the question from “is the building adaptable?” to “which layer changes, which remains, and what boundary protects both?”

The concept also explains why documentation is circular design. Layer boundaries, release routes, access, assumptions, and performance duties must outlive the first project team, or later teams rediscover the building destructively.

How to Recognize It

Look for a time map, not a diagram alone. A useful claim names each layer, its service life, its access route, and the conditions for changing it.

Strong versions usually show four things:

  • Different replacement logic for structure, envelope, services, fit-out, and contents.
  • Boundary details for fire, acoustic, waterproofing, airtightness, structural restraint, security, and maintenance access.
  • Access points and release routes for the layers expected to move first.
  • Records that tell later teams what can be touched, what must remain, and where the boundary sits.

Weak versions stop at the six labels while details still bond fast layers into slow ones or leave future teams without a safe route to change them.

How It Plays Out

In an office building, the base structure and cores may last for decades while tenant fit-outs change every five to ten years. A layer-aware project keeps partitions, ceilings, lighting, floor boxes, and data routes from being bonded to the frame. It records access to valves, dampers, fire-stopping, brackets, and cable paths.

In a façade retrofit, the skin is the pressure point. The old façade may be thermally weak, leaky, or worn out while the structure remains sound. The circular gain comes from replacing the failed layer while protecting the layers that still have decades of use.

In a school, services and space plan change faster than the frame. Teaching methods, technology, safeguarding requirements, ventilation expectations, and special-needs provision shift while the structure remains good. Accessible services and demountable partitions make that adaptation; buried services and wet-built partitions make demolition.

Older warehouse buildings often adapt because structure, skin, and space plan are loosely coupled: generous spans, high ceilings, simple envelopes, and visible services give later teams room to work. Highly integrated buildings can age badly because each system was optimized as one fixed composition. Once the first layer changes, the whole assembly fights back.

Warning

Don’t turn the six S’s into a slogan. A shearing-layer diagram has value only when the project team uses it to set access, connection, maintenance, replacement, and documentation decisions.

Consequences

Benefits

  • Helps adaptive-reuse teams decide what to retain, alter, remove, or recover.
  • Protects long-life value by keeping fast layers from damaging structure, skin, or site infrastructure.
  • Makes design for disassembly more practical because layer boundaries point to release routes.
  • Helps owners match maintenance and capital expenditure to expected layer life.
  • Improves material-passport records by tying products to their layer, change cycle, and evidence needs.

Liabilities

  • Becomes too neat when treated as a universal taxonomy rather than a project-specific model.
  • Adds coordination across architecture, structure, façade, MEP, interiors, fire, acoustics, facilities management, and procurement.
  • Conflicts with performance needs that bind layers, including compartmentation, weathering, airtightness, security, and structural restraint.
  • Produces little value when owners don’t update records after fit-outs, upgrades, and tenant work.
  • Can excuse premature replacement when teams assume fast layers should churn instead of first testing repair or maintenance.

Sources