Turned down in 1986 for a position as an “operator” in Springfield’s Department of Public Utilities, Regina McGuire complained to the Illinois Department of Human Rights that she had been the victim of sex discrimination. After considering her claim for an entire decаde (!), the idhr entered an order in 1996 directing Springfield to place her in its training program for the operator’s position, and to grant her back pay and seniority retroactive to 1987 if she completed the program successfully. The City put McGuire into the program as instructed, and she washed out in May 1998, at the end of an extended probationary period as Opеrator Trainee III. In this suit under Title VII of the Civil Rights Act of 1964, McGuire contends that this decision represents retaliation against the exеrcise of her right to complain to the idhR, in violation of 42 U.S.C. § 2000e-3(a). The district court granted summary judgment in Springfield’s favor.
As the district judge saw things, McGuire’s release from the training program in 1998 was too remote from her charge of discrimination in 1987 to allow an inference that the former was a response to the latter. Often we have observed that timing may offer a clue to cаusation (or its absence) when an employee charges retaliation: a short gap may suggest a causal link, while a long one undercuts an inference of causation. See
Lalvani v. Cook County,
*797
A causal link between the charge of discrimination and the employer’s action need not demonstrate unlawful retaliation, howevеr. Suppose that the idhr had ordered Springfield to pay McGuire $100,000 in back pay in lieu of placing her in the training program, аnd that the City had done so. There would be a causal chain: charge leading .to decision leading to payment. Yet the payment could not be labeled “retaliation” for the charge, kicking off another round of complaint. “Consequеnce” yes; “retaliation” no. An employer’s action can be called “retaliation” only if it makes the employee worse off on account of the protected activity. Forking out $100,000 in damages does not make an employеe worse off — even if the employee really wanted a larger award. To generalize, a series of events that an employee would pay to avoid might sensibly be called “retaliation,” while a series of events that an employee would pay to enjoy cannot be deemed retaliatory. Cf.
Henn v. National Geographic Society,
Another monetary example makes the point. Suppose once again that the idhr had required Springfield to pay McGuire $100,000, but this time the City failed to do so, writing a chеck for $25,000 but refusing on account of a budget shortfall (or even dissatisfaction with the idhr’s decision) to pay the remainder. Could this bе deemed “retaliation” for the original charge of discrimination and support a judgment under § 2000e-3(a)? We don’t see how. MсGuire would be better off than before (to the tune of $25,000); and if the City failed to carry out the idhr’s instructions, that would be a violation оf the idhr’s order, not of federal law. Similarly, if the National Labor Relations Board orders an employer that has resisted unionization at every turn to bargain collectively with its workers, and the employer engages in surface bargaining that collapses without producing a collective bargaining agreement, this obstinacy could not be thought “retaliation” against the union for filing an unfair-labor-practice charge.
Failure to pay a judgment or comply with an injunction entered by a сourt or agency cannot usefully be called “retaliation for filing the complaint”; nor is slow payment or even nonрayment a separate violation of federal law. See
Evans v. Chicago,
AFFIRMED.
