Why handover must be planned from the start
The condition for a successful rollout on the plant's side is at least 2 administrators and timely delivery of the list of companies, training materials, permit templates and the plant layout. If administrators are appointed in the last week, they will not get through the configuration, and they will learn about the system only as much as they see in the training. That is why handover starts in the first week, not the last.
This guide assumes a 6-8 week schedule. During that time the plant moves from questions about scope to independent work in the system, while the implementer gradually hands over further areas.
Four stages of handover
Handover is best divided into four stages, each with an end point that can be checked.
Stage 1. Appointing two administrators
At the start of the rollout the plant names at least two people. One person is not enough, because leave or a job change stops configuration changes. Ideally, the administrators come from different departments, for example safety and IT.
Stage 2. Joint configuration
The implementer and the administrators configure the instance together for the plant's process: roles, the list of companies, permit templates and the plant layout. The administrators make the changes themselves, and the implementer corrects and explains. The rule: whoever clicks, learns.
Stage 3. Administrator training
Administrator training takes about 6 hours for 2 people. This is the time when administrators practice daily actions: creating accounts, handling requests, adding materials, granting permissions.
Stage 4. Acceptance by a passed test training
In the 6-8 week schedule the training materials (videos and PDFs in two languages with tests) are prepared in weeks 3-4, and acceptance is a passed test training and a test permit with a PDF printout. They are carried out by the plant's administrators, not by the implementer: this is the proof that the handover has worked.
Who makes the changes at each handover stage (share of the plant)
What the administrator should be able to do after handover
The list of minimum skills is short and checkable: create an employee account, assign a role, add a training material, prepare and approve a permit, print a PDF document, and answer a user's question about lack of access. When the administrator can do this without help, the handover is effective.
Adding a video to the material library is a data change in the installation catalogue file, not a code change; the service administrator also edits the title, number, category, description and thumbnail from the browser. Video files have no public addresses and play only for logged-in users.
Support after handover
After the production start, user support (type C) has a response time of up to 7 days, and during the stabilization stage weekly status meetings take place. This allows the administrators to raise questions that appear only in real use.
Launching another module requires training for the implementation team and configuration for the plant's process; this training falls within the support under the maintenance agreement. Trainings and work beyond the scope are settled separately, indicatively at about 300 PLN gross per hour plus travel (indicative rates from 2025-2026 rollouts; individual quote).
Audit evidence of handover
To document the handover, keep: the list of two administrators, the record of administrator training, the passed test training, the test permit with a PDF printout, and the note from the last status meeting. Such a summary provides audit evidence that the plant can run the system on its own.
Video
Frequently asked questions
Why two administrators?
It is the condition for a successful rollout on the plant's side. One person is a single point of failure during leave or a job change.
Who carries out the test training at acceptance?
The plant's administrators. A passed test training and a test permit with a PDF printout are the proof that the handover has worked.
Is there support after handover?
Yes. User support type C has a response time of up to 7 days, and during stabilization after the start weekly status meetings take place.
Plan the handover of administration
We will agree with you on two administrators, training dates and the acceptance criterion right at the start of the rollout. Arrange a meeting with the InnerWeb team.
Let's talk