Sourcing
A job post's criteria, ideal profile and searches, the run and the longlists it leaves.
The job post entry where you decide who to look for and run sourcing. At the top it has See candidates, which opens the ATS, and Build a new longlist. Below, four tabs: Criteria, Ideal profile, Searches and Longlists.
| Who | What they can do |
|---|---|
| Owner and Recruiter | Everything: prepare, run sourcing and find contact info |
| Collaborator | Prepare the criteria, the ideal profile and the searches, close a run and add candidates. They don't run sourcing |
| Viewer | View and export |
Running sourcing needs a paid plan or the trial. Preparing it works on Free. The step by step for the first time is in Your first longlist.
Criteria, ideal profile and searches
What sourcing uses, one tab for each. The criteria and the ideal profile are edited in place and save themselves. At the end of the tabs, Propose criteria, Propose profile or Propose searches asks Reclee for a proposal for the open tab. If the ideal profile is missing or there are no searches, a notice at the top offers Propose what's missing.
| Tab | What it is | Actions |
|---|---|---|
| Criteria | Up to 10 sourcing criteria and the Threshold to get in, the match score threshold. Order sets the weight: the first one counts three times as much as the last. A Must-have criterion keeps anyone who fails it out of the longlist, wherever it sits. While a longlist is being built, the criteria can't change: close it or stop it first | Drag them to reorder, mark the must-haves and move the threshold. Add criterion adds one at the end. Empty, the tab offers Add the first one or Propose with Reclee. What Reclee proposes arrives as changes you accept or dismiss one by one, or with Accept all and Dismiss all |
| Ideal profile | The portrait of who you're looking for: country, city, level, years, where they work today, titles, skills and languages, plus an anti-profile, where explicitly not to look. It steers where to search, but doesn't score | Empty, the tab offers Create ideal profile or Propose with Reclee. Each row is edited where it sits, and Done closes it. What Reclee proposes is saved over the one you had, marked Needs review, and Approve signs it off |
| Searches | Up to 50 concrete queries per ideal profile, each with its filters and its performance. They need the ideal profile first | Add search opens all the filters, and Save search saves it. The ones Reclee proposes aren't saved until you add each one. Deleting asks for confirmation |
A search can be edited until it runs. After that it stays as it is, so the longlist says what it was built with. If an earlier longlist was built with other criteria, the tab says so: editing there only affects the next one.
What Reclee proposes spends AI usage. Criteria and searches don't change until you accept them. The ideal profile is saved, but while it's Needs review sourcing won't run.
The run
Build a new longlist opens the setup: what the run will use, for you to check, and two numbers you pick.
| What | What it is |
|---|---|
| Target | How many qualified people it looks for, up to 150. It starts at 150 |
| Cap | The most profiles it evaluates, between 250 and 2000. It starts at 500. Below it you see how much of this month's AI usage it may spend: whatever goes past what you have left is paid with purchased credits, and without them the longlist pauses when it gets there |
Without criteria, an approved ideal profile or searches, the run doesn't start and spends nothing. It doesn't start either if nothing changed since the last longlist, if one is already being built or if the job post is a draft: the button tells you why. Build a new longlist opens it without searching yet, and Search the first 20 profiles starts it. From then on the criteria, the ideal profile and the searches are frozen in the run: what you edit afterwards applies to the next longlist.
| What you see | What it is |
|---|---|
| Qualified | How many profiles passed the threshold, against the longlist's target |
| Profiles evaluated | How many were evaluated, against the cap |
| The searches | Each with its status, Running, Queued, Paused or Exhausted, and its performance over its last 20 profiles |
| The timeline | What happened on each page |
Each page brings 20 profiles and takes about two minutes. The run keeps going even if you close the tab, and whatever it found is saved. While one runs, another can't be built.
Searches run 10 at a time. One that drops below 20% performance gives its place to the next. If none of the first 10 reaches that minimum, it tries 10 more, and stops there: there's no third batch.
| How it ends | What happens |
|---|---|
| It reaches the qualified target | It closes on its own |
| It hits the cap, or the searches stop performing or finding profiles | It pauses and asks you: Search 20 more profiles, Add more searches or Close with the ones that qualified. Whoever launched it gets a notification with the reason, which opens the run. If the searches stopped performing or finding profiles, Reclee proposes new ones, which don't run until you approve them |
| This month's AI is used up | It stays open, paused, until usage comes back or you buy credits |
| Stop and close with what we have | You close it. Asks for confirmation |
Searching spends AI usage on every page. Once closed, the longlist is frozen, each qualified person enters the job post's ATS in the first stage, and you get a notification. Anyone who failed a must-have criterion stays out of the longlist and enters the ATS disqualified, with the reason Failed criterion or Insufficient data.
Longlists
Every longlist in one table: first the one being built, if there is one, then the closed ones, newest first. Each row shows its ideal profile, the date, the status, the qualified, the profiles evaluated and the average match score. Tapping the open one shows how the run is going.
When you open one:
| Part | What it has |
|---|---|
| Header | When it closed, how long it took, how many qualified out of how many were evaluated, and the average |
| Each row | The candidate, their role and company, how they did on each criterion as the longlist delivered it, whether they have an email or phone, the Match score and the coverage |
| How this list was built | The setup it ran with |
| The profile | When you tap someone: their summary and their evaluations, criterion by criterion |
Filters are by score, by the result on a criterion, by whether they have contact info and by the search that brought them. Who makes it in and who doesn't is in Your first longlist.
| Action | What it does | Who |
|---|---|---|
| Export | Downloads the list, or the selection, as CSV | Everyone |
| Add to job post | Adds the selected people to an ATS stage | Owner, Recruiter and Collaborator |
| Add to talent pool | Saves them to a talent pool list | Owner, Recruiter and Collaborator |
| Find contact info | Brings the email or phone of the selected people. First it tells you how many credits it costs and asks for confirmation | Owner and Recruiter |
From the profile you can also find a single detail, without confirmation. What each one costs is in Reaching out to candidates.
To get started
Open a job post and prepare its sourcing.