FaSQUAL: The BSIA-led Vetting Passport for the UK Security Industry Powered by Neotas
One trusted record. Verify once, then update proportionately based on role, risk, and change. Trusted across the security sector.
One trusted record. Verify once, then update proportionately based on role, risk, and change. Trusted across the security sector.
FaSQUAL is a new service from the BSIA that is designed to remove duplicate effort when employing individuals and contractors. The aim of FaSQUAL is to store the qualifications and career/vetting record of security industry professionals, contractors and officers so they can be reused by future employers without having to screen the individual from the start each time. Once an individual is screened and their qualifications verified, their record can be reused by the next employer who simply updates it and deploys the individual to work.
The security industry relies on fast workforce mobilisation. Traditional vetting processes are repetitive and get in the way of that.
FaSQUAL is the BSIA’s answer to that. It provides a secure, centralised system for vetting and qualification verification, helping security companies deploy faster, improve compliance, and reduce duplication while giving contractors and employees greater control over their verified vetting/career records.
FaSQUAL enables reuse of verified screening elements within BS 7858 refresh and review requirements. Employers remain responsible for determining when re-checks or updates are required based on role, risk, and time elapsed.
FaSQUAL provides a secure, centralised record of vetting and competency checks aligned with BS 7858 standards, enabling employers to hire faster, reduce duplication, and maintain consistent compliance.
Security officers with a FaSQUAL platform can be deployed significantly faster, reducing onboarding timelines and enabling quicker fulfilment of client contracts.
Alarm contractors and security organisations verify qualifications and vetting once through FaSQUAL. Once completed, verified elements within an auditable record can be securely reused across participating employers.
Automation removes manual processing, reduces human error, and enables screening teams to manage higher volumes with fewer resources.
Eliminates duplicate BS 7858 checks when hiring FaSQUAL-verified officers, reducing administrative workload, third-party verification costs, and screening overhead.
FaSQUAL operates on a transaction-based model that scales with workforce needs. Organisations are charged only when accessing verified elements within an auditable record, while the organisation that completed and uploaded the vetting is compensated.
FaSQUAL ensures screening is aligned with security industry standards and regulatory expectations, improving audit outcomes and reducing compliance risk.
FaSQUAL supports compliance and audit evidence but does not replace employer obligations under BS 7858, SIA licensing, or contractual requirements.
FaSQUAL gives you a recognised vetting passport that can be securely shared with participating employers, removing unnecessary duplication in screening.
Complete vetting once and securely share your verified profile with participating employers, eliminating repeated screening delays and unnecessary onboarding duplication.
Avoid repetitive verification checks when changing employers, enabling faster onboarding, quicker deployment, and more reliable access to new security opportunities.
Access your verified career record through a secure portal, allowing you to view, manage, and control who can access your verified personal information, eliminating the need for you to be fully screened each time you change employer.
Carry your verified vetting status across participating companies, improving career mobility, reducing friction, and strengthening trust with potential employers.
The FaSQUAL vetting journey follows a structured, transparent process
A participating security organisation initiates vetting through the FaSQUAL platform. The individual completes required screening steps digitally.
Screening checks are completed in line with BS 7858 principles, role-based risk, and employer-defined screening scope.
Verified screening evidence and associated metadata are securely stored within the FaSQUAL platform, including audit trails, verification dates, and evidence ownership.
The vetted individual retains their FaSQUAL record as they move between roles or employers.
When joining a new FaSQUAL-participating employer, the individual provides a single-use consent code that allows controlled access to their verified screening record.
Employers review reusable screening elements and identify any expired, role-specific, or missing checks that require proportionate re-screening.
Additional checks are completed where required and appended to the record. The employer reviews the screening outcome and confirms suitability for deployment.
The employer completes any required additional screening, confirms suitability, and deploys the individual. The individual continues to hold a trusted, auditable FaSQUAL vetting passport recognised across the UK professional security sector.
Neotas provides the secure digital infrastructure that enables FaSQUAL to operate efficiently, compliantly, and at scale.
Lower screening costs, improve compliance, and mobilise
your workforce with confidence.
Unlock the answers you’ve been seeking! Here are the top questions we deal with everyday.
Have a more specific question or requisition? We are here to help! Write us an email: [email protected]
FaSQUAL allows organisations to reuse verified screening elements within an auditable record, helping reduce unnecessary duplication while supporting compliance with BS 7858 requirements.
The platform captures verification steps, dates, and responsible parties, creating a clear and traceable audit trail. This provides organisations with reliable evidence of screening activity and supports them during certification, inspection, and client due diligence processes.
FaSQUAL supports proportionate screening by allowing employers to review previously verified checks and determine whether additional verification or updates are required based on role, risk, and time elapsed.
No. FaSQUAL does not replace employer obligations under BS 7858, SIA licensing requirements, or contractual screening requirements.
Employers remain responsible for determining whether screening checks are suitable for the role and whether any elements must be refreshed or supplemented. FaSQUAL provides access to previously verified screening evidence, which employers can review and reuse where appropriate.
Final decisions on risk acceptance, additional checks, and deployment always remain with the employer.
FaSQUAL provides a secure framework for storing and sharing verified screening information, but it does not replace regulatory or employer-specific requirements.
The platform does not replace SIA licensing or regulator-mandated licence checks, employer-specific inductions or site rules, or client-mandated contractual screening requirements.
It also does not replace role-specific risk assessments or employer decisions about when screening checks must be refreshed.
Organisations continue to apply their own compliance policies and screening procedures alongside the verified screening record held within FaSQUAL.
| Cookie | Duration | Description |
|---|---|---|
| AWSALBTG | 7 days | AWS Application Load Balancer Cookie. Load Balancing Cookie: Used to encode information about the selected target group. |
| AWSALBTGCORS | 7 days | AWS Classic Load Balancer Cookie: Used to map the session to the instance. This cookie is identical to the original ELB cookie except for the attribute &SameSite=None; |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
| debug | never | Cookie used to debug code and website issues |
| shown | session | Session cookie to control number of times a pop up is shown. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| AnalyticsSyncHistory | 1 month | Used to store information about the time a sync took place with the lms_analytics cookie |
| bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
| bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
| lang | session | LinkedIn sets this cookie to remember a user's language setting. |
| lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
| UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
| Cookie | Duration | Description |
|---|---|---|
| li_gc | 2 years | Used to store consent of guests regarding the use of cookies for non-essential purposes |
| rl_anonymous_id | 1 year | Generates an unique anonymous Id to identify a user and attach to a subsequent event. |
| rl_user_id | 1 year | to store a unique user ID for the purpose of Marketing/Tracking |
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gat_gtag_UA_107495977_1 | 1 minute | Set by Google to distinguish users. |
| _gat_UA-107495977-1 | 1 minute | A variation of the _gat cookie set by Google Analytics and Google Tag Manager to allow website owners to track visitor behaviour and measure site performance. The pattern element in the name contains the unique identity number of the account or website it relates to. |
| _gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| attribution_user_id | 1 year | This cookie is set by Typeform for usage statistics and is used in context with the website's pop-up questionnaires and messengering. |
| CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
| Cookie | Duration | Description |
|---|---|---|
| _fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
| fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt.innertube::nextId | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
| yt.innertube::requests | never | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |