> For the complete documentation index, see [llms.txt](https://help.join.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.join.com/create-and-manage-jobs/job-reports.md).

# Reports & analytics

Track how each job is performing in the Reports tab: applications over time, where they come from, how many are qualified, and how candidates move through your pipeline.

The `Reports` tab on every job shows you how that job is performing: how many applications it received and when, which sources they came from, how many of them were qualified, and how far candidates got in your pipeline.

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2FoL9R78W0PD4QN37mlrM9%2Freports-1.png?alt=media&amp;token=29262bcf-9b47-4732-aaa3-953e021b5312" alt=""><figcaption></figcaption></figure>

Use it to see which job boards bring you the right candidates, spot where candidates drop off, and share up-to-date numbers with your hiring team.

To open the `Reports` tab:

1. Click `Jobs` in the sidebar menu and select the job you want to review
2. Navigate to the `Reports` sub-tab within the job page

The tab is made up of five parts:

* A [date range filter](#date-range-filter) that applies to the whole page
* [Key metrics](#key-metrics) about the job and its applications
* The [Applications chart](#applications-chart), showing when applications came in
* The [Sources report](#sources-report), showing where applications came from and how many were qualified
* The [Pipeline report](#pipeline-report), showing how far candidates got in your hiring process

{% hint style="info" %}
Anyone with access to a job can see its `Reports` tab. If someone's access to the job is removed, they can no longer see its reports. See [Hiring team](/create-and-manage-jobs/hiring-team.md) to manage who has access to a job.
{% endhint %}

{% hint style="warning" %}
Reports are available for jobs published on or after 1 January 2025. The `Reports` tab isn't shown for older jobs.
{% endhint %}

***

## Date range filter

The date range filter sits at the top of the `Reports` tab and stays visible as you scroll. It's set to `Since published` by default.

Click the filter to choose a preset: `Since published`, `Last 7 days`, `Last 30 days`, `Last 90 days`

Or select a start and end date in the calendar to set a custom range. The range you pick is shown on the filter button.

How the filter behaves:

* **Presets move with time**: `Last 7 days` always means the 7 days up to today, so the range shifts forward each day
* **New jobs**: if the job was published more recently than the preset covers, the report starts from the publishing date. For example, `Last 30 days` on a job published 4 days ago shows those 4 days
* **Future dates**: you can't select dates after today
* **Saved per job**: JOIN remembers the range you chose for each job on your device. Using another device or clearing your browser data resets it to `Since published`

***

## Key metrics

Below the filter, five numbers summarise the job.

<table><thead><tr><th width="175.87890625">Metric</th><th width="353.671875">What it shows</th><th>Follows the date filter</th></tr></thead><tbody><tr><td><code>Total applications</code></td><td>Every application received for the job</td><td>Yes</td></tr><tr><td><code>Open applications</code></td><td>Applications that haven't been rejected or withdrawn, and haven't been hired</td><td>Yes</td></tr><tr><td><code>Rejected applications</code></td><td>Applications that have been rejected</td><td>Yes</td></tr><tr><td><code>Days open</code></td><td>How long the job has been published. After the first month, shown in months and days, e.g. <code>3mo 20d</code></td><td>No</td></tr><tr><td><code>Time-to-hire</code></td><td>The average time from receiving an application to hiring that candidate</td><td>No</td></tr></tbody></table>

`Days open` and `Time-to-hire` describe the job and its hires as a whole, so they stay the same whatever dates you select.

**Days open** counts from the day the job was published:

* Setting the job to `Offline` doesn't stop the count
* Archiving the job stops the count
* Unarchiving the job continues the count from the original publishing date

**Time-to-hire** shows `–` until someone is hired (moved to the 'Hired' stage of the job's pipeline). With one hire, it shows how long that candidate took from application to hire. With several hires, it shows the average. If you undo a hire, the value is recalculated.

`Open applications` doesn't include hired candidates, so it can be lower than the `Active` count on the job's `Applications` tab.

***

## Applications chart

The `Applications` chart shows how many applications the job received over time within the selected dates, with one line for each type of channel:

* **Organic**: applications from free job board postings and your career page
* **Paid**: applications from paid job board products
* **Sourced**: candidates you added to the job yourself, for example by importing them, adding them with the JOIN Chrome Extension, or assigning them from your talent pool
* **Contract**: applications from jobs boosted with your [LinkedIn contract](/post-and-promote-jobs/job-boards/linkedin.md#linkedin-contracts)

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2Fl6CdY0D9ctKFs6DeSUvx%2Freports-3.png?alt=media&amp;token=92445c05-eaa3-4a7e-8344-c7cff2d25211" alt=""><figcaption></figcaption></figure>

Only the channel types the job has received applications from appear in the chart and its legend.

Hover over any point on a line to see the date and the number of applications from each channel type.

For short date ranges, the chart shows applications per day. For longer ranges, it groups them by week, and the hover tooltip shows the week it covers (e.g. `August 31 – September 6`). For ranges longer than a year, the chart shows the last 12 months, grouped by month.

For the status and analytics of the job across all channels, open the job's `Postings` tab. See [Postings status](/post-and-promote-jobs/postings-status.md).

***

## Sources report

The `Sources` report shows where the job's applications came from and how many of them were worth pursuing, so you can compare sources by quality as well as volume.

Each source has its own bar, ranked from most to fewest applications, with the total at the end of the bar. Sources are shown by job board rather than by product, so all LinkedIn applications appear under `LinkedIn`, whichever LinkedIn product they came from.

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2FVA7L4lIWZVQtyhFFf05H%2FSources.png?alt=media&amp;token=183d7a16-8f81-4c33-a0c2-0e709f441fcd" alt=""><figcaption></figcaption></figure>

Each bar is split by where those applications stand now:

* **Hired**: in the `Hired` stage
* **Qualified**: moved past `Application Review`, but not hired
* **Unreviewed**: still in `Application Review`
* **Unqualified**: rejected at `Application Review` or before it, including candidates filtered out by knockout screening questions

Every application counts in exactly one group. If an application's status changes, for example you undo a rejection or move a candidate back to `Application Review`, it moves to the matching group.

Hover over a bar to see:

* `Qualification rate`
* `Total applications`
* The number of `Hired`, `Qualified`, `Unreviewed`, and `Unqualified` applications

The qualification rate is the share of all applications from that source that were qualified or hired:

> Qualification rate = (Hired + Qualified) ÷ Total applications

For example, a source with 4 applications, of which 1 was hired, 2 were qualified, and 1 was unqualified, has a qualification rate of 75%.

{% hint style="info" %}
Unreviewed applications are included in the total. A source's qualification rate goes up as you review its applications and move good candidates forward, so it's most useful once you've worked through `Application Review`.
{% endhint %}

### View sources as a table

Use the `Chart` and `Table` toggle at the top right of the report to switch views. The table shows the same data with these columns: `Source`, `Total`, `Qual. rate`, `Hired`, `Qualified`, `Unreviewed`, and `Unqualified`.

JOIN remembers which view you chose on your device.

***

## Pipeline report

The `Pipeline` report shows how many applications reached each stage of the job's pipeline, and what share of all applications that represents.

Stages appear in the job's current pipeline order, including stages that nobody has reached yet. The percentage on each stage is the share of all applications in the selected dates that reached it. `Applied` is always 100%, and every later stage is measured against that same total.

<figure><img src="https://1825767176-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEdFjOFlkC1DEfDv3nGRh%2Fuploads%2F1ARqWVfqDTJhXpq0d1eb%2FPipeline.png?alt=media&amp;token=ef0725be-73f6-4b7e-94fc-390e9ce071b7" alt=""><figcaption></figcaption></figure>

How applications are counted:

* **Furthest stage reached**: each application counts once at every stage up to the furthest one it has reached
* **Moving backwards**: if you move a candidate back to an earlier stage, they aren't counted again, and stages they had reached beyond it no longer count them
* **Skipped stages**: if you move a candidate straight from one stage to a later one, the stages in between count them as reached
* **Renamed stages**: stages always show their current name
* **Deleted stages**: candidates who passed through a deleted stage are counted in the stage you chose to move its candidates to when you deleted it. See [Pipeline management](/review-candidates/pipeline-management.md)

Hover over a stage to see:

* `Reached this stage`: the percentage of all applications that reached the stage
* `Total arrived`: applications that reached the stage
* `Advanced`: applications that moved on to a later stage
* `Pending`: applications currently in the stage, not yet moved on or rejected
* `Rejected`: applications rejected at this stage

If you undo a rejection, the candidate goes back to `Pending` in the same stage. The number of applications that reached the stage doesn't change.

### Hide the first stage

Every application starts in `Applied` and moves to `Application Review` automatically, unless it's filtered out by a knockout screening question. The gap between these two stages shows how many candidates your knockout questions filtered out. For example, if 100% reached `Applied` and 94% reached `Application Review`, your knockout questions filtered out 6% of applicants.

If the job doesn't use knockout questions, `Applied` and `Application Review` show the same numbers. Turn on the `Hide first stage` toggle to hide `Applied` and start the report from `Application Review`.

### View the pipeline as a table

Use the `Chart` and `Table` toggle to switch views. The table shows the same data with these columns: `Stage`, `Total`, `Reached`, `Advanced`, `Rejected`, and `Pending`.

***

## Share reports

Anyone with access to the job can open its `Reports` tab, so teammates on the hiring team can check the numbers themselves.

To share numbers with someone who doesn't use JOIN, switch the `Sources` and `Pipeline` reports to `Table` view and take a screenshot. The tables show every number, which is easier to read than the charts in a screenshot.

Exporting reports isn't available yet.

***

## FAQs

<details>

<summary>Why can't I see the Reports tab on a job?</summary>

The `Reports` tab is only available:

* For jobs published on or after 1 January 2025
* On desktop, not on mobile devices
* To users who have access to the job

If you open a link to the `Reports` tab of a job published before 2025, you're taken to its `Applications` tab instead.

</details>

<details>

<summary>Why does a report say there's no data?</summary>

If the job hasn't received any applications yet, the charts are empty until the first one arrives. If the job has applications but none were received within the dates you selected, choose a wider date range, such as `Since published`.

</details>

<details>

<summary>Why don't Days open and Time-to-hire change when I change the dates?</summary>

They describe the job as a whole: how long it has been published, and how long your hires took on average. They don't depend on when applications were received, so they stay the same for any date range.

</details>

<details>

<summary>Why does Time-to-hire show a dash?</summary>

No one has been hired for this job yet. The value appears as soon as you move a candidate to the `Hired` stage.

</details>

<details>

<summary>What counts as a qualified application?</summary>

An application is qualified once it has moved past `Application Review`, the first stage where you review candidates. Applications still in `Application Review` are unreviewed, and applications rejected at or before `Application Review` are unqualified. Hired applications are counted separately.

</details>

<details>

<summary>Why is my Open applications number different from the Applications tab?</summary>

`Open applications` doesn't include hired candidates, while the `Active` view on the `Applications` tab does. `Open applications` also follows the date filter, so it only counts applications received within the selected dates.

</details>

<details>

<summary>Why did the numbers change after I deleted a candidate?</summary>

When you delete a candidate or an application, all of its data is removed from every report on the job.

</details>

<details>

<summary>Where has the Channel Performance chart gone?</summary>

It has moved from the `Postings` tab to the `Reports` tab, where it's now called `Applications`. It also includes sourced and contract applications. See [Applications chart](#applications-chart).

</details>

<details>

<summary>Can I export a report?</summary>

Not yet. To share numbers outside JOIN, switch the `Sources` and `Pipeline` reports to `Table` view and take a screenshot.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.join.com/create-and-manage-jobs/job-reports.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.