Foreman on ELT — Work — Documentation

Creating and dispatching tasks

Mon, 01 Jan 0001 00:00:00 +0000

Creating and dispatching tasks#

Tasks are typically created from the office side based on a customer request (phone call, email, customer portal). The foreman is responsible for making sure each task has a suitable installer and that the work progresses.

Creating a task#

Field Service → Orders → Create or via the landing-page shortcut.

Required fields:

Field	Purpose
Customer	Customer (contact). If new, create in Contacts first
Location	Customer site — if there are several, pick the right one
Description	Brief for the installer — what to do, where to start
Scheduled date	Planned start date — required for the planning calendar

Optional:

Planning calendar

Mon, 01 Jan 0001 00:00:00 +0000

Planning calendar#

The planning calendar is the foreman’s main tool — it shows all installers and their tasks side by side at a glance.

Open: Field Service → Planning Calendar.

Core view elements#

Days on the horizontal axis, installers on the vertical.
Each task is a coloured bar whose width = estimated duration.
Task colour = state or priority (office configures).
Green border = task complete. Can be filtered if desired.

Time-range zoom#

Top-bar buttons / quick selectors:

Inviting an assistant installer

Mon, 01 Jan 0001 00:00:00 +0000

Inviting an assistant installer#

The primary installer invites assistants onto a task when an extra pair of hands is needed at the site. This is an organic social flow: foreman doesn’t need to micro-manage, installers arrange amongst themselves and work agile.

Invitation from the PWA (installer side)#

Primary installer opens the task in the PWA.
Top of the task: “Request help” button.
Pick another installer from the list.
The task sends a push notification to the selected installer.

Accepting the invitation (assistant side)#

The assistant sees:

Approving hours and expenses

Mon, 01 Jan 0001 00:00:00 +0000

Approving hours and expenses#

Weekly rhythm: the foreman reviews the week’s hours and expenses before they move to invoicing or payroll.

Why approval matters#

Installer-submitted lines can contain errors (wrong day, wrong task, wrong amount).
Business needs review: approved line → billed to customer → ELT’s revenue. A bad line → customer complains.
Tax authority requires: mileage and per diems must be documented sensibly before payroll.

Approving hours#

Field Service → Timesheets or HR → Timesheets.

Installer status

Mon, 01 Jan 0001 00:00:00 +0000

Installer status#

This page gathers the views from which the foreman can see in real time what installers are doing and where things are slowing down.

Workers list#

Field Service → Workers.

Shows all fsm.person rows at ELT — practically every installer with rights to take tasks. Columns:

Name + Email
User — Odoo user link (elt_user_id, 200.7+)
This week’s hours — summary
Active tasks — how many
Certificates / competencies (if used)

Click a row → the person’s detail view, calendar, history.