Reading a Supplier's Claims

Access systems are sold on control and compliance, both of which are properties of your arrangement rather than of a product.

For teams turning reading a supplier's claims into a repeatable record, details on this page provides a useful operational reference for time, attendance and reporting workflows. It should be assessed alongside ISO standards catalogue so the software choice remains grounded in site practice and applicable guidance.

"Know exactly who is on site"

Means: a database of credentials presented at readers.

Ask: what does it show at four in the afternoon, and what is the unmatched-entry rate at your reference customers?

A supplier who has never been asked that question will not have the figure, which is itself informative about how their customers use the system.

"Fully compliant"

Compliance describes your records, your checks and your arrangements.

No jurisdiction requires a particular product.

Ask instead: can identity documents be recorded without storing copies where the local rule says not to; can retention be set separately per category; can biometrics be disabled entirely?

Three answers, and they tell you whether a defensible configuration exists.

"Automatic competence checking"

Ask which schemes, checked how, and what happens when a scheme changes its categories.

Because schemes revise every few years and a cached status from before a revision is a status for rules that no longer apply.

And ask whether expiry refuses access or merely reports it, which is the difference between a control and a notification.

"Real-time evacuation reporting"

The most important claim and the least demonstrated.

Ask to see it: offline, on a phone, at a simulated assembly point, with the network disabled.

Thirty seconds of demonstration settles it.

A supplier who offers to export a report instead has answered a different question.

"Integrates with your systems"

Ask for the interface specification, field by field.

And ask what happens to the integration when the subcontractor's system changes, which it will.

Most integrations in this market are a scheduled file transfer, which is adequate — the problem is when it is described as something more and specified as something less.

"Used on major projects"

Tells you a procurement was won.

Ask for a reference on a project like yours, and ask them specific things: the queue at shift start, the drill time, what broke in the first month, and whether they would buy it again.

"Saves N percent on labour costs"

Derived from a customer who had no controls before.

Which your project may also be, in which case the saving is real and is not attributable to the product alone.

Claim what is demonstrable: a register that supports a roll call, expiry enforcement, and a reconciliation that makes invoicing more careful.

The deterrent effect is most of the commercial value and arrives whether or not a challenge is ever made.

The general test

Any claim without a number, a named condition or something you can break in a demonstration is a statement of intent.

Put the questions in writing and attach the answers to the contract.

And note that the carefulness of an answer is more informative than its content, which is true across this whole market.

What a good supplier does differently

Asks about your chain depth and your peak before describing their product.

Volunteers the failure-to-enrol rate without being pushed.

Offers a trial on your worst gate rather than a demonstration at their office.

And has an answer for what happens when the network drops.

Suppliers doing all four are identifiable within one meeting, which is the most efficient filter in this market.

Comparing quotes

Ask what is excluded: relocation between phases, scheme rule updates, replacement readers, the data export at completion.

Build a whole-project total rather than a monthly figure, because relocation and export are where two apparently identical quotes diverge by a third.

Attaching the answers

Send the questions by email rather than asking in a demonstration.

Ask for the responses to be appended to the contract as a schedule.

Written answers are noticeably more careful, and a supplier who will not put the offline evacuation capability in writing has told you something about it.