Where the risk window comes from
The risk window is the time from the moment the card fell out of the owner's hands until the moment the system stopped honouring it. It has two parts. The first is the time until the loss is noticed, which depends on the employee and is often the longest: a card lost on the way home is noticed the next morning. The second is the time from the report to the block, which depends on how the organisation's procedure is set up.
The organisation shortens the first part poorly, because that requires changing people's habits. It shortens the second part through the procedure: deciding who accepts a report at any hour, who blocks the card in the access control system, and whether the report has to pass through several people. The calculation below concerns this second part.
Assumptions of the illustrative calculation
We assume a plant employing 500 people, where a card has an annual loss rate of 3 percent. That gives 15 incidents a year, on average one every 3-4 weeks. For these 15 incidents we compare three variants of the average time from report to block. The times are assumptions for the calculation, not a measurement from a specific plant.
Variant A: the report waits for the next office shift and the block follows after 18 hours on average. Variant B: the security desk officer accepts the report and passes it to the access control administrator during working hours, on average after 4 hours. Variant C: the security desk officer accepts the report at any hour and blocks the card straight away, on average after 1 hour.
- Variant A: 15 incidents times 18 hours gives 270 hours of exposure a year.
- Variant B: 15 incidents times 4 hours gives 60 hours of exposure a year.
- Variant C: 15 incidents times 1 hour gives 15 hours of exposure a year.
Hours of annual exposure at three block times
What 270, 60 and 15 hours mean in practice
In variant A a valid card that its owner does not have stays in circulation for more than 11 full days a year. Variant B reduces this to 2.5 days, and variant C to less than a day. Each hour of exposure does not mean an attempt to use the card, only the possibility of its use by an unauthorised person.
This exposure is not priced in money without the plant's own data, because the cost of an event depends on what the gate protects. For a plant where the warehouses behind the gate hold valuable goods, an hour of exposure costs something different than for a plant with offices only. That is why this page gives no damage amount, only the number of hours, which the plant can multiply by its own risk estimate.
Why the block of the physical card and the block of access are two things
InnerWeb is a software manufacturer that does not sell or install the active cards, readers and label printers, so the procedure for blocking the physical card sits with the access control system, while the access and attendance procedure sits with InnerWeb. At a gate running the InnerWeb system, a deactivated RFID card stops identifying its former holder, because card lookup skips cards carrying a deactivation date. A plant shortens the window when both blocks, in the access control system and in the access system, happen in one step of the procedure.
How to shorten the window without extra cards or equipment
Shortening the window is first of all an organisational decision. The security desk officer is present around the clock, so having the officer accept the report eliminates waiting for the office. The one condition is that the officer must have the authority to block the card or direct contact with the person who has it.
The second factor is that a lost and blocked card should still not leave the employee without a way in. A temporary QR badge issued by security or the secretariat lets the employee enter the site while the card is replaced. Without it, employees are reluctant to report a loss because they fear a day without access, and this lengthens the first part of the window.
How a plant can convert these values into its own data
To replace the assumptions with measurements, a plant needs three numbers: how many cards were reported lost in the last 12 months, how long it took from the report to the block, and how many incidents were reported outside office hours. The first two come from the loss report register, the third from the hours recorded in the reports. Once converted, the team can compare its own result with variants A, B and C above and choose which target is realistic.
Annual exposure of lost cards at a 500-person plant
| Parameter | Value |
|---|---|
| Number of employees | 500 people |
| Annual card loss rate | 3 percent |
| Loss incidents | 15 a year |
| Time to block in variant A | 18 hours |
| Time to block in variant B | 4 hours |
| Time to block in variant C | 1 hours |
Result: Annual exposure is 270 hours in variant A, 60 hours in variant B and 15 hours in variant C. Moving from A to C reduces it by 255 hours, which is more than 94 percent.
Note: Illustrative calculation. The block times are assumptions for the calculation, not a measurement from a specific plant. The plant substitutes its own values from the loss report register.
Video
Frequently asked questions
Is a 3 percent annual card loss rate realistic?
It is an assumption for the calculation, which the plant replaces with its own rate from the loss report register. For 500 people it gives 15 incidents a year, or one every 3-4 weeks.
Does shortening the window require buying new readers?
No. The shortening comes from the procedure: who accepts the report, who blocks the card and whether a temporary badge is available on the spot. InnerWeb does not sell readers and integrates with the existing access control system.
Is exposure measured in hours the same as the risk of a break-in?
No. Exposure measures the time during which an unauthorised person could use the card. The plant assesses the probability and the consequences based on what the given gate protects.
Calculate the risk window for your plant
We will run the calculation with you on your own loss report data and show how the security system shortens the time to access block. Book a conversation with the InnerWeb team.
Let's talk