Got (Raw) Milk? How About Jurisdiction? Something's Sour in the Raw-Milk Case

08 August 2014 Wisconsin Appellate Law Blog

Yesterday, the Wisconsin Court of Appeals released its unpublished opinion in Farm-To-Consumer v. Wis. DATCP, 11AP2264, a closely watched case involving Wisconsin’s regulation of raw-milk production. A couple of local farmers had sought a declaratory judgment, invalidating a Wisconsin law criminalizing the distribution and sale of raw milk. The court of appeals’ decision was a long time coming (two years after it was submitted on the briefs), yet perhaps it should not have come at all.

The plaintiffs appealed from the denial of their motion for summary judgment. Appellate courts in Wisconsin typically do not have jurisdiction to hear appeals from the denial of a summary-judgment motion because decisions denying motions for summary judgment do not dispose of the entire matter as to the parties, a cardinal rule for creating final, appealable orders. The opinion from Wisconsin’s court of appeals appears to have missed the issue entirely.

Under Wis. Stat. § 808.03(1), a final judgment may be appealed as of right when it “disposes of the entire matter in litigation as to one or more of the parties.” The denial of a summary-judgment motion does not dispose of a matter. A trial is required, even for declaratory-judgment actions. Wis. Stat. § 806.04(9). The rule’s only exception is if a party requests a permissive appeal. Torgerson v. Journal/Sentinel, Inc., 210 Wis. 2d 524, 563 N.W.2d 472 (1997). Nothing on the docket indicates that any party sought permission here.

It’s not hard to see where the court of appeals went awry. In Wambolt v. W. Bend Mut. Ins. Co., 2007 WI 35, 299 Wis. 2d 723, 728 N.W.2d 670, the Wisconsin Supreme Court required that all final orders and judgments must state that they are final for the purposes of appeal. The circuit court in this raw-milk case entered two orders, one denying summary judgment and the other deciding a motion to clarify. Each erroneously stated that it was final.

The plaintiffs appealed these orders, and the State moved to dismiss the appeal for lack of jurisdiction. In a February 14, 2012 order, the court of appeals held that it had jurisdiction because both of the circuit court’s orders complied with Wambolt‘s directive that an order state that it is final. It did not address whether the circuit court’s decision disposed of the entire matter as to the parties so that it was in fact “final.”

Calling a nonfinal order final doesn’t magically make it final if it isn’t. Otherwise, circuit courts could expand the jurisdiction of the court of appeals dramatically, and typically jurisdiction is something that the court of appeals doesn’t assume lightly. A few of the appellate briefs cast the circuit court’s decision as an affirmative grant of summary judgment for the State. But that’s not a fair reading of what the circuit court did. The State didn’t ask for judgment in its favor, and the circuit court didn’t grant it.

It will be interesting to see if a petition for review is filed. If the case reaches the Supreme Court, this absence of appellate jurisdiction should preclude review on the merits. It would be odd if the Wambolt rule—meant to remove doubt as to whether the circuit court intended an order to be final (so that a potential appellant doesn’t miss the jurisdictional significance of a truly final order)—were to be transformed into a way that the circuit court could supplant the court of appeals’ exclusive authority to decide to review what in fact is a nonfinal order.

This blog is made available by Foley & Lardner LLP (“Foley” or “the Firm”) for informational purposes only. It is not meant to convey the Firm’s legal position on behalf of any client, nor is it intended to convey specific legal advice. Any opinions expressed in this article do not necessarily reflect the views of Foley & Lardner LLP, its partners, or its clients. Accordingly, do not act upon this information without seeking counsel from a licensed attorney. This blog is not intended to create, and receipt of it does not constitute, an attorney-client relationship. Communicating with Foley through this website by email, blog post, or otherwise, does not create an attorney-client relationship for any legal matter. Therefore, any communication or material you transmit to Foley through this blog, whether by email, blog post or any other manner, will not be treated as confidential or proprietary. The information on this blog is published “AS IS” and is not guaranteed to be complete, accurate, and or up-to-date. Foley makes no representations or warranties of any kind, express or implied, as to the operation or content of the site. Foley expressly disclaims all other guarantees, warranties, conditions and representations of any kind, either express or implied, whether arising under any statute, law, commercial use or otherwise, including implied warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Foley or any of its partners, officers, employees, agents or affiliates be liable, directly or indirectly, under any theory of law (contract, tort, negligence or otherwise), to you or anyone else, for any claims, losses or damages, direct, indirect special, incidental, punitive or consequential, resulting from or occasioned by the creation, use of or reliance on this site (including information and other content) or any third party websites or the information, resources or material accessed through any such websites. In some jurisdictions, the contents of this blog may be considered Attorney Advertising. If applicable, please note that prior results do not guarantee a similar outcome. Photographs are for dramatization purposes only and may include models. Likenesses do not necessarily imply current client, partnership or employee status.

Related Services