June 29, 2026|Franchise Frontlines
June 29, 2026 | United States District Court for the Middle District of Florida | Slip Copy — Not Yet Reported (2026 WL 1855554)
Executive Summary
In a slip-copy order available only by its Westlaw citation, the United States District Court for the Middle District of Florida granted a motion to dismiss brought by defendants Unified HR, LLC and CoAdvantage Resources, Inc. in an employment dispute filed by pro se plaintiff Dafney Robertha Ceneus, who sued under Title VII of the Civil Rights Act of 1964, the Fair Labor Standards Act, and the Florida Private-Sector Whistleblower Act. The threshold legal issue was whether Ceneus had plausibly alleged that Unified HR and CoAdvantage were her employers, where her complaint attributed all day-to-day control to a third defendant, Itel BPO Smart Solutions, Inc., and tied the moving defendants only to back-end payroll and paperwork. Ceneus argued that because CoAdvantage was her “employer of record for payroll, benefits, and tax purposes” and Unified HR appeared as the “Client Company” on her paystubs, the three companies operated as a “single, integrated enterprise and/or joint employers.” Unified HR and CoAdvantage argued that these administrative markers did not show operational control, that the complaint improperly lumped all three defendants together, and that the Title VII claim against CoAdvantage was independently barred for failure to exhaust before the EEOC. The court agreed on each point, holding that the complaint lacked the operational facts necessary to plead a joint-employer or single-enterprise relationship, that it was an impermissible shotgun pleading, and that CoAdvantage was absent from the administrative record; it dismissed the claims against the moving defendants without prejudice and gave Ceneus fourteen days to replead.
Relevant Background
According to the complaint, Ceneus began working for Itel BPO Smart Solutions, Inc. as a customer service agent in October 2024. After a series of payroll delays and missing wages, she posted in a company-wide communication channel that failing to pay employees was illegal and threatened to contact the Department of Labor. She alleged that management then banned her from communication tools, placed her under intense scrutiny, and fired her in February 2025.
Ceneus sued three separate entities. Her complaint acknowledged that Itel “exerted primary control over [her] day-to-day work,” provided her equipment, managed her supervisors, and made the ultimate decision to terminate her. To reach the other two defendants, she relied on administrative markers: she alleged that Unified HR was identified as the “Client Company” on her paystubs and that CoAdvantage was her “employer of record for payroll, benefits, and tax purposes.” From those details, the complaint asserted that all three corporations operated as a “single, integrated enterprise and/or joint employers.”
Unified HR and CoAdvantage moved to dismiss the claims against them, arguing that there were no facts demonstrating operational control or administrative exhaustion. Ceneus responded by emphasizing her pro se status and arguing that, because her claims focused heavily on payroll discrepancies, the entities responsible for processing her checks were naturally proper defendants. The complaint also noted that only Unified HR was listed as the employer on her EEOC charge.
Decision
The court began from the premise that, for any of Ceneus’s claims to proceed against Unified HR or CoAdvantage, she had to plausibly allege that they were her employers, citing Lyes v. City of Riviera Beach and related district-court authority. Because she “explicitly gives Itel credit for her day-to-day management,” the court reasoned that her case against the other defendants “lives or dies on a ‘joint employer’ or ‘single enterprise’ theory.” Applying the ordinary Twombly plausibility standard, the court accepted the well-pleaded facts as true but disregarded “conclusory allegations, unwarranted factual deductions or legal conclusions masquerading as facts.”
The court set out the controlling standards it drew from Eleventh Circuit precedent. Quoting Layton v. DHL Express (USA), Inc., it described the joint-employer inquiry as “a highly contextual, fact-driven inquiry that looks past formal agreements and straight at the economic realities of the workplace,” asking whether the alleged joint employer “retained control over the essential terms and conditions of employment, such as the authority to hire and fire employees, supervise and control work schedules or conditions of employment, determine the rate and method of payment, and maintain employment records.” For the related single-enterprise test, it balanced the four Lyes factors: interrelation of operations, centralized control of labor relations, common management, and common ownership or financial control.
Measured against those standards, the court held that the complaint “lacks any operational facts touching on these elements.” The allegations against the moving defendants were “purely administrative” — CoAdvantage processed taxes and benefits, and Unified HR’s name appeared on the paystubs — and “processing paychecks is a far cry from dictating structural employment conditions.” The complaint never suggested that Unified HR or CoAdvantage had a hand in hiring, set her hours, told her how to handle customer calls, or orchestrated her termination; “to the contrary, she attributes all those critical operational decisions directly to Itel.” Citing Roundtree v. Tegna, Inc., the court concluded that “Administrative proximity is not workplace control,” and that the joint-employer and single-enterprise allegations failed as a matter of law.
The court identified two further defects. First, it held the complaint was “a classic pleading trap: it is a shotgun pleading” that “lump[s] separate parties together indiscriminately,” citing Weiland v. Palm Beach County Sheriff’s Office; while collective grouping “might fly” had a single-enterprise or joint-employer relationship been established, “that is the horse, and collective pleading is the cart,” and a plaintiff “cannot use a shotgun framework to bootstrap a joint-employer theory into existence.” Second, the court held that the Title VII claim against CoAdvantage independently failed for lack of administrative exhaustion under Virgo v. Riviera Beach Associates, because only Unified HR was named on the EEOC charge and CoAdvantage was “completely absent from the administrative record”; the narrow “identity of interest” exception had no application absent any baseline joint operational control. Because Ceneus proceeded pro se, the court dismissed the claims without prejudice and allowed fourteen days to plead “more specific operational facts, if any exist,” cautioning that she “cannot sue every company whose name or logo appeared on her employment paperwork.”
Looking Forward
For employers, franchisors, and branded systems that rely on professional employer organizations, co-employment arrangements, or shared payroll and benefits administration, this order is a useful defense-side marker on how one court tested a joint-employer pleading at the outset of a case. On this record, the court drew a clean line between back-office functions and employment control: it held that payroll processing and an entity’s name on a paystub, standing alone, did not make either moving defendant an employer, because the complaint itself located hiring, supervision, and termination with the operating company. That reasoning is confined to the Middle District of Florida and to the plaintiff’s own allegations, but it may inform how other courts approach analogous attempts to convert administrative touchpoints into employer status.
The analysis maps by analogy onto the PEO and shared-services arrangements common in franchised and multi-entity systems, where a brand entity or administrative provider may facilitate payroll, benefits enrollment, or paperwork without assuming the essential functions of an employer. The court’s framing that “Administrative proximity is not workplace control” could offer persuasive support when a plaintiff tries to treat a payroll processor or administrative affiliate as a joint employer on thin facts. The order also rewards disciplined allocation of employment functions: because the plaintiff’s own complaint attributed day-to-day control to the operating company, the joint-employer theory failed on its face. Operators and their administrative providers may reduce exposure by structuring and documenting their arrangements — in contracts, service descriptions, and actual practice — so that the operating employer visibly retains hiring, supervision, discipline, scheduling, and termination authority while the administrative provider stays in its lane.
The procedural holdings offer additional, cautionary leverage. The court’s treatment of the pleading as a shotgun complaint illustrates the potential value of insisting that a plaintiff specify what each defendant actually did rather than billing “Defendants” collectively, and its exhaustion holding is a reminder that Title VII’s administrative prerequisites may need to be checked entity by entity. Employers should not overread the outcome, however. The dismissal was without prejudice, the plaintiff may attempt to replead, and the court did not hold that a PEO or payroll processor can never be a joint employer; on a different record showing genuine control over employment terms, the result could differ. The measured lesson is that, at least on the facts before this court, administrative involvement alone did not establish employment liability.
Thomas O’Connell is a Partner at Buchalter LLP and Chair of the firm’s Franchise Practice Group. For questions about this article or media inquiries, you can contact Tom at toconnell@buchalter.com.
This article is based solely on the opinion of the Court in this matter. The author has not conducted any independent investigation into the facts. For the avoidance of doubt, each statement related to the law and facts in this article is drawn from the Court’s opinion in this case. It was drafted with the assistance of an artificial intelligence system. AI systems can make mistakes, including in describing legal authority. Readers should independently confirm any legal authority before relying on it.
This communication is not intended to create, and does not create, an attorney-client relationship or any other legal relationship. No statement herein constitutes legal advice, nor should it be relied upon or interpreted as such. This communication is for general informational purposes only and is not a substitute for legal counsel. Readers should not act or refrain from acting based on any information provided without seeking appropriate legal advice specific to their situation. For more information, visit www.buchalter.com.
