Human resources

One record per person, and everything hangs off it

Contract, role, manager, skills, time off, equipment and pay all point at the same employee record. Change the person's manager once and every approval route that depended on it follows.

The directory

Who works here, and who they report to

Departments, managers, job titles and contracts on one directory — which is also the org chart, because it is drawn from the same field rather than maintained beside it.

An Odoo employee record beside the organisation chart.

Confidential data

The private fields stay private, by rule

Salary, bank details, identification and personal addresses sit behind record rules rather than behind an agreement not to look. HR sees them; a team lead sees a colleague.

An Odoo employee record showing approvers and access roles.

Skills

What people can do, written down somewhere

Skills, levels, certifications and languages on the record, so staffing a job is a search rather than a question asked around the office.

An Odoo employee resume with skills and levels recorded.

Recruitment

A pipeline for hiring, not an inbox for CVs

Applications by stage, per vacancy, with interviews scheduled against the candidate and the notes kept on them. A hire becomes an employee record without being retyped.

An Odoo job position with its hiring process and expected skills.

Time off

Balances that are counted, not remembered

Allocation, accrual and carry-over per policy; requests approved against a balance the system holds; a calendar everyone can see before they book anything.

An Odoo time off dashboard showing balances and allocations.

Appraisals

Reviews on a schedule the system keeps

Review cycles that come round on their own, with the questions asked of the employee and the manager kept together and the outcome staying on the record.

Screenshots show the Odoo interface, captured from Odoo's public demo database or published by Odoo S.A. at odoo.com — not Rkieh Productions client systems. Odoo is a trademark of Odoo S.A. Rkieh Productions is an Odoo partner and implements and configures Odoo for its clients; what any given system does depends on edition, enabled modules, hardware and the agreed solution design.

In scope

What the module covers

The people processes this work configures, and what each one is responsible for once it is running.

Employee records

Contracts, departments, managers, documents and the private fields only HR should reach.

Recruitment

Vacancies, applications by stage, interviews and the step that turns a hire into an employee.

Onboarding

The equipment, accounts, paperwork and introductions a new start needs, as a list somebody owns.

Attendance

Hours worked, captured at a kiosk or on a phone, against the schedule they were expected on.

Performance processes

Review cycles, the questions asked in them, and what was agreed staying attached to the person.

Expenses

Receipts submitted from a phone, approved on a route, and reimbursed or re-invoiced from the same record.

Hiring

From an open role to somebody's first day

Talk to us about people processes

A vacancy published, applications arriving into stages rather than an inbox, interviews booked against the candidate, and an offer that becomes an employee record with the contract, the manager and the start date already on it. The point is not that each step is faster — it is that nobody retypes the candidate into a second system to make them an employee.

Odoo job positions with applications and progress per role.

Connected

Where people data has to reach

An HR system that stops at the HR department leaves everyone else keeping their own copy. These are the joins that prevent it.

Timesheets

Hours booked against the job or project they were spent on, by the person the contract belongs to.

Payroll

Contracts, allowances, absences and approved expenses feeding the run rather than being re-entered into it.

Projects and planning

Who is available, who is already committed, and what they are qualified to be assigned to.

Documents

Contracts, certifications and identification held against the employee, with expiry dates that raise themselves.

Approvals

Time off, expenses and equipment routed to the manager the record says, not the one somebody remembered.

Access control

What a person can open in the system follows the role on their record, and changes when the role does.

Approvals

Requests go where the record sends them

ERP and business operations

Time off, expenses, equipment and contract changes each follow a route configured once. The manager sees what is waiting, the employee sees where it got to, and nothing depends on an email reaching somebody who is themselves on leave.

An Odoo time off list awaiting approval, by employee and type.

What changes

Four things HR stops doing by hand

Keeping a second list

The directory, the org chart and the payroll input are one record.

Counting leave balances

Accrual, carry-over and remaining days are held by the policy, not a spreadsheet.

Chasing approvals

Requests route themselves and show the employee where they got to.

Hunting for documents

Contracts and certifications sit on the person, with expiry dates that speak up.