Status tracking

What is status tracking: a definition for anyone responsible for a queue

Status tracking is the practice of recording which stage each item of work has reached in a defined sequence, and displaying that so the state of the whole queue, and of any single case within it, can be read directly rather than reconstructed by asking people. It answers two questions at once: where has this one got to, and how is the queue doing.

The term covers two views that are often confused. There is the internal view a team works from, and the external view a customer sees when they check progress. Both are built on the same underlying status model.

What does status tracking mean?

A status is a named stage, not a description. Received, assigned, awaiting information, in assessment, decided, closed. The value of the set comes from being small, mutually exclusive, and meaningful to everyone who has to read it.

Tracking is what happens around that. Every change is timestamped and attributed, so a case carries not just its current stage but the moment it entered each earlier one. That second part is what turns a status field into a measuring instrument.

How does status tracking work?

• The status model. The list of allowed stages and the transitions permitted between them. Six to eight stages is typical. Past about ten, people start guessing.
• Ownership alongside status. A stage without a named owner tells you where work is sitting but not who moves it next. That pairing is the core of case management.
• Timestamps on transitions. Entered assessment at 09:14, left it at 15:40. Duration by stage then falls out for free.
• A waiting state that is labelled honestly. Awaiting customer is not the same as awaiting us, and merging them hides the only queue you can actually do something about.
• The queue view. Everything open, grouped by stage, sortable by age, filterable by owner. This is the artefact managers actually use, and it is the point of the whole exercise.

How is queue health measured?

Three numbers do most of the work, and all three come out of the transition timestamps.

• Age of the oldest open item. The single most useful figure on any queue board, and the one an average is guaranteed to hide.
• Time spent in each stage. Shows where work waits. One stage almost always dominates, and it is rarely the one people assume.
• Work in progress. How many cases are open at once, which is the number connecting the other two.

The relationship between them is not a matter of opinion. Little's Law, proved by John D. C. Little in Operations Research in 1961, states that the average number of items in a stable queue equals the average arrival rate multiplied by the average time an item spends in the system. Read operationally: if work arrives faster than it leaves, no amount of reprioritising changes the outcome, and time in the system rises in step with the backlog. Status tracking is what supplies both inputs.

Status tracking explained: a Monday morning service queue

Forty vehicles are open. The board shows twenty six in awaiting customer approval, eleven in assessment, three waiting on parts. Average cycle time looks acceptable, so the queue looks fine.

Sorted by age, four of those twenty six have been waiting nine days or more, and each was last touched by the same advisor before annual leave. The average said nothing useful. The age column said all of it. On the insurance side the equivalent measure is claims cycle time.

How status tracking differs from reporting and from an audit trail

• Reporting looks backwards at completed work in aggregate. Status tracking is about open work, right now, at the level of the individual case.
• An audit trail records every action for accountability, including plenty with no bearing on progress. Status tracking records a deliberately small subset, chosen because each entry changes what somebody should do next.
• A shared inbox is where status gets read and changed in daily use. Status tracking is the discipline underneath the screen.
• A notification pushes a change out to somebody. Status tracking is the pull equivalent, available whenever anyone chooses to look. Teams relying only on the push version lose whatever nobody happened to read.

Common mistakes with status tracking

• Statuses that describe feelings. Urgent, chasing and problem are not stages. They belong in a priority field or a tag.
• A dumping ground stage. Any status holding a third of the queue has stopped being a stage. It is where work goes to become invisible.
• Setting status at the end. A status filled in retrospectively records that the work finished, not how it moved, and the stage durations become fiction.
• Customer facing statuses copied from internal ones. In assessment means something to the team and nothing to the person waiting. Map the two deliberately.
• Measuring only what closed. Cases that never close are invisible in completion metrics, and they are usually the ones generating the complaints.