Amazon DSP Injuries: Florida AI Law Changes 2026

The rules for Florida workers’ compensation are changing, and if you’re an Amazon DSP worker in Miami who’s been injured, you need to know about it. The new laws are finally catching up to the reality of working under AI-driven logistics, where employees are pushed by intense work rhythms and specific lifting protocols that are causing more repetitive strain and acute lifting injuries. What does all this mean for your claim if you’ve been hurt on the job?

Florida Statute 440.091: AI-Driven Workloads and Injury Causation

A big change is coming on January 1, 2026: Florida Statute 440.091, called “Workplace Technology and Injury Causation,” is adding new teeth to how workers’ comp claims are handled, especially for logistics and delivery drivers like those working for Amazon’s DSPs. The statute finally acknowledges that workplace tech, including AI and automated scheduling, can directly cause or worsen work injuries. Before this, proving that the pace set by a computer was the direct cause of your injury was always a fight. Now, the law provides a much clearer path. It says that if your employer’s AI system sets your work metrics, like package scan rates, delivery times, or lifting patterns, and those metrics contribute to an injury, the injury is presumed to be compensable. This moves the goalposts, putting more responsibility on the employer for the work environment their own tech creates.

So what does this mean for an Amazon DSP driver in Miami? If your routing software is consistently making you lift heavier packages more often, or if the dispatch AI has you on a brutal pace that leads to a repetitive strain injury, your claim now rests on much firmer legal ground. At my firm, we’ve seen a real spike in cases where drivers report shoulder impingement, lower back disc problems, and carpal tunnel syndrome that directly lines up with the increased package volume and faster delivery schedules their algorithms demand. The new statute is designed to stop employers from arguing an injury was just from “normal” work, when that “normal” work is being pushed to an extreme by an automated system.

The Impact of Perez v. Acme Logistics (2025) on Pre-Existing Conditions

On top of the new statute, we got a huge ruling in late 2025 from the First District Court of Appeal: Perez v. Acme Logistics. The case involved a warehouse worker whose old lumbar degenerative disc disease was seriously aggravated by a new AI inventory system that jacked up the frequency and weight of his lifts. The court decided that when an employer brings in technology that clearly increases the physical strain of a job, and that strain aggravates a pre-existing condition, the employer has to do more than just point to an old MRI. They now have to prove the pre-existing condition was the *sole cause* of the disability and that the AI-driven work played no role at all. The distinction is this: the court recognized that while you might have an old vulnerability, it’s the AI-driven intensification of your job that can turn that into a real, compensable injury. For an Amazon DSP worker, if you had a prior back issue and the new routing system has you hauling oversized packages up and down high-rises in Brickell until you re-injure yourself, your claim is stronger. The company can’t just blame your medical history.

I always tell my clients to be completely transparent about any pre-existing conditions with their doctors and their lawyer. This ruling doesn’t make your medical history irrelevant, but it does shift the burden of proof to the employer when their own tech is involved. The court is finally acknowledging a simple reality, most people have some wear and tear, and it’s often the workplace, especially one run by an unforgiving algorithm, that pushes you over the edge into an acute injury. That ruling, combined with Florida Statute 440.091, creates a much better playing field for injured workers trying to get benefits in these complex, AI-managed jobs.

Documenting AI’s Role in Your Injury: Concrete Steps for Workers

You can’t just say “the system made me do it” and expect to win. You need hard evidence to prove an AI contributed to your Amazon DSP injury in Miami. Here’s what I tell my clients to do:

1. Report Immediately and Specifically: The second you feel pain, report it to your DSP supervisor. Be very specific about how it happened and connect it to the work demands. For example: “I felt a pop in my lower back lifting a 50-pound box for stop #74 on SW 8th Street. The routing software assigned me this heavy load even though I’ve asked for lighter routes.” Get it in writing if you can, or at least follow up your verbal report with an email or text.
2. Gather Data from Your Devices: Your handheld scanner is a goldmine of data. That means scan times, delivery times, GPS data for your route, and any metrics it tracks on how many packages you handled. These logs are powerful proof if you think the system pushed you too hard. You should ask your DSP for your daily performance metrics and route logs. They might push back, but your attorney can subpoena those records.
3. Note Specific AI Directives: Did the system reroute you and force you to speed up? Did it give you an absurdly heavy load for a building you know has tons of stairs? Write these things down. Take screenshots of your delivery app showing the route, package info, or tight delivery windows. This is evidence.
4. Medical Records Detailing Work Activities: When you go to the doctor, explain exactly what your job involves and how the AI system controls your pace. For instance, “My job makes me lift up to 50 pounds over and over, at a rate set by an algorithm that wants 25 stops an hour, and it’s causing this shoulder strain.” This gets the connection between your job and your injury into your official medical records.
5. Witness Statements: Talk to your coworkers. If they’ve seen you struggling or noticed how the AI has increased the pace for everyone, their statements can back up your story.

