What it reports
Reporting in Otper is generated from the work itself — the cards your team already moves across the board. Nobody assembles it, nobody updates a slide the night before, and nothing is entered twice. You pick a date range and the boards you care about; what comes back is the current state of those boards.
That matters more than it sounds. A status report that someone compiles by hand is a report about what they remembered. A report derived from card activity is a report about what happened.
The metrics
| Metric | What it answers |
|---|---|
| Tasks completed | How much work actually finished in the period. |
| Throughput | Cards created against cards completed per day, week or month — is delivery keeping up with intake? |
| Work in progress | How much is open right now, so you can see load rather than infer it. |
| Bottlenecks | Average days cards spend in each list, ranked and scored, so the slowest stage is named rather than guessed at. |
| Overdue work | Every card past its due date, who is on it, and how many days it has been. |
| Delay risk | Open cards running longer than the team's median completion time, or with less time left than that median. |
| Stuck work | Cards with no activity for seven days or more — usually a blocked handoff nobody escalated. |
| Work by owner | Assigned, in progress, completed and commented, per person. |
| Workload balance | Each person's share of active work against the team average, flagged when someone is carrying too much. |
| Due-date spread | Cards grouped by when they fall due, so next month's crunch is visible this month. |
| Label distribution | Where effort is going by workstream, priority or whatever your labels encode. |
| Board comparison | The same numbers side by side across boards, for anyone running more than one. |
Where the numbers come from
Every metric traces back to something that happened on a card. "Completed" is a card that was closed. A bottleneck is measured card movement between lists, not an estimate anyone typed in. Delay risk is computed from your own team's median completion time, not an industry average that has never seen your work. When a number looks wrong, you can open the cards behind it and find out why.
Reading a report
Illustrative example
A marketing team opens the last 30 days. Forty-two cards completed against forty-seven created, so intake is running slightly ahead of delivery — a gap that compounds if nothing changes. Six cards are overdue. Review is holding cards for 4.2 days on average, the longest of any stage, which is where those six lost their time. One person is carrying 23% of active work against a team average of 20%.
That is four decisions in one screen: pull someone into Review, rebalance one person's load, chase six specific cards, and either slow intake or accept the growing gap. None of it needed a meeting to discover.
Getting it out of Otper
Export the selected boards and date range as CSV for your own analysis, or as PDF for a stakeholder who just wants the read. If you want the numbers somewhere else entirely — an internal dashboard, a warehouse, a weekly digest — the same reporting data is queryable through the GraphQL API, so nothing has to go through a manual export step.
Common questions
Do I have to set the reports up?
No. Every metric is derived from board activity you are already generating. Pick a date range and the boards you want included, and the numbers are the current state of those boards.
Can I report across several boards at once?
Yes. Scope a report to one board, a few, or everything you have access to, and compare boards side by side in the same view.
Can I export the report?
Yes — CSV or PDF, for the boards and date range you have selected.
Where does "delay risk" come from?
From your own history, not an industry benchmark. Otper computes the median time your team takes to finish a card, then flags open cards that have already run longer than that, or that have less time left before their due date than the median.
Can I pull these numbers into our own dashboard?
Yes. The same reporting data is available through the GraphQL API, so an internal dashboard can query it directly instead of waiting on an export.
Does this replace our status meeting?
It removes the data-collection half of it. Nobody needs to go around the room asking what got finished and what is late, because that part is already on screen — which leaves the meeting for the decisions.
Related features
Kanban board software: owned work and visible flow
Lists that model your real workflow, cards that carry the whole story.
Task ownership software
Responsibility lives on the card, and stays attributable afterwards.
Project timeline tool for delivery visibility
The same cards, drawn on a timeline. One set of dates, never two.