A door access control system records who opened which door, when, and whether entry was granted or denied. Read on its own it is a security log. Read alongside rosters, HR records and attendance, the same entry events show who is actually on site, how busy each area is, who enters outside their shift and whether leavers still hold working credentials.
Door access control data is the event log a door access control system creates each time a credential is presented at a reader: a card, fob, PIN, phone or a digital wallet badge. Each event typically holds a person or credential ID, a door or zone, a timestamp and a result (granted, denied, door held open, forced). Most organisations keep this log for investigations and then rarely open it. That is a missed opportunity, because it is one of the few workforce records produced automatically, at the moment something happens, without anyone filling in a form.
This guide explains what the data contains, the questions it can answer, a worked example, and the limits you should know before relying on it. If you are new to joining records from different systems, our guide to what workforce intelligence is covers the wider idea.
What does a door access control system actually record?
The exact fields vary by vendor, but a modern access control system usually logs the following for every event:
| Field | Example | Why it matters |
|---|---|---|
| Credential or person ID | Employee 1042 | Links the event to an HR record |
| Door or zone | Warehouse dock 2 | Shows where, not only whether, someone was on site |
| Timestamp | 06:52:14 | Compared with the roster start time |
| Result | Granted / denied | Denied attempts point to wrong permissions or misuse |
| Direction (if fitted) | In / out | Needed for reliable occupancy counts |
| Door state alarms | Held open 4 minutes | Tailgating and propped-door risk |
Cloud access control platforms add useful context such as credential type (plastic card or mobile credential), site, and who issued or revoked the credential. If you are comparing credential types, this overview of wallet credentials versus plastic badges explains the practical differences, including why a phone-based credential is harder to lend to a colleague.
Which workforce questions can door entry data answer?
Once entry events sit next to the roster and HR records, five questions become straightforward to answer.
- Who is actually on site? The first granted entry of the day is a strong signal of arrival. Comparing it with the roster shows late arrivals and no-shows within minutes, rather than at payroll. See how this links to attendance and absence tracking.
- Is each area covered? Zone-level entries show whether the trained people are in the right part of the building, which matters more than total headcount. This feeds shift coverage decisions.
- Who enters outside their shift? Repeated entry on rest days or long after a shift ends can mean unrecorded overtime, fatigue risk or a permissions problem. It is worth a conversation, not an assumption.
- Do leavers and contractors still have access? Any granted entry by someone marked as left in HR is an urgent finding. Expired contractor credentials that still work are a common gap. This is core to security and access risk review.
- How many people are in the building right now? With in and out readers, entry data supports occupancy counts and an evacuation roll-call list. UK employers have duties to plan for workplace fire safety and evacuation, and a reliable on-site list helps.
How to compare entry events with rosters: a worked example
Here is an illustrative example for a single site with one morning shift. The numbers are made up to show the method.
| Employee | Rostered start | First entry | Clock-in | Finding |
|---|---|---|---|---|
| A | 07:00 | 06:48 | 06:58 | Normal |
| B | 07:00 | 07:21 | 07:00 | Clock-in before entry: check how the clock-in was made |
| C | 07:00 | none | none | No-show: cover needed |
| D | Rest day | 08:15 | none | Off-shift entry: confirm reason |
| E (left 31 Oct) | none | none (2 denied) | none | Credential revoked correctly; denied attempts logged |
The useful rule is simple: exception = entry event that does not match the roster or HR status, or a time record with no matching entry. In this example, three of five rows need a person to look at them, and none of them would appear in a standard attendance report. Employee B is the classic case: a time record that says 07:00 while the door says 07:21.
A checklist for reading access data well
- Map every reader to a zone and site, and keep the list current when doors change.
- Use one person ID across HR, rostering and the access control system, so events link without manual matching.
- Decide which reader counts as "arrival" for each site (usually the perimeter or main door, not internal doors).
- Fit or configure exit reading where you need occupancy; entry-only data overstates who is still inside.
- Review exceptions weekly, not every event: off-shift entries, leavers' attempts, held-open alarms and arrival gaps.
- Record what was found and what was done, so the review itself becomes audit evidence.
- Tell staff what is collected and why, and keep it to the stated purpose.
What are the limits of door access data?
Entry events are good evidence, but they are not the whole picture.
- Tailgating. One credential, several people through the door. Turnstiles, door-held alarms and a culture of not holding doors reduce this.
- Shared credentials. Plastic cards and fobs can be lent. Mobile credentials tied to a personal phone are harder to share, which improves the data as well as security.
- Entry is not work. Arriving at 06:48 does not mean working from 06:48. Use entry data to question time records, not to replace your pay rules.
- Privacy. Using access logs to monitor workers is a form of monitoring. The UK ICO's guidance on monitoring workers expects a lawful basis, clear information for staff, proportionality, and a data protection impact assessment where the risk is high. This article is not legal advice.
Choosing an access control system with the data in mind
If you are reviewing or replacing a door entry system, ask a few data questions alongside the security ones: can events be exported or read by API in near real time; does it log denied attempts and door states, not only granted entries; can credentials be revoked centrally the moment HR marks a leaver; and does it support mobile access control and digital wallet credentials as well as cards. A cloud door access control platform with Apple Wallet and Google Wallet employee badges is one example of a system built around central revocation and per-person mobile credentials.
Next step: turn entry events into workforce answers
Start small. Export one week of entry events for one site, put them next to the roster and the leavers list, and apply the exception rule from the worked example. Most teams find at least one off-shift pattern or stale credential in the first pass.
TeamzMate reads attendance, access, scheduling and HR records together, flags exceptions like the ones above for a person to review, and explains them in plain language. Decisions stay with your managers. If you want to see it with your own data, book a demo, or read how 12 workforce analytics metrics fit alongside access data.