A Trends tab that shows whether orders are getting faster

Your production dashboard has a new Trends tab. It answers one question: is a finished order taking less time than it used to?

The main chart plots the hours booked against each completed order, in the order they closed out, with a running average across the whole run. The average line is the one to read. A single order swings on one bad shift, but the average falling means the crew is getting quicker, and the average flattening means the run has settled.

A Hours Saved per Order figure sits above it. That's how many fewer hours a recent order takes than an early one, comparing the most recent fifth of the run against the earliest fifth so one unusual order doesn't look like a trend. It needs twenty finished orders before it will show you anything, because below that a "fifth" is one or two orders and the number swings wildly.

Underneath, two views of your stages side by side. Hours by Stage shows where the run's time actually went, as a share. Avg Hours per Stage shows what each stage costs you on a typical order, which is a different question and often a different answer: a stage can be a big share of the total simply because every order has one. Click a bar to trace that stage on its own.

The table lists every completed order with its hours, grouped by the order it came in, so a release of ten reads together with its total. Clear the grouping control on the table for the flat list.

It counts finished orders only. An order still on the floor hasn't booked all its hours yet, so including it would look like a sudden speed-up that never happened.

Elsewhere on the dashboard

Hours has a new Crew on Completed Stages table. Every stage finished in the range, and who booked hours to it. Expand a stage to see the crew. It shows hours rather than a count of stages on purpose: a stage is usually two to six people, so the hours are what add up honestly.

Next to it, a Completed, No Hours figure counts the stages that were signed off with nothing booked against them. That's not automatically a problem, since time can be booked to the order instead, but it's the number that tells you whether stages are being ticked without being timed.

Plan vs Actual hides projects that didn't move. A project shows if it booked hours or completed something inside your date range. The figures themselves are unchanged, since planned and spent are whole-budget numbers, but a quiet project no longer pads the list.

The cost code widgets work again. The weekly cost code table and the two cost code charts had been coming up empty. That was a failing request behind the scenes, not missing data, and it's fixed.

With them showing, one more thing was wrong: cost codes have only been recorded since June, so every hour before that was landing in the same Unknown pile as genuinely uncoded work, and the coded share read far worse than reality. Those are now two separate buckets, and the percentage only counts hours that could have carried a code. The union code view is gone entirely, since nobody's sessions carried one, and the duplicate Hours by Cost Code chart is gone too.

Production rate reads properly again. It was measuring against a planned figure that only exists when a route is broken into steps, so it came up empty. It now uses the estimate set on the stage itself. Stages whose estimate is wildly out of step with the time logged against them are left out, so one bad number cannot swing a whole week.

Four KPI cards now click through to the tab that explains them, joining Orders Completed on Plan vs Actual. Variance to estimate has been dropped from the Hours tab, since Plan vs Actual already covers variance properly.

Tables are taller across every tab, and a table grouped by name now sorts in the order you'd expect, so order 9 comes before order 10 instead of after it.

The date filter also gained This Year and Last Year.