All Collections
Problem solving
Mobile App
The intervention is completed in a wrong date
The intervention is completed in a wrong date
Thao Nguyen avatar
Written by Thao Nguyen
Updated over a week ago

It may happen that an intervention that has just been completed from the mobile app does not transmit the correct intervention dates on the web application. This article aims to detail the use cases that can cause problems, or rather a confusion, and how to avoid them.

How does this happen?

Let's take as an example an intervention created from the web application on 01/01 which has a planned date of 01/31.


"You regularly notice that interventions have dates carried out which do not correspond at all with what was actually done in the field by your technicians, they tell you that they have not modified the interventions before the intervention date. you do not see any changes to this information in the history, and you don't understand why or how this is happening?"

Process :

When the person in charge of creating and planning the intervention assigns this intervention to a technician, the intervention will then be present in the next synchronization that the technician will do on the Organilog mobile application. That is to say that if the technician synchronizes his information to update it on his Organilog mobile application on 02/01, his daily schedule will be updated and he will then find the intervention created by the planner for 31/01 on 31/01.

If the technician consults this intervention from the mobile application in edit mode, i.e. he clicked on the pen to modify the information, and even if he does not enter any information, or does not modify anything if he clicks on "Save" at the bottom of the page, the current date will be entered in the " Start date " field of the " Intervention carried out " section.
So in this example on 02/01. At the next synchronization of its data on the mobile application, this information will be sent to the web application, and will therefore fill in the intervention form, in the previously mentioned part.

Why is the date filled in automatically?

The reason why the " Start date " of the " Intervention carried out " part is automatically filled in when you click on "Save" at the bottom of the edit page of an intervention from the Organilog mobile application is that in most of cases, all activities combined, an intervention is closed on the day it was planned. This saves time in editing information and also avoids typing errors.

How to prevent this from happening?

Start first by informing your employees who use Organilog of this mode of operation so that the information is known and that the "errors" are understood.

Solutions #1: Go Back Instead of Save

Indeed, when the technician out of curiosity or necessity enters edit mode on an intervention before its scheduled date when he has no information to enter and instead of clicking on "Save" at the bottom of the page, he uses the arrow at the top left to go back, no information is recorded, and therefore no information is synchronized.

Solution N°2: Display the dates performed in edit mode

For double security, and to allow your technicians to check the information before sending it, it is also possible to display the " Start date " and the " End date " of the " Intervention carried out " part on the edition in the Organilog mobile application.

To do this, enter the " Settings " of the Organilog mobile application, enter the " Modify an intervention " menu again and check " Modify dates ".
The dates will now be displayed when an intervention is edited, and will therefore allow the technician to check if the dates are correct.

Solution N°3: Lock interventions

We do not recommend this solution for the multiple errors it can generate.

It is indeed possible to lock an intervention so that it cannot be modified, and therefore, even if the speaker enters date and time information in this intervention from his mobile application, and synchronizes, the information will be blocked and will not appear in the intervention sheet on the web application.

To learn more about locking interventions, see this article.

Did this answer your question?