InnerWeb
Skip to main content

Found card after a block: why it should not be reactivated

A blocked card returns to the employee after two days, and they ask for it to be reactivated so they do not have to wait for a new one. We recommend against it: nobody knows who held the card in the meantime. We describe the arguments, the exceptions and the steps for security.

15
new cards a year at a plant of 500 people
Source: sample calculation

The situation and the temptation to reactivate

An employee reported the loss of a card on Thursday, the card was blocked, and on Saturday someone found it in the car park and handed it in. Reactivating the card looks sensible: it saves the cost of a new one and the employee's time. However, the arguments against are stronger, because for two days the card may have been in other people's hands.

The recommendation applies to a production plant with a card-based access control (KD) system. InnerWeb is a software producer and does not replace cards or readers, so the final decision on the fate of the physical card belongs to the administrator of the KD system, while access and attendance remain on the InnerWeb side.

Why the system and the procedure say: a new record, not an overwrite

In InnerWeb, revoking a badge creates a new record instead of overwriting the old one, so the badge history of the person stays in the system. This principle reflects the philosophy of the whole procedure: a loss event should be visible in the history, not erased by reactivation.

At the gate a revoked RFID card stops identifying its former owner, because the card lookup skips cards with a revocation date. If the plant manually reversed the block in the KD system while the card remained revoked in the attendance system, a discrepancy would arise, which is described in the implementation notes on consistency of the block between the KD and the OHS systems.

Card states in the employee's history

Card states in the employee's historyWith reactivation the history has two active periods and one blocked period, with a new card one of each.012statesReactivation (Active): 2 states2 statesNew card (Active): 1 states1 statesActiveReactivation (Blocked): 1 states1 statesNew card (Blocked): 1 states1 statesBlocked
  • Reactivation
  • New card
Source: Sample calculation: number of active and blocked periods in the card history

Practical arguments

The first argument is the risk of cloning. A card that was outside its owner's control may have been copied, and nothing on passive cards reveals that. The second is evidential simplicity: issuing a new card gives a clean start in the register, while reactivation complicates the review of swipes, because the same card has active, blocked and active-again periods.

The third argument is cost. For the sample calculation of 15 events a year at a plant of 500 people, this means 15 new cards a year. With such a small number, the saving from reactivation is negligible compared with the risk.

What to do with the found card

Security takes the found card, confirms in the register of reports that the card is known and blocked, and then hands it to the administrator for destruction or withdrawal. The employee receives a replacement card issued in line with the procedure, and in the meantime a temporary badge.

It is also worth making a short review of swipes from the period between the block and the finding: a scan of the blocked card ends in a refusal, and the trace of such attempts shows whether someone tried to use it.

  • take the card and record the date and place where it was found,
  • confirm in the KD system and in InnerWeb that the card is blocked,
  • hand the card to the administrator for withdrawal,
  • issue a replacement card according to the procedure,
  • check the ledger for attempts to use the card during the block.

Are there exceptions

One exception the plant may adopt in the procedure concerns blocks ordered by mistake, for example an order for the wrong card. Reactivation then corrects an error rather than responding to a loss, and it should have a separate entry with the justification and the approval of a second role. The rule does not apply to a card that was actually lost.

Checklist

Video

Frequently asked questions

Is reactivation always wrong?

For a loss, yes, because nobody knows who had the card. Only reversing a block ordered by mistake is acceptable, with a separate entry.

Does InnerWeb reactivate a revoked badge?

Revocation creates a new record instead of overwriting the old one, so the history stays, and a new badge is a new record.

What about the cost of a new card?

With the sample calculation of 15 events a year at a plant of 500 people, that is 15 cards, so the cost is small compared with the cloning risk.

Let's write this rule into your procedure

We will help turn the rule of a new card instead of reactivation into the security and HR procedure.

Let's talk