# Slow hiring manager feedback after interviews: fixes you can start on your Mac today

> Slow hiring manager feedback after interviews costs candidates and offers. Learn the causes and fixes you can use on a Mac, with or without Lazur.

URL: https://www.lazur.app/for/recruiters/problems/slow-hiring-manager-feedback-after-interviews
Updated: 2026-11-09

Slow hiring manager feedback after interviews usually means nobody owns the next step. The fix is a scorecard deadline, a reminder that fires on the due day, and a short debrief held after the last score is in. You can start this week with the apps you already use on your Mac.

## Quick answer

- Slow feedback usually means nobody owns the scorecard deadline.
- Measure the gap in business days before you change anything.
- Greenhouse recommends one business day for scorecards after each interview.
- Hold the debrief only after the last scorecard is in.
- Lazur can point, guide, and draft the nudge. You still send it.

## What hiring manager feedback delays costs you

- **Candidates walk away.** Survey research lists slow or missing communication among reasons candidates withdraw. The Talent Board research, reported by SHRM, names poor communication or no feedback as top reasons. A withdrawn candidate shrinks your shortlist, and the search starts again.
- **Your name with candidates.** Feedback also shapes whether people apply again. Greenhouse's 2024 candidate report found that most candidates would reapply after feedback, even when they were not offered the job. Silence removes that chance.
- **Hours your team spends chasing.** Each late scorecard means someone chases it. The hiring manager gets asked again, the recruiter writes another message, and the debrief moves. No study I could find puts a dollar figure on those hours, so count your own.
- **Scores made from memory.** A scorecard filled in late is weaker. Interviewers forget the detail that mattered. The debrief then leans on whoever spoke last. No study I could find measures how much this changes hiring quality, so treat it as a risk, not a proven loss.

## Why it happens

1. **Nobody owns the scorecard deadline.** Scorecards compete with the rest of the day. Without a named owner and a due day, the form drops to the bottom of the list. The recruiter may know the deadline, but the interviewer may never have seen it written down.
2. **The debrief waits for one more opinion.** Teams often hold the debrief for the last person to submit. One late scorecard then delays the whole loop. The group could decide with the scores in hand, but nobody wants to make the call early.
3. **The request arrives in the wrong place.** Hiring managers often work in calendars and chat, not in the applicant tracking system. An ATS notification can be missed. A dated message in the channel they read most is harder to miss.
4. **Interviews are not structured.** When each interviewer asks different questions, the debrief can turn into a long account of what each person heard. Google's re:Work guide recommends the same questions for every candidate and a scoring guide for each.
5. **Every candidate email needs approval.** Some teams want the hiring manager to approve each note. That approval waits on the same busy calendar. Agreed templates for yes, no, and next step let the recruiter send on the day of the decision.
6. **Nobody measures the wait.** Teams rarely track the time between steps. Without dates, the delay feels normal. A tracker with one column for each stage makes the slow step visible within a single role.

## How to fix it