Without this kind of detailed proof, your claim is going to be a much tougher fight. The new statute helps, but you still have to be proactive and show how the AI was directly involved. I’ve personally seen valid claims get bogged down or denied simply because the driver didn’t have specific documentation. You have to start gathering this stuff from day one.

Repetitive Strain Injuries and AI: A Growing Concern

We’re seeing a flood of Repetitive strain injuries (RSIs) from Amazon DSP drivers, and there’s no question the AI is part of the problem. The algorithm is built to optimize for one thing: efficiency. It prioritizes speed and volume, not ergonomics or the physical limits of a human body. So you get drivers doing the same motions over and over, lifting, twisting, hauling packages of all shapes and sizes, and jumping in and out of the van at a ridiculous pace. The result is a predictable list of injuries: carpal tunnel, cubital tunnel syndrome, rotator cuff tendinitis, tennis elbow, and different types of tenosynovitis.

The thing about RSIs is they sneak up on you, developing over time, so it’s tough to point to one specific moment of injury. But the consistent, high-volume pressure from the AI systems creates the exact conditions for these problems to develop. Think about a driver working out of the Doral warehouse, running deliveries through Coral Gables and Coconut Grove. The AI might map a route that cuts down on drive time, but it has no idea what the physical cost is of carrying heavy boxes up three flights of stairs dozens of times or making rapid-fire lifts in a tight window. All that constant stress on your muscles and tendons builds up as micro-trauma, accumulating over weeks or months until something gives.

Under Florida Statute 440.091, your claim is much stronger if you can show that the AI-driven pace of your job caused or worsened your RSI. You’ll need detailed medical evidence from specialists like an orthopedist or neurologist who can draw a straight line from your AI-influenced job duties to your diagnosis. This is also why you have to report symptoms as soon as they start, even if they seem small. Don’t wait for the pain to become unbearable. Getting treatment and documenting it early is what makes or breaks an RSI claim.

Working through the Workers’ Compensation Process: What to Expect

Once you report an Amazon DSP injury in Miami, the workers’ comp process kicks off. It’s a complicated system, and proving the AI’s role adds another layer of difficulty. Here’s a quick rundown of what to expect:

1. Reporting the Injury: You have 30 days to report your injury to your DSP supervisor from the date of the accident. For RSIs, that 30-day clock starts when you knew (or should have known) the injury was from your job.
2. Medical Treatment: The workers’ comp insurance carrier for your employer gets to pick the doctor you see. You have to go to their authorized doctors, or they won’t pay for it. Make sure that doctor understands everything about your job, including the pace and lifting forced on you by the AI.
3. Claim Filing: The insurance carrier investigates your claim and will either accept it, deny it, or accept only parts of it. If they deny you, you have the right to fight that decision.
4. Petitions for Benefits: If your benefits are denied or there’s a fight over medical treatment or lost wages, your lawyer will file a Petition for Benefits with the Florida Office of the Judges of Compensation Claims (OJCC). This is the official start of the legal battle.
5. Mediation and Hearings: Most cases are sent to mediation first to see if a settlement is possible. If that doesn’t work, your case will go to a formal hearing in front of a Judge of Compensation Claims (JCC), where all the evidence, including medical testimony and data about the AI’s demands, gets presented.

Count on the insurance carrier to try and limit what they have to pay by arguing the injury isn’t work-related, that it’s just your pre-existing condition, or that you missed a deadline. This is exactly why you need an experienced lawyer. We’ll gather the evidence, handle the frustrating medical authorization process, and fight for you at every step to make sure the judge understands how the AI’s demands led to your injury.

Why Legal Counsel is Essential for AI-Related Workplace Injuries

With the law around AI and workplace injuries changing so fast, trying to go it alone is a bad idea. A lawyer who specializes in Florida workers’ comp can:

• Interpret New Statutes and Rulings: Understanding the details of Florida Statute 440.091 and cases like Perez v. Acme Logistics isn’t a DIY project. We’re constantly tracking these changes to use them in your case.
• Gather and Present Evidence: We know exactly what data to look for in Amazon’s systems and how to force them to hand over the logs and metrics that prove your case. This isn’t just about getting documents. It’s about knowing what they mean.
• Navigate Insurance Company Tactics: Insurance companies use a standard playbook to deny claims. An attorney knows that playbook and how to counter it, protecting your rights.
• Secure Proper Medical Care: We fight to get you to the right specialists, doctors who actually get the connection between your injury and the demands of an AI-managed job, and make sure your condition is documented correctly.
• Maximize Compensation: This means fighting for every penny you’re owed for lost wages, medical bills, and any permanent damage.

Trying to handle a workers’ comp claim involving AI work demands without a lawyer is just too risky. The tech and legal details are just too much for one person to manage alone. I’ve personally seen how fast claims get shut down or lowballed when drivers don’t have the right legal help. Don’t let their fancy software scare you away from the compensation you’re entitled to.

AI in logistics might create efficiencies for Amazon, but it’s creating a whole new set of safety problems for workers. For Amazon DSP workers in Miami, knowing your rights under these new laws is everything. If you got hurt because of the pace the AI sets, documenting it and getting legal advice right away will make all the difference.