"Review documents for order 12345."
That's a task, in most tools.
Then you spend four minutes across three tabs working out what order 12345 actually is.
Most of the fulfillment here runs without anyone watching it. The board exists for the rest — the exceptions, the approvals, the one package that needs a human to look at before it goes out. Everything else, the machine keeps.
Three ways to look at the same pile:
→ Kanban — columns you drag cards between
→ Table — sortable, paginated, overdue in red, due-soon in orange
→ Timeline — a horizontal calendar that zooms across 14, 28 or 60 days
Each task carries a status, a priority, a type, an effort size, and a due date that says "Today" or "2d" instead of making you do date arithmetic. Plus an assignee from the employee directory, a reporter, and color labels.
So far, so ordinary. Here's the part that isn't.A task links to the actual business it's about. Eleven-plus record types: orders, associations, products, forms, flows, letters, owners, units, work orders, violations, invoices.
And every link renders live context onto the card. A task about a violation shows the fine amount, the unit and the owner. Right there, without leaving it.
Threaded comments with @mentions. Attachments on the task and on individual comments.
And the workflows run the board themselves — five steps: create a task, update one, change its status, find one, add a comment.
So when a package hits a review gate, the task is already on the board, already pointing at the order that caused it. Approval steps go further: one task per approver, created automatically.
The generic-board version of this is a card called "Estoppel — Maple St???" under a comment thread that reads, in full: "which one" / "the other one".
Work that arrives with its context attached is work that gets done.Next: how the platform gets a human's attention without becoming one more thing that emails you.