An outdated user list makes an access control audit harder because the audit is a comparison: the people the system says can enter, checked against the people who should be able to. When the system's list holds former employees, departed tenants, shared cards, or unlabeled credentials, that baseline is wrong, and every finding built on it becomes uncertain. You cannot tell intended access from leftover access.
An audit is two lists held side by side
An access control audit asks whether the system's idea of who can open which doors matches the building's idea of who should. One side is the system's records: each user and credential, with the doors and times assigned to it. A credential is whatever a person presents at the reader, such as a card, a fob, or a phone. The other side is the real roster of people and their roles today.
Both sides have to be current for the comparison to mean anything. If the system side is stale, a mismatch could be a real exposure or just a record nobody removed. The audit starts producing questions instead of answers.
Signs in the user report that point to a stale list
A name nobody on the current roster recognizes is the plainest sign. It could be a former employee, a departed tenant, or a contractor from an old project. Until someone identifies the name, its access cannot be called intended or unintended.
Duplicate and shared entries come next. The same person listed twice leaves you unsure which record is live. An entry labeled something like Cleaning or Front Desk, with one card passed around, breaks the link between a credential and a person. The event log, which is the system's record of each credential use at a door, then shows a card but not who held it. Unlabeled credentials, a card number with no name attached, give you even less to go on.
Long inactivity is a strong hint but not proof. An entry with no door use over a long stretch often belongs to someone who has left, though a person on extended leave looks identical in the report.
The reverse counts too. Someone on site every day with no record under their own name is getting in some other way, usually on another person's card or by following others through the door. Either way, the log cannot account for their entries.
Wrong people in the records, or right people getting wrong results?
The simplest way to sort a list problem from a system problem is to ask which side the mismatch lives on. A stale list shows up as wrong people in the records, while the doors behave the way they were set up. A system problem shows up as the right people, with current and correct records, getting the wrong result at the door.
System-side symptoms look different. A current user is denied at one reader but admitted at others in the same access group. A door stays unlocked when its schedule, the set of times a door or group is allowed in, says it should be locked. A reader signals a grant while the lock stays shut. Those point toward the reader, the lock hardware, the wiring, or the configuration, not the roster.
Untracked credentials sit in between. Cards handed out from a spare stack, or reissued without changing the name, open doors normally, but the record no longer says who holds them. Treat that as a records problem. No amount of door testing will fix it.
Why a messy list slows down the rest of the audit
Each unexplained entry turns into its own small investigation. Someone has to work out who the entry belongs to and whether that person still needs those doors, and often nobody owns the answer, especially for vendor cards and shared credentials.
Meanwhile the real audit question waits: which doors open to which groups, and does that match intent. Effort goes to chasing records instead of reviewing doors.
Cleaning the list first narrows the field. Once the records match a current roster, any odd result left over is more likely to be a door, reader, or schedule issue, and there are fewer of them to look at.
Reconcile the list first, then note what looks like a fault
Reconciliation is desk work. It needs the system's export and a current roster, nothing more.
- Export the current users and credentials, with access groups and last activity if the report includes them, and save an untouched copy.
- Get a current roster from whoever is responsible for each group of people, such as employees, tenants, and vendors.
- Match names line by line and mark each entry as confirmed, duplicate, shared, not on roster, or unknown.
- Flag unknowns for follow-up rather than deleting them.
- Separately, write down any door behavior that looked wrong: which door, which credential, what time, and what happened.
If door-level problems remain after the list is clean, hand a contractor the original export, your marked-up roster, and the door notes. Together they show which questions are about records and which need someone at the door. Atlas Integrated Security works on commercial access control in New York City, and you can call (347) 357-0985 for help with the doors and system behavior your notes flagged.
Frequently asked questions
Should unknown entries be deleted right away during an audit?
Unknown entries in an access control audit are usually better disabled than deleted. Disabling a credential stops it from opening doors but keeps the record and its event history. If the entry belongs to someone still on site, you turn it back on. If it belongs to someone who left, the history still shows when the card was last used.
Does a clean user list prove the doors are configured correctly?
A clean user list does not prove the doors are configured correctly. It only shows that the records name the right people. Whether each access group opens the right doors, and whether schedules match building hours, has to be checked at the doors by having a current user with a known assignment try them and noting the result.
Who should own the master list of people who need access?
The master list of people who need access works best with one named source per group. HR or office management usually holds employees, leasing or the property manager holds tenants, and whoever hires vendors holds contractor names. The access control system should follow those sources, not stand in for them.
What records are useful to have on hand before a review of door access?
Beyond the user export, a review of door access is easier with a list matching system door names to physical doors, a description of what each access group is meant to open, an inventory of spare or unissued cards and fobs, and an earlier export to compare against. Together these show intended access, not just current settings.
Tell us about the building.