Reports

Open Monitoring → Reports once you have a few weekdays of connected integration data. Reports reuse the same filters as the monitoring board (team, integrations, human/agent) so a filtered board and its report stay aligned.

Core metrics include overall SPACE score, effective active minutes, efficiency, engagement, and integration-specific throughput (messages, commits, PRs, Jira story points and task counts).

• Weekly — aligns to your org week-start day (Organization → Schedule). Good for sprint-adjacent check-ins and standup prep.
• Monthly — calendar month in the organization timezone. Better for capacity planning and longer rhythm changes.

Each rollup aggregates worker-level statistics that passed your enabled-statistics configuration. Disabled statistics do not appear in totals or deltas.

Every core metric shows a delta against the prior period of the same length — e.g. this week vs last week. Deltas are signed (+/−) with neutral handling when there is no baseline yet.

The manager summary highlights top movers up and down on score and throughput so you can follow up while it still feels supportive, not punitive. Movers are contextual signals, not rankings.

When your plan includes AI agents and workers are tagged AI agent, reports can split human vs agent contribution on shared metrics (commits, PRs, effective time).

AI agents skip the Satisfaction dimension in SPACE scoring — it does not apply to non-human workers. Human-only metrics (break patterns, satisfaction proxies) stay on the human side of the split. See SPACE scoring.

Report denominators use the same fair totals policy as monitoring:

• Excluded weekdays (org-defined non-credit days).
• Minimum logged-day minutes — days below the threshold drop out of averages and totals.
• Organization-local date keys via dateKeyTz — no UTC drift across timezones.

This is intentional noise control. Activity on excluded days can still appear on individual timelines; it simply does not inflate team averages.

1. Set timezone and week start under Organization → Schedule before trusting week boundaries.
2. Enable the statistics you care about under Organization → Statistics.
3. Filter monitoring to the team or integration slice you want, then switch to Reports for the same context.
4. Drill into a person from comparison cards to see the underlying timeline for the period.
5. On Small team and above, export CSV bundles from Organization → Exports for offline analysis within your retention window.

• “Reports replace 1:1s.” They surface where to ask questions — not answers about intent or blockers.
• “Zero delta means nothing happened.” Fair totals or disabled statistics can flatten totals while events still occurred.
• “Monthly is four weeks.” Calendar months vary in length; compare like periods (month vs prior month), not arbitrary 28-day windows.