Behavior | What happens |
Candidate carried over from a prior open period | Excluded from the average and shown as NA — Recruiterflow won't guess which open window the scouting speed belongs to. |
Job Role has no assigned user | The hire is bucketed as NA in both the bar graph and table rather than dropped. |
Candidate moved out of Hired after being counted | Removed from all Time to Scout calculations on the next data refresh. |
Candidate has no hire date | Excluded entirely — there's no reliable qualifying event to measure against. |
No Group By applied | A single bar shows the overall average Time to Scout across all qualifying hires in the selected period. |
Multi-select custom field grouping | A hire can appear in more than one group if the custom field has multiple values selected. |
Things to know
Time to Scout only ever looks backward from a hire — it can't tell you anything about candidates still in an open pipeline.
Job-level Time to Scout is always an average, even for a job with a single hire.