What a governing layer is, and what it is not

Most organisations we meet don't have 1 access control system. They have 4, at different sites, bought in different decades. Each one works fine on its own.

The trouble starts when someone asks a question that covers all of them.

The questions nobody can answer quickly

Who can get into our sites today? How many of them don't work for us? Whose certificate expired last month? Who let the contractor through the north gate on Tuesday, and why?

An access control system can't answer those. It was built for another job: deciding whether a badge held to a reader opens a door. It does that job well.

It doesn't know why the badge exists. It doesn't know the same person carries another badge at another site. It also has no idea that their safety induction runs out on Friday.

Why replacing everything is the wrong first move

The obvious reaction is to standardise: pick 1 access control system, replace the others, and the question goes away.

It is also the most expensive route, and it pays back nothing for years.

Replacing an installation means new readers, controllers, cabling and commissioning at every door. You write off hardware that still had years left in it. Each site becomes its own project, planned around operations that can't stop. You only see the benefit when the last site is finished.

Many organisations that start this way never finish. Priorities shift, budgets move, and they end up with 3 systems instead of 4 and the same governance problem.

What a governing layer does

A governing layer sits on top of the access control you already run. It holds the identity, decides who is eligible and keeps the evidence. Your installed systems keep opening doors.

In practice it does 4 things.

It keeps 1 record per person, whether they are an employee, a contractor, a visitor or a supplier. When someone changes role, employer or site, that same record is updated. No second record appears.

It keeps checking who is eligible for each area. A person becomes eligible when every requirement is met. They lose it on the day one requirement lapses.

It sends the result to each access control system, through that manufacturer's own published interface. The door then does what the record says.

It records every decision with its reason and its approver, the moment the decision is made. Nobody has to piece that together from logs later.

What it isn't

It isn't an access control system. It doesn't open doors, talk to readers or replace controllers. If it goes offline, your installed systems keep enforcing the last state they received.

It isn't a second workforce database. We read people data where it already lives: in human resources, your directory and your contractor platform. A copy would drift from the original, and you would find out during an audit.

It isn't a badge printer with a database attached. Issuing credentials is one of the things it does.

It isn't a replacement programme under another name either. If a proposal for a governing layer includes new field devices, it is something else.

What changes

First, the question gets an answer. The number of people who can enter a site becomes something you look up, instead of something you reconcile.

Second, you can start small. It works from the first site you connect, and the others follow when they're ready. A site you acquire next year is added by configuration.

Third, evidence stops being a project. The list of everyone allowed into a named area on a given date, with reason and approver, is a query.

None of it requires replacing a single reader. We designed it that way from the start.

Curious where your own sites stand? The access governance scorecard has 10 questions and takes 5 minutes. Take the scorecard Talk to us