How Multi-State Delivery Operators Build a Living Compliance Posture Against AB5 and Copycat Laws
Platforms need real-time compliance monitoring across state contractor rules.
Delivery operators that work across states need real-time independent contractor compliance monitoring as part of onboarding, credentialing, insurance and payments, with rules based on where each contractor works. AB5-style laws make a one-time audit insufficient because both the rules and a contractor’s work geography can change. A living compliance posture treats those changes as operational events to detect and document as they occur.
Why AB5-style laws create a compliance problem that grows harder to manage as delivery operations expand across state lines
The work location is the trigger. If a contractor performs work in California, AB5 applies to the engaging company regardless of where it is headquartered, subject to applicable exemptions. A delivery network needs a way to link each engagement to the rules where the work happens.
AB5 codifies the ABC test as a presumption of employment, placing the burden on the hiring entity to prove all three prongs. Failing one makes the worker an employee with the associated obligations. For delivery businesses, Prong B is particularly difficult because it requires work outside the company’s usual course of business. Delivering packages for a delivery company is not a persuasive example of that distinction.
California and Massachusetts are the only states whose primary wage-law ABC tests lack a “place of business” alternative to Prong B, although Massachusetts retains that alternative for unemployment insurance. AB5 also reaches the California Labor Code, the Unemployment Insurance Code and Industrial Welfare Commission wage orders.
How the regulatory landscape across states is actively shifting, not settled
Geography is only one axis of the problem. Time is the other, as the federal rule cycle demonstrates. The Department of Labor’s six-factor economic-reality rule took effect on March 11, 2024, but Field Assistance Bulletin 2025-1 stopped its enforcement on May 1, 2025. The department then issued a proposal on February 26, 2026, to replace it with a modified 2021 framework. The existing rule can still be used in private litigation, so companies can still face claims under it even though the agency has stopped enforcing it.
State policy is moving in a different direction. Five states have enacted portable benefits laws, and nine more introduced bills in early 2026. Their safe harbors provide that offering compliant contractor benefits does not, by itself, establish an employment relationship under state law. That protection has a boundary. Participation in Georgia’s or West Virginia’s framework does not shield an operator from federal classification claims.
AB 1340, signed in late 2025, gave approximately 800,000 rideshare and delivery drivers union rights in 2026 while preserving their independent contractor classification under Prop 22. Operators must now account for collective bargaining within a contractor model. These changes across states add, remove and reshape obligations that operators must distinguish.
What Prop 22 settles for California app-based delivery — and what it leaves open for everyone else
Prop 22 supplies a durable but narrow California carve-out. Approved in November 2020, it exempts qualifying app-based transportation and delivery drivers from AB5. Platforms cannot impose a set schedule or minimum hours, require acceptance of requests, restrict other app work during non-engaged time, or restrict other lawful work. Calling a business “app-based” does not satisfy those conditions.
The California Supreme Court unanimously upheld Prop 22 in Castellanos v. State of California on July 25, 2024. The court held that the relevant provision did not conflict with the Legislature’s constitutional power over workers’ compensation because that power does not exclude the electorate’s initiative power. Covered drivers are explicitly outside California workers’ compensation.
The protection covers only qualifying digital-platform rideshare and delivery work in California. An operator that controls scheduling or restricts other platform work contrary to the conditions loses the protection even within California. There is no federal or multi-state safe harbor that offers the same protection. For a national network, Prop 22 is one jurisdiction-specific rule.
The real cost of misclassification when Prop 22 protection does not apply
Outside that protection, misclassification can turn an operating assumption into layered financial exposure. California Labor Code 226.8 provides penalties reaching $10,000 to $25,000 per violation for a pattern or practice of willful misclassification. Back taxes, benefits obligations and civil claims come on top. This is not a filing correction with an inconvenient fee attached.
PAGA exposure can grow with each violation and pay period, so the longer a classification problem lasts, the more it can cost. A small California contractor population does not exempt a national operator from the state’s enforcement regime. Settlements in documented cases of courier misclassification have reached multi-million-dollar sums. For operators without the legal resources of a large company, costs on that scale can cut profits and even threaten the business.
The recurring delivery pattern is straightforward Prong B failure. When delivery is the company’s usual business, its drivers perform that business. More polished contractor paperwork does not change that relationship. The business risk therefore begins with the operating model, while the financial consequences accumulate through the engagements and payments made under it.
Why the insurance stack is both a compliance signal and the first place a misclassification argument is built
Insurance choices can become evidence of how an operator understood the working relationship. Workers’ compensation is built for employees and mandated by state law, while occupational accident insurance is standard for IC-classified delivery platforms. Extending workers’ compensation to contractors can support a misclassification argument, depending on the governing rules. Coverage is not a separate administrative island.
Jurisdiction also changes what that evidence means. Prop 22 requires covered California platforms to provide occupational accident insurance. Washington, by contrast, requires workers’ compensation for rideshare drivers during dispatch platform time or passenger platform time.
Occupational accident insurance covers medical expenses, disability income, and accidental death and dismemberment up to policy limits. It does not provide workers’ compensation’s exclusive-remedy shield, so contractors can still bring claims in some circumstances. Other policies address different exposures, including commercial auto liability, cargo insurance, commercial general liability and non-trucking liability for owner-operators. They are not interchangeable. Commercial auto liability covers damage caused to others in an accident, leaving the cargo being delivered outside that coverage and making an apparently complete insurance file potentially incomplete in practice.
Why quarterly audits cannot continuously monitor independent contractor compliance
A periodic audit establishes what was true when someone looked. It cannot, by itself, detect what changes next. Consider a contractor who is onboarded to work outside California and later adds a California route. The engagement acquires AB5 exposure without any change to the company’s headquarters, and a static onboarding record need not produce an alert. “Not based in California” identifies only the company’s location.
The same timing problem applies to expired licenses, lapsed insurance and new regulatory requirements. Each event can happen between reviews, while high turnover means there are always new engagements to verify. A station running dozens of routes daily does not encounter these events on the auditor’s calendar. Manual review must contend with the pace of the operation as well as the pace of lawmaking.
PAGA’s statute of limitations is one year, but practitioners recommend keeping compliance documentation for four years to cover the longer PAGA, wage-claim and UCL lookback window. An audit can inspect those records, but it cannot recreate verification that was never documented.
What a living compliance posture actually requires in the contractor lifecycle
The operating response is to embed jurisdiction-aware verification throughout the contractor lifecycle. It starts at onboarding, where contractors should be able to submit auto insurance, background check consent and license documentation digitally. TIN verification and KYC checks should run in real time. Speed must not create a verification gap. The goal is to shorten onboarding from weeks to days while establishing the evidence needed for the engagement.
That evidence then needs to stay current. For non-CDL last-mile contractors, a valid state driver’s license, a clean driving record and proof of insurance are engagement requirements. Ongoing credentialing must track renewals and coverage rather than assume that the original documents remain valid. A successful initial check is the beginning of the record.
Real-time monitoring adds the geographic trigger to that ongoing verification. The system should flag an expired license, lapsed insurance certificate or route entering a new jurisdiction before the contractor completes a delivery. A California route addition must prompt assessment of the applicable AB5 obligations and any qualifying protection. In portable benefits safe-harbor states, monitoring must also document compliant benefit contributions if the operator seeks that state-law protection.
The 1099-NEC reporting threshold changes to $2,000 or more for tax years beginning after 2025, with inflation adjustments beginning in calendar year 2027. Payment infrastructure needs the correct threshold at the correct time. RTP and FedNow settle in seconds around the clock, while Same Day ACH operates within business-day windows.
How to build the back-office infrastructure that makes continuous compliance scalable rather than a manual burden
To make that operating model scalable, operators need automated, unified verification, monitoring and payment functions. Separate tools create version drift when a jurisdiction changes its rules and each system requires an update. A unified platform can update the relevant verification logic in one place.
The practical evaluation criteria follow from the lifecycle. The infrastructure needs digital onboarding, ongoing credential and insurance monitoring, jurisdiction-aware route flags, documented benefit contributions and payments configured for current reporting rules. Records must remain stored and retrievable across the appropriate retention period. These capabilities are more useful criteria than an unqualified promise of “real-time compliance.”
Automation also changes the economics of contractor turnover. A station running dozens of routes seven days a week needs repeated onboarding, making verification speed a direct cost lever. Bulk insurance purchasing through a workforce management platform can convert individual purchases into pooled costs as the network grows. Contractors also benefit from fast onboarding, continuous coverage and instant pay access, which can support retention. With driver replacement estimated at $500 to $1,500, reducing avoidable churn has a concrete back-office payoff.
The compliance advantage operators gain by treating jurisdiction-aware monitoring as infrastructure rather than overhead
Continuous monitoring gives operators a reusable way to enter jurisdictions without rebuilding their compliance process each time a rule changes. An operator that can onboard in days, verify credentials in real time and retrieve four years of compliance history has more operational room to expand. Its records travel with the engagement. That is a stronger foundation for growth than a policy approved once and rediscovered during litigation.
Portable benefits offer a concrete example of that advantage. Utah, Alabama, Tennessee, Georgia and West Virginia provide state-law safe harbors for compliant benefits arrangements. Operators that administer and document qualifying contributions can establish the relevant protection before a claim arises. The protection is limited, but usable.
The commercial payoff extends beyond legal defense. A shipper comparing last-mile partners can distinguish an operator with documented, continuous compliance across its work jurisdictions from one relying on periodic checks. Real-time monitoring makes changes visible while they can still be managed as operating events. In a margin-thin business, the ability to demonstrate that control makes the operator a lower-risk partner and gives its compliance infrastructure commercial value.
