Since 2009
Time in Status + SLAmonday.com · runs on monday codeTime in status for monday.com, saved as numbers
The app records how many hours each item spends in each status and saves them to number columns, so you can use them in formulas, filters and dashboards. It can also trigger an automation when an item stays in a status too long.
| Item | Status | Time in Waiting (h) |
|---|---|---|
| Renewal — Aldridge | Waiting on client | 62.5 |
| Onboarding — Peak Fit | In progress | 18.0 |
| Migration — Northbay | Done | 9.25 |
What it adds to monday
Two actions, one trigger, one view, and an AI check.
Track time in status
An automation action that writes the hours an item spent in each status into number columns — Time in Done (h), Time in Stuck (h) — and the moment it entered its current status into a date column, Status since.
Item stuck in status
A workflow trigger that fires when an item has been in a status for more than N hours. Notify, escalate, reassign or change the status with monday's own actions — it plugs into the recipe builder like any native trigger.
Record cycle time
An action that writes the hours between entering status A and status B. Lead time, time-to-first-response, however your team defines the clock.
Time in Status board view
Live per-item durations while you look at them, plus an account-wide summary — without exporting anything.
AI bottleneck analysis
One click in the board view. It names the statuses that slow the board down, how bad each one is, and a fix to try. It reads status names and hours only.
Why numbers matter
Durations are saved as numbers, not text
The established app in this category writes durations back as text. Text cannot be summed in a formula column, filtered with "greater than", sorted meaningfully, or charted on a dashboard — which is what everybody wanted the duration for in the first place.
Hours land in number columns the app creates or adopts by title. Every native monday feature — formulas, dashboards, filters, sorting, exports — treats them as the numbers they are.
It writes only the number and date columns it manages, and it writes to no people column, no status column and nothing you created.
On first sight of an item it rebuilds history from the board's activity log, then keeps its own record of every change. When the account's retention window passes and the log is gone, your totals are still correct.
It runs on monday code, monday's own hosting. It stores board, item and column ids, status labels and timestamps. No item names, no people, no email addresses. The AI analysis sends one board's status names and hours to Anthropic's Claude API, and only when someone clicks the button. The full list of what is stored →
Where teams use it
Anywhere a status means somebody is waiting.
Time in each queue against an SLA, and an escalation when a ticket sits too long in one.
Days between "Screening" and "Offer", per role, without anyone maintaining a tracker.
Where the queue actually forms, as a chart, instead of the stage everyone assumes it is.
How long work waits in "With client" — the number that makes a difficult conversation easy.