Create a Recruitment Funnel Dashboard From Excel or CSV

Upload applicant data to visualize recruitment stages, source performance, recruiter workload, role pipelines, offer acceptance, and hiring outcomes.

Supports structured .csv and .xlsx files. Public examples use synthetic data. Review VizMint's current privacy and retention policy before uploading sensitive information.

Drop your CSV or Excel file here to generate instant insightsDrag and drop your file here, or click to browse
Demo

See recruitment exports become funnel KPIs and charts

Use the fixed preview below to switch between the source spreadsheet and a dashboard sample. Open the full demo in a new tab for every KPI and chart used in the recruitment funnel workflow.

Recruitment Funnel Dashboard

Interactive preview from the sample recruitment dataset

Open

Switch preview

Total Records

48

rows in sample

Total Total Time to Hire Days

14,992

sum of Total Time to Hire Days

Total Applicants

5,581

sum of Applicants

Total Time to Hire Days vs Applicants

Grouped by Date

Full dashboard with all KPI details and 6 charts is on the demo page.

Open full demo

What the live demo includes

  • Source rows with applicant counts, stage breakdowns, recruiter, source, and department fields
  • Auto-detected KPI cards for applicants, hires, offers, and conversion rates
  • Recruitment funnel and stage-conversion charts from the sample
  • Source performance and recruiter workload comparison views
  • Applications-over-time trend and role pipeline views
  • Switch between Spreadsheet and Dashboard tabs in the live preview
  • Open the full demo in a new tab for all generated chart types

The sample tracks 4 sources across 12 months, with 5,581 applicants and 535 hires cumulatively.

Sample results: App→Screen 61.6%, Interview→Offer 41.9%, Offer→Hire 71.7%, overall 9.6% conversion (535/5,581).

Why This Workflow Is Useful

The Decision It Supports

See where candidates drop out and how time-to-stage varies by role, source, and recruiter.

Why the Result Can Be Trusted

Workforce reporting depends on consistent definitions for headcount, exits, transfers, contractors, and reporting dates. Public examples use privacy-safe synthetic records.

Example Dataset

The sample covers 4 sources and 4 recruiters across 12 months. Overall conversion is 9.6% with an average 28-day time to hire per candidate.

Why VizMint is different from a generic template

  • Begin with the structured file the user already has.
  • Explain required fields before upload and show detected mapping after upload.
  • Display formulas, reporting scope, exclusions, and missing-field behaviour beside the result.
  • Use one synthetic file across the download, preview, expected results, screenshot, and demo.
  • Connect headline metrics to the records or grouped table that explain them.
  • State plan, export, privacy, integration, and automation details only when they are available in the current product.

The workflow is designed around consistent workforce definitions, privacy-safe proof, and auditable counts.

Turn Your Data Into a Clear Recruitment Funnel Dashboard

Recruitment reporting depends on a consistent applicant-stage model. This workflow separates current-stage reporting from stage-history analysis because time in stage and stage-to-stage velocity cannot be reconstructed reliably from a simple current-stage export.

The result brings the most important metrics, trends, and exceptions into one view, while keeping the supporting records available for review.

