← Back

Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice

← All guides

ADMT for Staffing Agencies and Independent Contractors: Who Is the Deployer When Work Is Allocated?

The short answer: California's significant-decision list is the only one in the kit's data that names the arrangement expressly: employment or independent contracting opportunities or compensation. A platform or agency that uses a tool to allocate work, rank contractors, or set compensation is making significant decisions about those contractors — and the ADMT duties (risk assessment, pre-use notice, opt-out where given, access answers) follow from January 1, 2027. Staffing adds a structural question the other sectors do not have in the same form: when an agency's tool screens a worker for a client's site, who is the deployer? The answer follows the decision, not the org chart — and this guide works through the common shapes.

Check your duties and dates — free Build your first notice — free

What is a staffing decision here? Any decision about a worker's access to work — screening, ranking, assignment, scheduling into a role, continued eligibility, or compensation — where an automated tool replaces or substantially replaces the human decision-making (California's test), materially influences it (Colorado), or is a substantial factor (Connecticut's employment frame). The kit's employment type in Colorado also expressly reaches hiring for roles the worker will perform at another business's site.

Shape one: the platform allocates directly

Where a platform's own tool ranks contractors and allocates opportunities — the dispatch, the shortlist, the offer order — the platform is the decision-maker in substance: its tool, its decision, its duties. The contractor-facing artefacts carry the platform's name: its pre-use notice before the tool evaluates the contractor, its opt-out routes, its access answers explaining the logic, outcome, and purpose of an allocation decision.

Compensation tools belong in the same analysis. A tool that sets or adjusts contractor pay rates is deciding an element the California list names expressly — compensation — and 'the algorithm sets the rate card' is a description of an automated decision, not an exemption from one. Rate-setting and allocation tools both belong in the inventory with their weights assessed honestly.

Shape two: the agency screens for the client's site

The classic staffing triangle: the agency screens, the client hosts the work, the worker is employed or engaged by one of them. The deployer question is answered per decision: whose tool screened this worker for this opportunity, and whose process decided? Where the agency's tool does the screening and ranking, the agency carries the deployer duties for that decision — its notice, its explanation, its review queue — even though the work happens at the client's premises.

Where the client also runs tools (a client's own assessment at the site gate, the client's scheduling system), those are the client's decisions with the client's duties. One worker's journey can therefore legitimately carry two deployers' notices at two points — which is correct, because two different tools made two different decisions. The error to avoid is each party assuming the other's notice covers its own step.

Worked example: TrueNorth Staffing Group

Example — fictional business, real duty structure. TrueNorth is a fictional staffing group placing workers with California and Colorado clients. It mapped its workflows per decision, and the map drove the build:

Shape three: the client's tool, the agency's workforce

The mirror case: the client deploys a tool over the agency's supplied workers — performance scoring, re-assignment, eligibility for further placements. The client is the deployer of that tool; the duties for its decisions are the client's. But the agency has a practical exposure the contract should address: its workers will ask the agency what happened, and the agency needs the cooperation clauses (documentation, data access, notice of material updates) to answer them and to manage the relationship.

Agencies should therefore run the vendor-deployer analysis in both directions: as deployers of their own tools, and as affected parties in their clients' deployments, with the four contract clauses from Vendor vs Deployer adapted into client agreements. The finding per client — whose tool, whose decision, whose notices — belongs in the register next to the tool entry.

Colorado and Connecticut for staffing, briefly

Colorado's employment type covers hiring, promotion, termination, and scheduling without an independent-contracting carve-out in the kit's data — agency hiring into Colorado roles should be planned under the five duties, with the same per-decision deployer analysis. Connecticut's employment track concerns applicants and employees under its AEDT frame, with its notice pair for tools deployed on or after October 1, 2027 and the no-defence rule already live.

The California analysis remains the most developed for contractor models, because its list names the category. A multi-state agency should map each client workflow once — tool, decision, deployer, states — and let the map drive three states' artefacts from the one record, as the kit's single-chain design supports. The general employment guide is at ADMT Notices for Hiring and Employment Decisions.

Records across the triangle

Staffing records fail at the seams: the agency holds the screening record, the client holds the assignment outcome, and the worker's question joins them. Whichever party owes the duty for a decision must hold that decision's complete file — notice, reasons, data summary, outcome, and follow-ups — and the inter-party agreements should make the data flows match the duty allocation, so the responsible party is never reconstructing from the other party's systems under a clock.

Build the map before the volume: for each client workflow, one line in the register — tool, decision, deployer, states, record location, review owner. Run each line through the free checker under the deployer's facts. When a worker asks, the line tells you whose file answers, whose contacts respond, and whose 30 days (in Colorado) is running.

  1. Map every staffing workflow per decision: whose tool, whose decision, who is deployer — including dual-tool journeys
  2. Include allocation and rate-setting tools in the inventory; compensation is a named significant decision in California
  3. Issue the deployer's own notices for the deployer's own decisions; never assume the other party's notice covers your step
  4. Put documentation, update-notice, and data-access clauses into client agreements wherever the other party's tool touches your workers
  5. Hold each decision's complete file with the party that owes its duty, and run each register line through the free checker

Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.

Build your first notice — free

Related guides

See all ADMT guides for the full set.

Frequently asked questions

Are independent contractors covered by California's ADMT rules?

Yes. The significant-decision list expressly includes employment or independent contracting opportunities or compensation.

We are an agency — the client makes the final call. Who owes the notice?

Follow the decision: if your tool screened and ranked the worker for the opportunity, that screening decision carries your deployer duties, even if the client decides placement afterwards. Where the client's own tool also decides, the client owes the duties for its step.

Does a pay-rate algorithm count?

Compensation is named in California's list. A tool that sets or adjusts contractor compensation is making a significant decision in the kit's data, and belongs in the assessment and notice programme.

What about Colorado staffing?

Colorado's employment type covers hiring, promotion, termination, and scheduling. Agency hiring into Colorado roles should be planned under the five duties with the same per-decision deployer analysis.

How should staffing records be organised?

Per decision, with the duty-owing party: the complete file (notice, reasons, data summary, outcome, follow-ups) held by the deployer of that decision, with client agreements making the data flows match the duty allocation.

Build your first notice — free