The Mid-Loop Recruiter Update Reference, One Row per Status Message

Use this reference when a recruiter sends a vague update in the middle of an interview loop: "still interviewing others", "the role is on hold", "we'd like to add a round", "waiting on feedback", or nothing at all. It covers the stretch from the first screen to the final round, before any offer or rejection call. Each row lists the internal hiring states the message usually stands for, the evidence that separates them, the one question to send back, and the tracker status to set with a dated recheck.

When to nudge is a separate job, covered in the follow-up cadence guide. Offer-stage calls are covered elsewhere too. This page turns a single message into a status change you can act on while you run several loops in parallel.

What a between-rounds update is, and what sits behind it

A between-rounds update is any message from the hiring side, or any silence, after your first screen and before an offer or rejection call. The words are only the top layer. Under them sit the sender's workload, the state of the panel's feedback, the requisition's state in the hiring system, and whoever owns the decision.

Terms used throughout:

• Loop: the full sequence of interviews for one role at one company.
• Requisition (req): the approved, budgeted opening that the hiring system tracks. Your loop exists because a req exists.
• Scorecard: an interviewer's written evaluation of you, submitted into the hiring system after a round.
• Hold: a req that is paused but not closed. Greenhouse lists "the job is placed on hold while your organization priorities other roles" as a reason for closing a job.
• Freeze: a hiring stop that applies across the organization. Workday-linked requisitions in Greenhouse carry a status that "must be one of open, closed, frozen, or filled".
• Live / At risk / Parked: the three tracker statuses this guide assigns. Live means you are actively preparing. At risk means you are preparing but expect a negative outcome. Parked means you have stopped spending time on the loop until its recheck date.

Who is actually sending the message

The sender's role tells you how close the message is to the decision. In Refolk's index of professional profiles, recruiters far outnumber the coordinators who handle scheduling:

My reading is that a vague update often says more about the sender's workload than about you. One former technical recruiter described the reqs "40-plus I managed at any given point". A person carrying that many reqs writes generic status lines. Log who sent the message. A coordinator relaying a scheduling change and a hiring manager writing to you directly are different kinds of evidence.

The lookup table: one row per update

Find the phrase you received in the first column, then read across to the states behind it, the evidence that tells them apart, and the default status. The sections below cover each row in more depth.

Reading each row: what it proves and how it lies

Each message proves less than it seems to and misleads in its own predictable way. Read the row that matches your message and skip the others.

"We're still interviewing other candidates"

What it proves: the req has not been filled, and your loop has not been formally closed.

Usual states: the most common is that other candidates are still partway through their loops. The second is that you are being held as a comparison while someone else moves ahead. The third is a polite stall before a decline. No hiring system publishes a stage for "first-choice candidate holding an offer", so "I'm their backup" is a guess, not a state you can confirm.

How it lies: it sounds neutral but can cover any of the three states. The Resilient Recruiter's advice fits here: "take the statement at face value, but not at hope value".

What separates the states: whether they gave you a date for finishing the other conversations. A date means a process with an end. No date means you cannot tell a comparison from a stall.

"The role is on hold" (freeze, exception approval)

What it proves: the req has left the open state in some form. Hold, freeze, and closed are distinct values in hiring systems. A "hiring freeze exception approval" means someone has to approve the req again before it reopens.

Usual states:

• The org is prioritising other roles, which Greenhouse lists as a named close reason.
• A wider hiring freeze. In one survey of 600 HR managers, Careerminds found 66.7% of employers had implemented hiring freezes, and 48.5% expected recruitment to stay paused for the next twelve months.
• Waiting for re-approval. In Greenhouse, "reopening a closed job with job approvals will retrigger the job approval flow".

How it lies: "on hold" sounds temporary, and it might not be. Nobody publishes a rate of held reqs reopening versus closing. One institutional rule is documented: at the University of Washington, "Requisitions frozen for more than 60 days will be closed." That is one employer's policy, not a universal rule, but it shows that a hold usually comes with an expiry.

A hold is a state in the requisition system, not a mood, and it usually has an expiry you can plan around.

"We'd like to add another round"

What it proves: the decision is not made, and someone wants more information or another voice.

