Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the luckywp-table-of-contents domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/awdrcom/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/awdrcom/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/awdrcom/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/awdrcom/public_html/wp-includes/functions.php on line 6114

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /home1/awdrcom/public_html/wp-includes/functions.php:6114) in /home1/awdrcom/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":4102,"date":"2022-02-04T09:29:00","date_gmt":"2022-02-03T23:29:00","guid":{"rendered":"https:\/\/awdr.com.au\/?p=4102"},"modified":"2022-02-28T10:12:21","modified_gmt":"2022-02-28T00:12:21","slug":"swearing-in-the-workplace","status":"publish","type":"post","link":"https:\/\/awdr.com.au\/swearing-in-the-workplace\/","title":{"rendered":"Swearing in the Workplace"},"content":{"rendered":"\n\n\n

We explain whether or not you can get fired for swearing in the workplace. The topic of swearing and whether you can be fired for swearing is much more complex these days. Moreso than ever before. This is evident in the case of Illawarra Coal Holdings vs Matthew Gosek<\/a> where the applicant was dismissed for using language such as \u200b\u201cf*****g dog\u201d,\u00a0\u200b\u201cc***\u201d and\u00a0\u200b\u201cdog c***\u201d towards\u00a0his fellow colleagues.<\/p>\n\n\n\n

Example of a Fair Work Cases involving swearing<\/h2>\n\n\n\n

On appeal the Fair Work Commission provided consideration to all aspects of the case of Illawarra Coasl Holdings vs Matthew Gosek<\/strong> in their outcome. <\/p>\n\n\n\n

In the Outcome the Commision states, “Having conducted the evaluative judgement that the discretion requires, and based on the findings I have made about the evidence as a whole before the Commission, I do not, on balance, consider the dismissal to have been harsh, unjust or unreasonable. In particular, I do not consider that the mitigating circumstances are so compelling as to render dismissal for what were serious acts of misconduct to be so disproportionate as to be harsh. <\/p>\n\n\n\n

Mental illness may explain the misconduct in part, but the consumption of alcohol does not excuse it even if it also partially explains the behaviour. <\/p>\n\n\n\n

The misconduct was at the higher end of the scale \u2013 involving threats specifically directed to individuals and not simply foul language. It was destructive of working relationships and inconsistent with the policies and values espoused by the employer. It was unwelcome. At the time, and to varying degrees subsequently, it upset and offended the recipients. Its workplace impact was ameliorated by the timely and contrite apologies and the spirit in which those apologies were, for the most part, received and accepted by some of the employees. The other mitigating factors relating to length of service and an unblemished prior record are weighty but on balance do not displace a sound, defensible and well-founded reason for dismissal.”<\/p>\n\n\n\n

\"you<\/figure>\n\n\n\n

Can You Be Fired for Swearing?<\/h2>\n\n\n\n

Yes and no, as it depends on the circumstances. Swearing and the use of bad language is not explicitly considered to be serious misconduct under the Fair Work Act. You need to refer to your internal workplace policies and code of conduct. However, if you have been fired <\/a>or dismissed, in some circumstances you could file for unfair dismissal. <\/p>\n\n\n\n

There may be instances where swearing in a threatening manner could be reasonable grounds being stood down while your employer completes a workplace investigation. Provided you have been provided with procedural fairness around the investigation, if it is found that your swearing was connected with a threat of assaulting or abusing another employer this could lead you in hot water. In these instances, your behaviour could very well be deemed reasonable grounds for dismissal on the basis of serious misconduct.<\/p>\n\n\n\n

Have You Been Unfairly Dismissed or Fired For Swearing?<\/h2>\n\n\n\n

If you have been unfairly dismissed due to swearing, dependant on the circumstances you may have a claim for unfair dismissal. Contacting our team for workplace advice will enable us to better understand the circumstances around the swearing and how we may be able to assist. <\/p>\n\n\n\n

Resources & Guides for Employees<\/h2>\n\n\n\n