The Reports page
Two tabs:Overview
Recruiting figures — positions, applications, stage throughput and time-in-stage — computed from
the pipeline history, with an export.
Newsletter
Subscription preferences for the hiring-manager report described below.
The hiring-manager report
A recurring e-mail sent to each hiring manager about their own positions. Per position it lists the active application count and the top few applicants with their stage, application date, and fit score where one exists.
A fit score appears only where the applicant consented to AI processing. Where they
opted out it is absent — the same as when no score exists for any other reason, so an
opt-out is not visible as a signal. See AI transparency.
Where the other numbers live
Each module surfaces its own, because each carries its own masking and scoping rules:The rules any number obeys
Salary figures respect visibility
Salary figures respect visibility
Masking is applied before aggregation, not after. A figure that would let the viewer derive an
individual salary they are not permitted to see is not shown. See salary
visibility.
Scoping still applies
Scoping still applies
A manager’s view covers their own scope — their positions and their direct reports. Reporting is
not a route around the permission model.
Small populations
Small populations
The same k-anonymity reasoning as surveys: a “team average” over three people is three people’s
data wearing a hat.
No individual rankings
No individual rankings
Per ADR-006, the platform does not produce top-10% / bottom-10%
reports or any other ranking of people against each other. The hiring-manager report lists
candidates for one position; it does not rank employees.
Pagination
Every list endpoint behind a report is bounded — each clamps alimit parameter and
returns a pagination block. Unbounded queries are blocked in CI rather than left to
reviewer diligence, so a report over a large population pages instead of trying to
materialise everything at once.