Gallagher Access Control & Security Installation in Sydney

What Gallagher actually does

1. 1

   Policy-based access rather than door-by-door permissions

   Access is expressed as who may be where under what conditions, and the system derives door permissions from that. A change in policy — a new role, a new restricted area, a new competency requirement — is one central change rather than edits to dozens of individual permission entries, and the system can explain a refusal in terms an auditor understands, which a flat permission list cannot.

2. 2

   Competency and induction-driven access

   Access to a space can be conditional on a qualification, licence, induction or competency with an expiry attached to the cardholder. When it lapses, the door stops opening for that person automatically — converting a compliance obligation that normally depends on somebody remembering into one the building enforces by itself.

3. 3

   Two-person rules, anti-passback and enforced conditions

   Spaces can require two authorised people present before they open. Anti-passback prevents a credential being passed back for a second entry and keeps the on-site record honest, which is what makes muster reporting trustworthy. Cardholders can also be required to acknowledge a site rule or hazard notice at the reader before entry, with the acknowledgement recorded.

4. 4

   Alarm management and operator workflow

   Alarms arrive with context and a defined response: what happened, where, which camera covers it, what the operator should do, and a record of what they actually did. On a site with a control room this is the difference between an alarm system and an alarm response capability. It is also where Gallagher's design assumptions show — the platform expects somebody to be responsible for alarms, and is at its best when that is true.

5. 5

   Perimeter, video and site systems in one operator view

   Perimeter detection and fence-line security report into the same interface and policy model as the doors inside, so a perimeter event and an internal door event sit in one log with one set of operator procedures — removing the usual problem of a perimeter system nobody watches because it lives somewhere else. Gallagher also integrates with major video management platforms so events tie to footage, and brings intruder detection, intercoms and building systems into the same view. Each integration adds a dependency across two products' version cycles: worth carrying where it solves a real operational problem, not because it appeared on a feature comparison.

6. 6

   Reporting built for audit and emergency response

   Muster and evacuation reporting that tells a warden who is actually on site, competency reporting showing who is permitted where and why, and a full record of refusals alongside admissions. If your organisation has ever had to reconstruct who was in a building at a particular time and found it could not, this is the capability that solves it.

Where Gallagher is the right call

• Sites where access has to be conditional on competencies, inductions or licences that expire
• Industrial, utility and high-consequence facilities where the perimeter and the internal doors should be one system
• Organisations that must produce an auditable answer to who was permitted where, and why, including refusals
• Sites with a control room or a responsible operator position, where alarm workflow genuinely matters
• Facilities needing two-person rules, enforced anti-passback or trustworthy muster and evacuation reporting
• Buildings where a head-office standard, insurer or specification has nominated Gallagher
• Campuses and multi-site organisations wanting one policy model applied consistently everywhere

When to choose something else

• Gallagher is the wrong purchase for a site that only needs doors to open for the right people. Its value is policy enforcement and audit; if nothing on your site is conditional on competency, two-person rules or perimeter integration, you will pay for capability you never configure. For most straightforward NSW commercial sites we recommend Inner Range Integriti instead, and we install both.
• The platform assumes somebody owns it. Policy models, competency records and operator workflows need an organisation that maintains them; without that, competency expiries stop being updated and the policy engine degrades into an ordinary permission list with a larger licence fee. Worth being honest about before buying, not after.
• Commissioning and configuration are a larger share of a Gallagher project than of a comparable system, because the design work is the policy model rather than the door schedule. A quote that prices hardware carefully and configuration vaguely has not understood the project.
• Ongoing licensing, version currency and integration modules are real recurring costs, generally above the equivalent for a mid-market platform. We state them as separate lines so the ongoing figure is visible next to the capital one.
• Where the requirement is tight access-and-alarm integration on one controller for a growing commercial site rather than policy enforcement, Integriti usually delivers the same outcome for less. We have no commercial reason to steer you either way.
• Any system that can refuse entry on a competency rule can also refuse entry to somebody who needs to get in. The override and exception paths — who grants them, how they are recorded, what applies in an emergency — are part of the design, and one that has not addressed them is incomplete.

Taking over an existing Gallagher system

Compliance & licensing

What moves the price

Gallagher is quoted door by door with the configuration effort priced separately, itemised ex-GST. What moves the number:

• Controlled openings — reader, locking hardware, request-to-exit device and a cable run back to the controller
• Controller sizing and spare capacity — what expansion costs later is a decision made at design time, not discovered at it
• Policy complexity — competency rules, two-person rules, anti-passback and enforced conditions are configuration and testing effort, the larger half of the project
• Software licensing and modules — base licensing, integration modules and any per-cardholder licensing, quoted as their own recurring lines
• Perimeter scope — fence-line detection and gate integration is its own discipline with its own hardware and commissioning
• Integration scope — video, intruder detection, intercom and site-system integrations are each their own configuration and testing effort
• Credential technology — secure smart credentials and mobile credentials against basic proximity, sized against your population and turnover
• Cabling and building fabric — riser access, ceiling space, fire-rated penetrations, and the distance from each opening back to the controller
• Operator workflow build — alarm procedures, screens and reporting setup where a control room exists

Treat a Gallagher quote with vague configuration pricing as incomplete. On this platform the policy model is the project; hardware is the easy half.

Frequently asked

What makes Gallagher different from other access control systems?

It is a policy engine rather than a door controller. Most systems answer whether a credential opens a door right now; Gallagher answers whether a person is currently permitted in a space given their role, competencies, inductions and where they already are — and records the reasoning, including refusals. That is why it appears on sites where the consequence of the wrong person in the wrong room is serious.

Can Gallagher restrict access based on training or inductions?

Yes, and it is the platform's most persuasive capability. Access to an area can be made conditional on a competency, licence or induction with an expiry attached to the cardholder. When it lapses the door stops opening for that person automatically, rather than depending on somebody noticing a spreadsheet.

Should we choose Gallagher or Inner Range Integriti?

Match it to the requirement. If the need is tight access-and-alarm integration on one controller for a commercial site that will grow, Integriti usually delivers the same outcome for less. If access has to be conditional on competencies, two-person rules or enforced conditions, if the perimeter should be in the same system, or if you must produce an audit-grade answer about who was permitted where and why, Gallagher is the better fit. We install both and have no reason to push either.

Can you take over an existing Gallagher system?

Yes. We start with an audit — hardware condition, software version, licensing position, how the policy model and competency rules are actually configured against how the site believes they are, and who holds the administrator credentials. Competency rules in particular get tested rather than trusted, because a rule that was never enabled is a compliance exposure the site does not know about. Then we price adopting, restructuring or replacing, with the reasoning visible.

What reporting can Gallagher produce?

Muster and evacuation reporting showing who is actually on site, cardholder and competency reporting showing who is currently permitted where and on what basis, and a complete event record including refusals as well as admissions. Anti-passback is what makes the on-site figure trustworthy, so it is usually designed in where muster reporting matters.

Is Gallagher too much for a small commercial site?

Usually, yes. If nothing on your site is conditional on competency, two-person rules or perimeter integration, you would be paying for capability you never configure. We will tell you that and quote Integriti or a simpler controller instead — the right-sized system is a better outcome for both of us than an oversold one.

What happens if a competency rule locks someone out in an emergency?

That is a design question we settle explicitly rather than leave to chance. Exit paths keep free egress in every power state regardless of any policy rule, and the override and exception paths — who can grant them, how they are recorded, what applies in an emergency — are designed, documented and tested at commissioning. A policy-driven design that has not addressed overrides is incomplete.