Monday morning, and the dispatcher is laying out the week. They drag a job from the buffer onto Thursday, and it lands on today at midnight and disappears from the plan before anyone notices. Small things like that cost more nerves than serious breakdowns, because they happen every single day. On 3 August 2026 we released a set of changes that take several of them out of daily work.

Dispatcher calendar: the job stays where you drop it

Dragging a job from the buffer onto the calendar was setting the wrong date. Instead of landing on the chosen day and time, the job ended up on today at 00:00. The dispatcher had to find it and correct it by hand, and if they did not notice, the technician simply did not go anywhere. We have fixed it. The job is saved exactly where you drop it.

The second change concerns the dialogs that appear after a double click — on a job or on an empty slot in the calendar. They were wide and almost empty, with three buttons squeezed into the left corner and no indication of which job they related to. Now it is a compact list. Each entry has an icon, a name and one sentence explaining what will happen if you click it. The header shows the job number and the times. We moved deletion away from the other options so it is harder to hit by mistake.

In daily work that means less undoing, fewer corrections and confidence that you are clicking on the job you have in mind.

The job form opens faster

You reported that adding and editing a job “sometimes takes a long time”. We checked it on the live system. The window itself appeared quickly, but on average more than 3 seconds passed before the form was ready to fill in. One time in twenty, over 5.

The cause was mundane. Every time the form opened, the system fetched the same lists again from scratch: departments, additional statuses, staff, watchers and equipment. That is data which changes once every few days, and it was being fetched dozens of times a day. Now the system remembers it for 10 minutes and reaches for the ready-made copy the next time.

One caveat. After adding a new department or a new member of staff, the change is visible immediately. In rare situations it may appear with a delay of up to 10 minutes — in which case refreshing the page is enough.

Photos taken on a phone reach the service report

Some photographs taken on a phone were being saved without the correct file type marker. The effect was that the photo was in the system but did not appear on the service report. The technician had proof the work had been done, and the customer could not see it. In a dispute, that photograph is often the only argument you have.

Now the system recognises the file type from its content rather than from its description, and corrects the marker automatically. It works regardless of which phone the technician uses or what settings they take photos with. Nobody in the company has to do anything or upload anything again. The photos are simply where they should be: in the report the customer receives.

Job handover and mileage in reports

Settling up with a subcontractor or with a technician from a neighbouring region usually ends in counting by hand. When the job changed hands, and how many kilometres had to be driven.

Two new tags have been added to custom report templates. The first inserts the moment a job was handed over to another employee. The system now records that date, so there is somewhere to take it from. The second calculates the travel distance from the employee’s address to the job address and gives it in kilometres.

Anyone settling with subcontractors per job, or paying extra for travel, now has that data straight in the report instead of assembling it from the calendar and a map. The tags are inserted into your own template just like the others, so the report you already use only needs two extra entries.

An additional technician with the full task description

When you added another technician to a job, the form had no “Additional description” field, and the text entered earlier on the main job was not carried over. The second person therefore travelled with nothing but the address and had to ring for the details.

The field is back where it belongs and saves correctly. Arrangements made with the customer, the floor number, the gate code or a note about access to the boiler room stay with the job instead of circulating over the phone.

Permissions visible in the user list

Checking who is an administrator, who is a dispatcher and who is a field worker meant opening each account for editing one by one. With a dozen or more people that is a quarter of an hour of clicking, and it usually gets done at the moment you have least time.

The user list has gained a “Permissions” column. Everyone’s role is visible from a single screen. It comes in handy when taking on a new employee and when tidying up after someone leaves the team.

The changes are already live

Everything described above has been working in Fieldworker since 3 August and requires no installation and nothing to switch on. If something in your daily work still takes longer than it should, write to us — most of the fixes above started with exactly that kind of report.