Home/Blog/Greenhouse Scorecard Reminders: Setup and AI Handoff
Recruiting operations

Greenhouse scorecard reminders: fix missing feedback before adding AI

Configure Greenhouse scorecard reminders, check Slack and manual follow-ups, and build a reviewed AI queue without sending duplicate interviewer nudges.

Remqa · November 17, 2026 · 5 min read

Short answer

Configure Greenhouse scorecard reminders from Job Setup > Notifications for the relevant job. Use the native reminder schedule first, then add a custom AI workflow only for preparing reviewed exception lists and follow-ups that the native process does not cover.

  • Native reminders already cover the first email and recurring follow-ups
  • Slack reminders depend on the interviewer enabling the integration
  • Check the candidate, job, stage and interviewer before any manual reminder
  • Custom AI should prepare exceptions, not invent or submit interview evidence

The interview is over. The hiring team wants to debrief, but one scorecard is missing. A recruiter sends a message, a coordinator sends another, and the interviewer also receives the reminder already configured in Greenhouse. Before adding another AI nudge, identify which reminders are already running and which specific piece of feedback is still outstanding.

Start with the native settings. Then define the exception that needs help. A custom assistant can prepare a queue of unresolved items or draft a careful follow-up. That is a different job from evaluating a candidate. The operating pattern below keeps those responsibilities separate.

Configure the native reminder on the right job

Greenhouse lists Job Admin and above for scorecard reminder configuration. Open Jobs, choose the relevant job, and go to Job Setup > Notifications. In Scorecard Notifications, select Configure beside Scorecard Reminders. Check the job before changing anything. A reminder setting reviewed for one requisition should not be treated as evidence that another requisition has the same setup.

The default email reminder is sent one hour after the scheduled interview ends. It repeats once per day for up to 10 business days after the interview or until the scorecard is submitted. The message uses the organization’s Default Scorecard Due email template. Greenhouse says the default scorecard reminder notification cannot be edited or deleted, while the template content is managed separately.

Choose a custom schedule deliberately

The custom configuration allows the first reminder one hour after the interview, three hours after the interview, or at End of day. Greenhouse defines End of day as 6:00 p.m. in the interviewer’s timezone. Do not interpret that option using the coordinator’s own clock when the panel works across regions.

Optional follow-up reminders have selected times and a frequency of Daily, every 2 days, or every 3 days. Submission stops the reminders. The configuration also allows selected stop criteria that stop reminders when any selected criterion is met. Review the actual available choices in your account instead of assuming that every pipeline status has the same effect.

DecisionNative behaviorOperator check
First emailDefault or custom timingConfirm scheduled interview end and timezone
Follow-up cadenceCustom times and frequencyCompare against coordinator outreach
Slack deliveryAdditional applicable remindersConfirm interviewer integration is enabled
StoppingSubmission or selected custom criteriaCheck current state before another nudge

Greenhouse states that either the default or a custom notification is always sent. You cannot deactivate Scorecard Reminder notifications entirely. Design any extra process around that boundary. A custom integration should not assume that switching to Custom eliminates all native reminders.

Check Slack delivery separately

The reminder window includes Turn on Slack notifications. When enabled and saved, interviewers who have enabled the Slack integration receive applicable scorecard reminders through Slack as well as email. Turning on the job setting alone is not proof that every interviewer will receive a Slack message.

For rollout testing, choose an agreed test case and check the recipient’s integration state. Record which delivery route was expected and which was observed. Keep test candidate details out of broad channels. If someone reports a missing reminder, distinguish a schedule problem from an integration or audience problem before adding another delivery route.

Use manual reminders for a verified exception

Greenhouse supports a manual reminder from the candidate profile. Locate the correct job, select Stage, expand the correct stage, and click Send Reminder. The dialog allows templates, recipients and attachments, plus edits to the subject and body. Review these fields before selecting Send Email.

The manual reminder documentation lists Job Admins who can view and edit candidates and prospects, and Site Admins. Treat this as a separate permission check from configuration access. A teammate who helps maintain a workflow should not automatically receive authority to send every candidate-related message.

