Contractor Onboarding Compliance

No 1099 reaches their first job uninsured.

Most contractor onboarding collects insurance after the work starts: a COI someone remembers to chase, or doesn't. 1099Policy makes coverage and proof part of onboarding. You set the requirement, verify what contractors bring, enroll the ones who can't, and gate the first assignment on a compliant status.

See how it works →Book a walkthrough
Set requirementsVerify or enrollGate the first jobKeep the proof
The problem

Where contractor onboarding compliance leaks.

Onboarding a 1099 isn't done when the paperwork is signed. It's done when they're insured, documented, and cleared to work. Three gaps open up between those two moments.

Work starts before coverage does

The contractor takes their first assignment while the COI is still "on its way." If something happens in that window, the exposure is yours.

"Send a COI" only works sometimes

Established contractors send a certificate. One-person crews often have nothing to send — and onboarding stalls on a document that may never arrive.

Proof scatters across systems

Certificates land in inboxes and drives. When a client or insurer asks who was covered on day one, there's no single record to point to.

What makes this different

Verify the ones who can. Enroll the ones who can't.

A checklist or a COI-request email only handles contractors who already carry insurance. 1099Policy handles both halves of your roster in one onboarding step. Contractors who bring a certificate are verified through COI Review. Contractors who have nothing enroll in coverage in their own name through Fractional Insurance, in under a minute.

Either path ends the same way (a compliant status and a certificate on file), so onboarding never dead-ends on a contractor who can't produce a COI.

01 // Incoming Certificate Review
Certificate parsed & validated
[ PARSED // OCR ]
Checked against your requirements
[ RULESET // MATCH ]
Cleared without enrolling
[ STATUS // CLEARED ]
Verified or enrolled, automatically.
1099Policy reads every contractor and routes them to the right path. No manual triage.
Enforcement

Gate the first assignment on compliant status.

Compliance is only real if it's enforced. Coverage status is exposed through the API, and a webhook fires the moment a contractor is cleared, so your onboarding flow can hold the first assignment until a policy reads active. No one starts work uninsured because they slipped past a manual step.

Read the API reference
A note on classification

In-name coverage reads as an independent business.

A contractor who carries insurance in their own name and entity looks like what they are: an independent business, not an employee. It's one supporting signal in a worker-classification analysis under tests like the ABC test, alongside the contract, the degree of control, and the economics of the relationship.

We surface the signal and keep the documentation. The classification call itself is one for you and your counsel to make. Either way, "separately insured, with proof on file from day one" is a much stronger position than "we never collected anything."

Policy matches registered entity name
SECURE_LEDGER // ATTACHED_ID: 1099_AOR_2026
[ ENTITY // MATCH ]
In practice

Onboarding compliance for a staffing marketplace.

The challenge. A field-services marketplace onboarded contractors fast to fill shifts, but insurance was a back-office email chase. Some contractors worked their first shift before any COI existed, and a quarter of applicants had no coverage to send at all, stalling their activation.

The solution. Enrollment moved into the signup flow. Contractors with coverage upload a certificate that's verified automatically; contractors without it enroll in their own name in under a minute. The marketplace gates the first shift on a compliant status returned by the API.

The result. Activation got faster, not slower (no one waits on a back-office chase), and zero contractors reach a shift uninsured.

M. Alvarez: Premium Shift Request[ SHIFT // ALLOWED ]
S. Park: No COI on file[ GATE // BLOCKED ]
Trusted by

The teams that staff, dispatch, and pay contractors.

Wieden+Kennedy
BBDO
DDB
Golin Ketchum
Octagon
CreatorIQ
FAQ

Onboarding compliance questions.

At minimum: confirm the contractor is set up as an independent business, decide which coverages you require, verify or provide that coverage, and keep the proof on file before they start work. The hard part isn't the steps - it's enforcing them every time, at scale, without someone manually chasing each new hire.

Requiring a COI only works for contractors who already have coverage and will send it. Onboarding compliance here covers both cases: contractors who bring a certificate are verified through COI Review, and contractors who don't enroll in their own name on the spot - so onboarding never stalls on someone who can't produce one.

Yes. Coverage status is exposed through the API and a webhook fires when a contractor is cleared, so your onboarding flow can gate the first assignment on a compliant status. A contractor can't quietly start work uninsured.

Collect their certificate during onboarding and verify it through COI Review - it parses the ACORD certificate, checks limits and dates against your requirements, and flags gaps. Contractors with valid coverage clear the bar without enrolling; the rest enroll for the missing line.

Coverage is issued in the contractor's own name and entity, which is consistent with treating them as an independent business. It's one supporting factor - classification depends on the full relationship and the applicable test, such as the ABC test. 1099Policy isn't a law firm and this isn't legal advice.

Workers' compensation, general liability, professional liability (E&O), media liability, and cyber - individually or combined, sized per engagement. You define the requirement once and every contractor must meet it before their first assignment.

Make insurance a step in onboarding, not a chase after it.

See how requirements, verification, on-the-spot enrollment, and an API gate keep every 1099 compliant before the first assignment.