InnerWeb
Skip to main content

QR token next to a KD card: best practices for the contractor coordinator

Not every contractor should get a card from the access control system, and not every one can simply be written on a sheet of paper at the gate. Below are best practices for the contractor coordinator: the criteria for choosing an identifier with a QR token versus a KD card, and how both solutions coexist in one plant.

120
fewer administrative operations a year with 60 contractors
Source: sample calculation

Two carriers, one person

At a chemical plant two identity carriers meet at the gate: the card from the access control system, usually issued to employees and selected long-term contractors, and the identifier with a QR token read at the gate. Their coexistence is not a contradiction. The KD card answers the question whether the reader should open a door or a barrier, while the QR token answers the question whether the person meets the entry conditions in the InnerWeb system.

InnerWeb is a software producer, not a device maker. It does not produce or replace access control readers. The QR token is a complement that allows people to be covered by control when issuing a KD card would be too costly or too slow.

Practice 1: decide by contract length and scope of entry

The simplest criterion is the duration of the contract. For contractors who will enter the site for several months and through many doors, a KD card is justified, because they work in the same rhythm as employees. For contractors on a contract lasting a few days or a one-off job that takes them to a single hall, an identifier with a QR token is sufficient.

The second criterion is scope: whether the person must open internal doors controlled by readers. If so, a KD card is needed. If the person enters only through the main gate and stays close to a host, a QR token is usually enough.

  • Long-term contract and many passages: KD card.
  • Short contract, one gate: identifier with a QR token.
  • One-day visit: invitation and QR token.

Administrative operations for 60 contractors a year

Administrative operations for 60 contractors a yearBar chart: 180 operations for KD cards and 60 operations for identifiers with a QR token.050100150200operationsKD card: 180 operations180KD cardQR token: 60 operations60QR token
Source: Sample calculation: 3 operations per card, 1 per QR identifier, 60 people

Practice 2: do not duplicate verification, link the events

If a contractor has a KD card and the plant also uses a QR gate, decide which event is the source of truth for presence. InnerWeb receives card tap events from the KD system through a webhook, so a card tap can feed the same data as a token scan. Card reader events can be linked to qualifications, permits, attendance and working time records.

The worst solution is a parallel paper list. The contractor coordinator should require that any adopted path ends with an entry in one register.

Practice 3: the QR token identifies, it does not grant permission

The QR token on the badge is read at the gate, but simply holding the badge does not open the way onto the site. The verdict depends on trainings, qualifications, a permit or visit, and the activity of the account. The contractor should know this before arriving, and should not find out at the gate.

It is worth printing the badge only after the induction training is completed, or including in the invitation a clear note that the gate checks the conditions at every scan.

What happens to the badge after the contract ends

The housekeeping rule: the end of the contract closes the person's account in the external companies module, and the badge stops being a permission. The coordinator should review the list of active contractor accounts once a month and compare it with the list of active contracts.

Practice 4: count the cost of carriers over the whole cycle

The sample calculation shows the logic of the choice. With 60 contractors a year on short contracts, issuing a KD card to each would mean 60 cards to program in the KD system, collect and return. A QR identifier printed from the system does not require any change in the KD system configuration. Card costs depend on the supplier and the plant's policy, so we do not give amounts, only the number of administrative operations.

Assumed: a card requires 3 administrative operations per person (request, programming, return), and a QR identifier requires 1 operation (printing from the system). The difference for 60 people is 120 operations a year.

Practice 5: set the rule and document the exceptions

One decision table in the plant's instruction works well: type of contract, scope of passages, carrier. Exceptions are reported by the contractor coordinator and approved by the chief of security. Without this table, security and the purchasing department make decisions independently, and after a year the plant runs four different schemes.

Example calculation

Carrier handling for short contracts

Assumptions
ParameterValue
Contractors on short contracts60 people a year
Operations per KD card3 operations
Operations per QR identifier1 operation

Result: 180 operations for KD cards versus 60 for QR tokens, a difference of 120

Note: Sample calculation; the number of operations depends on the plant's procedures and the KD supplier.

Checklist

Video

Frequently asked questions

Does InnerWeb issue access control cards?

No. InnerWeb is a software producer and neither makes nor replaces the KD system readers.

Does a contractor with a KD card also need a QR token?

It depends on the chosen model. A card tap can feed the same data through a webhook, and a QR token is needed at a gate with a verdict.

Does the QR token contain personal data?

No. It is an unguessable string assigned to a person in the system.

Who should choose the carrier?

The contractor coordinator, according to the decision table, and exceptions are approved by the chief of security.

Match carriers to contracts

We will help you prepare a decision table for your contractors and connect KD events with the QR gate. Book a conversation with the InnerWeb team.

Let's talk