A reminder is not interview evidence. Missing feedback should remain missing until the interviewer supplies it. Do not let an assistant infer ratings from a calendar entry, a recruiter’s impression or another panel member’s scorecard.

Build an AI exception queue with a narrow purpose

The following controls are a recommended custom design, not a description of native Greenhouse AI. Start by deciding what qualifies as an exception. Examples include a recruiter-confirmed debrief blocked by missing feedback or a manual follow-up that needs a different recipient. Do not create an exception merely because an automatic reminder has not yet reached its scheduled send time.

  1. Identify the candidate, job, interview stage, interviewer and expected scorecard together.
  2. Record when the interview was scheduled to end and when the state was last checked.
  3. Check the native schedule and any coordinator outreach before drafting another message.
  4. Prepare a short draft that names the missing action without including unnecessary candidate details.
  5. Let an authorized operator review the recipient, wording and current scorecard status before sending.

A useful queue entry explains why it exists. Include the source of the missing-state observation and a plain reason for escalation. If the integration cannot establish whether a scorecard was submitted, label the item unknown and route it for checking. Unknown should not silently become overdue.

Recheck state at the send boundary

A queue can become stale while someone reviews it. Recheck whether the scorecard is still missing immediately before sending. Also check whether another coordinator has already followed up. Keep a small action journal tied to the specific interview assignment so retries do not create another reminder for the same reviewed action.

If a send attempt returns an uncertain result, pause that item and reconcile it with available delivery evidence before retrying. Do not claim a message failed solely because the integration did not receive a clean response. This is a custom operating safeguard, not a promise that Greenhouse exposes a particular delivery endpoint or duplicate-prevention feature.

Test the handoff and avoid common mistakes

Test a submitted scorecard, an outstanding scorecard, a rescheduled interview and two jobs for the same person. Ask the operator to confirm that each queue item points to the right assignment. Compare results against the actual profile rather than trusting a summary alone. Keep the AI input limited to the context needed for the reminder.

Common mistakes include adding Slack without checking the interviewer integration, treating an old queue row as current, copying candidate notes into a reminder, and sending manual messages without reviewing native cadence. Another is treating reminder completion as permission to summarize the interview. Our guide to Notetaker and scorecard review addresses that separate evidence workflow.

How Remqa helps with recruiting operations

Remqa builds AI agents for recruiting teams around explicit sources, reviewed actions and clear operating ownership. For missing scorecards, the useful starting point is a verified exception queue that works alongside native reminders. Bring your current settings, a sample blocked debrief and the team’s escalation rules. An engineer can help define the handoff before adding another message sender.

FAQ

Questions people ask.

Where do I configure Greenhouse scorecard reminders?

Open the job, go to Job Setup > Notifications, and select Configure next to Scorecard Reminders in the Scorecard Notifications section. Greenhouse lists Job Admin and above for this configuration.

What is the default Greenhouse scorecard reminder schedule?

The default email goes out one hour after the scheduled interview ends. It repeats once per day for up to 10 business days after the interview or until the scorecard is submitted.

Can scorecard reminders be disabled entirely?

Greenhouse says either the default notification or a custom notification is always sent. The configuration does not support deactivating Scorecard Reminder notifications entirely.

Does enabling Slack replace the reminder email?

No. Interviewers who have enabled the Slack integration receive applicable reminders through Slack as well as email when Slack notifications are turned on for scorecard reminders.

Can an AI agent fill in a missing scorecard?

A missing scorecard is missing interviewer evidence. The custom workflow recommended here prepares a follow-up queue and draft message for review. It does not create ratings or submit feedback on an interviewer’s behalf.

Talk to an engineer

Want an engineer to look at your setup?

Book a free 30-minute call. We look at your tools and your team's week and tell you what we would do first.

Book a free 30-minute call
30 minutesFree, with an engineer
Your stackWe look at what you run today
Straight answerIncluding when we're not the fit