Concept
Consequences of a Defective Order
Contents and persons bound
Consequences of a Defective Order
Rule 65(d)(1) directs the judge who grants an injunction to state the reasons it issued, to state its terms specifically, and to describe the restrained or required acts in reasonable detail without pointing to the complaint or another document.1 The rule is phrased as a command to the drafting judge, and a command invites an obvious question: what happens when the judge falls short? The three clauses announce no remedy, so the answer comes from the job the requirements do. They make the order a sound foundation for enforcement, and the enforcement tool that rests on that foundation is contempt, the court’s power to fine or jail a person who disobeys.
Two consequences follow, and they pull in opposite directions. The first is severe: an order that fails the rule generally cannot support a finding of contempt, and one that fails badly enough is treated as no injunction at all. An injunction is a personal command backed by a personal sanction, so a person may be punished only for violating a command that the order itself made readable and fixed. A judge’s evident intention does not fill a gap in the text. The H.K. Porter decree, which borrowed a settlement agreement by reference instead of stating the forbidden acts, shows one version of the problem, and the next subsection takes it up.
The second consequence tempers the first. Courts do not treat every departure from the rule’s wording as fatal, because a drafting slip that left the judge and the parties knowing exactly what conduct was forbidden does not undermine enforcement the way a truly unclear order does. A flaw matters in proportion to how far it defeats the rule’s purpose of giving later enforcement a solid foundation. Both consequences belong in one analysis. Ask first whether the order contains an operative command that meets Rule 65(d)(1), and then ask how serious any shortfall is. The subsection after the contempt discussion draws the line between technical and substantial defects.
No Contempt Without Compliance
Contempt punishes disobedience, so every contempt remedy presupposes something that was disobeyed, and H.K. Porter Co. v. National Friction Products spells out what that something must be. Before either the compensatory or the coercive side of civil contempt can be brought into play, there must have been disobedience of an operative command capable of enforcement, and that command, if it is in substance an injunction, must also comply with Rule 65(d).2 The conditions come in sequence. The first asks whether the court commanded anything at all, and the second asks whether a command that does exist was written in the form the rule demands. A movant whose order fails either one holds something that cannot carry a contempt motion, however plainly the other side departed from what the movant expected.
The plaintiff in Porter invoked the contempt power on the strength of an April 15, 1968 order that did no more than incorporate a settlement agreement by reference.3 The Seventh Circuit found the first condition unmet. The court had entered a judgment approving the obligations the settlement created, but its language did not turn a contractual duty into an obligation to obey an operative command, so the case resembled a declaratory judgment about contract obligations.4 The court added that even if the order could be read as a command, incorporating the agreement ignored the rule’s mandatory requirement that an injunction describe the restrained acts without reference to the complaint or another document.5 Calling the error “serious and decisive,” the court held that it precluded the plaintiff from invoking the contempt power.6 The compensatory and the coercive remedies fell together because the defect lies in the order, and every sanction that depends on proving a violation depends on the order. A settlement “made part of the decree” therefore raises a question rather than answering one: does the decree itself command anything? The usual exam error is to treat incorporation as if it converted every promise in the agreement into an order enforceable by contempt.
The reason for the rule lies in what a contempt hearing is for. The hearing asks whether the defendant broke a command that already existed, and a defendant cannot break a command whose content the order never fixed. If contempt could rest on such an order, one proceeding would have to decide what the court meant and whether the defendant violated it, and the sanction would land on someone with no way to know beforehand where the line ran. Porter framed the point in terms of liberty and due process. Because contempt proceedings, civil or criminal, expose a person to coercive or penal measures, the judge must speak clearly, explicitly, and specifically, even when the person facing sanctions is only an officer of a party rather than a party of record.7 The stakes are concrete at the enforcement stage, where a person bound by a decree that enjoins a statutory violation can be summoned on a rule to show cause and made to explain why he should not be jailed, fined, or otherwise sanctioned.8 The cost of a defective order lands on the party who obtained it, who loses the use of the contempt power, while the enjoined party is not punished for the judge’s drafting slip. A party who wants contempt available therefore has a practical reason to make sure the order it obtains can carry a contempt motion.
In Porter the defendant’s alleged breach of the agreement made no difference to the result, because the decree supplied no command for the breach to violate. Here the judgment names the forbidden act, the place, and the deadline in its own words, so an operative command exists and it satisfies Rule 65(d)(1). The contempt hearing can go forward, but a compliant order only opens the door and does not decide the outcome. A finding of indirect contempt also requires that the defendant intentionally or willfully disobeyed the order without a justifiable excuse, such as inability to comply.9
A defective order also has a consequence for the party it was meant to restrain. In Reich v. ABC/York-Estes Corp., 64 F.3d 316 (7th Cir. 1995), the restrained party appealed, and the Seventh Circuit dismissed the appeal for lack of jurisdiction because, given the failure to comply with Rule 65(d), there was no injunction.10
The reasoning runs in a chain. The purpose of Rule 65(d) is to provide a solid foundation for any later proceeding to enforce the injunction, as by a motion to hold the defendant in contempt, and an order that fails the rule is not an injunction and places the party under no obligations.11 An order that is not actually or at least potentially coercive imposes none of the tangible harm that Article III requires for standing to seek judicial relief, including relief in the form of an appellate judgment.12 Without obligations there is nothing to coerce, without coercion there is no harm, and without harm the court of appeals has nothing to review. The court summarized the result this way: “[a]n injunction that has no binding force cannot be appealed.”13
Reich involved a second rule as well, Rule 58, and the court held that the failure to comply with either rule compelled dismissal.14 The two decisions are mirror images. In Porter the party who wanted enforcement lost the contempt remedy, and in Reich the party who wanted to challenge the order lost the right to review, yet both outcomes rest on the premise that an order that does not bind does nothing. How deep the defect runs still matters, because Reich itself disclosed that an earlier decision had not dismissed an appeal when the violation there was technical rather than substantial. The next subsection takes up that line.15
The same premise reaches contempt that has nothing to do with the wording of Rule 65(d). A criminal contempt finding under 18 U.S.C. § 401(3) must rest on the violation of an identifiable court order, one specific enough that the defendant had an opportunity to know that his behavior was disobedience.16 In In re Stewart, 571 F.2d 958 (5th Cir. 1978), a judge presiding over an unrelated jury trial learned that a juror had been demoted at work because of jury service, and he told the juror to inform the supervisor that the judge would not tolerate the demotion of a citizen for serving on a jury.17 The supervisor, Stewart, disputed that any demotion had occurred, and the judge held him in contempt. One defect in that finding was the absence of any specificity in the supposed order, because a remark relayed through a juror gave Stewart no identifiable command to obey.18 A companion requirement, applied in Gucci America, Inc. v. Weixing Li, 768 F.3d 122 (2d Cir. 2014), asks that the order be clear enough that a party can learn from its four corners what it must do, and an ambiguity in the term “defendant” defeated a contempt finding there.19 These requirements overlap with Rule 65(d)(1) because they share a source, the principle that a person punished must first have been told what to do. They also reach orders that are not injunctions at all, such as an oral directive or a subpoena, so an exam answer on contempt should check both the rule’s contents requirements and whether an identifiable, clear command exists.
Technical Versus Substantial Defects
The prior subsection ended on the harshest consequence of a defective order. In Reich v. ABC/York-Estes Corp. the Seventh Circuit called that consequence “quite dramatic”: an order failing Rule 65(d) is not an injunction and places the restrained party under no obligations.21 The same opinion then qualified the result. The court disclosed that in Chicago & North Western Transp. Co. v. Railway Labor Exec. Ass’n, 908 F.2d 144 (7th Cir. 1990), it had not dismissed an appeal from an order that fell short of the rule, because it had held the violation there to be technical but not substantial.22 Two orders that both depart from the rule can therefore land on opposite sides of a line, and the task here is to see what puts them there.
The line comes from the purpose the court attributed to the rule, which is to provide a solid foundation for any later proceeding to enforce the injunction, such as a motion to hold the defendant in contempt.23 A foundation is a functional idea. A contempt court needs to know what the defendant was told to do, and a court of appeals needs an order it can read and review, so a drafting flaw matters to the degree that it takes those things away. When an order lacks some wording the rule asks for but the judge, the parties, and the record all fix the same conduct, nothing about later enforcement is at risk, and voiding the order would penalize the party who won it for a defect that hurt no one. When nobody can say what was enjoined, the foundation itself is missing, and enforcement would require someone to invent the command after the fact.
In Chicago & North Western the defendant was already subject to a preliminary injunction, and the plaintiff moved the district court to make that injunction permanent.24 The Seventh Circuit nevertheless called the shortfall technical, and it relied on three facts. Both parties and the judge knew precisely what conduct was enjoined, because the judge had simply made the preliminary injunction permanent. Neither party could claim ignorance or prejudice. And the proceeding in which the preliminary injunction was granted had produced a sufficient record setting the boundaries of the injunction.25 Each fact answers the purpose described above. Shared knowledge means a later contempt court would find no dispute about what the defendant had been told. The absence of prejudice means the party who might be punished lost nothing by the omission. The existing record means the missing detail could be recovered from a place where the court had already settled it.
The order in Reich offered none of that. The restrained party, ABC, was left in the dark about what conduct might have been enjoined and could not tell whether an injunction had been entered at all.26 The court reasoned that without orders complying with Rules 58 and 65(d), no one except the district judge could determine whether an injunction existed or what it enjoined, and it treated the violation as substantial.27 Because both rules had been so clearly violated, the court took the double failure as showing that the district judge had no intention of enjoining ABC from future conduct, and it dismissed the appeal.28
Set side by side, the two decisions differ in a single variable. Both orders lacked detail the rule requires, so a count of missing words does not separate them. What separates them is whether anyone could tell, from the order and the surrounding record, what was enjoined. In Chicago & North Western the parties and the judge could, and in Reich no one could. A reader who counts omissions will misplace the line, because the court measured how much of the foundation for enforcement survived the flaw.
H.K. Porter Co. v. National Friction Products shows the substantial side from another direction. The decree there approved the obligations the parties had taken on in a settlement agreement and merely incorporated that agreement by reference, and the Seventh Circuit called the resulting error “serious and decisive.”29 A student might expect the written agreement to supply the boundaries, as the earlier record did in Chicago & North Western. Yet a party may incur a legal duty by settling, and the judgment must still set forth an unequivocal command in specific detail before it can support contempt, whereas the decree in Porter never turned a contractual duty into an obligation to obey.30 Even if both sides understood the settlement terms perfectly, what they understood was what they had promised each other, which differs from what a court had commanded. In Chicago & North Western, by contrast, a court command already existed in the preliminary injunction, and the permanent order carried it forward.31
Steps 3 and 4 do the real work, because they ask whether the foundation for enforcement survived. This sorting comes from one court of appeals’ account of its own decisions, and the text of Rule 65(d) says nothing about technical or substantial violations, so on an exam present it as the way a court reasons from the rule’s purpose rather than as a test the rule itself states. The usual mistakes run in both directions. One treats every missing detail as fatal, which would void orders that everyone understood. The other treats the judge’s evident wish to restrain as enough, when the question is whether the order and the record let anyone tell what was restrained. Even where a court forgives a technical flaw, the drafting judge cannot count on that forgiveness, because it depended on facts outside the order.