Per-dispatch coverage for 1099 field-service techs. From assignment to active policy in 45 seconds.

WC and GL issued in the contractor's name and embedded in your dispatch flow, so you keep your techs 1099 and skip the broker calls. No monthly retainer, no per-tech minimum, no payroll markup.

See it live → EOR vs 1099 calculator

The dispatch coverage gap

Techs roll on jobs without coverage. Customers are noticing.

Same-day dispatch outruns same-week broker paperwork. The friction points your dispatcher already knows by name.

Worst-case math

Uninsured worker. Both legs amputated. A $2.4M tort settlement.

P.I. & I. Motor Express paid $2.4M after not carrying WC for an injured worker. Coverage in the tech's name would have blocked the lawsuit. That's the gap per-dispatch WC closes.

Per-dispatch billing

Annual WC is the wrong fit for a workforce that bills per ticket.

You bill per dispatch, and coverage should too. It turns on when the ticket opens, and you're billed on the jobs you actually run, not estimates.

Multi-state reality

Techs cross 3 states a week. WC class codes don't.

Coverage auto-routes by jurisdiction, so PA, NY, and NJ each settle into the right class without dispatcher math.

COI sprawl

Property managers expect a fresh COI per service window.

Auto-issue, auto-store, auto-renew, so your dispatcher stops chasing broker certificates.

Repeat-work advantage

Insured techs accept faster. Faster techs win repeat business.

Coverage gets your techs the job, and reliable, same-day starts are what keep the customer coming back.

We work with 1099 contractors and we'd been pushing them to carry insurance, but early on they resist, and if they're only doing part-time work they don't need a full annual policy. Coverage per job, through an API, is exactly the structure that works.

Built for the dispatcher's screen

Four capabilities, built for the dispatch workflow.

What happens between the customer accepting the quote and the tech tapping 'on-site': coverage threaded through the Assignments API.

POST /v1/assignments

{
  "contractor": "cn_DKM2Rd9Qa",
  "job": "jb_fieldElec",
  "work_state": "NJ"
}

1. Bind WC and customer-property GL the moment a tech accepts the work order.

Your dispatch system hits the Assignments API. We return a quote priced by class code and jurisdiction. The tech opts in once; subsequent assignments re-bind automatically within the policy window.

Per-dispatch premiumActive

• Policy ID: po_HVz3q4n
• Dispatches: 3
• Earned per job: $420.00
• Rate per $100: $1.85
• Premium due: $23.31

2. Premium meters per dispatch, audited on actuals, not estimates.

Annual policies always end in a true-up. Ours doesn't. Premium is recorded per assignment, reconciled in real time, and shown in the dispatcher's portal at any time.

General liability

• Additional insured
• Insured: Marcus Lane
• Each occurrence: $1,000,000
• Damage to premises: $100,000
• General aggregate: $2,000,000

3. Coverage in the tech's name. Customer named on the COI before the truck arrives.

GL in the tech's name with the customer-of-record automatically listed as additional insured for the dispatch window. The certificate the property manager actually accepts.

Active dispatches by state

• PA, 87 dispatches this week (most active)
• PA · 9405
• 31.5%
• NJ · 9410
• 25.7%
• IN · 9410
• 19.8%

4. Multi-state class code routing applied automatically.

Tech in New Jersey bills 9410. Same tech crosses to Pennsylvania next morning, bills 9405. Routing happens at assignment, so the dispatcher doesn't think about it, and the audit doesn't either.

Frequently Asked Questions

• Do field-service techs need workers' comp if they're 1099 contractors?
  Often, yes. Property managers, national accounts, and enterprise customers increasingly require proof that every tech arriving on site has active workers' comp in the contractor's name.

• Can coverage bind per dispatch instead of as an annual policy?
  Yes. 1099Policy can activate coverage around the job window, route it to the right state and class code, and record premium against the actual dispatch.

• What happens when a tech crosses state lines?
  The assignment should be rated by where the work happens. We route coverage by jurisdiction at dispatch time so each job lands in the right state, class code, and certificate record.

• Can the customer or property manager be added to the COI?
  Yes. The tech remains the named insured, and the customer-of-record, property manager, or enterprise client can be added where the contract requires it.

• How does this fit into a dispatch workflow or API?
  Your dispatch system can send the job details, work state, class, contractor, and customer requirements before the assignment is released. 1099Policy returns the coverage status and certificate record.

• Who is the named insured on the policy?
  The independent field-service contractor or tech is the named insured. The coverage follows the work without converting the tech to W-2.

Bind coverage the moment a tech accepts the job.

Embed WC and GL in your dispatch API. No monthly retainer, no broker delay, no per-tech minimum.

Get Started Book a Demo