Analytics
The analytics your delivery actually produces
Throughput, resolution time, velocity and workload — computed from your real board, not a spreadsheet you keep by hand. Ask for any chart in plain English, and get one rendered from your data.
Live today
The numbers, from the work itself
No manual roll-ups. TaskForce reads your board and computes the delivery metrics teams actually track — updated as work moves.
Throughput
Opened vs resolved over time, by week or by day.
Resolution time
How long work takes to close, with the trend vs last period.
Velocity
How much gets resolved per cycle.
Active cycles
What's in flight right now, and how full it is.
Burndown
Remaining work against the ideal line, per cycle.
Team workload
Who's carrying what, day by day — before anyone is buried.
See who's overloaded, then route the next work with Smart Assign .
Ask in plain English
Describe the chart. Get it from your data.
Type a question and TaskForce builds the chart from your real board — then let you pin the ones worth keeping.
And when a question can't be answered from your data, it says so — and suggests one it can — instead of inventing a number.
People and coding agents share the same delivery surface, so analytics can measure both — just like Smart Assign and Collaboration.
Rendered from your board · this cycle
- Inès 9
- Léo 7
- Maya 5
- Claude Code 4
"Revenue by region" isn't in your data — it says so and suggests resolved by label instead.
Illustrative — not a TaskForce customer metric.
Beta
See where delivery gets sent back
A classic tracker tells you what's late. Because TaskForce runs through validated checkpoints, it can measure not just what shipped, but where work gets rejected, revised or sent back — the step where your process actually hurts. It's early, and grows as orchestration does.
- Framing4%
- Specification9%
- Approach31%
- Contracts12%
- Breakdown6%
- Quality checks8%
Approach is where your process actually hurts — nearly a third of runs go back there.
- Trade-off not explained (11)
- Conflicts with an existing decision (6)
- Scope drifted from the spec (4)
Illustrative — not a TaskForce customer metric.
Where this goes
PlannedMeasurement that feeds the next run
Reporting is the start. The direction is a loop: a pattern that keeps costing you — an approach repeatedly sent back — can become context in Memory, so the next run can start with context learned from the last.
In plain terms
The questions it answers, day to day
Not a wall of dashboards — the handful of answers a lead actually needs, computed straight from the board.
Opened vs resolved this week?
Throughput at a glance, by day or by cycle.
Is resolution time getting worse?
The trend on how long work takes to close, against last period.
What slipped this cycle?
What's in flight, what shipped, and what carried over.
Who's overloaded right now?
Workload by person, day by day — before anyone gets buried.
How much ships per cycle?
Velocity, so planning starts from reality instead of a guess.
Where do runs get sent back?
The checkpoint that keeps costing you — only a checkpoint system sees it.
Ask any of these in plain English, or pin the ones your team checks every week.
Measure the delivery, not the busywork
Get the metrics your board already contains — plus the delivery signals that become possible when work moves through validated checkpoints.