21Apr

Criminal record checks are now standard practice in many industries, used to manage organisational risk, meet regulatory obligations, and support safer hiring. But while useful, these checks are not risk-free, and mishandling them can lead to legal issues and reputational damage.
 
Employers can usually request a check from applicants or employees, but only where it’s clearly relevant to the role. For example, a check may be appropriate where the role involves working with vulnerable people, financial assets, or sensitive information. However, applying a blanket approach without role-specific reasoning can expose an organisation to claims of unfair treatment or discrimination.
 
A criminal record does not automatically make someone unsuitable for a role. The nature of the offence, how long ago it occurred, any pattern of behaviour, and its relevance to the role should all be considered. Employers also need to be mindful of privacy obligations, particularly as job applicants don’t fall under the same privacy exemptions as current employees. Criminal history is classified as sensitive information, and must be handled with care, stored securely, limited to those with a genuine need to know, and destroyed when no longer required.
 
Spent convictions laws differ across Australia, and employers must take care not to rely on information they shouldn’t consider. Often, candidates disclose more than is necessary out of confusion or caution, and decision-makers may mistakenly act on that information.
 
Problems commonly arise when checks are requested too early, applied inconsistently, or when candidates are not given a fair chance to explain the context of a past offence. The strongest approach is one that’s fair, proportionate, and well-documented.
 
Criminal record checks can support informed decision-making, but only when used appropriately. If your current process needs review, The BelRose Group can help you implement policies that are both effective and legally compliant.

Leave a Reply

Your email address will not be published. Required fields are marked *

This field is required.

This field is required.