Odoo Planning: roles, batch publishing and open shifts

What Odoo Planning 20 covers, how it is configured and what to check: roles, shifts, automatic scheduling, publishing, field service and when custom development is needed.

ProductOdooplanningturniERP19 November 2026 · 14 min read

Odoo Planning manages the scheduling of shifts for employees and material resources. It must be kept distinct from Odoo Project: Planning says when and where resources work, Project says which tasks they complete. It integrates with HR (employee availability, contracts, time off), with Timesheets (actual hours against planned) and with Sales (linking shifts to the service orders sold). This article describes what the module covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise.

When an implementation is healthy

A planning implementation works when five conditions hold:

  • all employee shifts are created and published from Odoo, with no shifts on Excel or WhatsApp;
  • employees receive shift notifications directly from Odoo and can see their own plan;
  • time off and public holidays are automatically excluded from planned shifts;
  • automatic scheduling assigns open shifts to available, qualified resources, without manual matching;
  • planned hours are reconciled with actual timesheets to detect over- and under-use.

The module covers seven areas: shifts (creation, publishing, recurrence), resources (employees and materials), roles (skill or function), open shifts (unassigned, with automatic scheduling), templates (reusable predefined shifts), field service (customer interventions planned as shifts, from Odoo 20) and reporting (planning analysis, utilisation).

The Gantt view and the planning views

The module has four views: the Gantt (default) is the main screen, where you drag, resize, split and duplicate shifts; the list shows all shifts in tabular form, with multiple editing and export; the calendar gives a monthly overview of shifts per resource; the pivot adds up planned hours by resource, role, project and period.

In the Gantt the colour of the shift indicates its status. Solid colour: planned and published, the employee has been notified. Diagonal stripes: planned but not yet published, a draft the employee knows nothing about. Grey background: the employee is on time off in that period. Progress bar: shift in progress with linked timesheets.

Administrators can change the dimension of the plan. By resource shows one row per employee or material and says who works when. By role shows one row per role and says the coverage by function in each time slot. By project shows the allocation of resources by project. By sales order shows the capacity committed to each customer order.

Resources: employees and materials

Planning works with two types of resource. Employee resources are linked to the HR employee record. Their availability depends on working hours (from the contract), time off and public holidays, and the roles assigned decide which shifts they can be scheduled for automatically. Material resources are equipment, vehicles, rooms, tools, anything with limited availability: they are not linked to an employee and have no time off or contracts. They are used, for example, to schedule a van for deliveries, a meeting room or a machine. Materials can also be given roles, for example the "Forklift" role for a vehicle.

Roles are the matching key

A role represents a function or a level of skill and is the bridge between what a shift requires and who can cover it. Some examples: cashier, senior cashier, warehouse worker, forklift driver; head waiter, bartender, kitchen staff, head chef; first-level field technician, second-level technician, project manager.

Each employee has one or more roles, and one is set as the default, which automatic scheduling uses to resolve conflicts. Each shift or shift template states the required role. The logic of automatic scheduling is this: an open shift requires the "forklift driver" role; the function looks for employees with that role; discards those on time off, those outside the contract period and those who already have a shift in that slot; assigns first the available employee for whom that role is the default one. If roles are not configured, automatic scheduling cannot work, because Odoo has no criterion for matching resources and shifts. Roles can be generic ("operator"); they need not be granular.

Publishing separates planning from communication

Shifts exist in two states: planned (visible to administrators) and published (visible to employees). A draft shift, with diagonal stripes, has been planned by the administrator but the employee is not notified and sees it only in the administrator's Gantt. A published shift, in solid colour, has received Publish: the employee gets an email with the details and the shift appears in their "My plan" view (a dedicated Planning portal for those without a user).

Bulk publishing works like this: you plan the whole week, review it, use Publish from the plan choosing the period and whether to include or exclude open shifts and certain employees, then Publish and send, and all employees are notified together. Employees without a work email are completed in the window (Save and send the plan). The right flow is to build the plan as a draft, review it for conflicts, and publish it in a batch. Publishing shifts one by one creates notification noise and confuses employees.

Time off and contracts are respected automatically

Planning integrates with HR with no extra work. When an employee requests time off in the Time Off app and it is approved, a grey background appears on their Gantt, automatic scheduling skips them and, if a shift had already been planned, the administrator receives a visual conflict warning. An employee on a fixed-term contract does not receive shifts outside the contract period, so they are not scheduled beyond the end date of the relationship. Public holidays, configured in HR (Employees, Holidays), are automatically excluded from assignment.

Open shifts for flexibility and self-service

Open shifts are published without a resource and employees can take them. You create a shift leaving the resource field empty and stating the required role; with Publish the shift appears in the portal as "Available". The employee sees it, uses "Take this shift", the shift is assigned to them and the administrator is notified.