Use this page to answer questions such as:

  • How many applicants are in each stage?
  • Which sources produce qualified candidates and hires?
  • Where does the funnel lose applicants?
  • Which recruiters or roles have the largest pipeline?
  • What is the offer acceptance rate?
  • See How the Source File Becomes a VizMint Output

    Use the downloadable sample to follow the source rows, field mapping, validation, and final output as one reproducible workflow.

    Before: Structured Source Data

    5 of 48 rows

    The source preview highlights the exact columns and representative rows used by the workflow.

    DateQuarterSourceRecruiterTotal Time to Hire Days
    2025-07-01Q3 2025LinkedInMaya Chen319
    2025-07-01Q3 2025ReferralNoah Smith336
    2025-07-01Q3 2025Careers PagePriya Das217
    2025-07-01Q3 2025Job BoardJordan Lee136
    2025-08-01Q3 2025LinkedInMaya Chen402.4

    After: Generated VizMint Output

    The finished output includes the KPI cards, charts, tables, and report views described below.

    Total Applicants5,58112 months · 4 sources
    Total Hires5359.6% overall conversion
    Offer-to-Hire Rate71.7%535 of 746 offers

    Total Time to Hire Days vs Applicants

    Grouped by Date

    Columns to Include in Your File

    VizMint works best when every column has one clear heading and each row represents one consistent record. Fields that are not available should not be invented; dependent outputs should be hidden or clearly marked as unavailable.

    Columns to include in your file

    Applicant ID

    Requirement
    Required
    Example
    ID-10042
    Purpose
    Needed for the core workflow

    Application Date

    Requirement
    Required
    Example
    2026-06-01
    Purpose
    Needed for the core workflow

    Current or Final Stage

    Requirement
    Required
    Example
    Qualified
    Purpose
    Needed for the core workflow

    Source

    Requirement
    Recommended
    Example
    LinkedIn
    Purpose
    Adds an important comparison or breakdown

    Recruiter

    Requirement
    Recommended
    Example
    Jordan Lee
    Purpose
    Adds an important comparison or breakdown

    Role

    Requirement
    Recommended
    Example
    Product Manager
    Purpose
    Adds an important comparison or breakdown

    Stage Date

    Requirement
    Recommended
    Example
    2026-06-01
    Purpose
    Adds an important comparison or breakdown

    Department

    Requirement
    Optional
    Example
    Sales
    Purpose
    Adds detail when present

    Location

    Requirement
    Optional
    Example
    North
    Purpose
    Adds detail when present

    Offer Date

    Requirement
    Optional
    Example
    2026-06-01
    Purpose
    Adds detail when present

    Hire Date

    Requirement
    Optional
    Example
    2026-06-01
    Purpose
    Adds detail when present

    Final Outcome

    Requirement
    Optional
    Example
    Hired
    Purpose
    Adds detail when present

    What VizMint Can Generate

    Applicants

    5,581 applicants across 48 source-month records in the sample scope.

    Applicants by Stage

    Screen: 3,437, Interview: 1,779, Offer: 746, Hired: 535.

    Stage Conversion

    App→Screen 61.6%, Screen→Interview 51.8%, Interview→Offer 41.9%.

    Offers

    746 offers extended across the sample scope.

    Hires

    535 hires with an overall 9.6% applicant-to-hire conversion.

    Rejections

    4,835 rejections recorded across all source-month records.

    Offer Acceptance Rate

    71.7% of offers resulted in hires (535 of 746).

    Source-to-Hire Conversion

    Breakdown by source when the source field is present: 4 sources in the sample.

    Charts and Visualizations

    Charts and visualizations

    Recruitment Funnel

    Required Fields
    Stage counts, applicants
    Business Question
    Shows recruitment funnel for the selected records and reporting scope.

    Applications Over Time

    Required Fields
    Application date, applicant counts
    Business Question
    Shows applications over time for the selected records and reporting scope.

    Source Performance

    Required Fields
    Source, applicant counts, hired counts
    Business Question
    Shows source performance for the selected records and reporting scope.

    Role Pipeline

    Required Fields
    Role, stage counts
    Business Question
    Shows role pipeline for the selected records and reporting scope.

    Recruiter Workload

    Required Fields
    Recruiter, applicant counts, stage counts
    Business Question
    Shows recruiter workload for the selected records and reporting scope.

    Stage Conversion

    Required Fields
    Stage names, stage counts
    Business Question
    Shows stage conversion for the selected records and reporting scope.

    Offer Acceptance

    Required Fields
    Offers, hires, withdrawn
    Business Question
    Shows offer acceptance for the selected records and reporting scope.

    How to Use This Workflow

    STEP 1

    Upload the File

    Upload the workflow-specific sample or a user file with clear headers and one record per row.

    STEP 2

    Choose the Worksheet

    Select the correct worksheet when the workbook contains multiple sheets.

    STEP 3

    Confirm Field Mapping

    Confirm the detected header row and field mapping before generation.

    STEP 4

    Review the Preview

    Review the data preview, exclusions, and validation warnings.

    STEP 5

    Generate the Output

    Generate the dashboard, chart, report, presentation, or answer.

    STEP 6

    Review Calculations

    Review KPI values, calculations, charts, and source traceability.

    STEP 7

    Save or Export

    Save, share, or export using capabilities available on the active plan.

    How the Calculations Work

    How the calculations work

    Stage Conversion

    Formula or Method
    Applicants reaching next stage ÷ eligible applicants in previous stage × 100
    Required Fields
    Stage counts or stage-history records
    Important Rule
    Accurate history requires stage dates or stage-history records.

    Offer Acceptance

    Formula or Method
    Accepted offers ÷ total valid offers × 100
    Required Fields
    Offers, hires, withdrawn, rejected offers
    Important Rule
    Define cancelled and withdrawn offers.

    Time to Hire

    Formula or Method
    Hire date − application date
    Required Fields
    Hire date and application date
    Important Rule
    Requires both dates and a completed hire outcome.

    What This Workflow Requires and Does Not Automatically Do

    • Current-stage files cannot provide complete time-in-stage history.
    • VizMint should not be described as an applicant tracking system.
    • Stage labels require normalization.
    • Public examples must use synthetic applicant data.
    • Export, privacy, and plan limits should only be promised when confirmed in production.

    Common Data Problems and How to Fix Them

    Common data problems and how to fix them

    Duplicate applicants

    Recommended Fix
    Use a stable identifier, review repeated rows, and remove or reconcile duplicates before calculation.

    Inconsistent stage names

    Recommended Fix
    Standardize labels so the same entity or category uses one consistent value.

    Missing stage dates

    Recommended Fix
    Add the missing field when available; otherwise hide dependent metrics and explain the limitation.

    Unnormalized source values

    Recommended Fix
    Document the rule, standardize the source data, and validate the corrected result before generation.

    Private candidate data

    Recommended Fix
    Use consistent date formats and align records to the same reporting period.

    Who This Workflow Is For

    • Recruitment teams
    • HR leaders
    • Talent acquisition managers
    • Hiring managers
    • Recruitment agencies

    Common Use Cases

    • Weekly hiring review
    • Source analysis
    • Role pipeline review
    • Recruiter workload planning
    • Offer tracking

    Why Use VizMint for This Workflow?

    • Start with an existing spreadsheet or export instead of rebuilding the data in a complex analytics system.
    • See which fields are required before generating the output.
    • Review formulas, exclusions, and missing-field behaviour transparently.
    • Refresh the analysis with a newer file instead of manually updating every chart.
    • Move from raw rows to a clear report that is easier to review with colleagues or clients.

    Share and Export Your Results

    Available sharing and export options depend on the live VizMint plan. Publish only capabilities confirmed in production, such as saving the analysis, downloading images or PDF files, exporting PowerPoint, creating private links, refreshing a saved report, or removing branding on eligible plans.

    Do not hardcode plan limits, file-size limits, privacy promises, or export features until product and billing owners confirm them.

    Recommended Supporting Articles

    • • How to Build a Recruitment Funnel Dashboard
    • • Headcount Reporting by Department, Role, and Location
    • • Employee Retention vs Turnover

    Frequently Asked Questions

    Choose the Right Approach

    Excel alone is enough when

    • The dataset is small and the report is genuinely one-off.
    • One spreadsheet owner can safely maintain formulas, pivots, and ranges.
    • The audience does not need a repeatable upload-to-output workflow.

    A traditional BI tool is a better fit when

    • The organization needs governed models, live connectors, row-level security, and enterprise distribution.
    • A data team can maintain transformations and a semantic layer.

    VizMint is a strong fit when

    • The starting point is a structured CSV or Excel file.
    • The user needs a guided workflow without manually building every formula and chart.
    • Clear field requirements, transparent calculations, reproducible samples, and shareable outputs matter.

    VizMint analyzes exports; it does not replace the accounting, CRM, help-desk, HR, warehouse, advertising, or project-management system that produced them.

    Ready to Create Your Recruitment Funnel Dashboard?

    Upload a structured CSV or Excel file to generate the supported metrics, charts, and comparisons for this workflow.