Vermont Information Processing, Inc. v. NLRB

CourtCourt of Appeals for the D.C. Circuit
DecidedMay 26, 2026
Docket24-1360
StatusPublished

This text of Vermont Information Processing, Inc. v. NLRB (Vermont Information Processing, Inc. v. NLRB) is published on Counsel Stack Legal Research, covering Court of Appeals for the D.C. Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Vermont Information Processing, Inc. v. NLRB, (D.C. Cir. 2026).

Opinion

United States Court of Appeals FOR THE DISTRICT OF COLUMBIA CIRCUIT

Argued October 15, 2025 Decided May 26, 2026

No. 24-1360

VERMONT INFORMATION PROCESSING, INC., PETITIONER

v.

NATIONAL LABOR RELATIONS BOARD, RESPONDENT

CHRISTOPHER BENDEL, ET AL., INTERVENORS

Consolidated with 24-1375

On Petition for Review and Cross-Application for Enforcement of an Order of the National Labor Relations Board

Stephen D. Ellis argued the cause for petitioner. With him on the briefs was Carl “Ott” Lindstrom. Tillman J. Breckenridge entered an appearance. 2 Gregoire Sauter, Attorney, National Labor Relations Board, argued the cause for respondent. With him on the brief were Ruth E. Burdick, Deputy Associate General Counsel, Meredith Jason, Assistant General Counsel, and Usha Dheenan, Supervisory Attorney.

Before: MILLETT, WALKER and PAN, Circuit Judges.

Opinion for the Court filed by Circuit Judge PAN.

Opinion concurring in part and dissenting in part filed by Circuit Judge WALKER.

PAN, Circuit Judge: Employees often wonder how much money their coworkers are making. Such information might help them negotiate salary raises, serve as a point of comparison when seeking other employment, or simply satisfy their curiosity. Sharing salary information among employees is a protected activity under the National Labor Relations Act. In this case, the National Labor Relations Board (NLRB) determined that Vermont Information Processing, Inc. (VIP) illegally fired four employees for creating and disseminating a salary-sharing spreadsheet. The Board ordered VIP to offer the employees reinstatement and to compensate them financially. VIP petitions for review of that order, while the NLRB cross- applies for enforcement.

We hold that substantial evidence supports the Board’s determination that VIP illegally fired one of the employees, Christopher Bendel. But with respect to the other three workers, the Board impermissibly broadened its theory of liability to include an additional consideration beyond the scope of the NLRB General Counsel’s complaint against the company. We therefore grant each petition in part, deny each petition in part, and remand for further proceedings. 3 I. Factual Background

VIP is a software company that services the beverage industry. It employs software engineers to build and maintain applications used by its customers, and it organizes those engineers into small software-development teams.

In February 2022, VIP began rolling out a restructuring plan. As part of the roll-out, software engineer Christopher Bendel met with his supervisor, Sam Graefe, to discuss how the restructuring would affect Bendel’s role. The meeting did not go well. Bendel was dissatisfied with the new position that management had designed for him and expressed his concerns to Graefe. He ended the conversation abruptly and then called Graefe’s supervisor, Director of Development Christopher McGinty, to discuss his concerns. Prior to those conversations, Bendel had informed both Graefe and McGinty that “he had offers from other companies.” J.A. 851. When Graefe and McGinty compared notes about their interactions with Bendel, Graefe noted that Bendel “didn’t seem too happy about our conversation,” while McGinty wrote that it “wasn’t a pretty conversation.” S.J.A. 4–6.

Later that day, Bendel messaged another software engineer, Kaleb Noble, on VIP’s Google Workspace platform. Bendel described his meeting with Graefe as a “shitshow” and claimed that he had “hung up on [Graefe].”1 J.A. 1137–39. During that conversation, Noble asked Bendel, “Do you mind me asking your salary . . . ?” J.A. 1141. Bendel informed Noble that his salary was $95,000, and Noble responded that his was $87,000. Bendel then asked, “[W]anna start a [salary]

1 Graefe has never confirmed that Bendel hung up on him, and Bendel later testified that he had been “puffing [his] chest a little bit in the chat with” Noble. J.A. 594. 4 spreadsheet?” Id. After Noble agreed, Bendel created a spreadsheet and shared it with Noble, and Noble said that he would share it with two other software engineers, Gordon Dragoon and Kestrel Swift. Noble described the spreadsheet’s purpose as follows: “The idea in my mind is so if you wanna ask for a raise you got some reference to see if you’re getting fisted lol.” J.A. 1145. Bendel agreed. Bendel and Noble shared the spreadsheet with Dragoon and Swift, and all four employees entered their names, positions, and salaries into the first four rows.

