Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the easy-footnotes 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 /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-document-embedder 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 /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-tables-pro 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 /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the spam-free-wordpress 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 /var/www/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the themelia 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 /var/www/wp-includes/functions.php on line 6121

Deprecated: The called constructor method for WP_Widget class in wpcs_search_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 6121

Deprecated: The called constructor method for WP_Widget class in wpcs_most_view_Widget is deprecated since version 4.3.0! Use __construct() instead. in /var/www/wp-includes/functions.php on line 6121
Hostility to Employee’s Alleged “Disloyal” Conduct Supports Retaliation Claim – Pospis Law, PLLC
Warning: Trying to access array offset on value of type null in /var/www/wp-content/themes/themelia/inc/themelia.php on line 274

Hostility to Employee’s Alleged “Disloyal” Conduct Supports Retaliation Claim

In Vosburgh v. American Nat. Red Cross, 2014 WL 4826688 (N.D.N.Y. Sept. 29, 2014), the court denied defendant’s summary judgment motion regarding plaintiff’s retaliation claim (but granted it regarding plaintiff’s wage and individual liability claims). As to her retaliation claim, the court held:

[T]o prevail at the pretext stage of the McDonnell–Douglas analysis, a plaintiff must show that the employer’s proffered non-retaliatory reason is both false and a pretext for retaliation. There are disputed issues of fact as to whether Defendants’ proffered reasons for reassigning Plaintiff were false. Furthermore, Defendants’ hostility to Plaintiff’s “disloyal” conduct, combined with the relative temporal proximity between Plaintiff’s CCL Complaint and her reassignment, might support an inference that Defendants’ proffered reasons are pretext for retaliation—i.e., that retaliation was the but-for cause of Plaintiff’s reassignment. … Accordingly, Plaintiff has met her burden at the pretext stage, and Defendants are not entitled to summary judgment on Plaintiff’s retaliation claim.

Share This: