Open a workbook someone has lived in for three years and you can read their working life in the tab bar: Sheet1, Sheet1 (2), FINAL, FINAL new, dont use, and a mysterious xx. Nothing in it is wrong, exactly — but nobody, including the author, knows where anything lives. Workbook organisation is the grid mindset one level up: a file, like a sheet, has an architecture, and the habits cost nothing at the start and everything when skipped.

One sheet, one job

The organising rule of the whole course, applied to tabs: each sheet does one kind of thing. The mature shape, which you’ve met as the dashboard’s three layers, generalises to any workbook:

  • Inputs — the named settings a human might change, in one place, labelled.
  • Data — one Table per sheet, nothing else on it. Data sheets are warehouses, not workshops.
  • Calc — the working layer: lookups, summaries, staging.
  • Output — what people see: the report, the print-ready page, the chart sheet.

A small model might merge Calc and Output; a personal tracker might be two tabs. The rule isn’t “four sheets” — it’s that when you add something, there’s an obviously right tab for it, and when a colleague opens the file, the tab names are the documentation.

Tab hygiene: thirty seconds each, permanent payoff

Name every sheet the moment it exists (double-click the tab) — Orders, Inputs, Monthly Report, never Sheet7. Short, because tab space is precious; specific, because Data2 is a promise of future confusion. Colour with meaning (right-click → Tab Colour): one scheme, used sparingly — say, green for inputs, grey for reference, red for do-not-touch. Four colours with rules beat eight colours with vibes — the highlighting principle again. Order tabs left-to-right as a reader would want them: outputs first, machinery behind. And hide the plumbing (right-click → Hide) — staging sheets and reference tables confuse more than they inform. (Hiding is tidiness, not security — anyone can unhide.)

the archaeology Sheet1 Sheet1 (2) FINAL FINAL new dont use xx the architecture Report Inputs Orders Customers Calc reader first, machinery behind — the tab bar becomes the documentation
Same file, reorganised. The second tab bar answers "where does X live?" before anyone asks — which is the entire job of structure.

Linking between sheets (and between workbooks)

Cross-sheet references are ordinary references wearing a prefix — =Orders!B2, or better, =SUM(Orders[Amount]), which doesn’t care what sheet the Table lives on. Point-and-click builds them: start the formula, click the other tab, click the cell. Two habits keep them healthy: flow one way — outputs read from calc, calc reads from data; the moment sheets read from each other you’ve built circular spaghetti that the auditing arrows will one day have to untangle. And links between separate workbooks are a last resort — they break silently when files move or get renamed, and the honest alternative for feeding one workbook from another is a query, which declares its source and refreshes on purpose.

Navigation, for when the file grows anyway: right-click the tab navigation arrows for the jump-to-sheet list; Ctrl+PgUp/PgDn to walk tabs; and for genuinely big workbooks, a first-tab index of links (Insert → Link → Place in This Document) costs five minutes and reads as professionalism forever.

One job per sheet, names that document, flow in one direction. Structure is the cheapest feature you’ll ever add to a file — and like every foundation on the path, it was never about tidiness. It’s about the next person — who is usually you, later, in a hurry.