Updates may relate to the security and operation of the software. Their management requires accountability and verification, especially when the instrument supports essential activities. NIST describes the patch management process by including identification, priority, installation, and verification; the organization must adapt it to its context.
I propose to know the applications involved and to agree the path with those who have the technical skills. The urgency and timing of the intervention depends on the risk and the appropriate indications. The operational schedule must allow for a timely update and a verified resumption of work.
In a hypothetical example, an order preparation program is updated before a busy period. A verification of essential functions can recognize compatibility issues before many orders arrive. The test must follow the instructions of the technical support team.
The recording of the intervention should indicate outcome and problems still open. An installation that is started does not automatically amount to a completed verification. The continuity of the work depends on the possibility to know the actual status of the instrument and to communicate any limitations to the people who use it.