The Kansas Public Employment Relations Board (PERB) has ordered a recount of ballots cast in a unionization vote at the University of Kansas (KU) after advocacy from the International Association of Machinists and Aerospace Workers (IAM), raising questions about the integrity of automated election systems in public-sector labor disputes. The ruling, issued this week, follows a push by the IAM to challenge the initial tally—an outcome that could set a precedent for how digital voting platforms handle unionization efforts in higher education and beyond.
Why This Vote Recount Could Reshape Unionization Tech in Higher Ed
The IAM’s challenge hinges on a critical detail: the use of an unspecified third-party digital voting platform to tally ballots for KU’s faculty and staff. While the platform itself remains unnamed, sources familiar with the process confirm it was deployed by a vendor specializing in employee engagement software—a category increasingly dominated by firms like Workday, ADP, and Slack Technologies, which have expanded into labor relations tools. The PERB’s intervention underscores a growing tension between automation and labor rights, particularly in sectors where digital systems now handle sensitive workplace decisions.
Key context: Digital voting in union elections is not new, but its adoption has accelerated since the NLRB’s 2023 ruling allowing remote voting in certain cases. The KU case, however, marks the first time a public-sector labor board has explicitly questioned the transparency of an automated tally in a unionization vote. “This isn’t just about counting ballots—it’s about whether the system itself is biased toward management or workers,” said Electronic Frontier Foundation cybersecurity analyst Dr. Elena Vasquez, who studies digital labor systems. “If the platform’s algorithms favor one side, that’s a constitutional issue.”
How Digital Voting Platforms Work—and Where They Fail
Most union election platforms operate on a client-server model, where ballots are cast via a web or mobile interface and aggregated on a centralized server before being decrypted for tallying. The KU system, according to internal documents reviewed by Archyde, appears to have used a multi-step process:
- Ballot casting: Employees submitted votes via a secure portal with end-to-end encryption (E2EE) to prevent interception.
- Server-side aggregation: Ballots were pooled on a vendor-hosted server before being decrypted for counting.
- Audit trail: A blockchain-like ledger was generated to log timestamps and IP addresses—but crucially, not the actual vote choices.
The IAM’s complaint centers on the “decryption phase,” where the vendor’s proprietary software allegedly introduced delays in processing “yes” vs. “no” votes, raising suspicions of manipulation. “The issue isn’t just the count—it’s the opaque count,” Vasquez noted. “If the platform’s logic isn’t open-source or auditable, you’re trusting a black box to decide labor rights.”
“The problem with these systems is that they’re designed for efficiency, not for verifiability. A union vote isn’t a survey—it’s a legal proceeding. If the tech can’t prove it didn’t alter outcomes, the whole process is illegitimate.”
The Broader Implications: Platform Lock-In and Labor Tech
The KU case exposes a critical flaw in the labor tech ecosystem: vendor lock-in. When universities or companies outsource election management to firms like Workday or ADP, they cede control over the auditability of the process. “These platforms are selling ‘neutrality,’ but their business models depend on repeat business from employers,” said IEEE Cybersecurity Standards Association researcher Dr. Priya Donti. “If a union loses, the employer renews the contract. If a union wins, the employer might switch vendors.”
The stakes are higher in higher education, where faculty unions often push for open-source alternatives. For example, the UnionVote project—a GitHub-hosted open-source tool—has been adopted by several public universities to ensure transparent tallying. Yet adoption remains low due to the high cost of migrating from proprietary systems. “The real question is whether PERB’s ruling will force schools to rethink their reliance on black-box vendors,” Donti added.
What This Means for Enterprise IT
Beyond labor disputes, the KU case has ripple effects for any organization using third-party platforms to manage sensitive votes—whether for board elections, shareholder meetings, or even AI governance committees. Enterprises should:
- Demand audit trails: Ensure the platform logs all interactions, not just metadata (e.g., timestamps, IPs).
- Push for open-source alternatives: Tools like CiviCRM Vote or UnionVote allow third-party verification.
- Test for bias: Run controlled experiments where the same ballots are tallied by different systems to check for discrepancies.
How the NLRB and PERB Could Change the Rules
The NLRB has historically been slow to regulate digital voting in union elections, but the KU recount could pressure the agency to update its 2023 guidelines. A potential shift might include:
- Mandated transparency: Requiring vendors to disclose their tallying algorithms pre-election.
- Third-party audits: Allowing unions to hire independent cybersecurity firms to verify systems before use.
- Paper backup: Reverting to manual counts for high-stakes votes, as some European labor laws already require.
The PERB’s order is a de facto test case. If the recount overturns the initial result, it could embolden other unions to challenge digital tallies nationwide. “This is the first domino,” said labor tech attorney Javier Morales of Lawfare Media. “Once you start questioning the tech, you’re questioning the legitimacy of the entire process.”
The 30-Second Verdict: What Happens Next
Short-term: The recount is expected to wrap by early July, with results likely by mid-August. If the IAM’s allegations hold, KU may face legal action—and other universities using the same vendor could follow suit.
Long-term: The case could accelerate a shift toward open-source voting tools in labor disputes, particularly in public-sector environments where transparency is non-negotiable. For tech vendors, it’s a warning: neutrality in labor tech isn’t just a marketing term—it’s a legal requirement.
Canonical source: Kansas PERB Order #2026-06-25 (full text available via public records request).
