What the support agreement gives
User support (type C) has a response time of up to 7 days, and during the stabilization stage after the start weekly status meetings take place. This rhythm is the core of the checklist: once a week you meet the implementer and go through the list of open questions. A response time of up to 7 days means questions need not be treated as failures, but also that they should not be left lying around.
The checklist covers eight weeks, because the first eight weeks after the start are usually the time when users get to know the system in production conditions, and the plant's administrators take on the role of first-line support.
Register of user questions
The simplest register is a table with five columns: date, who asks, what about, who answers, and whether it is closed. Each question gets an owner. Questions that repeat three times should be turned into training material: a short video or a card with instructions.
Adding a video to the material library is a data change in the installation catalogue file, not a code change, so the answer to a repeated question can appear in the library without waiting for the next system version.
Sample wave of user questions over eight weeks
Weekly status meetings
A status meeting should not exceed 30 minutes. A fixed agenda: new questions, repeated questions, response time, decisions to make. Each meeting ends with a list of tasks with dates and responsible people. The following week you start from this list, not from zero.
If during the week the need arises to launch another module, remember that it requires training for the implementation team and configuration for the plant's process, and the training falls within the support under the maintenance agreement. Schedule it at the meeting, not on the side.
Rhythm of the eight weeks
Weeks 1-2 bring the most questions about logging in, roles and basic actions. Weeks 3-4 bring questions about exceptions: people without a mailbox, external companies, trainings in another language. Weeks 5-6 are requests for configuration changes. Weeks 7-8 are preparation for closing the stabilization: who maintains the materials, who is the first line, what a request outside the scope looks like.
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). A conversation about this in week 7 is better than in week 9.
Checklist
Video
Frequently asked questions
How quickly will we get an answer to a question?
User support type C has a response time of up to 7 days. Urgent matters should be raised at the weekly status meeting.
Does every question require a formal request?
No. The plant's administrators answer some questions themselves, and only those they cannot resolve go to the implementer.
Does another module require separate training?
It requires training for the implementation team and configuration for the plant's process. The training falls within the support under the maintenance agreement.
Plan support after go-live
We will agree with you on the rhythm of weekly meetings and a simple question register before the production start. Arrange a meeting with the InnerWeb team.
Let's talk