InnerWeb
Skip to main content

Hosting a student group at the plant: a guide from invitation to exit

A group of 30 students from a technical university is a task for the secretariat that starts a week before the visit and ends with an exit scan. This guide walks through five steps: the list of addresses from the university, the bulk invitation, QR labels, training at the workstation and closing the day, without creating thirty accounts by hand.

144
addresses in one bulk invitation
Source: card
0
accounts created by hand by the secretariat
Source: card

Step 1: the list of email addresses from the university

The university provides the group supervisor with a list of student email addresses. The supervisor, an active internal employee of the plant, is also the person against whom the planned visit is booked. Without a supervisor a visit cannot be planned, so naming the person on the plant side is the first task.

A planned visit is equivalent to a one-day permit, with no time specified, for a person from an external company entering without work. Training, qualifications and an active account still decide entry, so the visit does not bypass induction training.

Visits are planned from today, at most 377 days ahead and for no more than 34 days at the same time. For a one-day group visit these limits do not matter, but for multi-week placements 34 days is the limit of a single planned visit.

Step 2: one bulk invitation instead of thirty accounts

The secretariat pastes the addresses into a bulk invitation. A single request handles up to 144 addresses with a preview before sending, so a group of 30 fits into one request. The limit is 5 requests per 13 minutes per user.

A bulk invitation does not create accounts: the student registers on their own. The secretariat does not retype thirty names, and the system does not create accounts for people who do not arrive. A label printing request can be attached to the invitation for the secretariat.

  • paste the list of addresses, up to 144 in one request
  • check the preview before sending
  • attach a label printing request if guests will not arrive with a code
  • remember the limit of 5 requests per 13 minutes

Limits for hosting a student group

Limits for hosting a student groupHorizontal bar chart: 144 addresses, 89 entries in the label list, 34 minutes of group lifetime.050100150valueAddresses in an invitationAddresses in an invitation: 144 value144Entries in the label listEntries in the label list: 89 value89Minutes of group lifetimeMinutes of group lifetime: 34 value34
Source: Documentation of bulk invitations and the registration station

Step 3: QR labels and the account language

The To print QR code list shows people who started training in the last 13 days and never had a printed label. It holds up to 89 entries and refreshes every 34 seconds. The secretariat prints labels for the whole group from this list.

The account language decides the version of the video and the interface. Polish and English are available by default, and the reactor also supports Russian and Ukrainian. For a mixed group with a few students from abroad, the secretariat chooses the language when the account is created, not at the training screen.

Step 4: group induction training at the workstation

The induction training can be played for the whole group at once, and the group completion records the entry for all participants with one click. The group stays on the server for 34 minutes. A student who scanned in after the training started is not added to the running session.

The rescan window is sliding and set in seconds, with a minimum of one second. A student who scans the code every dozen or so seconds is welcomed again and stays on the list of people present. The exit is recorded only after a real break.

What does the supervisor do during the training?

The supervisor stays with the group and confirms that everyone is counted. When someone scans in too late, the supervisor notes them for the next session. After the group completion, movement around the plant takes place under the supervisor's control, not the secretariat's.

Step 5: exit and closing the day

The last scan at the exit closes the entry. An entry without an exit scan closes automatically after 12 hours, and the Uncertain tab window is 24 hours by default. For security this means one thing to check after the visit: whether every student has an exit entry.

The audit evidence is the list of people with a training record and both an entry and an exit. The guide does not promise compliance with a specific regulation, but it provides a document that the safety manager can show to an auditor.

Checklist

Video

Frequently asked questions

Does the secretariat create accounts by hand?

No. A bulk invitation does not create accounts, the student registers personally, and the QR label is created together with the account.

What if a student does not have a university email address?

The secretariat can register them at the desk by providing first name, last name and a note of up to 64 characters. The account and the label are created in a single transaction.

Does a planned visit replace the training?

No. A visit replaces the one-day permit, but training, qualifications and an active account still decide entry.

Host a student group without manual work

We will show the whole flow from the bulk invitation to the exit scan. Book a demo with the secretariat and the safety manager.

Let's talk