Field Service in Odoo 19:
Scheduling, Dispatching & Mobile Workforce

Your Technicians Are Driving 40% More Than They Need To

Most field service operations we audit share the same pattern: dispatchers assign tasks manually from a spreadsheet or a Kanban board, technicians call the office to ask what's next, and nobody knows whether the right parts are in the truck until the tech arrives on site. The result is wasted drive time, missed SLA windows, return visits for missing materials, and invoices that take days to generate because the paperwork sits in someone's truck until Friday.

Odoo 19's Field Service module addresses every one of these pain points. It connects the planning calendar to the dispatch map, puts task details and worksheets on the technician's phone, tracks parts consumption against inventory, captures customer signatures on site, and generates invoices the moment a task is marked done. The entire loop from service request to paid invoice happens inside one system.

This guide covers the complete setup: installing and configuring the module, defining task types and worksheet templates, configuring the scheduling calendar and dispatch logic, enabling the mobile experience for technicians, tracking parts and materials, capturing signatures, automating invoicing, and building the reports that show whether your operation is actually improving. Every menu path, field name, and code example is from Odoo 19 Community and Enterprise.

Defining Task Types, Templates, and SLA Policies for Field Service

Task types are the backbone of an organized field service operation. They determine the default duration, worksheet template, required skills, and checklist items for each kind of job. Navigate to Field Service → Configuration → Stages to define your pipeline stages, then create task templates under Field Service → Configuration → Task Templates.

A well-structured set of task types looks like this:

To seed these task types via XML data files (recommended for version-controlled, reproducible setups):

<?xml version="1.0" encoding="utf-8"?>
<odoo>
  <data noupdate="1">

    <!-- FSM Project reference -->
    <record id="fsm_project_main" model="project.project">
      <field name="name">Field Service</field>
      <field name="is_fsm">True</field>
      <field name="allow_timesheets">True</field>
      <field name="allow_worksheets">True</field>
      <field name="allow_material">True</field>
    </record>

    <!-- Task templates -->
    <record id="fsm_task_template_install" model="project.task">
      <field name="name">Installation</field>
      <field name="project_id" ref="fsm_project_main"/>
      <field name="is_fsm">True</field>
      <field name="planned_hours">2.0</field>
      <field name="tag_ids" eval="[
        (0, 0, {{'name': 'Installation'}}),
      ]"/>
      <field name="description">
        Standard installation procedure:
        1. Site survey and safety check
        2. Equipment unboxing and inspection
        3. Mounting and wiring
        4. System commissioning and testing
        5. Customer walkthrough and sign-off
      </field>
    </record>

    <record id="fsm_task_template_pm" model="project.task">
      <field name="name">Preventive Maintenance</field>
      <field name="project_id" ref="fsm_project_main"/>
      <field name="is_fsm">True</field>
      <field name="planned_hours">1.0</field>
      <field name="tag_ids" eval="[
        (0, 0, {{'name': 'Maintenance'}}),
      ]"/>
    </record>

    <record id="fsm_task_template_emergency" model="project.task">
      <field name="name">Emergency Repair</field>
      <field name="project_id" ref="fsm_project_main"/>
      <field name="is_fsm">True</field>
      <field name="planned_hours">3.0</field>
      <field name="priority">1</field>
      <field name="tag_ids" eval="[
        (0, 0, {{'name': 'Emergency'}}),
      ]"/>
    </record>

  </data>
</odoo>

Scheduling Field Tasks with the Planning Calendar and Gantt View

Scheduling is where Odoo 19 Field Service shines over spreadsheet-based operations. The Planning module (Enterprise) integrates directly with field tasks, showing every technician's availability on a single Gantt chart. Navigate to Field Service → Planning to access the scheduling view.

Key scheduling fields on the task form:

• planned_date_start / planned_date_end — The scheduled window. These populate the Gantt bars and calendar events.
• user_ids — The assigned technician(s). In Odoo 19, tasks support multiple assignees for jobs requiring a crew.
• planned_hours — Expected duration. The Gantt view uses this to size the bar when only a start date is set.
• partner_id — The customer. Their address populates the map pin for route planning.
• date_deadline — SLA deadline. Tasks approaching this date get highlighted in the calendar.

The Gantt view allows drag-and-drop rescheduling: grab a task bar and move it to a different time slot or a different technician row. Odoo automatically updates planned_date_start, planned_date_end, and user_ids. Conflicts (double-booking a technician) are highlighted with a red overlay.

