Recruiter Candidate Tracking
Recruiter candidate tracking should help you answer a simple question: what do I know about this person for this job, and what needs to happen next? Contact details alone do not answer it. Neither does a status that has not been updated since the last conversation.
This guide focuses on choosing a useful candidate record. It is different from buying a resume database or judging a whole pipeline. Start with one candidate's role-specific story and check whether you can follow it without guessing.
Decide what belongs in the candidate record
List the information you need to resume work on a candidate: the job, available candidate material, your review, questions, current progress and next action. Identify where each item currently lives.
If the resume is in one tool, contact history in another and the decision in your memory, write down which record you will treat as authoritative. Do not assume a product imports, merges or synchronizes those tools. Confirm any needed connection individually.
Keep the record relevant to the hiring task. You do not need to collect every personal detail to decide whether a conversation is appropriate. If information is missing, record the question rather than filling it with an assumption.
The candidate evaluation guide helps distinguish supplied information from your interpretation.
Preserve the candidate's relationship with the role
One person may be considered for different jobs. Their skills do not change when you open another role, but the review questions can change substantially.
A planner role might emphasize scheduling and resource allocation. A coordinator role might emphasize records and handoffs. When testing software, open the candidate in the correct job context and check that the explanation is about that job.
Ask yourself whether you could accidentally use a conclusion from one role in another. Confirm the role before contact preparation, interviews and progress updates. A generic assessment of a person should not silently become a decision for every position.
Create a hiring brief that states the work and essentials for each job. That gives your record a stable point of reference.
Use the return-after-a-week test
During a demonstration, create a fictional candidate review with a realistic open question. Record a contact draft and a planned next step. Then ask someone to interpret the record without your verbal explanation.
This fictional example shows what they should be able to distinguish:
| Record detail | What it tells the next reader |
|---|---|
| Role: service coordinator | Which hiring decision the record concerns |
| Resume describes appointment scheduling | What experience is actually supplied |
| Complaint handling not described | What remains unknown |
| Contact draft prepared | Message wording exists; delivery is not established |
| Next action: ask for complaint example | The task to complete before the next decision |
If the reader says “contacted” when the record only shows a draft, the handoff is unclear. If they cannot tell which role is under review, the record is incomplete. These are useful buying questions, not a reason to collect more unrelated personal data.
Keep status tied to real events
Update progress when something actually happens. A request for an interview is not the completed interview. An offer discussion is not an accepted offer. A planned start date is not confirmation that someone started.
For manual work outside the product, decide how you will record completion. If you send through your chosen channel, check that action before marking your own progress. Do not infer delivery from a draft or response from silence.
During software selection, ask which actions are automatic, which are manual and what information the product retains. Confirm reminders, calendar connections, imports, exports and communications separately if they matter to your process. A candidate tracking label does not promise any of them.
Use available profiles within their limits
Jalvexa supports candidate sourcing and resume/profile upload, fit/evaluation, shortlist, contact preparation, interview preparation and hiring progress for a job. Sourced profiles are private one-hour previews of available name, title and location. They are not a permanent replacement for a fuller resume.
Review the input type before interpreting an assessment. A supplied resume may describe work history that a limited preview does not. Missing qualifications, availability and interest need confirmation. Uploaded resumes and Talent Network profiles use no sourcing units.
Jalvexa contact drafts are prepared and approved, not automatically delivered. Keep that distinction visible in your working process. The recruiting workflow guide connects the record with the surrounding hiring steps, and the Recruiter page shows the current product scope.
Compare the cost of your actual candidate work
Recruiter is $139/month with 100 sourcing units. Recruiter Pro is $299/month with 400; Recruiter Team is $599/month with 1,000. The core hiring features are the same. Uploaded resumes and Talent Network profiles use no sourcing units, so compare tiers around sourced-profile use rather than treating every candidate review as sourcing.
Shared team seats are not included merely because a plan is named Team, and sourcing add-ons are not available. Check pricing and confirm access requirements before buying.
Choose a record you can return to and trust: correct job, actual candidate information, truthful status and a clear next question. Tracking earns its place when it reduces reconstruction, not when it makes unsupported conclusions look settled.
Create your Recruiter account or explore Jalvexa for recruiters.