Skip to main content
Every workspace accumulates a mess of tags, categories, folders, and labels that mean almost the same thing and never line up. TorchRunner replaces all of that with one system: Areas. An Area is a unit of meaning in your practice. A client. A domain like “cash management” or “vendor risk.” A theme that cuts across engagements. Anything in the workspace, a task, a note, a document, an email, a contact, can be linked to one or more Areas through a single connecting layer.

​
Why one spine

Fragmented taxonomy is quietly expensive. Two labels that mean the same thing split your view in half. A folder structure that made sense in month one fights you by month six. Every new record type that invents its own categories adds another dialect you have to translate. Areas is the single dialect. One way to say what something is about, applied uniformly, so a query about “everything touching Acme’s renewal” returns the tasks, the notes, the documents, and the threads, because they all speak the same labeling language.

​
How linking works

Links are many-to-many and they go both directions. A document can belong to one client and one domain at once. A task surfaced under “vendor risk” also surfaces under the specific engagement it touches. You are not choosing one home for a record and losing the other connections.
Areas is the backbone the rest of the product hangs from. It is why a search or a roll-up in TorchRunner returns a complete picture instead of whatever happened to be filed in one place.