The test of a reporting feature is what happens when a number looks wrong. If the answer is that somebody exports a spreadsheet and reconciles it by hand, the dashboard is decoration.
Every number is a link
Every widget in Planner.day drills through to the tasks behind it. A cycle time that jumped last month is one click from the specific tasks that caused it. This is the difference between a chart that starts a conversation and one that ends it with nobody able to check.
What you can measure
The catalogue covers throughput, cycle time, velocity, reopen rate and overdue work, plus breakdowns by status, priority, assignee, type and custom field. You compose the dashboard from those widgets rather than accepting a fixed report somebody else designed.
Why it works across teams
Statuses in Planner.day are defined per list, so a design list and an engineering list can have completely different columns. Each status belongs to a reporting category: not started, in progress, done or closed.
That is the mechanism that makes cross-team reporting possible. “In review” and “QA” and “Awaiting sign-off” are different words for the same stage, and because each one declares its category, a throughput number spanning three teams means something. Without it, cross-list reporting either forces every team onto identical columns or quietly compares things that are not comparable.
A status can also be flagged blocked, which surfaces blockers separately from ordinary work in progress rather than burying them inside it.
Per person
A per-person analytics view covers workload, completion and cycle time, with the same drill-through to the underlying tasks. Time logged through time tracking rolls in alongside it.