Skip to main content
Reports turn the activity on your pipeline into numbers you can act on. They read from the same records you work every day, so figures match what you see in the pipeline. No separate data warehouse or export required.
Harly reports dashboard showing applications, hires, time to hire, offer acceptance, and hiring trends.

Hiring performance, pipeline health, and time-to-hire reporting.

What you can measure

Pipeline health

Pipeline health shows how many applications sit in each stage per job, so you can see bottlenecks before they become stale candidates.

Hiring velocity

Source and outcome

Reading a report

1

Choose a report

Open Reports in the sidebar and select the report type.
2

Apply filters

Filter by job, department, date range, or owner to scope the view. A narrow filter is usually more useful than a workspace-wide aggregate.
3

Interpret the data

A number is a prompt to look, not a verdict. High age-in-stage means you should look at what is blocking those applications — it does not mean those candidates are unqualified.
4

Act on the record

Open the underlying applications from the report view. A report is read-only; changes happen on the pipeline.
Reject with a consistent reason on every application. Reporting is only as useful as the reasons behind it — clean reasons make drop-off analysis trustworthy. Train every recruiter to use the same set of rejection reasons rather than free-form text.

Metric definitions

Every report, the dashboard, scheduled report emails, the AI assistant, and the API read the same definitions, so a figure means the same thing wherever it appears.

Population

Counts include applications whose job and candidate are both still present (not soft-deleted). Closed and draft jobs stay in historical figures.

Applications received

Applications in the population whose application date falls inside the report window.

Hire

An application whose current status is hired. Its hire date is the most recent move into a stage whose kind is hired. Harly reads the stage kind, not the stage name, so a stage renamed “Welcome aboard” still counts. Hires recorded before stage kinds existed fall back to the earliest “hired” activity event, and then to the last update time. Each application counts once, in the window that contains its hire date.

Time to hire

Hire date minus application date, in days, for hires in the window. Averages and the median are shown to one decimal place. The distribution buckets are 0–14, 15–30, 31–60, 61–90 and 90+ days, using whole days.

Offer acceptance

Accepted offers divided by the sum of accepted and declined offers, where the decision date falls in the window. Offers still pending are not counted. When nothing was decided in the window there is no rate, rather than a rate of zero.

Funnel

For applications received in the window, the number that ever reached each stage kind, either in their stage history or in their current stage: Applied, Screening, Interview, Offer, Hired. Conversion is measured against applications received, not against the stage named “Applied”, so renaming a stage does not change the funnel.

Source effectiveness

For each application source, the number of applications and hires, and hires per application as a whole percentage. A source with no applications shows no conversion rather than zero.

Windows and time zone

  • A window is made of whole calendar days in the reporting time zone, so “Last 30 days” means 30 calendar days, the same on the dashboard, the Reports page and the scheduled email.
  • The presets are Last 30 days, Last 90 days and Last 12 months.
  • Days and months are measured in the workspace’s reporting time zone, set in workspace settings. If no zone is set, or the saved zone is not recognised, Harly uses UTC. Changing the zone changes which day a late-evening event falls on, and is reflected in every report immediately.

Small groups are hidden in diversity reports

Diversity breakdowns count applicants received in the window. A group with fewer than 5 applicants is shown as suppressed, with no counts, so that individuals cannot be picked out of a small group.

Export and API

For custom analysis or dashboards outside Harly, use the API:
See API overview for pagination, scopes, and available filters.
Candidate data is personal data. Export only what is necessary for a specific analysis, store exports securely, and delete them when the purpose is complete. See privacy for the full retention workflow.

Next steps

Candidates and pipeline

The records reports are built from.

API overview

Export data programmatically for custom dashboards.

Privacy

Handle exports and retention compliantly.

Automations

Automate actions triggered by pipeline events.