Arsalan YasinMost recruitment rollouts I get called into share one symptom. The Odoo Recruitment module is installed, a few job positions exist, and the hiring pipeline still lives in a shared inbox and a spreadsheet. Nobody trusts the system because it was switched on before anyone agreed what it was replacing. That is a process problem wearing a software costume, and it is the most common reason an applicant tracking system is never adopted.
In every Odoo business implementation project where HR is in scope, I treat recruitment as a workflow design exercise first and a configuration exercise second. The module is not difficult. Getting your screening criteria, approval points and onboarding handover to survive real candidates takes judgement. Here is the sequence I use.
Step 1: Map the Hiring Process Before You Configure Anything
Open a whiteboard, not Odoo. Write down every step a candidate passed through for one role you hired recently, including the informal ones: the phone screen the operations manager does before anyone else sees the CV, the reference check that sometimes happens. Those undocumented steps break rollouts three weeks in.
Define the Pipeline Stages Your Team Actually Uses
Odoo ships with sensible default recruitment pipeline stages in the kanban view, and the temptation is to keep all of them plus extras. Resist that. Every stage you add is one somebody must drag a card into, and unused stages make a pipeline unreliable. For most small and mid sized Australian businesses, five or six is the honest number: New, Initial Qualification, First Interview, Second Interview, Contract Proposal, Contract Signed.
The test for keeping a stage is simple. Does a different person own the candidate once the card lands there, or does a different decision get made? If neither is true, it is a note, not a stage.
Step 2: Configure Job Positions Around How You Really Hire
A job position carries the department, recruiter, interviewers, expected number of new employees and the published description that feeds your website and external job boards.
The field skipped most often is the interviewer list, and it matters most for adoption. Interviewers see only the applicants on their own positions, so a hiring manager logs in to four candidates instead of the whole company’s pipeline. That access design is usually the difference between managers using Odoo and managers asking HR to email them CVs. Set the recruitment team and hiring target at the same time so the position reports against a number.
If you are scoping this alongside a wider go live, my guide on how to prepare for an Odoo implementation project covers the stakeholder alignment and data preparation groundwork that makes the HR phase far less painful.
Step 3: Build Screening Into the System, Not Into People's Inboxes
If a recruiter still reads every CV to check whether an applicant holds a licence or the right work rights, you have automated filing and nothing else. Interview forms, built on the Survey app and attached to the job position, are the lever. Send a short qualification form automatically at the New or Initial Qualification stage and keep it to knockout questions only: work rights, licences, certifications, notice period, salary expectation, location. Ten questions maximum, because longer forms cost you good candidates through friction rather than fit. Enable CV digitization if your application volume justifies the credits.
Refuse Reasons That Produce Reporting, Not Just Cleanup
Most teams treat refuse reasons as housekeeping. Configured properly they become your first real hiring dataset. Build a short, mutually exclusive list such as Not qualified, No work rights, Salary expectation out of range, Withdrew and Position filled, and attach an email template to each so candidates get a courteous reply automatically. Six months on, that list tells you whether your advertisements attract the wrong people or your salary bands have drifted.
Step 4: Capture Applications From Every Source Automatically
Configure the recruitment email alias so applications sent to a generic address create applicant records with the CV attached. Publish positions to your Odoo website so the online form writes straight into the pipeline. Where you advertise externally, use distinct source tracking so you can compare candidate sourcing channels on cost per hire rather than impressions.
The rule I give clients is blunt. If an application arrives by a route that does not create a record automatically, that route gets fixed or retired. Manual re entry is where pipelines rot.
Step 5: Handle the Offer Stage Before It Handles You
The offer step is where functional design usually breaks, because it crosses from HR into finance and legal. Decide who approves a salary package before it is sent, and where that approval is recorded. Use the salary configurator for variable benefits, and online signature so the signed contract lands against the applicant record.
Australian employers should settle award classification and superannuation details here, not after the start date. Getting them wrong creates payroll corrections later and complicates Single Touch Payroll reporting.
Step 6: Make the Handover to Onboarding One Click
When a candidate accepts, the Create Employee action converts the applicant into an employee record and carries the contact details, CV and interview history with it. This is where the investment pays off, because onboarding starts with a populated record instead of a blank form.
What the Employee Record Needs on Day One
Agree the minimum viable employee record before go live: legal name, tax file number declaration status, superannuation fund, bank details, emergency contact, start date, manager, department and work location. Then build an onboarding plan as activities or a project template that fires on employee creation: equipment request, system access, induction booking, policy acknowledgement and probation review date, each with an owner and a deadline. A new hire’s first week is the most visible output of this rollout, so design it with more care than the stages.
Step 7: Prove the Rollout Worked With Recruitment Analytics
After a quarter of clean data, the built in reporting gives you time to hire, source effectiveness, stage conversion rates and recruiter workload. Track two numbers at minimum: median days from application to signed contract, and the percentage of hires still employed at six months. The first tells you whether the process is efficient. The second tells you whether your screening criteria work.
A Rollout Sequence That Holds Up in Practice
Run it in this order. Map the current process. Configure stages and refuse reasons. Set up two or three job positions with interviewers assigned. Build the qualification form. Turn on the email alias and website publishing. Hire one role end to end as a pilot, fix what broke, then open it to every position and retire the old channels on a date set in advance. A pipeline running in parallel with email never wins, because email is always easier on the day.
If you would rather not learn these lessons on your own hiring, I am happy to walk through your recruitment workflow, stage design and onboarding handover and tell you where it will break. Book a Consultation, bring one role you are hiring for now, and we will map it properly.
Conclusion
A recruitment module rollout succeeds on decisions, not configuration. Agree your stages, restrict what interviewers see, screen with structured questions rather than inbox intuition, make refuse reasons reportable, and treat employee creation as the finish line. Do that and Odoo Recruitment becomes the place your hiring actually happens, with clean data flowing into onboarding and payroll.
Frequently Asked Questions
How long does an Odoo Recruitment module rollout usually take?
For a business hiring under fifty people a year, allow two to four weeks: about a week to configure stages, job positions and interview forms, then a pilot hire to validate the workflow. The configuration is fast. The process agreement takes the time.
Do I need the Employees app to use Odoo Recruitment?
Yes, and you should want it. Recruitment depends on Employees for departments, job positions and the Create Employee action. Without it you lose the onboarding handover, which is the main reason to implement the module.
Can interviewers see every candidate in the pipeline?
No, and this is a key part of your access design. Interviewers see applicants only for positions where they are listed, while recruiters and HR administrators see the full pipeline. Set this before go live, because managers will not adopt a system that exposes salary expectations for other teams.
Is CV digitization worth enabling?
It depends on volume. Parsing applicant details from a CV consumes credits, so for a handful of applications a month manual entry is cheaper. Past roughly fifty a month, the time saved and the record completeness justify the cost.
How do I stop applications still arriving by personal email?
Publish one application route and close the rest on a fixed date. Configure the recruitment email alias, publish the position to your website, and point every job board advertisement at that single form.