Most recruitment teams hold some kind of weekly meeting about open vacancies, and many of those meetings run on memory. Each recruiter tells how things are going, the liveliest story gets the attention, and the candidates who quietly stalled are not mentioned at all. A weekly pipeline review works better when it is run straight from your Applicant Tracking System: the same short set of lists every week, drawn from recorded data, with every agreed action written back on the vacancy or the candidate before the meeting ends. Thirty minutes is usually enough, and the pipeline is in better shape afterwards than before.
What the review looks at differs per segment. Recruitment agencies want to see which client submissions are waiting for an answer and which vacancies have no fresh candidates. Staffing desks need to know which shifts or assignments for the coming week are not yet covered by available, checked candidates. Secondment teams look at assignments that end soon without a follow-up. Executive search firms check whether each search is moving at the pace promised to the client. In-house recruitment teams look at which hiring managers still owe feedback and which roles are behind their target date.
Why a review from memory falls short
- Recruiters talk about the vacancies that are going well and skip the ones that are stuck
- Candidates waiting on a client or hiring manager are forgotten, because nobody owns the follow-up
- Agreements made in the meeting end up in someone’s notebook and are lost by the end of the week
- Team leads cannot compare one week with the next, because each meeting looked at different information
A useful review looks at the same lists every week, so that what changed stands out on its own.
Five lists to review every week
- Vacancies behind their target fill date — roles where progress does not match the target fill date set on day one
- Candidates stuck too long in a stage — the same aging list the system uses for its alerts, oldest first
- Candidates without a next action — active candidates with no next-action date, or with one that has already passed
- Overdue answers — client submissions and hiring-manager feedback requests that are past their deadline
- Vacancies without activity or owner — open roles with no recorded activity in the past week, or without a single owner
Save each list as a fixed view or report in the Applicant Tracking System, filtered the same way every week, so nobody has to prepare slides or spreadsheets. If a list is empty, say so and move on.
How to run the thirty minutes
- Put the shared views on screen; personal notes and side spreadsheets stay closed
- Work through the lists one by one, oldest item first, and let the owner of each vacancy say in one sentence what happens next
- Record every agreed action straight away in the Applicant Tracking System, as a next action with a date and a person, rather than in separate meeting minutes
- Decide what to stop: a vacancy that will not be filled is closed with a documented close reason, and a candidate who is no longer in play is rejected or marked as withdrawn with a reason
- End with the items that need help from the team lead or another recruiter, and record who takes them over
What the review is not for
The weekly review is not a ranking of recruiters. Comparing people on how many candidates they moved this week invites them to move candidates early to look busy, and that spoils the pipeline data for everyone. It is also not the place to discuss one candidate in depth; that belongs in the conversation around that vacancy. And keep the set of lists stable for at least a quarter. Adding a new list every week makes it impossible to see whether things are improving.
Check whether the review is working
The Applicant Tracking System can show the answer from its own records: how many items were on each list at the start of each review, how many of last week’s agreed actions were completed by their date, and how the number of vacancies behind their target date develops over the weeks. Use the same discipline as in reliable time-to-fill reporting: actual counts from your own data, the number of vacancies or candidates behind each figure, a note whenever a filter changes, and no general benchmarks you cannot verify.
Where artificial intelligence may help — and where it must not
Artificial intelligence may prepare a short summary per vacancy of what changed since last week, point out items that have appeared on the lists several weeks in a row, or turn what a recruiter says in the meeting into a draft next action that the recruiter checks. It must stay secondary. Artificial intelligence does not replace recruiters, does not decide which vacancies to close or which candidates to reject, and does not set the team’s priorities. The Applicant Tracking System holds the lists and the record; the team makes the decisions.
A practical week to get started
- Build the five saved views in the Applicant Tracking System together with the team lead, using filters everyone agrees on
- Check that every open vacancy has an owner and a target fill date and every active candidate has a next-action date, otherwise the lists will be incomplete
- Book a fixed thirty-minute slot on the same day each week
- Hold the first review and record every action in the Applicant Tracking System before anyone leaves
- Start the second review by opening last week’s actions and checking which ones were done
Expect the first review to show more stalled items than anyone thought. That is the point; after a few weeks the lists get shorter.
Review the pipeline, then record the decision
A weekly review only helps when it looks at recorded data and ends with recorded actions. Use the same lists every week, decide per item what happens next, and write it back where the whole team can see it. Then explore the product or book a demo — we walk through saved pipeline views and a weekly review in BoldATS for your segment.