> ## Documentation Index
> Fetch the complete documentation index at: https://help.journeyfront.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> This is the Journeyfront Help Center for hiring teams. Journeyfront is an applicant tracking system (ATS). Use the Help Center's terms: job req, Candidate Profile (the person), Candidate Application (one person on one job req), hiring class. Link to the article you used in your answer.

# Quality of hire

> See how long your hires stay and how they perform, which parts of your hiring predict it, and how to get the outcome data in.

> [!NOTE]
>
> **Who can do this:** A job profile's **Dashboard** tab needs access to that job profile. The company versions need *Company Dashboard Access*. Seeing the employees behind the charts needs *Performance Access*. Recording a separation needs access to the employee's record; the **Employees** page needs *All Employee Access*.

**The questions it answers:** do the people we hire stay and perform, and does what we measure during hiring predict it?

A hiring process is only as good as the people it hires. Quality of hire reporting follows your hires after they start: how long they stay, why they leave and how they perform. Then it turns around and checks which attributes, activities, interview questions and interviewers predicted those results.

## Where the data comes from

Quality of hire reporting reads your employee records: each employee's job, **Start Date**, **End Date** and **Separation Reason**, plus their performance results.

| Data | How it gets into Journeyfront |
| - | - |
| Employees and start dates | Hiring a candidate creates their employee record with a start date. Your HR system's employee sync and **Employee Data Import** add employees too. See [Hire candidates](https://help.journeyfront.com/onboarding/hire-candidates.md). |
| End dates and separation reasons | Recorded on the employee record (see below), brought in by your HR system's employee sync, or imported. |
| Performance | Performance reviews your team submits (**Start**, then **Performance Review**), or **Employee Performance Data Import**. See [Performance reviews](https://help.journeyfront.com/employees/performance-reviews.md). |

If your HR system is connected and its employee sync is on, an employee who's terminated in your HR system gets an end date in Journeyfront on the next sync, with a separation reason: the one mapped from your HR system, or a general one when your HR system doesn't send a reason. See [HRIS integrations](https://help.journeyfront.com/integrations/hris.md#sync-employees-from-your-hr-system).

Imports are under **Settings**, then **Import Data**. See [Importing data](https://help.journeyfront.com/account-setup/importing-data.md).

### Record that an employee left

**1. Open the employee**

Click **Employees** in the top navigation and select the employee.

**2. Open Job Info**

Click the **Job Info** tab.

**3. Mark that they no longer work here**

Untick **Employee currently works here** and enter the **End Date**.

**4. Add the reason**

Choose a **Reason for Separation** (required) and add a **Separation Note** if it helps.

**5. Save**

Click **Save**. Turnover reporting includes the change.

![An employee's Job Info tab with an End Date entered, Employee currently works here unticked, a Reason for Separation selected and a Separation Note](https://mintcdn.com/journeyfront/GQjKlyAQmW_Mi7NI/images/reporting/turnover-and-performance/gen-job-info-separation.png?fit=max\&auto=format\&n=GQjKlyAQmW_Mi7NI\&q=85\&s=490b858a8426350ca4be6e906c856feb)

Your list of separation reasons is under **Settings**, then **Custom Options**, then **Separation Reasons**. See [Rejection and separation reasons](https://help.journeyfront.com/account-setup/rejection-reasons.md).

> [!TIP]
>
> Turnover reporting is only as good as your separation reasons. Keep the list short and clear, and make sure everyone who records separations uses it the same way, so you can tell early resignations from terminations.

## Open a job profile's Dashboard

Quality of hire reads best one role at a time, because what makes a great customer care associate isn't what makes a great collections agent. Click **Profiles** in the top navigation, open the job profile and click its **Dashboard** tab. Then pick a view: **Attributes**, **Activities**, **Interview Questions**, **Interviewers**, **Turnover** or **Performance**. See [Job profiles](https://help.journeyfront.com/employees/job-profiles.md#profile-dashboards).

## Turnover

**Turnover** shows when and how fast your hires leave. Set **From date** and **To date**, choose **Month**, **Qtr**, **6 Mo** or **Year**, and filter by **Separation Reason** or by a multiple-choice employee job field with **Job Field**.

![The Customer Care Associate job profile on Dashboard, then Turnover, with the Turnover By Hire Date chart showing, for each quarter's hires, the share still employed and the share who left within each length of time](https://mintcdn.com/journeyfront/I0KcpWh6dxv2HCWB/images/reporting/turnover-and-performance/profile-turnover.png?fit=max\&auto=format\&n=I0KcpWh6dxv2HCWB\&q=85\&s=c27aab8a1855087828dd36a284827cfd)

| Chart | What it shows |
| - | - |
| **Turnover By Hire Date** | For each group of hires, the share still employed and the share who left within 30, 60 or 90 days, 180 days, a year, two years, or after two years. A second chart shows the same as counts. |
| **Turnover After Hire Date** | How many people left in each month after they started, for the first two years. |
| **Turnover Time of Year** | How many people left in each calendar month. |

Click a bar to see the employees in it, with their job title, start and end dates, tenure and separation reason.

> [!TIP]
>
> Look at **Turnover After Hire Date** first. If many people leave in the first month or two, the problem is often expectations set during hiring, like how the job, pay or schedule was described, rather than the hires themselves.

## Performance

**Performance By Hire Date** groups your employees by when they were hired and shows the share at each performance rating, from **Exceptional** to **Very Poor**, so you can see whether newer groups of hires do better than earlier ones. Choose the **Performance Type** and **Performance Period**, and use the same dates, period and **Job Field** filter as on Turnover. A second chart shows the same as counts. Click a bar to see the employees in it.

![The Performance By Hire Date chart on a job profile's Dashboard tab, with each quarter's hires split by rating from Exceptional to Very Poor and the share of top ratings growing over time](https://mintcdn.com/journeyfront/I0KcpWh6dxv2HCWB/images/reporting/turnover-and-performance/profile-performance.png?fit=max\&auto=format\&n=I0KcpWh6dxv2HCWB\&q=85\&s=654bf9be7cfe8fb67fc61d5134473144)

## Attributes and activities

**Attributes** ranks the attributes you measure, such as Customer Focus or Problem Solving, by how closely candidates' scores went with how they did after they were hired. **Activities** does the same for the activities in your workflow, such as an assessment or a typing test.

Choose what to compare against in **Top Attributes Correlated with**: **Overall Performance** or **Employee Retention**. For performance, narrow it by **Performance Type**; for retention, by **Separation Reason**. Then set **From Date** and **To Date**.

![A job profile's Dashboard tab on Attributes, compared with Overall Performance, listing each attribute with its correlation, statistical significance, number of employees and a bar that is blue for the strongest relationships and gray for the weaker ones](https://mintcdn.com/journeyfront/I0KcpWh6dxv2HCWB/images/reporting/turnover-and-performance/profile-attributes.png?fit=max\&auto=format\&n=I0KcpWh6dxv2HCWB\&q=85\&s=b88d4fc56abac1474078b77ebd2001b6)

| Column | What it means |
| - | - |
| **Correlation** | How strongly the score goes with the outcome, from 0 (no relationship) to 1 (a perfect one). One star means the result is significant at the 5% level, two stars at the 1% level; stars appear only when there are at least 30 employees. **Insufficient Data** means there's no relationship to show or fewer than 10 employees. |
| **Statistical Significance** | The p-value: how likely a relationship this strong would show up by chance. Smaller is better; under .05 is the usual bar. |
| **Employees** | How many employees have both a score and an outcome. |
| **−** and **+** | Whether the relationship is negative or positive. The bar is blue when the correlation is 0.3 or more, gray when it's weaker. |
| Chart icon | Shows each employee's score against their outcome. |

Hover over the info icon next to an attribute to see its description. See [Attributes](https://help.journeyfront.com/scoring/attributes.md).

> [!TIP]
>
> Look for relationships that are strong, statistically significant and based on plenty of employees. A strong result from a dozen people is a hint to keep watching, not a reason to change your workflow.

## Interview Questions

**Interview Questions** uses the same table for individual interview questions, with an **Attribute(s) Measured** column. Use it to keep the questions whose scores predict performance or retention and to rework the ones that don't predict anything. See [Interview guides](https://help.journeyfront.com/interviews/interview-guides.md).

## Interviewers

**Interviewers** lists each interviewer with the number of **Candidates** and **Interviews** behind their result and their **Accuracy**: how closely their interview scores matched the hire's later performance. 100% means their scores predicted performance exactly. Click the chart icon on a row to see each hire's interview score next to their performance. See [Interview analytics](https://help.journeyfront.com/reporting/interview-analytics.md).

## The company versions

**Attributes**, **Interview Questions**, **Interviewers**, **Turnover** and **Performance** are also in the company **Dashboard** menu. They work the same way across every job profile in your account, which is useful for an account-wide turnover picture. For attributes, interview questions and interviewers, the job profile's own **Dashboard** tab gives a clearer answer, because it compares people in the same role.

## Other views of quality of hire

| Question | Where |
| - | - |
| Do hires from some sources stay longer or perform better? | **Source Effectiveness**, on the **Post-Hire Effectiveness** sheet. See [Source effectiveness](https://help.journeyfront.com/reporting/source-effectiveness.md). |
| How long do each recruiter's hires stay? | **Recruiter Productivity**, on the **Recruiter Outcomes** sheet. See [Recruiter productivity](https://help.journeyfront.com/reporting/recruiter-productivity.md). |
| Do hires who gave a certain screening answer perform better or stay longer? | **Screening Questions**. See [Screening question analytics](https://help.journeyfront.com/reporting/screening-questions-analytics.md). |
| Do hires score higher than applicants overall? | **Candidate Overview**, comparing **Avg Overall Score of Applicants** with **Avg Overall Score of Hires**. See [Applicant volume and pipeline](https://help.journeyfront.com/reporting/candidate-overview.md). |

## Close the loop

Outcome data makes the rest of your hiring smarter:

* **Check what you measure.** Use **Attributes**, **Activities** and **Interview Questions** to keep what predicts success and drop what doesn't.
* **Predict success.** Journeyfront builds predictive models for your roles from your employees' outcomes, such as performance and turnover. Candidates then get a predictive score that can count toward their overall score. See [Predictive models](https://help.journeyfront.com/scoring/predictive-models.md).
* **Coach interviewers.** Use **Interviewers** accuracy to calibrate your panel.

> [!TIP]
>
> Even without a predictive model, start collecting outcome data now. Every hire with a start date, an end date or a performance review adds to the history a model can learn from later. The [behavioral assessment](https://help.journeyfront.com/assessments/behavioral-assessment.md) is made for exactly this.

## FAQ

> [accordion] Why is the Turnover dashboard empty?
>
> It needs employee records with start dates, and end dates for anyone who left. Check that hires are being recorded (hiring a candidate creates the record) and that separations are entered on the employee's **Job Info** tab, synced from your HR system or imported. Also check your date range and filters.

> [accordion] Why does Attributes say Insufficient Data?
>
> A correlation needs at least 10 employees with both a score and an outcome. Widen the date range, or wait until more of your hires have performance reviews or separations recorded.

> [accordion] Why can't I click into a chart?
>
> Seeing the employees behind the charts needs *Performance Access*. Ask your Journeyfront admin to check your security role.

> [accordion] Where do performance scores come from?
>
> From performance reviews your team submits under **Start**, then **Performance Review**, and from performance data imported under **Settings**, then **Import Data**. See [Performance reviews](https://help.journeyfront.com/employees/performance-reviews.md).

> [accordion] Does Journeyfront update end dates from our HR system?
>
> Yes, when your HR system is connected and its employee sync is on. Employees terminated in your HR system get an end date and a separation reason on the next sync. See [HRIS integrations](https://help.journeyfront.com/integrations/hris.md).

## Related

> [card] [Predictive models](https://help.journeyfront.com/scoring/predictive-models.md)
>
> Turn your outcome data into a predictive score for candidates.

> [card] [Job profiles](https://help.journeyfront.com/employees/job-profiles.md)
>
> Where each role's Dashboard tab lives.

> [card] [Performance reviews](https://help.journeyfront.com/employees/performance-reviews.md)
>
> Record how employees perform.

> [card] [Employee records](https://help.journeyfront.com/employees/employee-records.md)
>
> Where start dates, end dates and separations live.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.