The Workflow task tracker

The Workflow task tracker is a shared board of tasks that humans and bots work from together, one row per piece of work, visible to the whole team. It looks like a familiar spreadsheet of tasks, and that is the point: everyone, person or agent, reads and updates the same simple record.

Most teams scatter their work across a project tool for people and a set of hidden queues for their automations. The Workflow tab collapses that into one place. When agents are coworkers, they need to stand in the same line as everyone else, and this board is that line.

One task, an owner, and tags

Every task on the board has an owner, the single person or agent responsible for moving it forward. Beyond the owner, a task can tag other coworkers who need to weigh in or take the next step. Owner plus tags is all it takes to describe who is on the hook and who is involved.

• Owner: the one coworker accountable for the task.
• Tags: anyone else, human or agent, who is looped in.

That small structure is enough to coordinate a team without ceremony. There is no separate intake form or routing config to maintain, just a row with a clear owner and a short list of who else it touches.

An owner is never ambiguous, and it is never shared. Exactly one coworker carries each task, which is what stops work from falling into the gap between two people who each assumed the other had it. Tags carry no such weight: they simply say who should be watching.

Views that answer "what is mine?"

The same board, filtered a few ways, answers the only question most people have when they open it. Each person sees their own slice of one shared source of truth:

• On me: tasks assigned to you to act on now.
• I own: everything you are accountable for.
• Tagged in: work where someone pulled you in.
• Involves me: the union of all of the above, your whole footprint on the board.

Nobody has to keep a private to-do list on the side, because the board already knows what involves you. The filters are just lenses onto the same rows, so nothing can drift out of sync between your view and everyone else's.

These are not four separate lists to keep in sync. They are one board seen from where you stand, so when a task changes owner or a tag is added, every view updates at once. That is the whole value of a single source of truth: there is only ever one copy of the work.

The handoff loop

Work moves between coworkers through a handoff. You tag a coworker, human or agent, on a task, and that creates a request that does not just sit quietly on a board they might not check. It is mirrored to email and Slack and lands on their board at the same time.

You: Hand off the "Refresh win-back copy" task to Mara,
and tag the scout to pull the latest lapsed 30 days counts.

Workflow: Handed off to Mara (emailed and Slack DM'd).
Tagged the scout; its counts are attached to the task.

The handoff loop is what makes the board feel alive instead of like a passive list. A request reaches a person where they already are, and it stays tied back to the exact task, so nothing gets lost in a thread or a forwarded email.

Handoffs run both directions across the human and agent line. You can hand a task to a person, a person can hand one to you, and either of you can tag an agent to take a piece of the work and report back. The loop does not care whether the coworker on the other end is a human or a bot, only that the request reaches them and stays on the record.

Why one visible record matters

When part of your team is made of agents, coordination and trust come from the same thing: visibility. Every action, human or agent, lands on this one board. You can see who owns what, who was pulled in, and what an agent proposed, all in one auditable place.

The board also feeds the rest of the harness. Your scheduled digests summarize the tasks that involve you, and the agent fleet files its recommendations here as ordinary tasks. One record in, many views out, and a single place where the whole team, human and agent, can see the work move.