Excel vs a Real Kanban Board for Managing Drawing Deliverables

Somewhere in your office right now is a spreadsheet called something like Drawing_Tracker_Rev12_FINAL_updated.xlsx. Every deliverable is a row; the columns hold number, title, owner, status, due date; conditional formatting turns overdue rows an accusatory red. It is the most universal project management system in the AEC world, nobody ever chose it, and it half-works — which is precisely why it survives.

This article takes the spreadsheet seriously instead of sneering at it: what the grid genuinely does better, what it structurally cannot do, and why the difference matters specifically for deliverables — work that flows through states — rather than tasks in general.

What the spreadsheet genuinely does better

Credit first, because it's real:

It's the register. A drawing list should be a table — sortable, filterable, exhaustive, matching the transmittals. As the authoritative record of what deliverables exist, the grid is the right shape and nothing beats it.

Bulk operations and arithmetic. Fifty rows re-dated, statuses counted, percent-complete computed, register exported for an appendix — grids eat this. Boards don't.

Zero training. Everyone already speaks spreadsheet. Never discount this.

If your tracker's job is record-keeping — an inventory of deliverables and their attributes — the spreadsheet isn't a compromise; it's correct.

What the grid structurally cannot show

The trouble starts because a drawing tracker gets asked a second job: managing flow — work moving through drafting, checking, revision, issue. And here three failures aren't Excel skill problems; they're properties of rows:

A status cell has no depth. "In Checking" reads identically whether the drawing entered checking this morning or three weeks ago — the cell shows state, never time in state, and time-in-state is where every bottleneck announces itself. The board's version is physical: cards pile up in a column, and a fat Checking column is visible across the room. Getting the same signal from a grid requires date-stamping every transition and building an aging report — which is to say, building a worse Kanban board out of formulas.

Rows don't queue. A column of cards has order — what's next is the card on top, argued about once, at the Monday walk-through. A filtered grid has sort order, which is not the same thing as an agreed sequence, and so the real prioritisation happens outside the tracker, verbally, repeatedly.

A grid has no limits. The single most valuable Kanban mechanism — capping work-in-progress so that checking capacity, the studio's true constraint, sets the pace — has no grid equivalent at all. Nothing about a spreadsheet pushes back when the office starts fifteen drawings while five sit unchecked; the red cells just accumulate. A WIP-limited column refuses, and that refusal is the management.

Underneath all three is the same root: a spreadsheet is a data structure; a board is a behavioural device. The grid records what happened. The board changes what happens next — what gets pulled, what gets finished before what gets started, where help goes today. Offices that "manage from the tracker" are mostly managing from the conversations around the tracker; the board moves those conversations into the artifact itself.

The honest answer: both, with a division of labour

The mature setup isn't board-replaces-spreadsheet — it's each doing the job it's shaped for:

The spreadsheet keeps the register. The complete, sortable inventory of deliverables — numbers, titles, revisions, transmittal history. The record.

The board runs the live flow. The subset of deliverables currently moving — through Drafting → Internal Check → Revisions → Ready to Issue → Issued — with one WIP limit on checking and a fifteen-minute Monday walk-through, right to left. The behaviour. (Our full studio setup — columns, card rules, the weekly rhythm — is in running a small design studio on a Kanban board.)

Taskboard is built to be the second half of that pair without the usual SaaS toll: browser-based, free, no accounts to create — and it saves the whole board as a JSON file, which for a spreadsheet-culture office is the decisive feature. The board lives in the project folder next to the tracker, versioned and backed up under the same discipline; snapshot it at each reporting date and you hold the dated flow-record grids can't produce. Plus the view the grid really can't do: the same cards on a Gantt timeline, showing next month's submission pile-up while it's still avoidable.

Pro tip: Migrate by subtraction, not replacement. Keep the spreadsheet exactly as it is; put only the currently active deliverables on the board — usually 15–30 cards, one afternoon's setup. Then delete the status column's conditional formatting from the spreadsheet. That small vandalism matters: it moves the "what's happening?" question to the board (which answers it) and leaves the register doing registry. Offices that run both in parallel with duplicate status columns end up maintaining two trackers badly.

Try the other half of the pair

The register you have is fine. Give the flow a tool shaped like flow — fifteen minutes to set up your live drawings as cards, no login, nothing to procure:

Open Taskboard → — free, Kanban + Gantt, and the board stays in a file you control, right next to the spreadsheet it just relieved.