Scenario · The bigger jobs
What am I supposed to be working on?
Start of the day. Work is spread across a support queue, a project board and a worklog.
The day's work is split across a support inbox, a project board and a log of what's already been done, and none of those three systems knows the other two exist — so the daily question of what's actually outstanding takes three separate tabs to answer honestly. This reads all three in one pass and surfaces exactly where they disagree — a closed ticket with no matching log entry, board work with no ticket behind it — which is where work quietly gets forgotten or done twice; deciding what to tackle first is still a judgment call this deliberately leaves alone.
What to ask for
See it work
A real run of Task board (monday.com):
$ node scripts/task-board-monday-com.mjs board 111111111
Task board (monday.com) — Example Workflow (fixture)
INFO — 6 item(s) · 5 open · 1 overdue
3 0 - New
1 6 - Completed
1 Roadblock
1 On Hold
report: ./out/task-board-monday-com-task-board-monday-com.html
$ node scripts/task-board-monday-com.mjs board 111111111 set "Task Status=On Hold" --items 1001
plan — Example Workflow Task Status → "On Hold"
Overdue and open
0 - New → On Hold
DRY RUN — nothing was written.
To apply: --apply --confirm 1
$ node scripts/task-board-monday-com.mjs board 111111111 set "Task Status=On Hold" --items 1001 --apply --confirm 1
plan — Example Workflow Task Status → "On Hold"
Overdue and open
0 - New → On Hold
written Overdue and open · Task Status
⚠ could not be confirmed live — could not re-read the column to verify — Monday API: monday-mock: unhandled query shape
applied 1 change(s)
rollback: ./out/rollback.json
$ node scripts/task-board-monday-com.mjs --rollback out/rollback.json
restored Overdue and open · Task Status
reverted 1 op(s)Three systems hold the work — client tickets, the project board, and the log of what has already been done — and none of them knows about the other two. The daily question is answerable in one pass instead of three tabs.
- Read the support queue. The helpdesk client turns the desk into a snapshot: every mailbox with counts by status, the total open load, and the most recent active conversations with customer, assignee and age. Age is the column that matters — an old open ticket is the one that becomes a phone call.
- Read the project board. The task board client reports what is open, what is done, what is overdue and how the work splits by status and by person. Overdue-and-unassigned is the pile that quietly grows.
- Read the pipeline and the log. The activity log client gives the completed work log and the open queue, which is the only place that shows what has already been done against a domain — frequently the answer to a ticket that looks new.
- Reconcile the three. A ticket closed on the desk with no matching log entry, or board work with no ticket, is the normal state and worth noticing. Work tracked in one system only is work that gets forgotten or done twice.
- [manual] Decide the order and commit to it. Down sites and client-blocking tickets first, then overdue board items, then the backlog. This is the judgement the tools deliberately do not make.
- Where a ticket looks finished, check it rather than trust it. The ticket QA orchestrator routes a completed ticket to the checks that fit its category and returns one verdict, which is a faster answer than reopening the work.
Three systems, no shared view
The reason this is worth a procedure rather than a habit is step 4. Each system is individually fine and the gaps only exist between them — a ticket with no log entry, board work with no ticket. Nobody sees those by looking at any one tool.
What this does not cover
Priority. It gathers what is open from each system and reports it; deciding what to do first is a judgement involving client relationships, promises made on calls, and things nobody wrote down anywhere. Every client here is read-only on this path, so nothing is assigned, closed or moved — it answers "what is there", not "what is next".