Operators trust procedures that sound like their site, so if a digitization project rewrites everything into a generic corporate template, people notice the unfamiliar wording and equipment names right away, and adoption drops because the procedure no longer feels like theirs.
The goal should be to change how the procedure is delivered, steps on a device instead of pages in a binder, without changing the content the site already wrote and approved. Interface works from the site’s own document, so the steps keep the language and names operators already know, and any change to the wording is something your team reviews rather than something that happens quietly in the background.