Approved installer register

Registers are the certification bodies' public face of vetting: a company appears only after audit, and entries carry scope detail - what the firm is certified to install or monitor. NSI's company finder is described as a searchable public register of more than 2,000 NSI-approved UK security and fire safety companies with per-scope detail.

SSAIB operates the parallel register, covering certified security and fire safety companies across the UK and Republic of Ireland, spanning installers, monitoring centres and guarding providers. Together they define the trusted-installer universe in these markets.

Format matters for anyone building on them: the cataloged records carry the tags 'directory', 'vendor-vetting' and 'alarm-installers', with delivery via HTML search results and PDF exports generated server-side from result sets - not CSV or an API. Crucially, neither body posts a reuse licence, so large-scale harvesting is unlicensed.

The absence of a licence is the headline risk. A lead-gen product or market map built on systematically harvested register data has no contractual basis for reuse, however public the pages are.

• Unlicensed does not mean unusable - it means negotiable. Bulk extraction beyond normal search use needs explicit permission from NSI (whose register lists 2,000-plus companies) or SSAIB.
• Directories decay. Any of the 2,000-plus certifications can be granted, suspended or lapse; an undated extract silently misstates today's approved universe.
• Format constrains engineering. HTML search results plus server-side PDF exports mean scraping or manual export cycles, with the associated fragility and terms-of-use exposure.

Use these checks to test whether a source delivers what the concept promises:

1. Match the certifier to your geography. NSI covers UK companies (2,000-plus listed); SSAIB spans the UK and Republic of Ireland - a UK-only panel needs only one, an all-island panel needs both.

1. Secure reuse permission before harvesting at scale. Neither register posts a reuse licence, so treat anything beyond interactive lookup as requiring written consent.

1. Timestamp every extract. Certification status changes; store capture dates alongside company and scope fields.

1. Plan around the delivery formats. HTML search results and PDF exports - not CSV/API - so build parsing and refresh processes accordingly.

1. Capture scope, not just names. Per-scope detail is what distinguishes an installer certified for alarm systems from a monitoring-centre operator.

Where to see it in context: security-alarm-services data.

Concepts that surround register-based vendor vetting:

• postcode-radius-search
• security-certification-schemes
• web-scraping