This site uses cookies to help improve your browsing experience. See our cookie policy for more information

OK

10:00

020 7837 5424

info@first-security.co.uk

Template Image

Intelligence Centre

The latest security industry news, debates, articles, blogs, research findings and more.

Understanding the security industry, for today and for the future.

Contact us today

Streamlining Security Screening

In his latest blog for Infologue.com, John Briggs, operations director for First Security, looks at the British Standard BS7858 and what the security industry needs to do to streamline the employee security screening procedure.

Screened or unscreened?

Security screening new employees can be a costly and time-consuming process for security companies. Often the procedure is not carried out as extensively as it should be, resulting in employees not being vetted correctly. With some security company’s contracts changing every couple of years, it also means employees are being screened more often, at a significant cost to their new employer.

Security officers must inform their new employer of their career history to ensure checks are made to confirm they are suitable to work in the security industry. In the past, this meant providing details of the past 20 years of their career. This timeframe was then reduced to 10 years, with the current industry standard being further reduced to only the past five years of a security officer’s employment history.

The onus is on security companies to physically go through a person’s list of ex-employers and contact them directly to confirm the dates they worked for that employer and that there were no instances of misconduct. In certain circumstances if they cannot obtain this information managers can choose to sign the employee off as screened without the full screening process having been completed.

The security screening process can get even more complicated when dealing with employees that are from overseas, as it’s sometimes nearly impossible to carry out the correct checks.

For the full blog please visit InfoLogue’s website.

First Security

comments powered by Disqus