Sarah’s HR team cut candidate feedback from 3–5 days to under 4 hours without an ATS upgrade. One Make.com scenario — triggered by a Google Forms submission, routed by hiring decision, and logged automatically in Google Sheets — handles every candidate response and reclaims 6 hours of HR time each week.

This case study is one component of the broader playbook detailed in Recruiting Automation with Make.com: 10 Campaigns for Strategic Talent Acquisition. If you are evaluating where to start with recruiting automation, candidate feedback is the workflow that delivers the fastest visible ROI — because its failure is visible to the people you are trying to hire.

What Was Breaking

Sarah’s team ran a manual feedback process that most HR leaders recognize immediately. After each interview panel, the hiring manager filled out a paper or Word-document evaluation, emailed it to HR, and Sarah’s team consolidated that input before sending a response to the candidate. That chain had three failure points.

Hiring managers submitted evaluations late — two to four days after the interview. Consolidation added another half-day of HR time. For rejected candidates, the feedback email got deprioritized in favor of advancing the candidates who were moving forward. SHRM research consistently identifies candidate communication as one of the top drivers of employer brand perception, and Sarah’s team was failing at it systematically — not through negligence, but through process design.

The operational cost was measurable. Sarah estimated her team spent approximately 12 hours per week across the full recruiting cycle on manual coordination, with feedback management accounting for roughly 6 of those hours. According to Parseur’s Manual Data Entry Report, organizations lose an average of $28,500 per employee per year to manual data handling inefficiencies — a figure that scales directly with team size and process complexity.

The harder cost was invisible. Candidates who did not hear back left reviews on employer platforms, told their networks, and in at least two documented instances turned down future opportunities with the organization. The problem was not the hiring decisions — it was the silence that followed them. For a deeper look at why this pattern persists, see How HR Can Fix Broken Hiring Processes.

Why Candidate Feedback Was the Right Automation to Build First

Before building anything, the right question is: which broken process damages the most people on the most frequent schedule? For Sarah’s team, candidate feedback hit that mark on both counts. It touched every open role. It affected external stakeholders — not just internal staff. And its failure was recurring and visible.

The OpsMesh™ framework calls this the friction-first principle inside an OpsMap™ audit: identify the process that creates the most external damage when it breaks, and automate that one before anything internal. Candidate feedback qualified. It was also simple enough to build in a single day without disrupting anything already in production.

The Make.com Build: Five Modules, No Code

The scenario uses five modules. No ATS. No new software licenses.

Module 1 — Trigger: Google Forms Submission

Sarah created a Google Form for hiring managers to submit post-interview evaluations. The form captures candidate name, candidate email, role applied for, interview date, decision (advance, reject, or hold), and free-text feedback notes. When a hiring manager submits the form, Make.com triggers immediately — no polling delay, no waiting for someone to check a spreadsheet.

Module 2 — Router by Decision Outcome

Make.com’s Router module reads the “decision” field and splits into three paths: Advance, Reject, and Hold. Each path sends a different email template. The Advance path sends a timeline update and next steps. The Reject path sends a respectful thank-you with optional feedback language pulled from the hiring manager’s notes. The Hold path sends a status acknowledgment with an estimated follow-up timeframe.

This routing step is where most manual processes collapse — teams write one template, send it to everyone, or send nothing at all. The Make.com router eliminates that bottleneck without any HR intervention.

Module 3 — Gmail Send

Each path uses a Gmail module to send the appropriate email from Sarah’s HR team address. The email body pulls candidate name, role, and hiring manager feedback notes dynamically from the form submission. The send fires within minutes of form submission — not hours, not days.

Module 4 — Google Sheets Audit Log

Every send, regardless of outcome, appends a row to a Google Sheets log: candidate name, email, role, decision, timestamp, and which template was sent. Sarah now has a live record of every candidate communication without manual entry. If a candidate follows up asking whether they received a response, the answer is one lookup away.

Module 5 — Error Handler

Make.com’s error handling is configured with a Break module set to retry three times at 60-second intervals before escalating. If a send fails after three attempts, a Slack notification fires to Sarah’s team with the candidate name, role, and error detail. No candidate falls through the cracks because of a transient API failure.

Build Time and What It Required

Sarah built this scenario in one business day with no prior Make.com experience. The only technical steps were connecting Google Forms, Gmail, and Google Sheets via Make.com’s native OAuth connectors — no API keys, no developer involvement. The router logic required selecting the “decision” field from the form output and mapping the three values. The email templates were copied directly from drafts Sarah already had in Gmail.

This is the pattern non-technical HR teams replicate reliably with Make.com: start with tools already in use, connect them through a scenario, and remove the manual handoffs between them.

Results After 90 Days

• Feedback cycle time: Dropped from 3–5 days to under 4 hours from interview completion
• Coverage rate: 100% of candidates received a response — up from 60%
• HR time reclaimed: 6 hours per week redirected from feedback coordination to strategic recruiting work
• Audit log entries: 312 candidate communications logged in the first 90 days, all traceable
• Employer brand: Zero new negative reviews citing communication delays in the 90 days following launch

The 6-hour weekly figure is conservative. It excludes time previously spent tracking down hiring managers for late evaluations, following up on missing responses, and handling candidate inquiries about application status.

Two Adjustments Sarah Made After Launch

Conditional required field for feedback notes. The original form included one optional free-text feedback field. After launch, Sarah noticed hiring managers were still leaving it blank for rejected candidates — the same avoidance behavior the automation was designed to eliminate. She added conditional logic making feedback notes required when the decision is “Reject.” Completion rate on that field went from 30% to 88%.

Two-hour delay on the Reject path. The immediate send worked well for Advance and Hold responses. For Reject, sending within minutes of form submission felt abrupt to hiring managers who reviewed the outgoing email before Sarah’s team did. Sarah added a 2-hour delay on the Reject path only. Candidates still hear within 4 hours — the benchmark is still met — but the delivery reads less automated.

How to Adapt This to Your Organization

The architecture generalizes. The specific tools — Google Forms, Gmail, Google Sheets — are replaceable with any equivalent in your stack. The pattern is:

1. Structured input form capturing the hiring manager’s evaluation
2. Make.com scenario triggered on submission
3. Router branching by decision outcome
4. Templated email send per path
5. Audit log append on every send
6. Error handler with retry logic and escalation

If your team uses a different form tool, a different email provider, or a different log destination, Make.com has native connectors for all of them. The logic stays identical. The connections change.

If you are evaluating whether candidate feedback is the right first automation for your team, the 7 questions to ask before you automate anything will help you confirm the priority before you build.

What Comes Next in Sarah’s Stack

Candidate feedback was the first automation Sarah’s team built, not the last. The 6 hours per week reclaimed from feedback coordination became the margin that funded three more builds over the following quarter: interview scheduling confirmation, offer letter generation, and new hire onboarding task creation. Each one followed the same pattern — identify the manual handoff that breaks most often, build the Make.com scenario that eliminates it, measure the time return.

The full set of recruiting automations this team deployed is documented in the broader playbook: Recruiting Automation with Make.com: 10 Campaigns for Strategic Talent Acquisition.

For HR teams dealing with broken operations more broadly — not just recruiting — the pattern Sarah was living before this build is the same pattern driving burnout across the profession. Process debt, not workload volume, is the root cause. Here is why small HR teams burn out — and why automating the right process first is how you stop the bleed.