Vertex Method Ltd

Our policies

Vertex Method Ltd publishes three of its policies here. Our approach to security and data is set out on the Security and data page, and our handling of personal data in the Privacy Policy.

Modern slaveryComplaintsAI use

Voluntary statement

Modern Slavery Statement

Vertex Method Ltd is not required to publish a statement under section 54 of the Modern Slavery Act 2015, because its turnover is far below the £36 million threshold. We publish this short statement voluntarily, because public-sector buyers ask every supplier how it addresses the risk.

Our business

Vertex is a small UK company that licenses a physical security assessment methodology and the IPSRM Field web app. It has no premises open to the public, no manufacturing and no physical products. Its work is carried out by its directors, with occasional input from named advisers.

Our supply chain

We buy software and online services: app hosting, sales and licensing, code hosting, website hosting, domain and email, and software tools used to build the product. We judge the risk of modern slavery in this supply chain to be low, but not nil.

What we do

  • We use established suppliers that publish their own modern slavery or human rights commitments, and we review any new supplier before taking it on.
  • We pay suppliers on their published terms.
  • We will not knowingly work with any organisation involved in slavery, servitude, forced or compulsory labour, or human trafficking. If we find a concern, we will act on it, including ending the relationship.
  • Concerns can be raised in confidence with the director.

This statement is approved by the director and reviewed each year.

Signed: Stephen Beels, Director · 20 November 2026

Putting things right

Complaints Procedure

If something we have done falls short, we want to know and to put it right. We acknowledge a complaint within 2 working days and answer it in full within 10 working days, or tell you why it will take longer and when to expect an answer.

How to complain

Email info@ipsrm.org with your name, your order or licence reference if you have one, and what went wrong. Technical problems with IPSRM Field can also go to support@ipsrm.org.

What happens

  1. We acknowledge and log your complaint.
  2. The director looks into it and replies in full, saying what will be done.
  3. If you are not satisfied, tell us. The director reviews the response and, where practical, asks an adviser with no involvement to look at it as well. The result is our final response.

Other routes

Complaints about how we handle personal data can also go to the Information Commissioner's Office. Nothing in this procedure affects your legal rights or our Terms of Sale.

Openness about tools

AI Use Statement

IPSRM Field contains no artificial intelligence, and no customer's assessment data is ever passed to an AI service. We do use AI tools in building the app and in drafting our own material, and we say so openly.

In the product

Scores, tiers, the Overall Exposure Position and the pre-report check are calculated by fixed, published rules, not by AI. The app connects only to its own site and to the licence service. A practitioner's findings, photos and reports stay on their device. If an AI feature is ever considered, it will be described publicly, and our Security and data page updated, before it is released.

In building the app

IPSRM Field is built by Vertex Method using Claude Code, Anthropic's AI coding tool, working to a written specification. Every change is checked by automated tests, and no version is released until the director has approved it.

In our own material

AI assistants help draft documents, marketing and correspondence. Everything published is reviewed and approved by the director, who is responsible for it. The IPSRM methodology is Stephen Beels's own work, drawn from his career in physical security.

Data and AI tools

  • No customer assessment data is entered into any AI tool.
  • Customers' and evaluators' personal details are not entered into AI tools unless a task needs them, and then only the minimum.

Approved by the director · 20 November 2026