ICIMS Talent Pools Setup: A Consultant’s Complete Guide

An ICIMS talent pools setup done right gives you a place to park candidates who aren’t right for today’s req but absolutely are for tomorrow’s. Configured wrong, talent pools become a graveyard of profiles nobody touches and metrics nobody reports on. We’ve audited a lot of ICIMS instances, and “we have talent pools, we just don’t really use them” comes up almost every time. Here’s how to set up ICIMS talent pools so they survive the first quarter and actually feed pipeline.

🎯What Is an ICIMS Talent Pool?

An ICIMS talent pool is a Talent Pool Profile, its own profile type in the ICIMS Talent Cloud, that holds a curated group of candidates organized around a shared attribute. Skill, function, location, alumni status, event, you name it. Candidates sit in the pool through a Recruiting Workflow connecting their Person Profile to the Talent Pool Profile, the same plumbing ICIMS uses to connect candidates to jobs.

The pool isn’t a job. It doesn’t post a job. It posts the talent community itself, so warm candidates can opt in and stay engaged until a real req opens.

Think of it as a labeled drawer instead of a junk drawer. Same candidates, different findability.

💡Talent Pool vs Talent Pipeline vs Recruiting Workflow

These three terms get mashed together in conversation and in ICIMS forums. Quick disambiguation, because the rest of the guide depends on it.

Every time a candidate joins a talent pool in ICIMS, that connection is a Recruiting Workflow record. Same statuses, same workflow rules, same reporting structure as a candidate on a job. That single fact changes how you should design the whole thing. If you’re hazy on the underlying structure, our walkthrough on the ICIMS data structure spells out how Person, Job, and Talent Pool Profiles connect.

📊When You Actually Need a Talent Pool

Not every nice-to-have idea deserves its own pool. Pools earn their keep when:

• You disposition a strong runner-up and want them findable in six months without a fuzzy keyword search
• You attend campus or industry events and need a holding tank for new contacts
• You run an alumni program for boomerangs
• You source proactively for hard-to-fill roles ahead of approved reqs (nurses, devops, niche sales, exec)
• You collect interest from passive candidates on your career site

🔧ICIMS Talent Pools Setup: Step by Step

Here’s the configuration order we use on every implementation. Skipping the early steps is where most teams quietly create the mess they’ll have to clean up next year.

1. Decide your taxonomy before you build a single pool

   Pool sprawl is the number one reason pool strategies rot. Before clicking Create Talent Pool, write down your full pool list on paper. Most TA teams need fewer pools than they think.

   Suggested starting taxonomy for mid-market:

   • One silver medalist pool per major job family (engineering, sales, ops, customer-facing, corporate)
   • One alumni / boomerang pool
   • One events / campus pool per active campaign (sunset old ones)
   • One to three specialty pipeline pools for hard-to-fill roles

   Total: usually 8 to 15 active pools. If your list runs to 50, you’re treating pools like saved searches. They aren’t.

2. Create the Talent Pool Profile

   In ICIMS, go to your Talent Pools area and create the Talent Pool Profile. Name it deliberately. The name is what shows up to candidates if you ever post the pool externally.

   Required fields at minimum:

   • Talent Pool name
   • Talent Pool Owner (the recruiter or sourcer accountable for the pool’s health)
   • Department or job family
   • Status (Active, Inactive)

   Pro tip: include a sunset date in the pool name or a custom field. Pools created for one-time events should expire. Otherwise they linger and pollute your reporting.

3. Configure postable fields and the Talent Pool Overview

   Postable fields control what candidates see if you post the pool to your Connect or career portal. The Talent Pool Overview is the description, and yes, it works a lot like a job description, except it’s selling membership in a community instead of an open role.

   Postable fields you typically want on:

   • Pool name
   • Description / Overview (HTML, supports basic formatting)
   • Location (or “Multiple Locations” / “Remote”)
   • Department or function
   • Pool image (optional, but tends to lift Connect portal conversions)

   Don’t post every pool. Internal-only pools (silver medalists, alumni, internal mobility) should not be postable. Configure that intentionally before going live, because a silver medalist pool showing on your public career site is a bad day.

4. Decide how candidates get in

   Three real paths exist. Pick one primary path per pool. Mixing all three on the same pool without governance creates dirty data fast.

   • Manual add from a Person Profile (recruiter clicks Add to Talent Pool)
   • Workflow rule auto-add when a candidate hits a specific disposition, status, or step
   • Self-signup through a Connect portal form or a Talent Pool posting on the career site

