Manage
Every candidate,
every stage on record
For recruiters who need to know where every candidate stands on every job. Each job has its own pipeline from Sourced to Placed, every move is kept in the application’s history, and the timeline shows who or what made it.
The problem
A stage without a history is just a label
On a spreadsheet or a shared board, a candidate’s stage is whatever someone typed last. When a client asks when a profile was submitted, why a candidate dropped out or who moved them back, the answer sits in somebody’s memory or inbox.
The same person is often on several jobs at once. Moving them forward on one role must not change their status on another, and a confirmed placement should never quietly slide back to an earlier stage.
What changes
- Each job has its own pipeline, so a stage change on one job never touches the candidate’s other applications.
- Every application keeps its stage history: which stage, when, from which stage, and whether a person, an automation, AI or an external source made the move.
- Rejections and withdrawals need a reason, so the pipeline explains its own outcomes months later.
- Moving a candidate to Submitted records the submission and, through a default rule you can pause, creates a client-feedback task for the job’s owner.
Payroll Specialist · Ghent
Illustrative — fictional dataSourced · 2
- Candidate D · Payroll Officer
- Candidate E · HR Administrator
Screening · 1
- Candidate C · Payroll Specialist
Submitted · 1
- Candidate B · Payroll Team Lead
Client Interview · 1
- Candidate A · Senior Payroll Specialist
Offer · 0
How it works
01
Set up the job
Assign a recruiter as owner and keep the ten standard stages, or only the ones this job needs. Sourced and Placed are always included.
02
Add candidates
Add people from a search, a shortlist, an import, the careers page or by hand. Each becomes an application on this job, normally starting at Sourced.
03
Move with a reason
Change the stage on the candidate’s card. Rejected and Withdrawn ask for a reason; Placed asks you to confirm the placement and the terms agreed so far.
04
Record interviews
Enter a date, time and location or video link. The application moves to Client Interview if it was not there yet. No invitation is sent.
05
Read the history
Job, candidate and client timelines show every stage move, message, document and AI action, each tagged with who or what caused it.
You provide
- Jobs with an owner and the hiring stages they use
- Candidates added from searches, shortlists, imports, the careers page or by hand
- Your stage decisions, outcome reasons and interview details
Jenny produces
- A board per job with one column per stage and the next action on each card
- A stage history per application: stage, date, previous stage and actor
- Interview records per job with their status and feedback
- Timelines on jobs, candidates and clients, filterable by communication, process, documents and AI
What it depends on
- Jobs and candidates in Jenny — history from another CRM or ATS imported by CSV first.
- Your own calendar for interview invitations: Jenny keeps the interview record but has no calendar connection.
Approval and privacy controls
- A stage change applies to one application only; the candidate’s other jobs are unaffected.
- Rejected and Withdrawn cannot be set without a reason.
- A confirmed placement cannot be moved back to an earlier stage.
- Stage moves requested through the Jenny assistant wait for your confirmation before they happen.
- Scheduling or completing an interview sends nothing. By default, completing one drafts a feedback request for you to review.
Current limitations
- There is no calendar connection: interviews are records in Jenny, invitations are not sent and availability is not checked.
- The ten stage names are fixed. A job can use fewer of them, but stages cannot be renamed or added.
- Interview times are entered and shown in Brussels time.
- Applications brought in from another ATS arrive as dated history on the candidate, not as live pipeline records.
Questions about recruitment pipeline
Which stages does the pipeline use?
Sourced, Contacted, Interested, Screening, Submitted, Client Interview, Offer, Placed, Rejected and Withdrawn. Placed, Rejected and Withdrawn close an application. A job can use a subset, as long as Sourced and Placed are part of it.
Can a candidate be on several jobs at the same time?
Yes. Each job holds its own application for that candidate, with its own stage and history. Moving someone on one job never changes their stage on another.
Does Jenny book interviews in my calendar?
No. There is no calendar connection. You record the date, time and location or video link in Jenny, which keeps the interview on the job and moves the application to Client Interview. Invitations go out from your own calendar as they do today.
What do the User, Automation, AI and External tags mean?
They say who or what caused a timeline entry: a person in your team, a rule or schedule you set up, work prepared by Jenny’s AI, or an event from outside the workspace. Where the candidate acted themselves, for example by applying on your careers page, the entry says so.
Can I see all pipelines together?
Yes. The reports show how many applications sit in each stage across jobs, filtered by period and job owner, with a link to the people in each stage.
Related features
- Job-to-candidate matching
From a job description to an explained shortlist — evidence, gaps and unknowns included.
Available - Presentations & outreach
Client introductions and personal outreach, drafted by Jenny and approved by you.
Needs setup - Recruitment reporting
Outcome counts you can trace back to saved records — and no time-saved figures.
Available - Careers page
Your open jobs on your own careers page, with applications landing in the pipeline.
Available
See it on your own vacancies and candidates
A short call with the founder: we look at how you work today and show the workflows that fit.