To give up a shift there is the swap: the employee uses "Ask for a swap" on their shift, the other qualified employees are notified, one accepts and the swap is processed. Alternatively you enable "Allow unassignment" in the team settings: the employee unassigns themselves, the shift goes back to open and another can take it.

Configuration

Shift templates collect recurring configurations as presets. The template "Morning cashier" has role cashier, start 08:00, end 14:00, and possibly the project. The template "Evening service at the restaurant" has role head waiter, from 18:00 to 23:30. When creating a shift you choose the template and all the fields are prefilled: only resource and date remain.

Recurring shifts are set with the Repeat switch: every one week, on Monday, Wednesday and Friday, until a date or a number of occurrences. They are planned (without publishing) up to six months ahead by default; beyond that, Odoo creates new recurrences gradually as the planning horizon advances.

For field or project activities there is the link with sales orders. A service product with Plan services enabled and a role, once the order is confirmed, generates shifts to be planned. The To plan button on the order opens the plan: you choose the open shift for the role, assign the resource, publish. The by-sales-order view shows which employees are planned for each customer order, and the timesheets of those shifts are linked to the order, so billable hours are tracked automatically. The Project field of the shift requires the Project planning setting, and shifts are linked to a Sales order (before it was the Sales order line).

Field Service in Odoo 20

In Odoo 20 field service is part of Planning (Planning, Configuration, Settings, Field Service, with billing, products, customer report, geolocation and worksheets). An intervention is a shift with a Customer and, in addition, an optional Sales order, a Worksheet and the Under warranty flag (materials and services added by the shift are not invoiced). It can be created directly in Planning, from a sales order or from a Helpdesk ticket (Plan intervention).

