Weekly Recruiting Report Template: Metrics That Lead to Decisions

A weekly recruiting report should show movement through the hiring process, where candidates are waiting, what the recruiter has learned, and which decisions the hiring team needs to make. Activity totals are useful only when they help explain progress or a problem.

A report that says “150 messages sent” does not tell a manager whether the search is on track. Add the audience, responses, qualified conversations, and reasons candidates declined. That context gives the team something it can act on.

Define the stages before counting them

Agree what counts as sourced, contacted, screened, presented, interviewed, offered, and hired. Decide whether the report shows unique candidates entering a stage during the week or the total currently in that stage.

Those are different views. A weekly flow report measures movement. A current pipeline view shows the work still open. Label both rather than combining them into one unexplained funnel.

Also define the unit: a person, an application, or a person-role pair. One candidate considered for two roles should not accidentally look like two unique people in a company-wide total.

Use this report structure

Section	What to include	Why it matters
Search status	Role, brief version, reporting period	Establishes scope
Stage movement	Unique entries into each stage this week	Shows progress
Open pipeline	Candidates currently at each stage	Shows remaining work
Waiting time	Stage entry date and owner	Exposes delays
Candidate feedback	Specific, anonymized themes	Explains friction
Decisions required	Action, decision owner, due date	Turns reporting into work

Keep personal details in the authorized recruiting system. A broadly circulated status report rarely needs candidate phone numbers, resumes, or private interview notes.

Calculate conversion rates with matching groups

A screening-to-interview rate can be calculated as candidates from a defined screened group who reach interview divided by the number in that screened group. State the group and observation window.

For illustration, if 12 of 40 screened candidates eventually reach interview, the rate is 30%. That example is arithmetic, not an Alivio result or an industry benchmark.

Dividing this week’s interviews by this week’s screens may produce a misleading rate if the interviews came from earlier weeks. Where that distinction matters, use cohorts or clearly label the number as an operational ratio rather than a true conversion rate.

Explain a bottleneck before prescribing a fix

Suppose qualified candidates reach the interview stage but repeatedly wait for scheduling. More sourcing might enlarge the queue. The report should identify the scheduling owner and ask for available slots.

If many relevant candidates decline the opening, summarize their stated reasons. Keep observed feedback separate from your interpretation. “Four candidates cited the fixed evening schedule” is more useful than “the market is difficult.” Use actual numbers only when your records support them.

End with a short decision list. Every request should name the person who can resolve it and the date the search needs the answer.

Which recruiting metrics should executives see?

Show progress against priority roles, material delays, offer status, and decisions that require executive action. Put detailed activity in a supporting view for the recruiting team.

Should a weekly report include a predicted hire date?

Only if the assumptions are visible. Separate a planning estimate from a commitment, and update it when candidate availability or internal approvals change.

Read Alivio’s guide to reducing time to hire for broader process questions. To discuss ongoing recruiting support, explore Recruitment-as-a-Service.