Skip to main content

Stack View

The Capacity Stack is a new way to read an office. Alongside the spatial floor map you already use, each floor now also shows as a horizontal stack — segmented bars showing how teams fill the floor on a given day.

Written by Madeline Frank

🧭 How to Get There

  1. Open the office you want to view and go to the floorplan editor.

  2. Pick the floor you want from the floor dropdown at the top.

  3. In the top-right corner, find the Floorplan ⇄ Stack toggle (the map and stack icons).

  4. Click the Stack icon to switch from the spatial map to the Capacity Stack view.

💡 Toggle back to the map icon anytime to return to the spatial floorplan.


🎛️ Setting the View

A few controls at the top shape what the stack shows:

  • Day – pick a specific weekday, or choose Peak / Low to auto-resolve each floor's busiest or quietest day from the last month

  • Data source – base the numbers on Bookings or Check-ins

  • Capacity – toggle between Effective and Physical seats

The KPIs up top

A row of cards summarizes the whole office:

  • Physical seats – total seats from the floor plans

  • Effective capacity – seats adjusted by sharing ratios

  • Allocated headcount – people assigned, from HRIS

  • Unseated – allocated people without a seat

  • Utilization – how full the office is


🏢 Floor Rows

The panel is a list of floors. Each row shows, at a glance:

  • Floor name, neighborhood count, and seat breakdown (dedicated / shared)

  • How full it is — people placed / capacity, plus a %

  • A roll-up bar segmented by team, colored per group

👉 Click a floor to expand it into its neighborhoods.


🧩 Neighborhood Rows

When a floor is expanded, each neighborhood shows:

  • Physical seats, sharing ratio, and effective capacity

  • Placed / capacity and a % — flagged 🔴 red when over capacity

  • A bar segmented by team: dedicated seats are dotted, shared seats are solid. Any overflow is clipped at the edge with an "Over capacity by N" note.

💡 Tip: The Effective / Physical toggle changes the denominator everywhere — summaries, percentages, and bar widths all follow it. If a floor looks more or less full than you expected, check which capacity mode you're in.


🪑 Dedicated vs. Shared Seats

Think of a neighborhood as an area set aside for a team. The desks in it come in two flavors:

  • Dedicated – desks reserved for someone in particular: a named person, or a different team. That seat is theirs, so it counts as exactly one seat for one person.

  • Shared – desks that aren't reserved for anyone specific. They're the neighborhood's common pool: free desks plus desks the team simply shares among themselves. People grab them as needed.


📈 Why the difference matters

Because not everyone comes in every day, a handful of shared desks can comfortably serve a larger team across the week. That multiplier is the sharing ratio (e.g. 1.5×) — and it applies only to shared desks. Dedicated desks stay one-to-one, since they're always held for their owner.

Example: A neighborhood has 20 desks — 8 reserved for specific people (dedicated) and 12 in the shared pool. At a 1.5× ratio, it can effectively seat:

8 + (12 × 1.5) = 26 people over a typical week.

That's the difference between physical capacity (20) and effective capacity (26).


📋 Quick Reference

Term

What it means

Capacity Stack

Horizontal, team-segmented view of how floors fill up, next to the floorplan

Peak / Low

Auto-resolves each floor's busiest / quietest day from the last month

Dedicated seat

Reserved for a specific person or team; counts 1:1

Shared seat

Common pool; multiplied by the sharing ratio

Sharing ratio

Multiplier applied to shared desks only (e.g. 1.5×)

Effective capacity

Dedicated + (shared × ratio)

Physical seats

Raw desk count from the floor plan

Over capacity

More people placed than capacity allows; flagged red with an "Over capacity by N" note


🎥 Video Walkthrough

Coming soon!


❓ Need More Help?

  • 💬 Use the chat bubble in the bottom-right corner of your screen to contact Support

  • 📧 Or email us anytime at support@gable.to

Did this answer your question?