The next day, between 8:00 and 9:00 a.m., VIP held a virtual all-hands meeting to launch its restructuring plan. During or immediately after the meeting, the four employees began sharing the spreadsheet link with other employees. Around twenty-five coworkers entered information into the spreadsheet. An employee who received the spreadsheet shared it with a supervisor, who shared it with Development Director McGinty, who passed it on to Operations Director Louise Morgan.

At 11:26 a.m., Morgan met with McGinty to view and discuss the spreadsheet. From the file-ownership information, they could tell that Bendel had created it. And they noticed a notation on the spreadsheet indicating that “100 [percent]” of VIP’s software developers were “underpaid.” J.A. 1293 (showing two adjacent spreadsheet cells, the first reading “% of underpaid devs” and the next reading “100”). Morgan and McGinty attributed that statement to Bendel, as the spreadsheet’s creator.2 When they told Chief Financial Officer

2 The record contains mixed evidence concerning whether Bendel actually added this notation, or whether a different employee did. But the record makes clear that, beyond identifying who originally 5 John Simard and other company leaders about the spreadsheet, Simard reacted strongly. Simard believed that the spreadsheet was “not appropriate,” “not accurate,” and “serve[d] no purpose.” J.A. 1028. In particular, he took issue with “the idea that [the spreadsheet] was being used to demonstrate that all of [VIP’s] programmers, a hundred percent of them[,] are underpaid.” Id. Based largely on Simard’s arguments, management decided to disable the spreadsheet. They then discussed Bendel’s future at the company and quickly decided to fire him.

At around 11:32 a.m., VIP management disabled Bendel’s internal accounts. The company remotely locked his computer and fired him at around noon. When informing Bendel of his termination, McGinty cited Bendel’s “feeling towards VIP” and his “attitude,” particularly “towards the restructuring and how he . . . was uninterested in partaking in that.” J.A. 855; accord J.A. 1130 (Bendel’s description of his conversation with McGinty). Management disabled the spreadsheet at around 12:19 p.m., but Dragoon informed Noble and Swift that he had already downloaded the spreadsheet and would transfer it to his personal email.

During and after these events, the four creators of the spreadsheet exchanged a plethora of colorful messages. Many of those messages pertained directly to the spreadsheet, their salaries, and their unhappiness with Bendel’s firing. Other messages went further afield. For example, the employees discussed their desire to leave VIP and to convince one of their coworkers to join them. They repeatedly used profanity to criticize VIP management; discussed “[p]urg[ing] [their] computers,” J.A. 1197; and talked about sharing their

created the spreadsheet, Morgan and McGinty made no further effort to verify that Bendel authored the notation. 6 complaints with a former VIP employee who was working for a VIP customer.

The day after Bendel’s termination, VIP’s Information Technology Director discovered the messages and forwarded them to management, prompting management to convene a meeting to discuss the messages and the fate of their authors.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Securities & Exchange Commission v. Chenery Corp.
318 U.S. 80 (Supreme Court, 1943)
American Federation of Labor v. Watson
327 U.S. 582 (Supreme Court, 1946)
National Labor Relations Board v. Strong
393 U.S. 357 (Supreme Court, 1969)
Curtis v. Loether
415 U.S. 189 (Supreme Court, 1974)
Franks v. Bowman Transportation Co.
424 U.S. 747 (Supreme Court, 1976)
Sure-Tan, Inc. v. National Labor Relations Board
467 U.S. 883 (Supreme Court, 1984)
Bowen v. Massachusetts
487 U.S. 879 (Supreme Court, 1988)
United States v. Burke
504 U.S. 229 (Supreme Court, 1992)
New Hampshire v. Maine
532 U.S. 742 (Supreme Court, 2001)
Pollard v. E. I. Du Pont De Nemours & Co.
532 U.S. 843 (Supreme Court, 2001)
Great-West Life & Annuity Insurance v. Knudson
534 U.S. 204 (Supreme Court, 2002)
Stoiber v. Securities & Exchange Commission
161 F.3d 745 (D.C. Circuit, 1998)

Cite This Page — Counsel Stack

Bluebook (online)
Vermont Information Processing, Inc. v. NLRB, Counsel Stack Legal Research, https://law.counselstack.com/opinion/vermont-information-processing-inc-v-nlrb-cadc-2026.