InnerWeb
Skip to main content

Good practices for personalising employee cards

Personalisation is the moment when a blank card becomes proof of identity: it receives the application, the keys, the number, the printout and the link to a person. Below are the practices that let you organise the station in HR or security so that a card never reaches a person without permissions.

5
practices for the personalisation station
Source: own elaboration
50
cards between sample checks (assumption)
Source: recommendation

What personalisation includes

Card personalisation covers writing the application and keys, assigning the number, and the printout and linking the card to a person in the register. Each of these elements can be carried out correctly, and yet the whole process will fail if the last step, the link to the person, was skipped or made on the wrong account.

That is why we treat personalisation as one process with one owner, not four independent activities. The owner is responsible for ensuring that a card leaving the station has its keys, number, printout and an entry in the register.

Practice 1: a station in a closed room with a register of blank cards

Blank cards have value, because each of them can be written with the keys of the plant. Keep them in a locked cabinet, and keep the stock in a register: how many cards were issued, how many remain, how many were destroyed. The difference between the stock and the number of entries in the register is the first signal of misuse.

The station should not be in an open office space. A room accessible to two people is enough, with a register of key collection for the cabinet.

Sample time of the steps for personalising one card (assumption)

Sample time of the steps for personalising one card (assumption)Bars: confirming the person 2 minutes, writing keys 1, printout 2, register 1.012minutesConfirming the person: 2 minutes2Confirming the personWriting keys: 1 minutes1Writing keysPrintout: 2 minutes2PrintoutRegister entry: 1 minutes1Register entry
Source: Sample calculation: times assumed for planning the station

Practice 2: the master key does not reach the operator

The station operator writes keys to a card without access to the master key. Good practice is key diversification: the card key is derived from the master key and the unique UID of the card, so the leak of one card key does not open the others. The master key remains under the control of the key administrator or in the SAM module.

If the personalisation tool requires the key to be entered in plain form, this is a signal to talk to the supplier, not a reason to write the key on a note at the station.

Practice 3: issue after confirming the person

A card is issued to a person who has an active contract in HR, and in the case of external companies, to a person on the list submitted by the inviting person. The recipient signs for the card, and the station checks an identity document. The photo on the printout must match the person collecting the card.

A different path applies to visitors: a visitor card has limited validity, limited zones and mandatory return at the exit, and the register indicates the inviting person. The QR code on the badge serves the gate, the invitation and logging in to training, but a scan does not log on by itself: confirmation by the person is required.

Practice 4: a register with the person carrying out the operation

The card register should contain the number, the person, the issue date, the status (active, blocked, returned), the reason for the change and the person who carried out the operation. Without the last field the register does not answer the question of who issued a card that later turned out to be a problem.

The register is kept in the system, not in a spreadsheet on the operator's drive. Status changes carry a time stamp, and an entry cannot be deleted: an erroneous entry is closed with a further entry giving the reason for the correction.

Practice 5: sample check after personalisation

Once per batch, for example every 50 cards issued, select a card at random and check it on a test reader: whether the number matches the register, whether the application responds with the correct key, and whether the printout is legible. A sample check catches configuration errors at the station before they affect the whole batch.

Cards that fail the check do not go to issue but to a separate box with an entry giving the reason. Only after analysing the cause does the station return to work.

Common mistakes that only show up after months

The most frequent mistake is personalising a batch of cards from a list that was not verified with HR. The card is technically correct, but assigned to a person who has already left or has different data. The second mistake is a printout with a different photo from the one in the register, which only comes to light when a guard checks it.

The third mistake is the lack of a procedure for cards that were not collected: a card printed but not collected by the person stays in a drawer with an active status. The rule is simple: a card not collected within 7 days changes its status to blocked, and the person receives a new one only after being confirmed again.

The fourth mistake is mixing the employee and visitor paths at one station without a distinction in the register. A visitor card that looks like an employee card makes it easier for people who should not be there to pass the gate. A clear appearance and a short validity are cheaper protection than a guard checking each person.

Conclusion for HR and security

Good personalisation is dull: the same steps, the same order, a register, and a sample check. InnerWeb does not personalise cards and does not supply the station, but it works with the result: if the register is correct, a card tap event is linked to the person, qualifications and attendance without additional corrections.

Checklist

Video

Frequently asked questions

Who should run the personalisation station?

A person appointed by HR or security, not the person who manages the master key.

Is scanning a QR code enough to enter?

No. A scan does not log on by itself: confirmation by the person is required.

What should be entered in the card register?

The number, the person, the issue date, the status, the reason for the change and the person who carried out the operation.

How often should the sample be checked?

For example every 50 cards issued, on a test reader.

Sources

Let us organise the personalisation station

We will show how the card register connects with tap events, qualifications and attendance in one system.

Let's talk