Audience
Internal
Displayed Description
Page Type
Article
Greenhouse movement vs activity
where we say “all ATSes including Greenhouse” your GH transition rules are set to stage movement
possible google sheet?
X columns
Dashboard Metrics
Category | Metric Options | Description | Differ by ATS? | Calculation/notes | |
Outreach metrics | |||||
Outreach activity | Outreach actions logged in Gem | no | number of activities people on your team performed (Viewed on LinkedIn, Added to Gem, etc) | ||
Outreach funnel | Prospect engagement with outreach logged in Gem | no | |||
Candidate metrics | |||||
Stage activity
(fka Candidate stage activity) | Uniqueapplicationsthat have entered a stage during the specified timeframe | GH: we use interview & offer data to determine whether candidates have entered those stages
all other ATSes: we go by stage movement | number of applications that have reached a given stage | ||
Time in stage | Time elapsed between an application’s entry into a stage,and some later stage | GH: we use the timestamp of the first interview or scorecard at the stage **will be ca
all other ATSs: we use the actual timestamp of when the app was moved into that stage | average(entered stage X timestamp - previous stage timestamp, over all applications)
• We average this over all the candidates in the pipeline
• This is only reported for “successful” candidates who moved to the next stage - active candidates (still in the stage) and rejected/dropped-out candidates (didn’t make it to next stage) aren’t included.
• Caveat: “Skipped” stages are counted toward this metric with a time of 0. | ||
Passthrough rate | % of applications progressed from a stage to asubsequentstage, inclusive of skipped stages | percentage of applications that progressed from one stage to another
• if a candidate skips past a stage, they’re counted towards having made it to that stage
• waiting candidates are counted in the denominator, but they can be filtered out by setting the date picker to the cohort “rejected/hired in last x days”. Dashboards uses rejected/hired for passthrough rate widgets. | |||
Current pipeline | Unique, active candidates in a stage, at this moment | number/list of candidates currently in a given stage | |||
Job metrics | |||||
Jobs | Includes both open and closed jobs | number of jobs, both open and closed | |||
Job openings | Includes both open and closed openings | this may be unique to GH | number of job openings, both open and closed
• one job can have multiple openings
from GH HC guide: a job refers to a specific position with the same hiring process and a candidate pool. A job opening , on the other hand, refers to the specific individual you are trying to fill. To put it simply, each job contains one or more job openings. | ||
Requisitions
fka Current open requisitions (LEVER) | Includes open, closed, and pending requisitions | ||||
Unfilled headcount
fka Current open headcount (LEVER) | Includes headcount allocated to open requisitions, excluding hires already made | i was thinking of calling the metric Unfilled headcount which we can calculate by taking a difference on total headcount allocated to the requisition and subtracting number of hires made so far (headcountTotal - headcountHired ). | |||
Time open | Average time elapsed since a job opening was opened, excluding closed openings | the average time that open job openings have been open
do we include weekends in any time to blank? I think we include
may need to specify that it’s an average unless you apply group by options? (ex Group by = “Job” separates out each Time open metric). but if one job has multiple opening, I assume we average together the multiple openings within a single job? | |||
Time to fill | Average time elapsed from a job opening’s open to close, for all closed openings | @Kevin L can we give the same definition for all ATSs? | the average amount of time that closed job openings took to get filled
drafts:
time from role open => role close. We calculate it using GH “Job Openings” so for a given job it might be an average across all the openings
The time a job was opened to a time a job was closed. If multiple reqs open for one role, we’ll take the average time open for reqs
JF: something isn’t adding up when i compare Time Open and Time to Fill in own internal dashboards. is the only difference that time to fill only looks at closed/filled job openings? | ||
Interview metrics | |||||
NOTE: update these descriptions for Lever as well, not just GH | Interviews | Includes both completed and scheduled interviews | number (or list) of interviews conducted | ||
Interview time | The sum of time elapsed between interview start time and end time | cumulative time elapsed between interview start and interview end | |||
Interview scorecards | Interview scorecards submitted | number (or list) of scorecards submitted | |||
Time to complete scorecard | Average time elapsed between interview end time, and when interview scorecard was submitted | GH only right now, Lever coming very soon (hopefully by end of Oct) | |||
Scorecard completion rate | Percentage of scorecards submitted of total scorecards assigned | GH only right now, Lever coming very soon (hopefully by end of Oct) |
Dashboard Widget Definitions
Category | Pre-set widget | Differ by ATS? | Logic & ATS Support |
Outreach | |||
Outreach Funnel by month | No | Prospect engagement with outreach logged in Gem (all ATSes) | |
Outreach activity | No | Outreach actions per recruiter (all ATSes) | |
Prospects added to Gem | No | New prospects added to Gem (all ATSes) | |
Open rate by month | No | % of outreach opened (all ATSes) | |
Reply rate by month | No | % of outreach that received a reply (all ATSes) | |
Interested rate by month | No | % of outreach that received an interested reply (all ATSes) | |
Hiring | |||
Total hires | No | Candidates that have accepted an offer (Greenhouse only)
Candidates that have moved to the “Hired”stage (all ATSes including Greenhouse) | |
Hires by month | No | Candidates that have accepted an offer (Greenhouse only)
Candidates that have moved to the “Hired”stage (all ATSes including Greenhouse) | |
Average time to hire | No | Sum of the average time in stage, for each stage, inclusive of both hired and rejected candidates (all ATSes) | |
Offer acceptance rate | Yes - stage movement/stage activity decision available for GH | %of candidates that accepted, of candidates that received an offer (Greenhouse only)
% of candidates moved to “Hired”,of candidates that received an offer (all ATSes including Greenhouse) | |
Offer decline reasons | Yes - “archive reason” for Lever | Breakdown of archive reasons (Lever only)
Breakdown of offer decline reasons (all other ATSes) | |
Hires by source type | Yes | Candidates that have accepted an offer (Greenhouse only)
Candidates that have moved to the “Hired”stage (all ATSes including Greenhouse) | |
Candidates with pending offers | No | Candidates that received an offerduring the specified timeframe, but have not yet accepted or rejected the offer (all ATSes) | |
Candidate count by stage | Yes - stage movement/stage activity decision available for GH | Current number of candidates with stage activity in each stage (Greenhouse only)
Current number of candidates in each stage (all ATSes including Greenhouse) | |
Jobs | |||
Current open jobs | Excludes closed jobs | ||
Current job openings | Excludes closed openings | ||
Current requisitions (LEVER) | Excludes closed and pending requisitions | ||
Unfilled headcount (LEVER) | Includes headcount allocated to open requisitions, excluding hires already made | ||
Time open by recruiter
Fka: Job time open by recruiter | Average time elapsed since a job opening was opened | ||
Average time to fill | Average time elapsed between when a job opening is opened to closed, across all closed openings (evenif not filled) | ||
New: “Median time to fill” | Median time elapsed between when a job opening is opened to closed, across all closed openings (evenif not filled) | ||
Interviews | |||
Interviews by week | Includes both completed and scheduled interviews | ||
Interview time by department | Sum of time elapsed between interview start time and end time | ||
Scorecard decisions | Breakdown of scorecard decisions of submitted interview scorecards | ||
Average time to complete scorecard | Average time elapsed between the interview end time, and interview scorecard was submitted | ||
Scorecard completion rate by interviewer | % of scorecards submitted of total interview scorecards | ||
Diversity | |||
Hires by gender | Candidatesthat have accepted an offer (Greenhouse only)
Candidates thathave moved to the “Hired”stage (all ATSes including Greenhouse) | ||
Hires by race/ethnicity []
• note there’s a period in this widget template that shouldn’t be here | Candidates that have accepted an offer
Candidates that have moved to the “Hired”stage | ||
Hires by gender | Candidates that have accepted an offer
Candidates that have moved to the “Hired”stage | ||
Hires by race/ethnicity | Candidates that have accepted an offer
Candidates that have moved to the “Hired”stage | ||
Prospects, by race/ethnicity
(fka First messages sent, grouped by race/ethnicity) | New prospects added to Gem | ||
Prospects, by gender
(fka First messages sent, grouped by gender) | New prospects added to Gem | ||
Peer benchmarks | |||
Average time to hire | Sum of the average time in stage, for each stage, inclusive of both hired and rejected candidates | ||
Offer acceptance rate | %of candidates that accepted, of candidates that received an offer (Greenhouse only)
% of candidates moved to “Hired”,of candidates that received an offer | ||
Hires by gender | Candidates that have accepted an offer
Candidates that have moved to the “Hired”stage | ||
Hires by race/ethnicity | Candidates that have accepted an offer
Candidates that have moved to the “Hired”stage |
Have any issues or questions on this topic? Please feel free to contact your dedicated Gem Customer Success Manager directly or our Support team at support@gem.com.