For recurring maintenance schedules, use the Recurrence feature on the task form. Set the recurrence pattern (daily, weekly, monthly) and Odoo creates new tasks automatically. Each recurrence inherits the template's worksheet, tags, and planned duration.

Mobile Experience: How Technicians Use Odoo Field Service on Their Phones

Technicians access their tasks through the Odoo mobile app (available on iOS and Android) or through a mobile browser pointed at your Odoo instance. The Field Service module provides a simplified mobile interface that strips away the back-office complexity and shows only what the technician needs.

The mobile task flow looks like this:

• My Tasks list — Shows today's assigned tasks in chronological order. Each card shows the customer name, address, task type, and scheduled time.
• Navigate button — Taps open Google Maps or Apple Maps with the customer address pre-filled. The address comes from partner_id.contact_address_complete.
• Start Timer — One-tap timer that creates a timesheet entry linked to the task. The timer runs in the background while the tech works.
• Log Materials — Scan barcode or search for products. Quantities are deducted from the technician's assigned warehouse (typically a van stock location).
• Fill Worksheet — The worksheet template renders as a mobile-friendly form. Technicians fill checkboxes, text fields, photo uploads, and readings.
• Customer Signature — A full-screen signature pad. The customer signs with their finger. The signature is stored as a binary field on the task.
• Mark as Done — Moves the task to the "Done" stage, stops the timer, and triggers the invoice generation if configured.

For the mobile experience to work well, ensure your technicians' user accounts have the Field Service / User access group (under Settings → Users → [User] → Access Rights). This group limits the visible menus to only Field Service features, reducing confusion for non-office workers.

Worksheet Templates and Customer Signature Capture

Worksheet templates replace paper forms. Navigate to Field Service → Configuration → Worksheet Templates to create them. Each template is a Studio-designed form (Enterprise) or a custom QWeb report (Community) that defines the fields technicians fill out on site.

Common worksheet template patterns:

The customer signature is captured via the sign_template_id integration or the built-in signature widget on the task form. When a customer signs, the binary data is stored in worksheet_signature and rendered on the PDF report. This provides legally defensible proof of service completion.

To auto-send the completed worksheet to the customer, configure a server action triggered when the task stage changes to "Done":

• Go to Settings → Technical → Automation → Automated Actions
• Model: project.task
• Trigger: When stage_id is set to your "Done" stage
• Action: Send email using a template that includes the worksheet PDF as an attachment
• Filter: [('is_fsm', '=', True)]

Invoicing from Field Tasks: Time, Materials, and Fixed-Price Billing

Odoo 19 supports three invoicing models for field service, all configured at the project level under Field Service → Configuration → Projects → [Your FSM Project] → Settings tab:

The invoicing trigger is the "Create Invoice" button that appears on the task form once a task is marked as done and has billable lines (timesheet entries or consumed products). For automated invoicing, create a scheduled action that runs daily:

• Find all FSM tasks in "Done" stage with linked sale orders that have uninvoiced delivered quantities
• Group by customer to create one invoice per customer per day (not one per task)
• Auto-confirm the invoice and send it via email

The industry_fsm_sale module adds a "Products" smart button on the task form. When a technician adds a product here, it automatically creates a sale order line. This is the bridge between field consumption and invoicing — no manual data entry back at the office.

Field Service Reporting: KPIs, Dashboards, and Continuous Improvement

Navigate to Field Service → Reporting to access the built-in analysis views. The default pivot table can be configured to show the KPIs that matter for field operations:

For custom dashboards beyond the built-in pivot/graph views, you can create spreadsheet dashboards (Odoo 19 Enterprise) that pull live data from the project.task model. The spreadsheet editor supports Odoo-specific formulas like =ODOO.PIVOT() and =ODOO.LIST() that query directly against your field service data.

The most actionable report for dispatchers is the daily utilization heatmap: a grid of technicians on the Y axis and days on the X axis, with cells colored by utilization percentage. Green cells (70-85% utilization) indicate healthy workloads. Red cells (over 100%) indicate overbooking. White cells (under 40%) indicate capacity that should be filled with preventive maintenance or other scheduled work.

3 Field Service Mistakes That Cost You Repeat Visits and Revenue Leakage

Optimization Metadata