Daily

Chase overdue interview scorecards

Each afternoon you get a list of finished interviews that still have no scorecard, with the interviewer's name.

Runs: Daily
Apps: Greenhouse
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every weekday at 3pm, email me the Greenhouse interviews that ended today or earlier where the scorecard still isn't submitted, grouped by interviewer.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Interviewers do the hard part, meeting a candidate for an hour, and then forget the five-minute part: submitting the scorecard in Greenhouse. Without it, the debrief stalls. Recruiters chase people on Slack one at a time, hiring decisions drift by a week, and the candidate who interviewed well is hired by a competitor before the team agrees. Memory fades too, so late scorecards are also vaguer and less useful.

Each day, interviews that have already ended are listed and checked for submitted scorecards. Interviewers who still owe one receive an email naming the candidate, the interview and how long ago it happened, so they can finish while the details are still fresh. Anyone can then finish the form before the details fade.

It helps recruiting coordinators who currently spend part of every week chasing feedback by hand.

What you get out of it

Hiring decisions move faster
With all scorecards in, the debrief can happen on schedule. Candidates hear back sooner, which reduces the number who accept another offer while waiting. Fresh impressions also make the discussion between interviewers more concrete.
Feedback is more accurate
A scorecard written the same day reflects what was actually said in the interview. Notes written ten days later are vague and shaped by hindsight. Without the delay of chasing, the whole panel is ready on the day it was planned for.
Recruiters stop being the nagging bot
Coordinators no longer have to message each interviewer individually. The reminder arrives automatically and the human relationship with interviewers stays friendlier. Coordinators keep a good working relationship with interviewers because the reminder comes from a neutral source, not a person asking for the third time this week, and it names exactly what is missing.
Fair process for every candidate
When every interviewer submits input, decisions are based on structured evidence, which is the best protection against bias and a documented basis if a hiring decision is reviewed later. Fairness matters most when a decision is questioned. A full set of scorecards written close to the interviews gives you something real to point to, rather than recollections gathered after the fact.
Visibility into who is consistently late
Over time the reminders show which interviewers need a nudge from their manager, which lets you address the pattern and not each individual instance. The data guides coaching conversations, such as which interviewers would benefit from calendar blocks right after each interview, and is more objective than anecdotes about who is slow.
A tidy record of the hiring process
When every interview has a matching scorecard, the candidate file is complete. That helps if a hiring decision is later reviewed, a candidate asks for feedback or a new recruiter takes over the role midway.

How it works

What happens, step by step

Every afternoon, ClickRuntime lists the Greenhouse interviews that have already ended.
It checks each one for a submitted scorecard.
You get an email listing the interviews still missing one, grouped by interviewer, so you know who to chase.

Before it runs live

Connect Greenhouse

What you get

RunsDaily

Chase overdue interview scorecardstoday, 9:00Succeeded

Email · Scorecards missing from 2 interviewersRobin Hale: - Technical interview (2026-10-17) Dana Park: - Culture add (2026-10-19)

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Greenhouse steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

scorecards_due_reminder.pyexample

from collections import defaultdict
from datetime import datetime, timezone, timedelta
from clickruntime import on_trigger, credentials, http, notify

def harvest(path, **params):
    resp = http.get(f"https://harvest.greenhouse.io/v1/{path}",
                    auth=(credentials.secret("GREENHOUSE_API_KEY"), ""), params=params)
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    now = datetime.now(timezone.utc)
    interviews = harvest("scheduled_interviews", ends_before=now.isoformat(),
                         ends_after=(now - timedelta(days=14)).isoformat(), per_page=500)
    missing = defaultdict(list)
    for i in interviews:
        for person in i["interviewers"]:
            if person.get("scorecard_id") is None:
                missing[person["name"]].append(f"{i['interview']['name']} ({i['end']['date_time'][:10]})")
    if missing:
        body = "\n\n".join(f"{name}:\n" + "\n".join(f"  - {x}" for x in items) for name, items in sorted(missing.items()))
        notify.email_me(f"Scorecards missing from {len(missing)} interviewers", body)
    return {"interviewers": len(missing)}

FAQ

Common questions

Which interviews trigger a reminder?

Scheduled interviews whose end time has passed and that have no submitted scorecard from the assigned interviewer. Interviews still in the future or already reviewed are skipped. Interviews with a submitted scorecard are left out entirely.

Will interviewers get a reminder every day?

They will until the scorecard is submitted, since the check repeats daily. If that feels too insistent, you can ask for a single reminder after 24 hours and a second after three days. Fewer, better-spaced reminders are often more effective than a daily one.

Can the recruiter also be copied?

Yes. Adding the recruiter or coordinator as a copy is a specific change, which helps when they own the follow-up. Approve the updated version and the next reminder includes them. That gives the coordinator a view of who has been reminded without extra work.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (daily). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a schedule