# Office seating chart

Seating charts are useful for exactly as long as they are accurate, which is why the ability to edit one in place matters more than how it looks.

Build it on top of the floor plan rather than as a separate diagram, and each desk can carry a name.

---

## When to reach for one

* Office moves, where the plan is the negotiation.
* Helping new joiners and visitors find people.
* Capacity planning: how many desks, and how many people.

---

## How to draw it in Capable

| **Route**  | **Use when**                                      |
| ---------- | ------------------------------------------------- |
| draw.io    | Desks as shapes on the floor plan, each labelled. |
| Excalidraw | A quick temporary layout for a specific week.     |

---

## A few things that catch people out

* Update it when people move, or take it down. A wrong seating chart is worse than none.
* Name desks as well as people, so you can refer to a desk that is currently empty.
* Consider what belongs on an internal page: a public site is not the place for a seating chart.

---

## Related

[WireframeLayout before visual design, on the page with the spec.](https://help.gocapable.com/diagrams/wireframe.html)

[Mobile app wireframeDevice frames, navigation and touch targets.](https://help.gocapable.com/diagrams/mobile-app-wireframe.html)

[ExamplesWorking diagrams you can copy.](https://help.gocapable.com/diagrams/examples.html)

---

_Fidelity is a choice, so choose it._