A botched migration takes down the client's storefront — and names the consultant.
E&O and Cyber in the consultant's name keep the firm out of the lawsuit.
Errors and omissions, cyber, and workers' comp sized to the contract. Client-ready COIs on day one of the SOW.
The SOW says insured. The broker quote takes three weeks. Five places that gap costs you margin.
E&O and Cyber in the consultant's name keep the firm out of the lawsuit.
Per-engagement coverage clears vendor review without the payroll markup.
Carrying coverage in the consultant's own name is one mark of an independently established business — supporting evidence for IC status, not proof of it.
E&O, Cyber, and WC issued in the consultant's name — your client added, limits above the MSA minimum — on day one.
A pre-cleared bench wins the next MSA faster.
What enterprise vendor management asks for — Professional Liability, Cyber, and WC sized to the engagement, itemized for the audit, defensible against AB5.
The Assignments API takes the engagement as input — contractor, job, and the enterprise client entity — returns a rate sized to the contract value, and binds coverage when the consultant opts in. Procurement gets a COI before kickoff.
Every engagement separates Professional Liability, Cyber, and WC, sized to the contract value. Even a solo consultant on a $50K MSA arrives with the line items procurement asks for — so your consultants clear vendor review without the back-and-forth.
Professional Liability, Cyber, and WC issue in the consultant's name with the enterprise client listed as additional insured per engagement. The COI procurement actually accepts on day one.
MSA-grade compliance checks run automatically: coverage in consultant's name, enterprise additional insured, Professional Liability and Cyber above minimum, AB5-defensible IC posture. The COI procurement actually approves.
All my technicians are 1099. The moment they join the platform I want to give them an insurance option — it has to be there before they take a job. Embedded, or let them upload their own, is exactly what I was looking for.
Per-engagement E&O sizing, cyber liability for client PII, and how our IC posture holds up to AB5 and 1099-K scrutiny.
Increasingly, yes. State labor regulators in CA, NY, NJ, and MA require WC coverage for any worker performing labor on an engagement — even when classified as 1099. The NY Fashion Workers Act (Q3 2026) makes this explicit for stylists, photographers, makeup artists, and production crews. Without WC in the creator's name, the brand engaging them becomes the de facto employer for liability purposes.
Not when the policy is in the contractor's name. 1099Policy issues coverage to the creator as the named insured — the brand or agency is added as a blanket additional insured. That's the legal opposite of an EOR arrangement, where the employer-of-record assumes the W-2 relationship. Courts, the IRS, and state regulators treat "coverage in the contractor's name" as a key indicia of independence.
The creator's policy responds first. WC covers medical, lost-wage indemnity, and rehab — paid directly to the creator at no cost to them. The brand's separate GL and additional-insured status protect against secondary liability. Without coverage in the contractor's name, the brand typically becomes responsible for medical bills and faces misclassification audit risk.
Yes. Per-gig, per-day, and annual options are all available. A creator who opts in once is automatically covered for every engagement that flows through 1099Policy — across multiple brands and agencies — using the same underlying policy. The blanket additional-insured structure lets each new brand engagement attach without re-underwriting.
Effective Q3 2026, any agency engaging models, stylists, makeup artists, photographers, or production crew must document workers' comp coverage at the start of each engagement. Coverage must be active during the engagement and verifiable on demand. 1099Policy's API delivers compliant COIs in seconds and stores audit-ready records by default.
The creator — always. Their name is on the COI, the carrier holds the policy in their entity, and claims pay out to them. The brand or agency is added as additional insured so they're protected against third-party claims arising from the engagement. The underlying policy never makes the brand the employer-of-record, which is what preserves 1099 status.
Insurance sized to the contract value, not a 12-month policy. Client-ready COIs available via API on day one.
