Candidate profile
Keep the CV, parsed fields, files, notes, source, and contact history together as the durable layer beneath individual applications.
Recruiting CRM
Keep candidate relationships useful beyond one application.
A recruiting CRM should preserve what the team already learned about a candidate and make the next relevant action visible. TiLab connects profiles, files, source records, notes, contact history, talent pools, and job applications without treating every person as a brand-new row.
Candidate continuity
Preserve context while each role stays distinct.
The candidate is a person with a continuing record; the application is their job-specific process. Keeping both levels makes it possible to reuse relevant context without confusing the status of one role with another.
- 01
Create the profile
Keep the candidate’s core details, CV, files, and notes on one record rather than rebuilding them for every vacancy.
- 02
Record the source
Attach the known source label and contact context so the team can later review where candidates and applications originated.
- 03
Organise the relationship
Use talent pools, ownership, notes, and next actions to keep relevant people visible before or between active job processes.
- 04
Connect a role
Create a job-specific application with its own pipeline stage, feedback, and decision context when there is a relevant opening.
- 05
Keep the history
Retain the activity and application context the team is permitted to keep, so a later conversation starts with an informed record.
The practical record
A CRM shaped around recruiting work.
Generic sales fields are not the centre of this workspace. The record is built around candidate context, relevant jobs, team ownership, and the evidence produced during a hiring process.
Talent pools and ownership
Group relevant profiles and make the owner and next action explicit so promising records do not disappear into an undifferentiated database.
Job-specific applications
Attach a candidate to a role without overwriting the context of another role, including stage, interviews, feedback, and the eventual outcome.
Searchable working context
Use structured candidate, source, application, and activity records to support the recruiter’s day-to-day review of who needs attention.
CRM discipline
A database is only as useful as its next action.
Moving an old spreadsheet into a new interface will not create candidate relationships. Decide what should be recorded, who owns follow-up, and when a stale record should no longer remain active.
Use the CRM for
Recruiting context that helps the team understand a candidate relationship and connect it to a relevant process.
- Profiles and files the team has a reason to retain
- Known source and contact history
- Talent-pool membership, ownership, and next actions
- Separate applications with their own stage and feedback
Do not expect it to
The CRM organises work the team performs; it is not presented here as an autonomous sourcing or communication engine.
- Find private candidate data on the open web
- Enrich profiles through an unlisted third-party source
- Contact people without a recruiter’s deliberate action
- Decide who should be hired or moved to the next stage
Common questions
Where the CRM ends and the ATS begins.
What is the difference between a candidate and an application?
The candidate profile holds continuing person-level context. An application connects that candidate to one role and carries its own pipeline, interviews, feedback, and decision trail.
Can one candidate have more than one application?
Yes. That separation is important: it preserves one profile while allowing each role to retain a different stage, owner, feedback set, and outcome.
Does TiLab source or message candidates automatically?
This page makes no such claim. The current CRM value is the connected record, talent-pool organisation, ownership, contact history, and the transition into an active job workflow.
Early access
Start with the records you already trust.
Use a controlled set of real candidate and application records to see whether TiLab improves ownership, continuity, and next-action visibility. The workspace is currently free in early access.