How time in a status is measured

Time in a field is how long an item has held its current value of that field. Teamhood records each change to the value as it is saved. The time is the moment of the last change subtracted from now.

The time is worked out in your browser and is not saved on the item. It is shown in whole days from one day on and in whole hours below that, rounded down, such as 4d, 3h or <1h.

Which fields have a time

Every select, people, checkbox and relation field has one, except Watchers. It is named after the field, such as Time in Status or Time in Assignee. The filter picker and Show fields list each under its field’s own history heading, such as Status history.

When the value last changed

Teamhood takes the latest of three moments:

when the item entered each value it holds now;
the last recorded change to the field, which also covers a value that was removed;
when the item was created.

The time since that moment is shown. Point at the time to see the moment, such as “In Review since 3 Oct 2026, 14:20”. The moment uses the organization’s time zone and date format.

On a board

On a board grouped by the field, a card shows the time since it entered the value of its own column. When the field is the swimlane field instead, the swimlane’s value counts.
On a field with several values, that rule means the card in Alice’s column shows the time since Alice was added.
Anywhere else, including on a mind map, a card shows the time since the value last changed.

The aging colour

An amber or red time says that the item has been in its value longer than usual. Teamhood compares the time with past stays in the same value. A stay is each time an item sat in a value, from entering it to leaving it. Only stays that ended in the last 90 days count.

Amber: as long as half of those stays or longer, up to 85% of them.
Red: longer than 85% of those stays.
No colour: shorter than half of them, or fewer than 10 such stays in the last 90 days.

The colour appears only for a field that holds one value. No value counts as a value, so an unassigned item is compared with past unassigned stays. Point at the time to read the comparison, such as “Longer than 85% of past items in Review”.

In tables, filters and sorting

Columns: in the tables of list, Gantt and schedule views, the column list offers a Time in column right after its field. The column is hidden by default. A row whose type does not carry the field shows a dash.
Sorting follows when the value last changed, so passing time never reorders rows. Ascending puts the most recent change first. Rows with no known time come last.
Filters take more than or less than a whole number of days. An item at exactly that number of days matches neither. Filters are checked again every hour, so an item can appear in or leave the results up to an hour late.
Exports write the time as days with two decimal places, under a header that ends in (days). A board export writes the time since the value last changed, even when a card shows the time in its column.

In the item details

The Time in each status section sits above Activity and starts folded. It covers the field set to Status under View defaults for the item’s type, if your role lets you read that field.

One row per value the item has held, in the order the item first entered them.
Each row shows the total time over every visit and the number of visits.
Current marks the value the item holds now.

The section loads the field’s history when you unfold it. The number of values beside its title shows only while the section is unfolded. If the history cannot load, the section says so and tries again with the next history refresh.

An item with no recorded change in that field shows one row for its current value. That row counts from when the value last changed. An item created before history is complete shows No status changes recorded instead.

Where the history comes from

Teamhood records each change to these fields when it is saved. Changes made by automations are recorded too. Changes from before recording began were rebuilt from the items’ Activity, back to mid-June 2026.

Your own changes show at once. The exception is a change that only removes one of several values, which waits for the next history refresh. Other people’s changes also arrive with a refresh. The history refreshes when a view opens, after your own changes save, when other people’s changes reach you, and every two minutes while the page uses the history.

Example

A task moved to Review on 3 Oct 2026 at 14:20. On 7 Oct at 17:30, the card reads Time in Status: 4d.

In the last 90 days, items left Review 20 times. Half of those stays lasted at most 2 days, and 85% of them lasted at most 4 days. The task has been there longer than 85% of them, so its time shows in red. A filter Time in Status more than 3 days includes the task.

Things that may surprise you

Nothing shows until the history has loaded. A Time in cell or card row is empty until then, and a Time in filter matches nothing.
An item may be timed from its creation, so its time is too long. This happens when the item has no change recorded since mid-June 2026 and no change to that field made in Teamhood since late September 2026.
Rebuilt changes can be off by up to a minute. Activity merges quick edits by the same person.
Automation changes from before recording began are missing. Activity never recorded them.
Totals from before history is complete are minimums. History is complete from 4 Aug 2026, or from the field’s creation if that is later. A value an older item held from before then reads At least and a time. When less than an hour of it is known, it reads Before history began instead. Point at the total to see the date.
A cloned item counts from its own creation, not from the item it was cloned from.