The new task list
This is the first screen a technician sees. It shows the jobs assigned to them, grouped into clear tabs, with the most common actions available right on each card — no need to open the task first.
What’s on the screen
The tabs at the top switch between Daily (today’s work), Tasks done, Late, Unassigned and Unplanned. A counter (e.g. Late 14) flags what needs attention.
Each card shows the task title, its location and equipment, and a status badge. The coloured buttons under a card are the actions the technician is allowed to take right now:
Begin or end the job.
Close it directly, if allowed.
Flag that more work is needed.
Pick up an unassigned job.
Finding the right tasks: filters & saved views
When a technician has a long list, the new filter sheet and saved views help them get to the right jobs in a couple of taps.
The filter sheet
Tapping the filter icon (top right of the list) opens a full sheet. Filters are organised into clear categories — Display, Locations, People, Dates, Equipment, Zones — and there’s a “Find a filter…” search box. The button at the bottom always shows how many tasks match (e.g. Show 5 tasks).
Saved views
A view is a saved set of filters. Pinned views appear as quick chips at the top of the sheet, and + New view saves the current filters for next time. The view selector (the small diagram icon in the header) lets a technician switch between their views instantly.
Opening a task: the new task screen
Tapping a card opens the redesigned task screen. Everything a technician needs is on one page, with the key actions pinned to the bottom.
Top to bottom
- The essentials — the linked ticket, the time slot, the location and the equipment.
- The description of what needs doing.
- Document the intervention — two big buttons, Dictate and Photo (covered in the next section).
- Documents — plans, photos and files attached to the job.
- Comments — the conversation thread for the task.
- Details — quick access to Costs, Chats, the parent ticket and Work periods.
The pinned bar at the bottom always shows the next actions: ▶ Start and ✓ End task.
Documenting the work: photos, voice notes & comments
We made it effortless to capture what happened on site — without typing on a phone.
Capture in one tap
In the Document the intervention block:
“Capture the state” — snap a picture straight into the task.
“Tap to speak” — the phone turns speech into text for a comment.
The comment thread
Every task has a comment thread. Technicians, managers and assignees can post messages, attach photos, and edit or delete their own messages. It’s the running log of the job — what was found, what was done, what’s left.
Closing a task — the easy case
For straightforward jobs, closing is genuinely one tap.
When a job has no mandatory fields and no required closing note, the technician simply taps ✓ Finish on the card (or End task inside the task) — and it’s done. No form, no extra screen.
A finished task is sent to the office as Done — ready for a manager to review and approve. (Technicians with the right permission can also Close it directly; see section 10.)
Closing a task — with fields & costs
When the ticket type requires it, ending a task opens a short form so the right information is captured before closing. The technician is guided — required items are clearly marked.
The closing form
Depending on how the ticket type is set up, the form can ask for things like Expertise, an Anomaly, a Charge number, dates (when the issue opened, when the technician arrived) and an unavailability duration. Anything mandatory shows a yellow REQUIRED tag and must be filled before the task can close.
At the bottom there’s a closing comment box and a file drop zone, then the green ✓ Mark as done button.
Logging costs
When costs are enabled, the task has its own Costs screen. Technicians can add hours, travel, materials and more, with a running Total. These costs flow straight onto the ticket for invoicing.
When a job isn’t fully done: follow-ups
Real interventions don’t always finish in one visit — a part is missing, a second trip is needed. The new follow-up tools handle exactly that.
Two ways to handle it
⚠ Requires follow-up — the technician flags that the job needs another intervention and leaves a short note (“waiting on a spare valve”). The ticket stays open until it’s resolved.
+ Create a follow-up task — when closing, the technician can spin off a new task for the remaining work in one go. Its title and description are pre-filled from the current job, so it takes seconds.
Documents shared from the ticket
Plans, schematics and photos attached to a ticket can now be pushed down to the relevant tasks — so technicians have the right reference on the job, not buried in the ticket.
What the technician sees
On the task’s Documents screen, shared files carry a small share badge and are labelled “Shared from the report”. They sit alongside any files the technician adds directly.
A technician can remove a shared document from their task (“Remove from this task”) — this only unlinks it from that task; the original on the ticket is untouched.
For managers: the desktop side window
On desktop, clicking a task opens a rich side window — the manager’s companion to the mobile screen. Everything about the task in one panel, without leaving the page.
The side window mirrors the mobile task screen: a header with the same actions (Start, End task, Close, Reopen…), then collapsible sections for Details, Documents, Comments, Costs and Work periods. Comments and documents stay perfectly in sync with what the technician sees on their phone.
The full ticket view
For managers: set it up
Most of what’s above is controlled per ticket type, under Settings › Ticket types. Here’s what to switch on.
The three task permissions
In each ticket type’s Report permissions table, you decide — role by role — who can self-serve closing and follow-ups:
| Permission | What it lets a role do |
|---|---|
| Can close (approve) their assigned tasks | Close a task directly, without waiting for a separate approval. |
| Can flag their assigned tasks as requiring follow-up | Mark a task Requires follow-up with a note. |
| Can close their tasks and create a follow-up task | Close a task and spin off a new follow-up task in one step. |
Sharing ticket documents with tasks
On demand: on a ticket, open a document’s Actions menu and choose Share with tasks, then tick the tasks that should receive it.
Automatically: on the ticket type, enable “Automatically share ticket documents with its tasks” — every document uploaded to those tickets reaches their tasks without any manual step.