The typical path: the intervention is published, the technician opens it (My map shows the day's interventions), records the work, fills in the worksheet and adds the materials used; the customer report is generated and signed; materials and time are invoiced through the linked sales order, unless it is under warranty. The main functions: recording of interventions on published shifts, geolocation at start and end, customised worksheets, materials used added to the order, time-based invoicing (with Project and Timesheets), customer report to be signed, technician's map (Planning, Planning, My map; administrators: Planning, Maps) and route planning with the Mapbox integration.

The flows

Creating the weekly plan. On Monday, in the planning week of the following one, the administrator opens the Planning app in the by-role view and reviews which shifts are open, that is unassigned. With Automatic planning Odoo assigns available resources to the open shifts. The administrator reviews the assignments (conflicts, overtime, missing roles), makes manual corrections if needed and then uses Publish, Publish and send: all employees receive the following week's plan.

Resolving conflicts. There are three types of conflict: double booking (an employee with two overlapping shifts, red warning in the Gantt), overlap with time off (a shift over an approved leave, warning with a grey background) and the end of the contract (a shift after the end date, a warning icon on the shift). It is resolved by reassigning the shift to another resource, splitting it or cancelling it. Odoo does not remove conflicting shifts by itself: the administrator must resolve it.

Reporting. The Planning analysis (Reporting, Planning analysis) compares planned hours with worked hours (if timesheets are integrated): per employee it says who is over- or under-used, per role whether there is a staff shortage in a function, per project whether the allocated capacity is enough. The utilisation rate is planned hours divided by the hours available from working hours, per cent. The target is between 80 and 90 per cent: below 70 there is under-use, above 95 a risk of burnout.

What changes with Odoo 20

Odoo 20 Enterprise is the reference. Before classifying a need as development (Studio or custom), it pays to test it against these functions.

The biggest novelty is precisely field service inside Planning, described above. In addition, shifts from sales orders (a service product with Plan services and a role, To plan button on the order) and the revised publishing (Publish on a single shift or from the plan for a whole period, with Publish and send; Planning portal for those without a user). The functions already present in Odoo 19 remain valid: automatic scheduling of open shifts by hours, roles, availability and time off, with undo and preview before publishing; splitting long shifts from the Gantt, creating multi-day shifts from the Gantt and several shifts from calendar templates; shift swaps at the employees' request; recurrences that take availability into account; the planning analysis that compares planned hours with actual attendance with coloured Gantt views; the integration with Rental, which creates and synchronises shifts for rental periods, and which now has a rental orders dashboard.

For development requests the guidance is this: shifts on spreadsheets, manual availability checks, custom shift-swap flows, separate planning-versus-attendance reports and separate technician dispatch tools are tested first against Odoo 20 Planning (including field service), Attendances, Time Off and Rental.

The justifications you hear

In the company they sayIn reality
"We plan in Excel and share on WhatsApp"Excel has no integration with time off, does not know contracts, does not plan automatically and gives employees no self-service. Every change has to be redistributed by hand.
"Our plan never changes, we don't need a tool"Stable plans are the easiest to configure in Odoo (recurring shifts) and still benefit from the integration with time off and visibility for employees.
"We don't assign roles because everyone does everything"Without roles automatic scheduling cannot assign anyone to open shifts. Roles can be generic ("operator"): they need not be granular.
"Employees don't need to see the plan in advance"People who do not know the plan in advance have more absenteeism and less satisfaction. The portal view costs nothing extra once the shifts are published.
"We publish shifts one at a time as we define them"Planning and publishing in a batch is faster and creates less notification noise. You plan the whole week, then publish once.
"Planning is linked to Project, why is it a separate app?"Planning schedules when work is done, Project manages which tasks get completed. They can be linked (shift, project) but they serve different operational purposes.

Warning signs

  • Plans kept in Excel, WhatsApp or shared calendars outside Odoo.
  • No role configured: automatic scheduling is unusable and all shifts are assigned by hand.
  • Shifts never published: employees do not see their plan.
  • Time off not integrated: employees with shifts assigned during approved leave.
  • No shift template: every shift is created from scratch, with a lot of administrative work.
  • Timesheets not linked to shifts: impossible to compare planned and actual hours.
  • Recurring shifts not used for stable plans: the administrator recreates the same shifts every week.
  • Open shifts never used: no self-service or flexibility for employees.
  • Planning horizon reviewed to less than a week: employees are notified late.

How to check a configuration

After configuring or assessing the planning, the check goes through these controls:

  • all employee resources are configured with correct working hours and roles;
  • there is at least one role for each distinct function or skill in the team;
  • a default role is set for each employee (automatic scheduling uses it as priority);
  • there are shift templates for the three to five most common types of recurring shift;
  • recurring shifts are configured for all stable weekly or monthly patterns;
  • the integration with time off is verified: approved leave appears as grey blocks in the Gantt;
  • public holidays are configured in HR and respected by automatic scheduling;
  • Automatic planning has been tried: open shifts go to qualified, available resources;
  • portal access is confirmed: employees see the plan in "My plan";
  • the batch publishing flow is established: you plan the whole week, review it, publish once;
  • open shifts are configured for at least one team, for employee self-service;
  • if there is field service or projects: the link with order lines is tried and shifts are tied to billable service orders;
  • the planning analysis is reviewed: utilisation per resource and role is monitored every month.

Standard, configuration, integration or custom development

To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: resource planning by roles, employees or generic resources; planning of shifts and schedules with a Gantt view; comparison of planned and actual hours through timesheets; conflict detection (double booking, over-allocation); integration with Project (tasks), Manufacturing (work orders), Sales and Helpdesk; field service inside Planning (interventions, worksheets, signed customer reports, technician's map, invoicing); open shifts published to employees for self-assignment.

Five questions help classify every gap before asking for a development:

  1. How is staff planning handled today? Shifts on Excel, an external tool, informally? Excel is standard. A dedicated workforce-management tool requires assessing replacement versus integration.
  2. How are resource conflicts (double booking, over-allocation) found? By hand or with a tool? Manual detection is a standard gap, solved by Planning's conflict warnings.
  3. Is planning tied to projects or manufacturing orders? Or is it an island? If it is disconnected it is a configuration gap: Planning must reflect manufacturing orders and project task assignments.
  4. How are plan changes communicated to employees? Email, WhatsApp, by word of mouth? Informal communication is solved with Planning's email and app notifications.
  5. Are there shift-based activities (factory shifts, field crews, retail)? If so, configuration with shift templates. Complex shift rules defined by union agreements may be custom development.

The typical classification of the most common cases is this:

Frequent gapTypical pathSigns that push towards custom
Staff shifts on ExcelStandardA dedicated workforce-management system (Quinyx, NICE and similar) with payroll integration
No conflict detectionStandardNone
Planning disconnected from manufacturingConfigurationComplex finite-capacity planning, requiring APS-level algorithms
Informal communication of the planConfigurationNone
Dispatching technicians in a separate tool or on a sheetConfiguration (Planning's field service)A dedicated intervention-management platform with deep IoT and asset integration that the company intends to keep
This article is an OIAR skill

What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.

odoo-planningA guide to designing and checking the Odoo 20 Enterprise Planning module: shifts for employees and material resources, roles as the matching key, automatic scheduling of open shifts, batch publishing, recurrences, link with sales orders and Field Service. It contains the warning signs, the justifications heard in companies and the questions for deciding between standard, configuration, integration and custom development. It is needed when setting up or checking staff planning in Odoo, with or without interviews with operations and shift managers.