Usual states, from practitioner accounts:

• Tie-break: "if two interviewers see things differently, the hiring manager may schedule an additional round to break the tie."
• Doubt on one competency: an engineering manager described rounds being added when an interviewer "felt you either didn't meet the bar on one of their rubriks".
• Senior sign-off or a new stakeholder: a McKinsey coach describes the extra round as sometimes "a chat with the person leading the division".
• No decision owner: a former recruiting scheduler says that in broken processes rounds get added "because no one owns the decision".

How it lies: most candidates read an added round as a sign they are close to an offer. It is just as often a sign of doubt.

What separates the states: the scope of the round. A round scoped to one named competency points to a gap being tested. A short 1:1 with a senior leader points to sign-off. This cue comes from coaches and forums, and its reliability has not been established publicly. If the scope is a competency, compare it against the posting. Refolk scores your fit against a specific posting, which helps you see which requirement the extra round is likely probing, so you prepare for that one requirement instead of re-preparing everything.

"We're waiting on interviewer feedback"

What it proves: at least one scorecard or one decision step is outstanding.

Usual states: one or two panelists have not submitted, or a committee review is pending. Google's hiring committee review is reported to add one to two weeks.

How it lies: it sounds like the team is deciding right now. The measured data says something narrower. Most of the panel has already written their scorecards, and the wait is usually on one or two people.

After 48 hours, "waiting on feedback" usually means a few specific people are late. It does not mean the decision itself is under way. There is also a weak warning sign. Ashby reports that scorecard completion "tends to be higher for hired candidates than for those who are not", so a scorecard that stays missing correlates with a non-hire. That is a correlation, not proof.

"The hiring manager wants to move forward"

What it proves: one person with influence is positive about you.

Usual states: real intent that is waiting on approvals, or one voice that is not the whole decision.

How it lies: it feels like an offer, but it is not one. One Apple candidate was told the hiring manager wanted to make an offer, did an extra round, and was then ghosted after "almost 2 and half month in entire process".

What separates the states: a named next step with a date. Positive words without a dated step leave the loop At risk.

Silence after a round

What it proves: nothing on its own, which is why day counting fails.

Usual states: updates being batched by an overloaded recruiter, a committee step running, a hold nobody has told you about, or ghosting.

How it lies: silence feels like an answer, but it is not one. If you are searching "no update from recruiter after second interview", note that Indeed found 40% of candidates reported being ghosted after a second- or third-round interview, up from 30% the year before. Late-stage silence is common, and it is not always final.

What separates the states: whether a date someone named has passed, and whether the public posting is still up.

Evidence checks that separate the states

Four checks do most of the work: the public posting, the portal status, whether you were given a date, and how specific the scope is. Each check proves one narrow thing, and each fails in a known way.

Two notes on these checks:

• The portal is the weakest signal. In Greenhouse, "all active candidates will remain active on a closed job". An Active status shows that your record exists, not that the req does.
• No published source gives a reliability rate for reposted jobs, reference requests, or competing-offer questions. Use them to support a reading, never to settle one. If you want to test a signal yourself, log it for every loop and see afterwards which signals came before which outcomes.

Step-by-step: from message to tracker status

This takes about 15 minutes per message. Log it, find the row, check the evidence, ask one question, then set a status with a dated recheck. The procedure is the same for every row. Only the recheck clock changes.

The one question per row

Step 4 is where candidates over-ask. Send one question per update, and choose it so the answer separates the states you listed. Do not use it to fish for reassurance.

Still interviewing others:
Thanks for the update. When do you expect to finish the other conversations, and what would the next step for me be after that?

Role on hold:
Thanks for letting me know. Is the req paused pending approval, or has it been closed?

Added round:
Happy to do it. What would you like this round to cover, and who will I be meeting?

Waiting on feedback:
Understood. Is the panel's feedback complete, or is the team still waiting on one or two interviewers?

Hiring manager wants to move forward:
Great to hear. What is the next step, and roughly when should I expect it?

Silence:
Checking in on the [role] loop after my [round] on [date]. Could you tell me where things stand and what the next step is?

