Recruiter KPI dashboard template: one screen per desk, built in a spreadsheet

A recruiter KPI dashboard should fit on one screen and answer three questions: is the recruiter doing the work that leads to placements this week, is there enough live pipeline to hit the month, and did it turn into placements and fees. That gives you three rows of about ten numbers, each shown against a target worked out from your own desk's history, with a simple color rule. Build it in a spreadsheet from a single log of events, and review it weekly, not daily.

This page is the layout and the build. The definitions and formulas for each metric are in recruiting agency metrics, and the written commentary that goes alongside the numbers is in the recruiter weekly report template.

The dashboard layout

RECRUITER: [Name]    DESK: [Specialism]    WEEK OF: [date]    MONTH TO DATE: [n] of [n] days

ROW 1 — INPUTS (this week)              Actual  Target  Status
  Client conversations (BD)               [ ]     [ ]     [ ]
  New job orders taken                    [ ]     [ ]     [ ]
  Candidate screens completed             [ ]     [ ]     [ ]
  Submittals sent                         [ ]     [ ]     [ ]

ROW 2 — PIPELINE (right now)
  Candidates at first interview           [ ]     [ ]     [ ]
  Candidates at final interview           [ ]     [ ]     [ ]
  Offers out                              [ ]      -      [ ]
  Accepted, not yet started               [ ]      -      [ ]

ROW 3 — OUTCOMES (month to date)
  Placements (starts)                     [ ]     [ ]     [ ]
  Fees / gross margin                     [ ]     [ ]     [ ]
  Fall-offs                               [ ]      -      [ ]

RATIOS (rolling 90 days)
  Submittal → interview      [ ]%     Interview → offer    [ ]%
  Offer → accept             [ ]%     Accept → start       [ ]%

Row 1 is what the recruiter controls this week. Row 2 is the pipeline that will become next month's placements. Row 3 is the result. A recruiter with strong inputs and a thin pipeline has a conversion problem; one with a full pipeline and no starts has a closing problem. The layout is built to show which.

Choosing the numbers

If your desks are contract, replace "fees" with gross margin and add contractors on assignment and extensions. If a recruiter works only delivery and not business development, drop the client conversation line rather than leaving it permanently red.

Setting targets from your own data

Work backwards from the outcome, using your desk's own conversion rates over the last two or three quarters. The figures below are an invented example, not a benchmark.

Two cautions. First, conversion rates calculated on a handful of placements are noisy; use a longer period, and see pipeline conversion rates by stage for how to count them on a cohort. Second, a target for submittals is only useful if quality holds. If the submittal-to-interview rate drops when the volume target goes up, the target is producing worse submittals, not more placements.

Building it in a spreadsheet

Three tabs. Everything on the dashboard is calculated from the log, so no one types numbers into the dashboard itself.

Tab 1: Log

One row per event. Export it from your ATS weekly, or keep it by hand if you must. Put the fee (or margin) on the start row, so revenue is counted when the placement actually starts.

Date | Recruiter | Client | Role | Candidate | Event | Value
2026-09-29 | Sam | Northfield | Payroll Mgr | C-1042 | Submittal |
2026-09-30 | Sam | Northfield | Payroll Mgr | C-1042 | Interview 1 |
2026-10-02 | Sam | Harbor Co | AP Lead | — | Job order |
2026-10-03 | Sam | Northfield | Payroll Mgr | C-1042 | Offer |
2026-10-03 | Sam | Northfield | Payroll Mgr | C-1042 | Accepted |
2026-10-20 | Sam | Northfield | Payroll Mgr | C-1042 | Start | 19000

Use a fixed list of event names (a dropdown) so that "Submittal," "submittal" and "Submitted" do not end up counted separately.

Tab 2: Targets

Recruiter | Metric | Weekly target | Monthly target
Sam | Submittal | 8 | 30
Sam | Job order | 1 | 4
Sam | Placement | - | 2

Tab 3: Dashboard

Each number is a count of the log, filtered by recruiter, event and date range. In Excel or Google Sheets, with the recruiter's name in B1 and the week's start date in B2:

Submittals this week:
=COUNTIFS(Log!B:B, $B$1, Log!F:F, "Submittal",
          Log!A:A, ">="&$B$2, Log!A:A, "<"&$B$2+7)

Fees month to date:
=SUMIFS(Log!G:G, Log!B:B, $B$1, Log!F:F, "Start",
        Log!A:A, ">="&EOMONTH($B$2,-1)+1, Log!A:A, "<="&TODAY())

Status (traffic light), with actual in C5 and target in D5:
=IF(C5>=D5, "Green", IF(C5>=0.7*D5, "Amber", "Red"))

Pipeline counts (row 2) need the latest stage per candidate rather than a count of events. The simplest way is a helper column on the log that marks each candidate's most recent row, then count only those. If that gets complicated, take the pipeline snapshot from the ATS each Friday and paste it in.

The 70% amber line is an example threshold; pick one your team agrees is fair and keep it the same for everyone.

A filled example

An invented week for one recruiter, to show how the rows read together:

Read across: delivery is healthy this week, but no new job orders came in and client conversations were light. In four to six weeks, this desk will run out of roles to submit to. The conversation in the one-to-one is about business development time, not submittal volume.

How to review it

In the weekly one-to-one, start with row 3 and work up. "One placement against two" leads to "one offer out" leads to "four at first interview, which ones are real?" That is a conversation about specific candidates, which is more useful than a conversation about effort. The pipeline names themselves are better covered in a short daily recruiting team standup than in a dashboard.

Mistakes that make dashboards useless

• Too many numbers. If a recruiter cannot say what their three red lines are without looking, the dashboard has too much on it.
• Activity targets without a quality check. Pair every volume number with the conversion rate that follows it.
• Ranking desks on raw placements. Roles differ in difficulty. See recruiter productivity metrics for fairer comparisons.
• Targets nobody can trace. If a recruiter asks "why eight submittals?", you should be able to show the calculation.
• Hand-typed numbers. They drift from the ATS within a month. Count from the log.
• Judging a week. One week is noise. Act on a trend across four or more.