A companion reads the Updates thread behind every stalled item, works out what it is actually waiting on, drafts the chase per owner, and stops for your approval before the board changes.
Statuses stop meaning what they say. The Updates tab holds the real story, and Friday’s status meeting is one person reading the board aloud while everyone silently corrects it.
A companion does that extraction. Connect your monday account and it reads boards, groups, items and the Updates conversation on each one. Reading needs no approvals. Every write stops on a card naming the item, the status and the text.
01
What one board pass gets you
The reading half needs no approvals.
The writing half stops for you at every item. One pass, with a clock on it:
Anything the connection does not cover, a companion opens as you: the boards, the groups, the status columns and the Updates conversation on each item. You connect monday once and see exactly what it can reach before you allow it, and the credential stays encrypted.
15:00: the board opens, grouped by status and sorted by last updated. 62 items, 14 untouched for three weeks.
15:04: each stale card opened and its Updates thread read, which is where the real story lives.
15:19: nine items get a proposed status correction, five get a written update asking the owner where things stand.
15:20: it stops. Every proposed write is shown as this item, this status, this text.
15:24: you approve eleven, edit two, skip one. The board is accurate for the first time since the sprint opened.
02
What can a companion see that the board cannot?
A board only knows what somebody typed into it, and the person who typed “waiting” three weeks ago has left. The reason item 47 is stuck is in a GitHub thread. The approval item 12 waits on is in somebody’s inbox.
A companion holds your monday session and your other tabs at once, so it checks the pull request, finds the email, and writes the real blocker into the update. Same pattern on Asana, ClickUp or Trello. Operations teams run it weekly and arrive at the meeting with the board already true.
03
Which half is a recipe, and which half is judgment?
A companion takes the fourteen ambiguous items, the ones where the answer sits in an Updates thread, a pull request or an email. Put it on a routine and Thursday at 15:00 the board gets walked whether or not anyone remembers.
The other half of a board’s upkeep is shaped when-X-then-Y. Status changes to Done, notify the owner. A date arrives, create the item. monday fires those itself the moment they happen.
Yes. Connect your monday account and a companion reads the boards, works out from the Updates threads what each stalled item needs, and stages the status corrections and written updates for your approval. You see exactly what it can reach before you allow it.
It reads the board, works out from Updates threads and linked context what each stale item needs, and stages status changes or written updates, each one shown to you for approval before it lands.
This is the strong case: a companion reads the board plus the repo, the inbox and the docs, then writes the status summary from evidence rather than from the status column. Finished runs are at real runs.
A companion does the reading and the judgment across your tools, on a schedule you set, and stages every board change for your approval. Mechanical when-then rules fire inside monday. Strawberry is free to download for Mac and Windows.
monday.com Strawberry