General workspace template

Almost everything worth tracking is the same three tables underneath: the things, the people responsible for them, and what has happened to them. This template gives you exactly that shape with nothing domain-specific bolted on, so the first thing you do is rename it. Say what Items really are, tickets, applications, assets, complaints, and Ferra renames the table, the links pointing at it and the dashboard built on top in one move.

Items gives every tracked thing a row: a name, a status, a priority, a due date, free-text notes, and an owner pointing at a row in People. The sample: Replace loading bay lights, In progress, High, due 6 Mar, quote approved and waiting on parts. People holds each person who owns items, with role, team, email and an Open items formula counting what they currently carry. Activity logs one row per update against an item: the date, a type such as Decision, what actually happened, and who it was by. That last table is what keeps a status field from going amnesiac.

Tickets. Applications. Assets, complaints, maintenance requests, grant submissions. Underneath, every one is the same skeleton: a thing with a status and an owner, a person who owns things, and a history of what changed and when. The nouns differ; the shape doesn't. Start from the shape and the relationships, the formula and the dashboard already work: what's left is the one part only you can do, which is saying what these rows are.

Rename it before you do anything else. Tell Ferra what Items really are. Items becomes Maintenance requests, Owner becomes Assigned engineer everywhere it appears, and the table, the relationship columns pointing at it and the dashboard built on top all rename in a single move. No hunting down stray mentions of the old name, and the sample rows travel with the change, so nothing sits half-renamed.

Status overview splits open, in progress, done and overdue by owner and by priority, and it earns its keep before you've decided what any of this is called. It keeps earning it after: what's overdue and who owns it, how the work splits across the team right now: answered without anyone building a view first.

“What's overdue, and who owns it” is the daily one. “What changed this week” reads Activity and comes back as a list of things that happened, not a diff. The sleeper is “which items have had no activity in a month”: the question that surfaces work that has quietly stopped moving. A status column alone can't answer it, because a stale row and an active one look identical until you check their history.

Reach for this when your process is genuinely your own and none of the other thirteen templates names what you do. Skip it when a closer one exists: if what you track is deals, candidates or shipments, start from that template and describe the differences instead. Adding a table to a working workspace is a sentence. Reconciling two sets of sample data is an afternoon.

Whatever list you run now imports directly: CSV, XLSX, a connected Google Sheet, even an email forwarded in and read into a table. People goes first, so items have someone to point at. Items next. Then rename everything into your own words: doing it after the import is fine, because the change applies to the structure and the rows together.