The sources disagree on whether to add leverage. Commenters on Blind advise that you "mention it to them that you may have an onsite or two coming up". That works only when it is true. See failure mode 7.

Setting the status

Two variables decide most statuses: whether you have a dated next step, and whether the update named a specific scope or reason.

How this goes wrong

Most errors come from treating one weak signal as proof. These seven come up most often, and each has a check that catches it.

1. Treating the portal as the truth. "Active" can persist on a closed job, so it gives a false sense that the loop is live. Check: look at the public posting, and ask whether the req is open, paused, or closed.
2. Counting days. "Ten days of silence means a reject" ignores committee steps, which add one to two weeks, and freezes, which can run around 60 days. Check: find the loop's row before you apply any clock. A feedback clock and a freeze clock differ by roughly thirty times.
3. Treating an added round as good news. Rounds are added when an interviewer "felt you either didn't meet the bar on one of their rubriks". Check: ask what competency the round covers. If it is one named skill, mark the loop At risk and prepare for that skill.
4. Taking positive feedback as proof. The Apple candidate heard that the hiring manager wanted to make an offer and was still ghosted after two and a half months. Check: a named next step with a date. Without one, the loop is At risk however warm the message was.
5. Mixing statistics from different surveys. Comparing Greenhouse's 75% ghosting figure from 2022 with its 52% from April 2024 as a trend is invalid, because the question wording changed between waves. Check: compare figures only within the same survey series and the same wording.
6. Trusting benchmarks with no traceable source. Several blog posts cite Gartner or SHRM figures on hold outcomes and decision times that cannot be traced to a primary source. One widely repeated "days to decision by company size" figure also has unclear provenance. Check: if you cannot find the original report, do not set a recheck date from it.
7. Bluffing about competing offers. Some forum advice amounts to inventing leverage. If a recruiter tests the claim, for example by asking for a timeline, a bluff can end the loop. Check: mention only real interviews and real deadlines, and state them as facts, not threats.

How often late-stage loops go silent

Post-interview ghosting is common in every survey wave, and ghosting after later rounds has grown. Use these figures as base rates. They do not predict what will happen to your loop.

How to read this table:

• Only compare within a series. Within Greenhouse's later waves, December's 61% was a nine-point rise on April's 52%. The 2022 figure used different wording, so it is not like-for-like with either.
• Regions differ. In the April 2024 wave, the UK figure was 42% and DACH was 65%. In the July 2025 wave, US Gen Z respondents reported 78%.
• Final rounds are not safe. In the April 2024 US data, 12% named "after final interview" as the stage where they were ghosted. In a separate NumberBarn survey of people ghosted after advancing, 13% were ghosted after a second or later interview, 8% after a final interview, and another 8% after being told they were a finalist.

What this means for your tracker: being at round three is not evidence that your loop is safe. Status comes from the row and the evidence, never from how far you have got.

Keeping several loops current

Parallel loops stay manageable only if every status has a date attached and dead loops leave the active count on schedule. Log each update as a new entry rather than overwriting the old one, so you can see how the loop has moved over time.

Company / role:
Round completed: [round], [date]
Message (verbatim): "[paste exactly]"
Sender role: Recruiter | TA Partner | Coordinator | Hiring manager
Row: Still interviewing | On hold | Added round | Waiting on feedback | HM forward | Silence
Candidate states: 1) [ ] 2) [ ] 3) [ ]
Evidence: Posting up? [Y/N] | Portal: [status] | Date given: [Y/N, date] | Scope named: [Y/N, what]
Question sent: "[text]" on [date]
Status: Live | At risk | Parked
Recheck on: [date] (48h feedback / 1 to 2 wks committee / about 60 days freeze / named date)

Parking a loop only helps if the rest of your search keeps moving while it waits. Refolk tailors your resume and drafts a cover letter for each new posting from your own history, so a loop stuck in a 60-day freeze does not also stall the applications that would replace it.

To keep this reference current, re-check the mechanisms rather than the numbers. Hiring systems change their status fields and approval flows, so read your target company's careers page and any posted hiring-pause guidance before relying on the 60-day freeze cadence. When a new ghosting survey comes out, compare it only with earlier waves that used the same question wording.