Record the source and contact purpose
Capture how the professional entered the database, who added the record, the date, the intended recruiting purpose and the communication basis selected by the responsible team.
Workflow blueprint
Recruitment CRM systems built around candidate permission
A relationship blueprint for recruitment teams that need to know why a person is in the database, what was agreed, and which client received which profile.
Keep candidate source, current preferences, approved communication, role conversations and client submissions reviewable while separating recruiting relationships from automated screening and employment decisions.
TL;DR — Keep candidate source, current preferences, approved communication, role conversations and client submissions reviewable while separating recruiting relationships from automated screening and employment decisions.
Confirm current role preferences
Ask the candidate to verify role family, location, availability, compensation expectation, working arrangement and any limits on which clients may receive a profile.
Approve and log each submission
Link the named vacancy, profile version, candidate approval, client, submission time and consultant so an old talent-pool record cannot authorise a new introduction.
Close outcomes and review retention
Record interview, rejection, withdrawal, offer or placement separately, then schedule correction, restriction or retention review instead of keeping every detail indefinitely.
Page-specific decision aid
A candidate permission and submission passport
The passport follows one finance professional from an attributed source through confirmed preferences, permission for a named vacancy, a controlled profile version, client submission, interview response, withdrawal from a second role and a future retention review. Candidate-provided facts remain separate from consultant and client notes.
- ✓An old contact record cannot authorise a new client submission.
- ✓One candidate can have different outcomes for different roles.
- ✓A retention review can correct, restrict or remove stale information.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Candidate source, purpose and communication choice documented
- ✓Preference, availability and profile confirmation dates visible
- ✓Every client submission linked to candidate approval and one profile version
- ✓CV parsing, screening, scoring and automated selection excluded without proof
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow