90% Faster Talent Pool Recall with Keap Tagging: How a Healthcare Staffing Team Fixed Candidate Chaos

Snapshot

Context and Baseline: A Database That Nobody Trusted

The problem wasn’t that the team had too few candidates. It was that they couldn’t find the right ones when they needed them.

Sarah, the HR Director at a regional healthcare organization managing 12 hours of recruiting coordination per week, had accumulated over 1,200 candidate contacts in Keap™ across two years of hiring activity. Every career fair, every referral, every online application had added contacts to the system. But the tagging had been applied ad hoc — by multiple team members, with no naming conventions, no approval process, and no documentation.

The result: 340 distinct tags in the system. Some were duplicates with different capitalization (“RN” vs. “rn”). Some were role titles with slight wording variations (“Project Manager” vs. “Project Mgr” vs. “PM-Agile”). Some were one-off tags applied for a single event and never used again. When Sarah’s team ran a saved search for clinical candidates available for night shifts in the metro area, the results were unreliable — sometimes returning 12 contacts, sometimes 4, depending on which tag variant the recruiter happened to remember.

According to SHRM benchmarking data, the average time-to-fill across industries runs well above 30 days. For specialized healthcare roles, APQC research confirms the ceiling is significantly higher. Much of that lag isn’t candidate scarcity — it’s pipeline opacity. Teams can’t see what they have because the data structure doesn’t let them ask precise questions.

Gartner research on talent acquisition technology consistently identifies data quality as the primary failure mode of HR systems — not feature limitations. The tool was fine. The taxonomy was broken.

Approach: Taxonomy Before Automation

The fix required a sequenced approach. Automation built on a broken tag structure amplifies the noise — campaigns fire on wrong segments, re-engagement sequences reach candidates who already accepted offers elsewhere, and reporting surfaces false confidence about pipeline depth. The sequence that actually works: audit first, taxonomize second, automate third.

Phase 1 — The Tag Audit

The first step was a complete export and audit of all 340 existing tags. Each tag was categorized by intent: role/skill, pipeline status, geographic preference, source channel, or engagement behavior. Duplicates were flagged. Orphan tags — applied once and never referenced by any campaign or saved search — were marked for deletion.

The audit revealed four systemic failure patterns:

• Case inconsistency: “RN,” “rn,” “Rn” treated as three separate tags by Keap’s™ system
• Role title sprawl: Seven variants of “Registered Nurse” with no merge rule
• Temporal tags with no expiry logic: “CareerFair-Spring2022” applied to 80 contacts, never referenced again, never cleaned
• Status tags that contradicted each other: Contacts tagged both “Status::Active” and “Status::Hired” with no automation to enforce mutual exclusivity

Parseur’s research on manual data entry costs documents the downstream cost of inconsistent records: teams spend significant hours re-cleaning data that was entered incorrectly at the source. The tag audit confirmed this pattern precisely — the cost wasn’t in the original tagging, it was in the recurring search failures that flowed from it.

Phase 2 — The 47-Tag Canonical Taxonomy

All 340 tags were collapsed into 47 canonical tags organized around five prefix categories:

• Role:: — Specific role titles aligned to actual job requisition language (e.g., “Role::RN-ICU,” “Role::PhysicalTherapist”)
• Skill:: — Certifications and technical skills separate from role titles (e.g., “Skill::ACLS,” “Skill::EMR-Epic”)
• Status:: — Mutually exclusive pipeline position (e.g., “Status::Active-Available,” “Status::Passive,” “Status::Hired,” “Status::Withdrawn”)
• Source:: — Original intake channel (e.g., “Source::Referral,” “Source::CareerFair,” “Source::OrganicWeb”)
• Geo:: — Geographic availability (e.g., “Geo::Metro-North,” “Geo::Willing-Relocate”)

A one-page taxonomy reference document was created and shared with every team member with Keap™ access. No new tags could be created without taxonomy owner approval. Existing tags outside the 47 were archived — not deleted immediately, to preserve historical campaign data — but removed from active automation rules.