- **Set one scorecard deadline, in business days.** Greenhouse recommends a minimum scorecard submission time of one business day after each interview. Write that rule into the interview plan. Tell each interviewer when you book them. A rule nobody heard about is not a rule.
- **Remind on the due day, with a name and a date.** Use the reminder your applicant tracking system offers. Greenhouse says its system sends an automatic reminder to interviewers, and managers can add more. In Slack, type /remind in a message field and use the format /remind [#channel] [what] [when].
- **Hold the debrief only after the last scorecard.** Greenhouse says the debrief should start only after late-stage candidates finish interviews and their scorecards are in. Book it for a fixed day, and keep it to 30 minutes to an hour. If one scorecard is still missing, the hiring manager decides how to proceed and writes that down.
- **Score every candidate on the same scale.** Google's re:Work guide says to ask the same questions, grade every candidate on an identical scale, and use a scoring guide. Keep each scorecard category to five or six attributes. Less to fill in makes it easier to finish on time.
- **Send the candidate note the same day.** Decide the next step in the debrief, then write the candidate note before the group leaves. If the decision lands late in the day, use Send Later in Mail to deliver the note the next morning. Choose Send 8:00 AM Tomorrow from the preset list.
- **Draft the notes before the debrief.** Write a version for each outcome before the debrief starts. Fill in the names after the decision. The wording is then ready, and nobody waits for approval on sentences.
- **Name a backup interviewer.** Ask the hiring manager for a backup before the loop starts. If the main interviewer is away, the backup submits, or the group decides on the scores it has. Write the rule down so nobody has to guess.

Most recruiters will tell you feedback is slow. Fewer can tell you how slow, in business days, for each interview loop. That gap matters. You cannot fix a delay you have not measured, and a guess usually makes the team look better than it is.

## Measure your own hiring manager feedback delay first

Pick a few roles that closed in the last month. For each one, write down the day the final interview ended, the day each interviewer submitted a scorecard, the day the debrief happened, and the day the candidate heard back. Count business days, not calendar days. Greenhouse's one-business-day minimum uses the same unit, so your numbers can be checked against it.

| Stage | What to record | Where to find it |
| --- | --- | --- |
| Final interview ends | Date and time the last interview finished | Your calendar or ATS interview log |
| Scorecard submitted | Date each interviewer submitted their scorecard | Scorecard history in your ATS |
| Debrief held | Date of the group decision meeting | Calendar event for the debrief |
| Candidate told | Date the candidate got a yes, no, or next step | Sent mail in Gmail or Mail |

_Dates to record for each closed role._

Read the gaps. Any gap longer than one business day between the last interview and the last scorecard breaks Greenhouse's minimum. Note the widest gap in each role. That is where your first fix goes.

- Long wait before scorecards: check whether interviewers saw a due date at all.
- Long wait before the debrief: check whether the meeting was booked before the last scorecard arrived.
- Long wait before the candidate hears: check whether the note waited for the hiring manager to approve the wording.

## A worked example from one interview loop

Take a candidate for a support role. The final interview runs on a Tuesday morning. Most interviewers submit scorecards on Wednesday. One submits the following Monday. The debrief moved to the Tuesday after that, and the candidate heard back that Friday. Nobody set out to slow this down. The candidate still waited through a long, quiet stretch.

Look at each step. The Wednesday scorecards met the one-business-day minimum. The Monday scorecard did not. One late score held up the whole loop. Nobody needed a new tool to see that. They needed a dated table.

The fix was small. Set a reminder for the late interviewer on the day the scorecard is due. Hold the debrief only after every scorecard is in. The aim is a reply in days, not weeks.

![A job interview in an office, the step before slow hiring manager feedback after interviews](https://images.lazur.app/content-images/problem/slow-hiring-manager-feedback-after-interviews/slow-hiring-manager-feedback-after-interviews-1-83e4d9.jpg)

- **79%** of candidates would reapply after feedback, even if they were not offered the job ([source](https://www.greenhouse.com/blog/2024-greenhouse-candidate-experience-report))
- **36%** of U.S. candidates had not heard back one to two months after applying ([source](https://www.shrm.org/topics-tools/news/talent-acquisition/candidate-experience-talent-board-research-candes))
- **1 business day** Greenhouse's minimum scorecard submission time after each interview ([source](https://support.greenhouse.io/hc/en-us/articles/360039539772-Structured-hiring-guide))

## What a good debrief looks like

A debrief is a decision meeting, not a status update. Greenhouse says it should run 30 minutes to an hour, review scorecard data, and start only after the late-stage candidates finish their interviews and scorecards are in. That last rule does most of the work. A meeting that starts with a missing score will wait for it anyway.

1. Confirm every scorecard is in before anyone speaks.
2. Read each score and the evidence behind it, one candidate at a time.
3. Check each candidate against the same attributes and the same scale.
4. Decide yes, no, or next step, and name the person who sends the candidate note.
5. Send that note the same business day, or schedule it for the next morning.

![Hiring team meeting at a table to decide on slow hiring manager feedback after interviews](https://images.lazur.app/content-images/problem/slow-hiring-manager-feedback-after-interviews/slow-hiring-manager-feedback-after-interviews-3-08232d.jpg)

## Write the nudge that gets a reply

A reminder works best when it names one person, one candidate, and one date. A vague message gets a vague reply. Here is a short draft you can change.

Hi, the debrief for the support role is set for Thursday. I still need your scorecard for the final interview. Could you submit it by end of day tomorrow? Thanks.

Schedule the note if the timing matters. In Mail, click the Send Later button in the message window, then pick a preset such as Send 8:00 AM Tomorrow. Scheduled messages wait in the Send Later mailbox in the sidebar. Double-click one there to edit it, then click Edit in the top-right corner. To cancel, select it and click Delete.

If you write in Gmail, read the [scheduled email steps for Gmail](https://www.lazur.app/how-to/schedule-an-email-to-send-later-in-gmail) before you rely on them. Test a scheduled note on yourself first, so you know what the recipient will see.

## Set reminders that fire on time

Reminders fail when they depend on memory. Use the tools that already notify you. In Slack, type /remind in a message field with the format /remind [#channel] [what] [when]. Channel reminders can repeat by day but not by hour. You can also open the three-dot menu > Remind me about this on a message. Slack's default reminder time is 9 a.m. in your time zone, and you can change it under Preferences.

Your applicant tracking system may already do this. Greenhouse says its system sends an automatic reminder to interviewers, and managers can add more reminders. Check that setting before you build a workaround.

> **Set the reminder on the due day:** Set the reminder for the day the scorecard is due, not the day of the interview. A reminder that matches the deadline tells the interviewer exactly what to do. Name the role and the candidate in the message.

## Mistakes that make feedback slower

- Waiting for a perfect write-up. A short, scored scorecard that arrives on time beats a long note that arrives late.
- Sending a reminder with no date. Please send feedback soon gives the interviewer nothing to act on.
- Holding the debrief before the last scorecard. The room then waits for one person.
- Using long scorecards. Greenhouse suggests keeping each category to five or six attributes so the form stays quick to fill in.
- Asking for approval on every candidate email. Agree on templates for yes, no, and next step before the loop starts.

Also avoid fixing only the candidate side. A status email buys you time. It does not replace a decision. The fix that counts moves the scorecard and the debrief.

> **Candidate data and regulated roles:** Candidate details are personal data. If you recruit for regulated roles, such as nursing, law, or accounting, follow your employer's rules before you paste anything into a tool. When you ask Lazur a question, the audio and the screenshot go to AI providers so Lazur can answer.

## Edge cases: panels, late hires, and sensitive roles

Panels make the rule harder. A large panel has more people to chase. Pick one owner for the scorecard list. That person posts the open items in one thread each day until the last score is in. A missing name is easy to lose, so the list needs every name on it.

![Recruiter at a laptop sending a nudge about slow hiring manager feedback after interviews](https://images.lazur.app/content-images/problem/slow-hiring-manager-feedback-after-interviews/slow-hiring-manager-feedback-after-interviews-2-6269d3.jpg)

Another edge case is an interviewer who is away. Ask the hiring manager for a backup before the loop starts. A missing scorecard should never sit silently. If nobody can submit, the hiring manager decides whether a short call replaces the scorecard, and the decision gets written down.

For a role with a fixed start date, the deadline moves up. Tell the hiring manager the decision day at the start of the loop. A decision day gives everyone a date to plan around, and it gives you a reason to follow up.

Rejected candidates still need a reply. Keep the note short and about the interview, not the person. One specific, job-related point is enough. Avoid comments you would not want read back to you.

## Candidate feedback after interview: what the surveys show

The 2024 Greenhouse report says 52% of candidates say they have been ghosted. The page does not say the ghosting followed an interview. It gives no sample size or method. Treat that number as a signal, not a measurement.

The Talent Board research, reported by SHRM, drew on 150 organizations and feedback from 240,000 candidates. Its top withdrawal reasons include time disrespected through poor communication or no feedback, and a process that took too long. It does not give percentages for those reasons.

No source I could find measures a dollar cost per day of feedback delay. Nor does one show that deadlines cut time-to-hire. Vendor guidance is useful, but it is not outcome evidence. Count your own gaps before and after a change, and trust those numbers more.

## Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac. Hold Option and Command to ask about anything on screen, and Lazur answers out loud. It can point at a button for you. It does not click buttons or operate other apps. You still send the reminder and the candidate note yourself.

Lazur helps most with the steps you keep forgetting. Ask where Send Later sits in the Mail window. Ask for a walk through a Slack reminder, one click at a time. Hold fn to dictate a note at the cursor, then read it before you send.

## What to do next

Start this week with one closed role. Count the gaps, set one reminder with a named day, and hold one debrief after the last scorecard. Then compare the gaps on the next few roles. If the widest gap is still the same step, change that step next. One change at a time shows you what worked.

If you keep loops in a sheet, [Google Sheets for recruiters](https://www.lazur.app/for/recruiters/google-sheets) shows a tracker setup. For scheduled notes, read [Gmail for recruiters](https://www.lazur.app/for/recruiters/gmail). When you want Lazur on your Mac, [download it](https://www.lazur.app/download) and check [pricing](https://www.lazur.app/pricing) first.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Draft a short note asking for the support role scorecard by end of day tomorrow.”: Lazur drafts a short nudge with the role, the candidate, and the due day. You edit it, then send it or schedule it with Send Later. (Drafts it)
- “Where is Send Later in this Mail window?”: Lazur circles the Send Later button on screen and labels it, so you know where to click.
- “Walk me through a Slack reminder, one click at a time.”: Lazur guides each step and waits for your click before it moves on.
- “Draft a short nudge to the hiring manager about the missing scorecard.”: Lazur drafts the text. You read it, edit it, and send it yourself.
- “Hold fn and dictate the candidate note.”: Lazur types clean text at your cursor in any app. You check it before you send.
- “Remind me at the debrief time to check for scorecards.”: Lazur adds a reminder to Apple Reminders, so the due day is on your Mac.
- “What does this scorecard rating mean?”: Lazur explains what is on screen and answers out loud.

## A plan you can start this week

- **Day 1: Count the gaps on one closed role.** Pick one role that closed in the last month. Write down the day the final interview ended, the day each scorecard came in, the debrief date, and the candidate reply date. Count business days between each step.
- **Day 2: Write the scorecard deadline down.** Add the deadline to the interview plan. Send it to each interviewer with the calendar invite. Ask the hiring manager to confirm it in the channel they read most.
- **Day 3: Turn on reminders.** Check the automatic reminder setting in your applicant tracking system. If you use Slack, set a /remind for each open loop on its due day. Slack's default reminder time is 9 a.m., and you can change it under Preferences.
- **Day 4: Draft a note for each outcome.** Write one note each for yes, no, and next step. Keep them short and specific. Save them as drafts in Mail or Gmail so the wording is ready before the debrief.
- **Day 5: Run one clean debrief.** Hold the debrief only after the last scorecard is in. Read each score, decide, and send the candidate note the same day. Log each date in your tracker.
- **Next week: Compare the gaps.** Count the same gaps on the next few roles. Check whether the scorecard step or the candidate step is still the widest. Change one thing at a time.

## FAQ

### How long should a hiring manager take to give feedback after an interview?

Greenhouse recommends that interviewers submit scorecards within one business day after each interview. That is vendor guidance, not a measured standard. Pick a rule your team can keep, write it down, and check it against your own dates.

### Is slow feedback normal?

Survey research says many candidates wait without an answer. That does not make the wait acceptable for your team. Measure your own gaps before you decide what counts as slow.

### What do I do if the hiring manager never sends feedback?

Escalate with dates, not with a complaint. Name the candidate, the interview day, and the missing scorecard. Ask for a decision by a fixed day. If there is still no reply, tell the candidate what happens next and when.

### Should I tell a candidate about the delay?

Yes, if you can give a real timeline. Say the decision is still in progress and name the day you expect an update. Do not promise a date you cannot keep.

### Can Lazur send the reminder for me?

No. Lazur does not click buttons or operate other apps for you. It can point at the Send Later button, guide you through it, and draft or dictate the text. You still press send.

### Does Lazur work in Gmail and Google Sheets?

Lazur works in any app on your Mac, including Gmail and Google Sheets in Chrome or Safari. It is not a plugin or add-in for any app, and it has no partnership with any app maker.

### Do I need a new tool for reminders?

Usually not. Mail has Send Later, Slack has /remind, and your applicant tracking system may already send scorecard reminders. Check what you have before you add another app.

### Does this advice apply to regulated jobs?

Follow your employer's rules on candidate and client data, especially for roles like nursing, law, or accounting. Keep identifiable details out of prompts and drafts unless your employer allows the tool. The timing advice still holds.

## Sources

1. [First impressions of employers often falling flat: 2024 Greenhouse Candidate Experience Report](https://www.greenhouse.com/blog/2024-greenhouse-candidate-experience-report), Greenhouse, checked 2026-11-09
2. [Research Reveals Candidates' Frustrations with Hiring Process (Talent Board CandE research)](https://www.shrm.org/topics-tools/news/talent-acquisition/candidate-experience-talent-board-research-candes), SHRM, checked 2026-11-09
3. [Structured hiring guide](https://support.greenhouse.io/hc/en-us/articles/360039539772-Structured-hiring-guide), Greenhouse Support, checked 2026-11-09
4. [Set reminders](https://slack.com/help/articles/208423427-Set-reminders), Slack Help Center, checked 2026-11-09
5. [Send email messages in Mail on Mac (macOS 27)](https://support.apple.com/guide/mail/send-email-messages-mlhlp1098/mac), Apple Support, checked 2026-11-09
6. [A guide to structured interviewing for better hiring practices](https://rework.withgoogle.com/intl/en/guides/a-guide-to-structured-interviewing-for-better-hiring-practices), Google re:Work, checked 2026-11-09