Reports (Admin)

The Reports area (app sidebar → Reports) turns your org's goal and usage data into five decision-grade views, switched between by the tabs across the top of the page. It opens on Adoption. It is visible to org admins and owners only. Most numbers are clickable: they open a panel listing the exact goals or check-ins they were computed from (the first 200 when there are more), and clicking a goal there opens a quick view of it.

The five reports #

Adoption

Six tiles over a span you choose (30 days by default): Check-ins, Active users, Goals with a check-in, Active cadences, Scored OKRs and Meeting coverage, each with a change against the equal-length span before it ("+2 vs prior period"), plus a weekly check-in trend line. Manual check-ins and Brev AI check-ins count; integration refreshes and rollups don't.

Check-in heat map

People × weeks grid of check-in activity, 12 weeks by default. Every active member appears, including members with zero check-ins. The silence is the signal. Switch between People and Teams to regroup the rows, hover a cell for its count, and click any cell to see that person's (or team's) check-ins for the week.

Teams on track

Org-wide tiles (goals in scope, % on track, off track) plus a per-team table: goal count, a status bar (on track / at risk / off track / not started) and average progress. It covers the current periods by default; pick one time period to narrow it. A Project with a due date is counted in the period containing that due date rather than the one it was authored in, so the number answers whether the work due this period is on track. A Project with no due date, or one whose due date falls outside every defined period, is counted in the period it was filed under. Click a team, a count, or a bar segment to see the goals.

Ownership & cascade

Distribution of goals by ownership altitude (company / team / individual), by cascade depth, and, for individually-owned goals, by the owner's org role. Includes the count of unaligned goals (non-company goals with no parent).

Attainment

Scored goals, scoring discipline at period close (how many closed goals actually got scored), average score, a score distribution across the 0.0–1.0 scale, and per-team scored counts and averages. Defaults to all periods; pick one for a quarter-close review.

• Known issue: on Adoption, the trend chart's heading always says last 60 days. The chart itself covers twice the span you picked in Window.
• Known issue: on Teams on track, Avg progress shows 100 times the real value (a team at 20% reads 2000%), on screen, in comparisons and in exports.
• Known issue: on Teams on track, the org-wide tiles count only goals that belong to a team, but clicking one lists every goal in scope, so the list can be longer than the number.
• Known issue: on Attainment with All periods selected, the per-team table counts only goals in the current periods, while the tiles and chart above it count every period. Pick a single period to get matching numbers.

Comparing time periods #

Teams on track, Ownership & cascade, and Attainment each have a Compare button next to the time-period filter. Tick up to three other periods (the button then reads Comparing 1, 2 or 3) and the report switches to comparison tables: your selected period, then a column per period you're comparing against, and one change column (an absolute difference and a percentage) between your selected period and the first period you're comparing against. Clear comparison in the same menu goes back to the normal view.

Adoption compares differently, because it's scoped to a span of time rather than a named period. Pick the span with the Window control (Last 30 days, Last 90 days, Last 6 months or Last 12 months), then choose how far back to compare in the Compare control beside it, for example "vs previous 90 days" or "vs previous 2 periods". The tiles turn into comparison tables. Every comparison span is exactly as long as the one you selected, so the changes compare like with like.

A team or person that had goals in an earlier period but none in the current one still appears, with an empty current column. A disappearance is usually the thing you're looking for. A blank cell means there was no value to measure, which is different from a measured zero; changes against a blank are left blank rather than shown as a 100% swing.

The Check-in heat map has no comparison control. Its columns are already weeks. To look further back, widen the grid with its Weeks control (Last 4 weeks up to Last 26 weeks).

Exporting a report #

Every report has an Export button offering CSV and Excel (.xlsx). The file contains exactly what's on screen (the same time period, the same comparison columns, the same rows), not an unfiltered dump, and is named after the report and today's date. Export waits until the report has finished loading.

In the Excel file, cells are properly typed: counts and scores are numbers, rates are percentages, and week dates are real dates. You can pivot or chart the sheet straight away without re-parsing anything. Each part of a report becomes its own sheet, and an About sheet records the period, the comparison, and the export date, so a file you open months later still says what it covers.

Who can see it #

Org admins and owners (see Roles & permissions). Everyone else doesn't see the sidebar entry or the command palette entries, direct links return a not-found page, and the underlying data endpoints reject them. Reports respect goal visibility: a private goal you can't open is also not counted in your report numbers. A drill-through list shows at most 200 entries, so a large count can be longer than its list.

Reports is also a paid module. If your workspace hasn't been turned on for it yet, an admin opening Reports sees the page with its content dimmed behind a card reading See how your team executes. Request access opens a short form asking what it would unlock for you; sending it notifies the Brev team, shows Request sent, and the button then reads Feature requested. Until access is granted the tabs, the time-period, Compare and Window controls and Export are not available. Once it is, they all are.

API and agent access #

The same aggregates are available to admins via the REST API (GET /v1/reports/*) and to agents via the brev_org_report tool, so agent workflows can consume identical numbers. Comparison is available there too: pass compare_time_period_uuids (or lookback_windows for adoption) and the response keeps the primary period where it was and adds a comparisons array alongside it. Existing integrations that don't pass them see no change.