InnerWeb
Skip to main content

Main task closure confirmation: notes for service teams

Technicians close tasks in the application out of habit, often before the work has really started. That is why, when the main task is closed within the first 55 minutes from the actual start of the work, the application asks for confirmation. Below are notes for the administrator: how to explain this to users and to the supplier.

55 min
confirmation window from the actual start of the main work
Source: card

Where the need for confirmation comes from

In the paper process closing a task required a signature, so mistakes were rare. In the application closing is a single click, and technicians used to ticking off items may close the main task right after starting it, because that is their routine with other systems.

The effect is unpleasant: the permit looks as if the work has finished when the technician has only just begun. The confirmation is meant to catch such cases without blocking legitimate, short jobs.

How the confirmation works

When an external employee closes the main task within the first 55 minutes from the actual start of the main work, the application asks for confirmation with Yes or No. The window is counted by the server clock, so the result does not depend on the settings of the phone's clock.

It is a soft confirmation, not a server-side block, and it applies only to the external view. A person on the plant side does not see this question, so their closings are not slowed down.

Why 55 minutes and not 60

The window follows the Fibonacci standard used at InnerWeb, not the round value of 60. If users ask about the unusual number, explain that it is a deliberate value from the standard, not an accident.

What a soft confirmation means

Answering Yes allows the task to be closed, and short jobs remain possible. The question is meant to stop the reflex, not to forbid closing.

Example: time from the start of the work to closing the task

Example: time from the start of the work to closing the taskBar chart: reflex closing 3 min, confirmation threshold 55 min, typical closing 180 min.050100150200minReflex after entry: 3 min3 minReflex after entryConfirmation threshold: 55 min55 minConfirmation thresholdTypical closing: 180 min180 minTypical closing
Source: Sample calculation: times assumed for illustration, 55 min threshold from the card

How to explain it to users

It is best to start with one sentence: the system asks because in the first hour of work a task is usually closed by mistake. Add that answering No leaves the task open and breaks nothing.

An example from real life works well in training: the technician opens the main task, reflexively clicks close after entering the place of work, and gets the question. It is worth showing this once on screen, before anyone sees it at the machine.

Talking with the service supplier

With the supplier talk about the fact that the confirmation is not an accusation against technicians, but a safeguard against a click error. Ask for examples where the supplier really finishes the work in less than 55 minutes, so that the administrator can consider how to frame this in the templates.

Remember the relation to other rules: the status of especially dangerous work is independent of the permit status, and unclosed tasks of this kind do not block the permit from moving between stages. Confirming the closing of the main task does not change these rules.

How to measure whether the confirmation helps

After a few weeks check how many times a user answered No, that is, withdrew the closing. Each such answer is a closing that could have been a mistake. If No answers are almost absent, technicians close deliberately and the confirmation is invisible. If there are many, it is worth going back to training.

A second signal is complaints about the question. If technicians regularly finish the work in less than 55 minutes, the template may have main tasks that are too fragmented. Then it is better to change the template than to ask users for patience.

Remember that the question is soft: it proves nothing about the quality of the work, and only reduces the number of accidental closings. The proof of performance remains in the tasks, the protocol and the permit records.

Finally, add a one-sentence instruction for external users, for example in the training invitation: close the main task only after the work is finished, and if a question appears in the first hour, answer truthfully. Such wording sets expectations and reduces the number of questions to the administrator. All numbers in the examples on this page are a sample calculation based on the assumptions given in the text, not data from a specific plant.

Video

Frequently asked questions

Does the confirmation block closing the task?

No. It is a soft Yes or No confirmation, not a server-side block.

Does the plant's user also see the question?

No. The confirmation applies only to the external view, that is, to the external company.

What if the phone's clock is wrong?

The window is counted by the server clock, so the phone setting does not affect the result.

We will show this to users on screen

Book a short training for administrators: we will go through the closing confirmation and set up the talk with the service supplier.

Let's talk