InnerWeb
Skip to main content

QR pass by e-mail: sending best practices for the host

A QR pass sent too early encourages arriving without training, and a pass sent twice raises the question of which code is valid. Below are practices that help the host choose the moment and the channel of sending, and understand what the system does automatically.

1
message with the code per person and badge
Source: card
64 characters
length of the QR code token
Source: card

Why the moment of sending matters

For the host the pass is the last element of the invitation: the guest gets the code and knows they can come. If the message arrives before the training, the guest appears at the gate and sees a red verdict. If it arrives twice, the guest does not know which code to show the guard.

The system assumes that the message with the code goes out once, at the right moment. The host does not have to watch this manually, but should understand the rules so as not to promise the guest things that result from a different order of events.

Sending practices

Six practices resulting from the rules of sending the access QR code.

1. Send the code only after the training

The message with the QR code goes out only when the gate would admit the person in terms of trainings. Permits, the visit and the health declaration do not block sending, because the code is needed to enter and to sign. The host should therefore expect the guest to get the code after completing the training, not right after the invitation.

2. Do not send the code manually in addition

The message is sent once: the guarantee comes from an atomic change of a flag in the database, so three independent triggers (new badge, completed training, queue) produce exactly one message. Manually resending the code through the same channel creates two messages that the system did not plan.

3. Make sure the e-mail and phone number are correct

E-mail has priority, and if there is no e-mail but a phone number is present, the code goes by SMS. A person with neither e-mail nor phone receives nothing, and the badge is printed by the security team. The host entering the guest's data should give at least one of these channels, so that the guest does not have to wait for a printout at the gate.

4. Remember that internal employees are excluded

Employees of the plant are excluded from sending the code. The host should therefore not promise an e-mailed pass to their own team: employees use their own badges and cards.

5. Explain to the guest what to show

The QR badge has a token generated at random (32 bytes, 64 hexadecimal characters), not from a number or a date, so it cannot be guessed. The guest may show the code on a phone screen or on a printout. It is worth writing in the invitation that the code is personal and must not be passed on to other people.

6. Invalidate the code when a badge is lost

Cancelling a badge creates a new one and keeps the history of the previous ones. The public address on the badge does not reveal anything about the person or the plant, so a stranger's phone that scans a lost badge will not learn who owns it. Even so, a lost badge should be reported, so that the security team cancels it and issues a new one.

Delivery channels of the code by priority

Delivery channels of the code by priorityHorizontal bar chart of the order of delivery channels: e-mail, SMS, printout by the security team.0123priorityE-mailE-mail: 3 priority3SMSSMS: 2 priority2Printout by securityPrintout by security: 1 priority1
Source: Order of channels per documentation of QR code sending; ordinal scale, not a statistic

Paper badge and printing at the gate

When a guest has neither e-mail nor phone, the badge is printed by the security team. The printout is neutral (plant logo, no server name) and scales to the label size given by the printer driver, not to a fixed format. Therefore when the type of labels changes, the template need not be changed; it is enough to set the right size in the driver.

The host can anticipate this case: if they know the guest will have no phone, they should warn the security team so that the label is prepared in advance. This shortens the queue at peak time.

How to check that the guest got the code

The host should check the status of the message in the system after the training is completed, rather than calling the guest to ask about their inbox. If the message did not go out, the most common causes are a missing e-mail address or an unfinished training. The remedy is correcting the data, not a manual resend.

Checklist

Video

Frequently asked questions

Will the guest get the code before the training?

No. The message goes out only when the gate would admit the person in terms of trainings.

Can the code arrive twice?

Not through the system's mechanism. The atomic change of the flag in the database produces exactly one message, even when three independent triggers run.

What if the guest has neither e-mail nor phone?

They receive nothing, and the security team prints the badge. It is worth warning the reception post so that the printout is prepared in advance.

Inviting guests and contractors?

We will show how the invitation, the training and the sending of the QR code look from the host's side, on demonstration data.

Let's talk