Skip to main content

Fill Skip Overs vs. Actual: How Recruiterflow Counts Stage Movements

Understand the difference between Fill Skip Overs and Actual counting modes, and how your choice affects pipeline reporting across Recruiterflow.

Written by Abhishek Satija

When a candidate skips stages in your pipeline, Recruiterflow needs to know whether to count those skipped stages or only the ones the candidate actually entered. That's what the Fill Skip Overs vs. Actual setting controls — and it affects how data appears across your job pages, dashboard, and reports.

What this setting does

This is a workspace-level default (set by Admins in Workspace Settings) that determines how candidate stage movements are counted everywhere in Recruiterflow.

  • Fill Skip Overs: When a candidate jumps from an early stage to a later one, every stage in between is counted as if the candidate passed through it. You get a fuller view of your pipeline.

  • Actual: Only stages the candidate physically entered are counted. Skipped stages show zero movement for that candidate.

How it plays out — a real example

Say your pipeline has three stages: Sourced → Recruiter Screen → Client Submission. A candidate moves directly from Sourced to Client Submission, bypassing Recruiter Screen entirely.

  • With Fill Skip Overs: Recruiterflow counts all three stages, including Recruiter Screen. The pipeline shows the candidate progressing through every step.

  • With Actual: Only Sourced and Client Submission are counted. Recruiter Screen shows zero movement for this candidate — because they never entered it.

Where this setting has an impact

Changing your default between Fill Skip Overs and Actual affects several areas:

  • Job and Company pages: Submission counts displayed on each job and company page reflect your chosen mode.

  • Dashboard Overview Widget: Stage movement summaries on the dashboard follow the same default.

  • Stage Movement Breakdown Report: Shows candidate flow across stages based on your counting mode.

  • Milestone Report: Key milestone counts (like number of submissions or interviews) are affected.

  • Custom pipeline reports: Any report you've built that involves job pipeline stages will reflect your default.

Which one should you use?

Choose based on what you want your data to show:

  • Use Fill Skip Overs if you want a broad view of how candidates move through your pipeline, even when they skip steps. Good for agencies that treat the pipeline as a funnel rather than a rigid sequence.

  • Use Actual if you want precise counts — only stages a candidate genuinely entered. Better for detailed reporting and performance tracking.

Note: This is an Admin-only setting in Workspace Settings and applies across your entire workspace.

Things to know

  • Changing this default updates how data is displayed going forward — it does not retroactively recalculate historical reports.

  • If your reports look inconsistent, check whether this setting was changed recently.

  • Individual report views may let you toggle between modes independently, regardless of the workspace default.

Did this answer your question?