A healthcare general counsel told us 1099 professionals can't get workers' comp. They can.
Every state lets an independent contractor carry WC in their own name. The misconception is what exposes your platform, not the law.
Every professional binds workers' comp in their own name before accepting a shift, with a COI issued before they step onto the floor. They stay 1099, and the uninsured-labor gap never lands on your audit.
Per-diem nursing, lab, and allied-health staffing have outpaced the paperwork. Five places clinical compliance leaks out.
Every state lets an independent contractor carry WC in their own name. The misconception is what exposes your platform, not the law.
EOR conversion is the most expensive way to solve a problem you don't have to create.
Coverage routes to the work state of each shift, not your HQ, so every shift is covered where the work actually happens.
Per-shift activation finishes before the contractor signs their first chart.
Coverage in the contractor's name supports facility audits and strengthens the case that each professional is independent.
What actually happens when a shift gets assigned to a 1099 healthcare professional, and where the credentialing-COI handoff finally lands clean.
The Assignments API takes the assignment as input, returns a rate against $100 earned, and binds the policy when they opt in. No broker call, no policy origination delay.
Each professional's coverage prices per shift in their own name: pay-as-you-go on $100 earned, no annual minimum. Collect it through your platform or let them remit directly. Either way, these contractors stay off your WC payroll.
The fractional insurance policy issues in the contractor's name, the structure your general counsel didn't realize was possible. It removes the misclassification trigger most plaintiffs reach for after an uninsured-injury claim.
Each shift binds in the state where the work happens, with that state's WC class code. One missed state line stops being one missed reclassification claim.
We're onboarding a lot of contractors for in-home care, and what we needed was workers' comp for the people driving out to seniors' homes. It's going to save us a lot of time and energy, and a lot of money.
Multi-state routing by work state, per-shift coverage windows, and the credentialing-WC parallel timeline, answered straight.
Often, yes. Facilities and staffing platforms frequently require active workers' compensation before an allied-health professional, therapist, tech, or home-health contractor can take a shift.
Not when the policy is issued to the contractor as the named insured. 1099Policy can add the staffing company, facility, or network as additional insured while keeping the underlying coverage with the contractor.
The contractor's policy is designed to respond first for covered medical costs, wage replacement, and related benefits. The facility or staffing platform stays attached to the certificate record for audit and contract purposes.
Yes, when the engagement is routed correctly. 1099Policy supports coverage by assignment, shift, or longer policy window, and stores the certificate trail by work state and facility requirement.
1099Policy handles the coverage piece, issuing and storing proof of insurance, and it slots alongside your existing license, background-check, immunization, and facility-packet workflows. We don't verify clinical credentials or licenses ourselves. Coverage just becomes one more item the staffing desk can confirm and file before the assignment starts.
The independent allied-health professional or contractor is the named insured. Their name or business entity appears on the COI, while the staffing company, facility, or health network can be added where required.
Issue workers' comp in the professional's name, route it per-shift, and pull a COI the same day. Stay 1099, stay compliant.