5. Build workflow rules for auto-add

   This is the leverage move. If recruiters have to remember to add silver medalists to the pool, they won’t. Workflow rules can do it for them.

   Common patterns we set up:

   • When disposition = “Not Hired – Strong Candidate” → Add to Silver Medalist – [Function] pool
   • When candidate completes the career portal “Join Our Talent Community” form → Add to General Talent Community pool
   • When candidate is dispositioned at offer stage → Add to Boomerang Watch pool
   • When candidate participates in event X → Add to Event 2026 Spring Campus pool

   Each rule needs an entrance criterion (the trigger), an action (Add to Talent Pool with the specific pool ID), and the right Workflow Profile mapping. If your workflow rules already feel fragile, fix the foundation first. We wrote a separate troubleshooting walkthrough for ICIMS workflow rules not triggering that covers the most common reasons rules silently skip.

6. Post the pool externally (only if it should be public)

   If the pool is meant for inbound interest, post it. In ICIMS Connect (the recruitment marketing layer) you post a Talent Pool the same way you post a job. The posting goes live on your Connect portal or, with the right configuration, alongside your standard career portal listings.

   Make sure:

   • The Talent Pool Overview reads like a real value proposition for the candidate, not internal copy
   • The “what happens next” expectation is clear (you’ll be considered for future X roles, you’ll get our newsletter, etc.)
   • The form behind the pool only collects what you’ll actually use to qualify or segment

   Pools that live in Connect become the front door of your nurture strategy. For more on the broader Connect / Engage layer, see our ICIMS CRM setup guide.

7. Build the report

   Without reporting, a pool is a junk drawer. Pull a saved search or build a report for each pool that tracks:

   • Total candidates in the pool
   • Net adds per month
   • Candidates who moved from the pool into a real Recruiting Workflow on a job
   • Last-touched date distribution (how stale is the pool?)
   • Engagement metrics if you’re using Engage / CRM features

   The conversion metric (pool → active workflow on a job) is the one that proves the pool is doing real work. Most teams skip it. Don’t be most teams. If your reporting feels like a black box generally, our ICIMS recruiting reports guide covers the report structure leadership actually reads.

🚪The Three Paths Candidates Take to Enter a Pool

Worth a quick zoom-in. Each path has a different cost-benefit profile, and most teams pick wrong.

Manual add

From any Person Profile, recruiters search for a Talent Pool and add the candidate. Highest precision, lowest volume. Best for one-off, high-touch additions like an exec referral or a known runner-up. Don’t make manual the only path or pools will starve.

Workflow rule auto-add

The most reliable way to keep pools fed. Set the rule once, it runs on every applicable workflow change forever. Audit annually because pool taxonomy drifts and rules outlive the pools they were written for. This path is where leverage happens.

Connect portal self-signup

Candidates fill a form, opt into a pool, become part of your community. Highest volume, lowest precision. You’ll get a lot of unrelated entries unless your form is well-designed. Use this for general talent community pools, not specialty pipelines.

⚠️5 Most Common ICIMS Talent Pools Setup Mistakes

The same five problems show up in almost every ICIMS audit we run. Each one is fixable, none of them fix themselves.

1. Building too many pools

   Pool sprawl kills the strategy. If you have 80 pools and 6 active recruiters, the math doesn’t work. Recruiters won’t remember which pool is for what, auto-add rules collide, and the report becomes unreadable. Start with 8 to 15, prove the value, expand only when a real use case emerges.

2. Posting internal pools externally

   Silver medalist pools, alumni pools, and internal mobility pools should not be visible on your career site. Check the postable settings before going live. The most embarrassing audit finding is a public-facing “Strong Candidates We Didn’t Hire” pool. Yes, we’ve seen it.

3. No owner per pool

   A pool with no name attached is a pool nobody cleans up. Assign a Talent Pool Owner field on every pool and tie pool health to that person’s QBR. Ownership is what makes the difference between a pool that’s curated and a pool that’s a graveyard.

4. No sunset plan for event and campaign pools

   Event pools and campaign pools accumulate. Schedule a quarterly review. Archive (don’t delete, you may need the OFCCP record) anything older than your engagement window. A two-year-old “Spring 2024 Career Fair” pool is doing nothing for you.

5. Ignoring Workflow Profile mapping on auto-add rules

   Auto-add rules only fire if the candidate is on the right Workflow Profile. Most mid-market and enterprise instances have multiple Workflow Profiles (different countries, regions, business units, hourly vs salaried). The rule has to apply to every Profile that should trigger it. We see this break constantly during audits, and the symptom is usually “our silver medalist pool stopped getting new entries last spring.”

❓Frequently Asked Questions