For a deeper look at how Keap™ tags and custom fields divide responsibilities in a candidate profile, see our guide on Keap tags and custom fields for candidate management.

Phase 3 — Backfill and Contact Enrichment

With the taxonomy defined, the existing 1,200-contact database required enrichment. Contacts were bulk-tagged by segment where data allowed: application source was recoverable from form submission history; role tags were inferred from the campaign sequence through which each contact had entered the system.

Approximately 200 contacts lacked sufficient data for accurate role or status tagging. These were placed into a dedicated re-engagement campaign — a short two-email sequence asking contacts to update their availability and role interest via a Keap™ form. Responses automatically applied the appropriate taxonomy tags. Non-responders after 30 days received a “Status::Dormant” tag and were removed from active pipeline views while remaining in the database for compliance-safe future reference.

This approach aligns with data hygiene principles that underpin GDPR-compliant data retention in Keap — candidates are not deleted prematurely, but they are segmented accurately so they don’t pollute active pipeline metrics.

Implementation: Automating Tag Application at the Point of Entry

The taxonomy only holds value if every new contact enters the system already tagged. Manual tagging at intake is the failure mode that created the original problem — it requires a human decision at a moment of high volume and low attention.

Form-Based Auto-Tagging

Every intake form on the careers page was rebuilt with role-specific routing. A candidate applying for a clinical position completed a form that automatically applied “Role::RN-ICU” (or the relevant role tag), “Source::OrganicWeb,” and “Status::Active-Available” on submission — no human action required. Career fair badge scans and referral intake forms followed the same logic.

Keap’s™ campaign builder handled all of this natively for form-triggered sequences. For ATS-sourced candidates — where data originated outside Keap™ — an external automation platform connected the ATS status field to Keap™ tag application, passing the candidate record through on disposition change.

This is the automation model described in our post on building perpetual talent pools with Keap automation — intake automation that builds the database as a byproduct of normal recruiting activity, not as a separate administrative task.

Status Tag Mutual Exclusivity

One of the more technically precise requirements was ensuring that “Status::” tags could not coexist on the same contact. A candidate tagged “Status::Hired” should not also carry “Status::Active-Available.” Keap™ campaigns handle this through remove-tag actions: when “Status::Hired” is applied, the campaign simultaneously removes all other Status:: tags. This mutual exclusivity logic was built into every status transition trigger — offer extended, offer accepted, declined, withdrawn, and re-entered pipeline.

Engagement Scoring via Tag Accumulation

Beyond pipeline status, the team introduced a lightweight engagement model. Candidates who opened three or more emails in a 90-day window received a “Engagement::Warm” tag applied automatically. Those who clicked through to role-specific content received “Engagement::High-Intent.” These engagement tags did not replace status tags — they layered on top, enabling saved searches that combined pipeline position with behavioral signal. A search for “Role::RN-ICU + Status::Passive + Engagement::Warm” returned candidates most likely to respond to a targeted outreach, even before a formal requisition opened.

McKinsey Global Institute research on talent strategy emphasizes that passive candidate pipelines — candidates not actively searching but open to the right opportunity — represent the highest-quality hiring channel when activated at the right moment. Engagement tagging is the mechanism that identifies that moment at scale.

Results: What Changed After the Taxonomy Went Live

The changes were measurable within 60 days of full taxonomy enforcement.

Candidate Recall Time

Before the taxonomy, locating qualified candidates for a specific role required manually scrolling contacts, checking individual profiles, and cross-referencing notes — a process that consumed 2 to 3 hours per role opening. After taxonomy enforcement, a saved search combining Role::, Geo::, and Status:: tags returned a filtered, accurate list in under five minutes. This mirrors the time-recovery pattern documented in Sarah’s scheduling scenario: structural fixes reclaim hours per week that compound across every hiring cycle.

Pipeline Visibility

For the first time, the recruiting team had a reliable count of active, passive, and dormant candidates by role category. This data fed directly into workforce planning conversations — the team could report to leadership how many qualified clinical candidates were in the pipeline before a position opened, rather than scrambling to source after the requisition was approved. Harvard Business Review research on proactive talent pipelining consistently shows that pre-positioned candidate pools reduce time-to-fill more than any single sourcing tactic.

Re-Engagement Sequence Performance

The “Engagement::Warm” automated re-engagement sequences — triggered quarterly to passive candidates — produced a meaningful response rate that surfaced available talent before roles were posted publicly. Several roles during the post-implementation quarter were filled from the re-engagement pipeline rather than through external job boards, reducing sourcing cost per hire. For context on what interview conversion looks like when the candidate pipeline is warm before outreach, see the Keap automation results in healthcare staffing case study.

Tag Proliferation Rate

In the two years before taxonomy enforcement, the team had accumulated 340 tags across 1,200 contacts — roughly 170 tags per year. In the 90 days following taxonomy enforcement, zero unauthorized tags were created. The taxonomy owner approval process held, and the one-page reference document proved sufficient for the team to self-govern without constant oversight.

Lessons Learned: What We Would Do Differently

Three execution decisions merit honest retrospective review.

1. The Backfill Should Have Been Smaller

Attempting to enrich all 1,200 existing contacts simultaneously created a 6-week backfill project that slowed taxonomy launch. In retrospect, the right approach was to set a recency threshold — contacts active within the past 18 months get enriched; contacts older than 18 months get a “Status::Dormant” tag immediately and are revisited only if they re-engage. This would have cut the backfill to roughly 400 contacts and compressed the launch timeline by half.

2. Engagement Tags Should Have Launched with the Taxonomy

The initial taxonomy launch covered Role, Skill, Status, Source, and Geo tags only. Engagement tags were added in week eight, after recruiters asked for a way to identify warm candidates without opening individual contact records. Building engagement tagging into the initial campaign architecture from day one would have delivered the full passive pipeline benefit from launch, not 60 days later.

3. A Quarterly Tag Audit Should Be Scheduled, Not Ad Hoc

Within 90 days of launch, two duplicate tags had emerged from a workaround one recruiter used for a specific event. A quarterly 30-minute audit — exporting the full tag list and scanning for prefix violations — catches this before it compounds. Scheduled maintenance prevents the drift that created the original problem. This governance model applies equally to the broader automation ecosystem described in our post on how Keap compares to a traditional ATS.

How to Replicate This in Your Keap™ Instance

The sequence that produced these results is repeatable for any HR team with an existing Keap™ database and inconsistent tagging history.

1. Export your full tag list. In Keap™, navigate to CRM → Tags. Export the complete list. Sort alphabetically to surface duplicates.
2. Categorize every tag by intent. Assign each existing tag to one of five buckets: Role/Skill, Status, Source, Geo, or Engagement. Any tag that doesn’t fit a bucket is a candidate for deletion.
3. Define your canonical 40–60 tag list. One prefix per category. Document it. Assign a single taxonomy owner with approval authority for new tags.
4. Rebuild your intake forms. Every form that adds a new contact to Keap™ should auto-apply at minimum: one Role:: tag, one Source:: tag, and “Status::Active-Available.” No manual tagging at intake.
5. Build status mutual-exclusivity logic. For every status transition in your pipeline, add a remove-tag action for all competing status tags in the same campaign step.
6. Set a quarterly audit calendar reminder. 30 minutes, export tags, scan for prefix violations. Fix immediately.

For the campaign mechanics of candidate follow-up once the taxonomy is live, see our guide on setting up your first candidate follow-up campaign in Keap.

The broader principle — fix the data structure before building automation on top of it — is the same discipline that drives every engagement we document in the Keap recruiting automation parent strategy. Tags are not a feature. They are the architecture that makes every downstream campaign, search, and report either reliable or not.