Why a card number must have an owner
A card swipe has value only when it is known who stands behind the number. A notification from the access control system contains the person's data and the company name, as well as the number of the active card. If a temporary card number is not assigned to a person for the time it is used, the notification shows a person with no context, and the time record and the evacuation list lose credibility.
A swipe by a person unknown to the system creates an account and a company from the notification data. The card pool therefore cannot be separated from the order of people and agency data.
Dividing the pool: a range of numbers per agency
The simplest practice is to assign ranges of numbers to agencies. For example, with three agencies and a pool of 150 cards, each agency gets 50 cards in a separate, recognisable range. As a result, if a card is misused, security knows whom to contact, and the monthly settlement of returns can be run per agency.
The drawback of fixed ranges is uneven load: one agency has a peak, another does not. The answer is a shared reserve of 10 to 20 percent of the pool, which security allocates ad hoc and records in a note with the agency name.
Cards to replace per year, example
- Without settlement
- With monthly settlement
Issue, return and deactivation
The issue of a card is recorded with the first name, surname and company of the person for whom the number is active. Before issuing, security checks the person's account: the search requires at least 3 characters of the surname, returns up to 13 results and does not reveal the card number. Return is just as important: only after the card comes back does the number go back to the pool and can be assigned to another person.
If the card has not come back, security blocks the number in the access control system and opens a new one from the pool. Swipes of a blocked card require an explanation, so they must not be ignored.
Monthly settlement of the pool
The monthly cycle covers a summary: how many cards were issued, how many came back, how many remain outside the site and which agency has the largest shortfall. For an example pool of 150 cards and a loss of 4 percent a month without supervision, 6 cards are lost each month, which is 72 cards a year. With regular settlement the loss may fall, for example, to 1 percent, which is 18 cards a year. This is an example calculation on assumptions, not site data.
Linking with the person's account and company
The panel for external companies and guests manages companies, their workers, pending invitations and guests, with a default company contact person and an optional logo. A guest can be moved to another company on the same account, so training results and the entry history stay with the person, and only the agency assignment changes. This makes it easier to maintain the pools when a person changes agency during the season.
Checklist
Video
Frequently asked questions
Does the card pool have to be split by agency?
It does not have to, but ranges of numbers make it easier to assign swipes to a company and to settle returns.
What should be done with a card that has not come back?
Block the number in the access control system, open a new one from the pool and explain the swipes of the blocked card.
Is the card number visible in the account search?
No. The search at the training workstation does not reveal the card number.
How do you link a card to a person who changes agency?
The person can be moved to another company on the same account, and the training and entry history stays.
Organise the card pool in your warehouse
Book a call about linking the card pool with the accounts of agency workers and companies in InnerWeb.
Let's talk