Vacancy, candidate and client submission
The recruiter tracks submissions by vacancy separately from the shared profile. After interviews, they can see who is waiting for client feedback and who has been told the decision.
Custom Development
A recruiter may coordinate several interviews for one vacancy, and a candidate may consider several roles at once. We’ll design a recruitment CRM that links each submission to a specific vacancy and the client’s decision.
These modules can be included in the project. We’ll agree on the scope and workflow rules after reviewing your processes.
The recruiter tracks submissions by vacancy separately from the shared profile. After interviews, they can see who is waiting for client feedback and who has been told the decision.
The recruiter records the agreed time, response needed and next step. Client comments can be kept separate from internal recruitment notes.
The account manager tracks the contractual guarantee period and the status of a replacement request. The new submission links to the original vacancy with its own history.
How teams can divide responsibilities and handle exceptions after rollout.
The recruiter sees the pending submission and the last client contact. The recruitment lead helps agree on a deadline, and the candidate receives an update.
The recruiter logs the reason and discusses next steps with the client. The vacancy goes back to sourcing, while authorized staff retain access to notes on previous candidates.
For the first rollout, we’ll work through one vacancy with several recruiters. A manager accepts the brief, a recruiter handles submissions, and the client provides feedback through the agreed channel. We’ll check resubmission, withdrawal of consent and reopening a vacancy for a replacement.
Once we agree on the requirements, we design the screens, build a pilot, and try it against the agreed use cases. We plan the rollout and follow-on modules with your team.
Discuss the First PhaseA candidate can have one profile and a separate set of stages and access permissions for each submission. A decision on one vacancy leaves the other pipelines intact.
The placement record can hold the start date and agreed guarantee terms. A replacement search links back to the original assignment to keep the history.
We’ll agree which fields to match and how to handle contact details, submission history and permissions to use the data. Recruiters will review uncertain matches manually. A trial migration will check that CVs and stages remain linked to the right vacancies and that access restrictions carry over.
We’ll review assignment types, submission stages and how employers provide feedback. We’ll also determine whether you need a client portal, calendars, CV migration and replacement tracking. Cost and sequencing can be estimated once we understand the workflows and data sources.
Tell us your industry, describe one process you want to automate, and let us know which tools your team already uses.