How we write about private security and workforce compliance.
Guidance on this site is written to be acted on, which is the reason to be clear about where it comes from and where it stops.
The team, not a named expert
Articles are published under “the SecureOptix team” because that is who writes them. We do not put a named author on an article unless a named person wrote it, and we do not have individual contributors yet.
When we do, they will be named, their relevant experience will be stated, and the articles they wrote will say so. An invented byline on guidance about private security and workforce compliance would be a claim about expertise rather than a description of it, which is worth less than nothing to somebody deciding whether to rely on the page.
The regulator is the source, not this site
Where an article covers a regulated detail — SIA licensing, BS 7858 screening and what a vetting file must contain — it is written to be directionally accurate and to send you to the Security Industry Authority for the current requirement. That is deliberate. Those details are revised, and a figure quoted secondhand from a blog post is the wrong thing to run an operation on.
If an article states a specific figure, date or threshold, it is because we could check it against the issuing body at the time of writing. Where we could not, the article says so rather than filling the gap.
The modified date means something
Every article carries the date it was published and, where it applies, the date the body was last materially revised. The second date moves only when the content actually changed — not for a typo, a formatting fix or a metadata correction.
That rule exists because churning the date on every edit is how a freshness signal stops meaning anything. If you are looking at a revision date here, something in the article is different from what it said before.
What this is not
None of it is legal advice, and none of it is a substitute for the Security Industry Authority. We write about private security and workforce compliance because it is what the product is for, which gives us a practical view of how the records are kept and where they fall down — not standing to tell you what the law requires of your organisation.
Where we describe what SecureOptix does, the Service Specification is the honest version, including the parts we do not do.
Tell us when it is wrong
If something here is out of date or incorrect, we would rather know than not. Email hello@secureoptix.co.uk with the page and what is wrong with it. Corrections to a regulated detail are made as soon as we can confirm them, and the article's revision date moves when they are.