The short answer
Start with a record you can act on.
Create one record for a person, then connect it to the opportunities where that relationship matters. Log only interactions you may need to revisit, and keep the next action near the conversation that prompted it.
- 01
Add the person once.
Save the name, role, company, and contact details you actually use. Do not create duplicate records for every conversation.
- 02
Connect the relevant application.
Associate a recruiter, referrer, or interviewer with the roles where the relationship has a direct bearing on your search.
- 03
Log the useful parts of the interaction.
Capture the channel, date, what was decided, and anything you will need before replying or interviewing again.
- 04
Leave with one next move.
A concise thank-you, material request, or timing check belongs in a task only when it is a real action you expect to take.
The fields that make a contact record usable
Keep only the details that help you recognize the person and continue the relationship thoughtfully.
- Name, organization, and role or relationship type.
- A contact method you have permission and reason to use.
- How you met or what they are connected to, such as a referral or a specific opening.
- The last substantive interaction and the next action, if there is one.
Separate people from applications
The same contact can matter across more than one role, while a single application can involve a recruiter, hiring manager, and several interviewers.
Treating people and applications as separate records prevents duplicate notes and makes the relationship easier to understand when a new opening appears. It also avoids assuming that a person represents every role at a company.
Write notes that support the next conversation
Good notes are specific enough to refresh your memory and limited enough to remain safe and respectful to retain.
- Record what was discussed, an agreed timing, and a stated next step.
- Avoid turning a private contact record into a dossier of speculation or sensitive personal information.
- Use a short interaction log rather than repeatedly overwriting one vague note.
Where HiredBase fits
HiredBase has a candidate-focused relationship layer: contacts can be linked to applications, interactions can be logged with a timestamp, and tasks can stay connected to the person and opportunity they concern.
That makes a job-search CRM useful without pretending it needs the complexity of a sales system. Start with the application, then add people only when the context changes what you do next.
Common questions
A system should make the next move clearer.
- Can one recruiter be connected to multiple applications?
- Yes. In HiredBase, a contact can be associated with more than one relevant application, so you can retain the relationship without duplicating the person.
- Should I track every person I find at a company?
- No. Add people whose relationship, interaction, or follow-up is genuinely relevant to your candidacy. A smaller record you trust is more useful than a broad list you never review.
- Can contact records help with interview preparation?
- They can provide context for the people involved in a process. HiredBase also supports linking interviewer contacts to interview rounds.
Put the method to work