Skip to main content

Reporting+ Applicant Journey

Adam Kavanagh avatar
Written by Adam Kavanagh
Updated over a month ago

What is Applicant Journey?

Applicant Journey is part of Reporting +. It lets you see how candidates move through your recruitment process and measure the time it takes to progress between stages. You can also count how many candidates entered a specific stage over a chosen period. You can build your own reports using this model or you can use the additional 23 predefined reports available.

What You Can Do:

  • Measure time between milestones (e.g., Unassessed → Hired).

  • Measure time between progression stages (e.g., Video Screening → Formal Offer).

  • Count how many candidates entered a stage (Single Stage).

  • Filter reports by vacancy or timeframe.

Switching Reporting Models

To use Applicant Journey:

  • Create a New report

  • Open Reporting Models → select Applicant Journey.

Key Things to Know

  • You can only measure time between two points (start and end).

  • This model counts applications only — no personal candidate details are included.

  • Stage names must be used exactly as they appear in Talos.

Creating Reports

Time Between Milestones

  1. Add Time field (Average Hours/Days).

  2. Set filter: Event Type = Milestone (essential – without this, results may be wrong).

  3. Choose Start Event (e.g., Unassessed).

  4. Choose End Event (e.g., Hired).

  5. (Optional) Filter by End Event: Date to choose a timeframe (e.g., last year).

Time Between Progression Stages

  • Same setup as milestones, apart from:

    • Event Type = Progstage

    • Start/End Events use Progression Stage names (must match exactly).

Single Stage Reports

  • Shows how many candidates entered a stage in a specific period.

  • Setup is similar to other reports, apart from:

    • Event Type = Single Stage

    • Only Start Event is needed.

    • Filter by Start Event Date to define the timeframe.

Report From Vacancy Created Date

  • Allows you to measure metrics from when a vacancy was created

  • Setup is similar to other reports, apart from:

    • Event Type = Milestone

    • Start Event must be Start Event = Vacancy Posted

    • End Event must be End Event = Milestone

    • (Optional) Filter by End Event: Date to choose a timeframe (e.g., last year).

Adding Applicant Journey Reports to Dashboards

  • Like any report, you can add these reports to your dashboards

  • If you are filtering on your dashboard, reports using this model will require different filters than reports that use the Applicant Core model. When you select to Add a Filter, you will see a dropdown called “Applicant Journey” which shows all filterable fields.

Reporting Intelligence – Applicant Journey (Beta)

We’re excited to introduce the Applicant Journey Model in Reporting Intelligence. With Tali, you can quickly create reports like time to hire and time to assess—helping you get insights in seconds.

Switching Models in Tali

To use the Applicant Journey Model:

  1. Open Tali within the top right-hand corner of Talos:

  2. Select the dropdown (it may currently show Applicant Core):

  3. Switch to Applicant Journey.

Example Questions You Can Ask

Here are some ways you can use Applicant Journey today:

Milestones

  • “What is my average time to hire?”

  • “What’s the average time between Unassessed and Shortlist?”

  • “Compare time to hire this year vs. last year.”

  • “How long in hours is it taking to assess candidates?”

Progression Stages

  • “What’s the average time between 1st Interview and Final Interview?”

  • “How long does it take to move candidates from Video Screening to Offer?”

Single Stages

  • “How many applications entered Video Screening last year?”

  • “How many candidates reached 1st Interview in Q1?”

Important Note

Because progression stages are more dynamic than milestones, Tali is still learning to interpret them. If you ask for reports on progression stages, or the number of candidates in a stage, we recommend double-checking the results to make sure they reflect your data accurately.

Did this answer your question?