60% Faster Internal Hiring with Make.com™: How Automated Talent Matching Transformed One HR Team

Internal mobility is one of the highest-ROI levers in talent strategy — and one of the most consistently under-executed. The problem is not strategy or intent. The problem is the process. Organizations that want to promote from within are running that process on spreadsheets, manual profile reviews, and email threads that HR teams do not have capacity to manage alongside every other open requisition.

This case study examines what happens when you automate that process using Make.com™ — specifically, how automating the internal talent matching workflow compresses time-to-fill, reduces attrition-driven losses, and returns strategic capacity to HR teams that have been buried in coordination work. It is one concrete application of the broader automation spine described in our parent pillar, Make.com for HR: Automate Recruiting and People Ops.

Context and Baseline: What Manual Internal Mobility Actually Costs

Manual internal mobility processes cost more than most HR leaders realize — and almost none of that cost appears on a single line item.

Consider the baseline state of a mid-size organization running internal mobility manually. When a role opens, HR sends an announcement to a distribution list, monitors replies, manually reviews employee profiles in the HRIS, cross-references a skills spreadsheet that was last updated six months ago, and emails individual managers to confirm availability. The average time from role confirmation to a shortlist of internal candidates: two to three weeks. That lag has a direct cost.

Research from McKinsey Global Institute consistently links strong internal mobility programs to higher organizational resilience and lower talent acquisition costs. SHRM data places the cost of replacing a departing employee at 50–200% of their annual salary — a range that accounts for recruiting fees, onboarding time, productivity loss, and the institutional knowledge that walks out the door. When an internal candidate could have filled the role in days, every week of delay increases the probability that an external search becomes necessary.

Asana’s Anatomy of Work research found that knowledge workers spend roughly 60% of their time on coordination, communication, and administrative work rather than skilled work. Internal talent matching, in its manual form, is a pure coordination problem — one that should not require skilled HR judgment to execute.

Approach: Designing the Automation Architecture

The automation architecture for internal talent matching is built around four core workflow layers. Each layer handles one distinct function; together, they replace the entire manual coordination chain.

Layer 1 — Skill Profile Enrichment (Continuous)

The matching engine is only as accurate as the data it queries. Manual skill profiles in most HRIS platforms are updated annually at best — and often reflect the role an employee held two years ago, not the skills they’ve developed since. The first automation layer runs continuously, pulling three data streams into a unified skill object for each employee:

• LMS completion records: Every course completion or certification earned triggers a profile update via API.
• Performance review tags: Structured competency ratings from the previous review cycle are mapped to skill categories and appended to the profile.
• Employee-stated preferences: Career interest forms submitted by employees are captured and stored as preference fields, not discarded after submission.

This layer does not require HR intervention. It runs in the background, keeping the matching database current without a single manual update.

Layer 2 — Role-Open Trigger and Internal Query (Event-Driven)

The highest-value automation trigger in the entire system is the moment a role is confirmed open. Most organizations treat this moment as the start of an external posting process. The automation treats it as the start of an internal query.

When a role status changes to “approved” in the ATS or HRIS, Make.com™ immediately fires a scenario that:

1. Reads the role’s required skills, experience tier, location parameters, and department.
2. Queries the enriched employee skill profiles for matches above a defined threshold (typically 75% or higher).
3. Separates results into full matches and near-matches (employees at 60–74% who have a specific skill gap that can be addressed via LMS).
4. Routes both lists to the hiring manager with source data visible — not a black-box recommendation, but a transparent profile summary with the matching rationale included.

This query runs in minutes. The hiring manager has an internal shortlist before the external job board posting is even drafted.

Layer 3 — Employee Opportunity Notifications (Preference-Matched)

Passive internal job boards fail because they require employees to self-discover opportunities. The automation inverts this. When a role is confirmed open, the system queries employee preference records and sends personalized notifications to employees whose stated interests align with the role — before or alongside the broader internal announcement.

Sarah, an HR Director in regional healthcare, discovered a parallel effect when her team implemented scheduling automation: reclaiming 6 hours per week of coordination time allowed her to rebuild processes that had been deferred for months. The same principle applies here — when employees receive a relevant, timely notification rather than a generic distribution list email, application rates from qualified internal candidates increase measurably, and HR’s follow-up burden drops.

Layer 4 — Application Routing and Status Automation

Internal applications that disappear into a hiring manager’s inbox without structured follow-up are a primary driver of employee frustration with internal mobility programs. Gartner research on employee experience consistently identifies process transparency as a top factor in whether employees perceive internal mobility as viable or performative.

The fourth automation layer handles application receipt, acknowledgment, status updates, and manager routing without HR coordination at each step. Employees receive automated status confirmations. Managers receive structured application packets, not raw email threads. HR receives a consolidated dashboard view rather than a fragmented inbox.

Implementation: What the Build Actually Looks Like

A functional first version of this workflow — role-open trigger, profile query, candidate notification, and application routing — is achievable in one to two weeks in Make.com™. Full skill-gap enrichment with LMS integration adds approximately one additional week. The implementation follows the same sequencing we apply across HR automation engagements:

1. Map the existing process end-to-end before building anything. Document every handoff, every tool, and every manual decision point. This is the OpsMap™ phase.
2. Identify the highest-friction trigger point. In internal mobility, it is almost always Layer 2 — the role-open query — because that is where the most time is lost and where automation delivers the fastest ROI.
3. Build Layer 2 first. Get the query-and-route workflow live and tested with real role data before building the enrichment or notification layers.
4. Add enrichment and preference-matching in parallel once Layer 2 is stable. These layers improve match quality but are not required for the core workflow to function.
5. Connect the LMS for near-match routing as the final integration. This is where the system begins developing talent proactively, not just matching existing skills.

The system integrates with standard HR tech stack components: HRIS for employee profiles, LMS for skill enrichment, ATS or project management tool for role data, and Slack or Microsoft Teams for notifications. No custom code is required at any integration point.

For teams evaluating build approach, our comparison of Make.com vs. custom code for HR automation speed covers the tradeoffs in detail. The short answer: custom code requires a developer for every workflow change; Make.com™ gives the HR operations team direct control.

Results: What Changes When the Automation Is Live

The measurable outcomes of a functioning internal talent matching automation fall into three categories.

Time-to-Internal-Shortlist: From Weeks to Hours

The most immediate result is compression of the time between role confirmation and an internal candidate shortlist reaching the hiring manager. Manual processes that took two to three weeks now complete in 24 to 48 hours. That compression represents a 60% or greater reduction in internal time-to-fill — and more importantly, it means internal candidates are evaluated before external search begins, not as an afterthought after a recruiter has already sourced external candidates.

HR Hours Reclaimed Per Role

Manual internal matching requires 10 to 15 hours of HR coordination per open role across profile review, manager communication, and application tracking. The automation reduces that to 1–2 hours of human review and final judgment. For an organization filling 20 internal roles per year, that recaptured time represents 160–260 hours — the equivalent of one to one and a half FTE months returned to strategic work.

Parseur’s Manual Data Entry Report puts the cost of a full-time employee dedicated to manual data work at $28,500 per year in direct labor costs. The parallel in internal mobility coordination is not identical but is directionally consistent: the hidden labor cost of manual matching is far larger than it appears on any single job posting.

Attrition Risk Reduction

This outcome is harder to isolate in a single cycle but is the most strategically significant. Deloitte’s Human Capital Trends research identifies career growth and internal mobility as among the top factors employees cite in decisions to stay or leave. Harvard Business Review analysis links transparent internal mobility programs to measurably lower voluntary attrition rates.

The automation does not solve every attrition driver. But it eliminates the process failures — the unanswered internal application, the role that was filled externally without an internal search, the career interest form that went nowhere — that are entirely within HR’s operational control to fix.

Lessons Learned: What We Would Do Differently

Start With Data Quality Before Building the Match Engine

The most common implementation setback is discovering mid-build that the HRIS skill profiles are too sparse to query meaningfully. If the average employee profile has fewer than five structured skill fields, the matching algorithm produces low-confidence results and hiring managers disengage quickly. Audit profile completeness before building Layer 2. If profiles are sparse, build Layer 1 first and run it for four to six weeks before activating the match query.

Define the Matching Threshold With Hiring Managers, Not Just HR

The 75% match threshold used in the architecture above is a starting point, not a rule. Hiring managers in technical roles often want a higher threshold; managers in leadership development programs want to see near-matches explicitly. Involve the primary hiring manager stakeholders in threshold calibration before go-live. This prevents the most common post-launch complaint: “The candidates don’t actually fit what we need.”

Employee Notifications Require Opt-In Framing

Automated opportunity notifications land well when employees have previously expressed preferences. They land poorly when employees receive unsolicited messages about roles they never indicated interest in. Build the preference capture step before activating Layer 3 notifications. A simple one-time preference form distributed to the full employee population, with responses stored in the automation, is sufficient.

Connect This to the Broader HR Automation Stack Early

Internal mobility automation is most powerful when it connects to adjacent workflows. When a candidate is selected for an internal transfer, the offboarding from their current role and onboarding into the new role should trigger automatically. Teams that automate new hire onboarding in Make.com™ and connect that workflow to internal mobility get compounding returns. Similarly, teams that automate training enrollment can use the near-match routing in Layer 2 to trigger development plans automatically for identified internal candidates.

For a view of how internal mobility fits into the full talent management automation roadmap, see our listicle on future-proof talent management with Make.com™ automation.

Closing: The Internal Talent You’re Not Using Is Already on Payroll

Every unfilled role that goes to external search when an internal candidate existed is a double cost: the recruiting spend to find someone external, and the retention risk of the internal employee who didn’t get the opportunity. That cost is not inevitable. It is the direct result of a process that was never designed to compete with external recruiting speed.

Make.com™ gives HR the infrastructure to fix that process — not with AI-driven talent intelligence or expensive talent marketplace platforms, but with a well-structured automation workflow that queries the data you already have, surfaces the candidates you already employ, and routes decisions to the managers who need to make them.

Building the automation spine is the prerequisite. Everything else — matching quality, attrition reduction, strategic HR capacity — follows from getting that spine in place first. That is the core argument of our parent pillar on Make.com for HR, and internal mobility automation is one of its most direct applications.

If you want to understand where internal mobility fits in your organization’s automation priority order, our HR reporting and analytics automation work is the right complement — because knowing which roles go unfilled longest, and which departments lose internal candidates to external offers, tells you exactly where to focus first.

The talent is already there. The question is whether your process can find it fast enough to matter.