Contingent workforce
The path from what a machine is documented doing to the party holding the record that makes the result official, with how well each step is backed. Where the sources settled nothing, the step says so.
-
What a machine is documented doing
Established by the evidence. Agents drafting SOW content - BOTH decisive cases unresolved after PR-03 -
The record it touches
Established by the evidence. Work order; statement of work; rate card; timesheet approval state; engagement status; employment-status determination -
What still has to happen first
Established by the evidence. STRUCTURAL - Pending Approval status and mandatory supplier acceptanceBoth readings still open the cases were left open rather than closed, and neither reading is settled unresolved-across-binding-boundary; 13 of 14 required cells returned not-established
Work order created in Pending Approval status; the supplier must accept
the source's own words, quoted exactly -
What makes the change count
Established by the evidence. Buyer configuration inside vendor product limits; HMRC for the statutory object -
Who holds the official record
Established by the evidence. SAP Fieldglass and Workday VNDLY hold the engagement objects; HMRC holds the CEST determination -
What the area relies on
Established by the evidence. SAP Fieldglass — contingent workforce work order, worker record and time sheet; Off-payroll working (IR35) regime and the Check Employment Status for Tax (CEST) service; Deel Contractor-of-Record engaging-entity system
The action that makes it official Supplier acceptance of the work order Done by The supplying counterparty. It counts because of a counterparty's acceptance. No machine is documented doing this.
What could this area not settle?
What this area recorded against its own findings, in its own words.
Recorded against itself by this area
4 of 12 events institutional; all four units missing from the cutoff register are unresolved because platform artifacts carry no page-visible date; PR-03 closed 13 of 14 cells at not-established
Can the act be undone, and by whom?
What did the evidence settle, dimension by dimension?
Eighteen structural dimensions, each carrying its own evidence state and what it does not establish.
| Question asked | What the evidence says | What it does not tell you |
|---|---|---|
consequential-objectD01 | Established by the evidence. Work order; statement of work; rate card; timesheet approval state; engagement status; employment-status determination | Not recorded by the method used for this area |
object-holderD02 | Established by the evidence. SAP Fieldglass and Workday VNDLY hold the engagement objects; HMRC holds the CEST determination | Not recorded by the method used for this area |
grammar-or-form-setterD03 | Established by the evidence. Buyer configuration inside vendor product limits; HMRC for the statutory object | Not recorded by the method used for this area |
composerD04 | Established by the evidence. The buyer user creates the work order; the client produces the SDS; agents draft SOW content (unresolved) | Not recorded by the method used for this area |
validatorD05 | Established by the evidence. Work order created in Pending Approval status; the supplier must accept; HMRC stands by the CEST result | Not recorded by the method used for this area |
binderD06 | Established by the evidence. Supplier acceptance of the work order; statutory effect for the UK objects | Not recorded by the method used for this area |
deterministic-automationD07 | Established by the evidence. Work orders are created into Pending Approval status by the platform; the status itself is product behaviour | Creation into a pending status is not the binding act; supplier acceptance is. |
agentic-capabilityD08 | Established by the evidence. Agents drafting SOW content, BOTH decisive cases unresolved after PR-03; and the GLA agent autonomously revising cost-centre start and end dates on a worker record | C-008 is the corpus's clearest evidenced autonomous mutation of a live record and is EXCLUDED ON OBJECT, not on mode. |
furthest-deterministic-actionD09 | Established by the evidence. Creation of the work order into Pending Approval status | Not recorded by the method used for this area |
furthest-agentic-actionD10 | Established by the evidence. Drafting statement-of-work content - BOTH decisive cases unresolved | NEITHER described nor unevidenced: 13 of 14 required cells returned not-established in PR-03. |
reversibilityD11 | Established by the evidence. PARTIAL: work orders and revisions can be withdrawn before a supplier takes action | Found without being sought. Reversibility was not coded as a field in this area. |
externality-radiusD12 | Established by the evidence. The employment-status determination has statutory reach: HMRC stands by the CEST result | Established for the statutory object only, not for the engagement objects. |
counterparty-assentD13 | Established by the evidence. Required: the supplier must accept the work order | Not recorded by the method used for this area |
rule-codifiabilityD14 | A source states this does not happen: A source addressed it and said no.. The binding act is a counterparty's acceptance, which the platform cannot evaluate | Not recorded by the method used for this area |
institutional-closureD15 | Established by the evidence. HMRC for the statutory object; the supplying counterparty for the engagement objects | Not recorded by the method used for this area |
authoritative-state-centralizationD16 | Established by the evidence. SPLIT: vendor platforms hold the engagement objects; HMRC holds the statutory determination | Not recorded by the method used for this area |
consequence-of-errorD17 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. What follows an erroneous work order, SOW or status determination is not established We looked and the sources we inspected did not settle it. | Partial reversibility is established; consequence of error is not. |
accountabilityD18 | Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. No stable answerable party evidenced; PR-03 closed 13 of 14 cells at not-established We looked and the sources we inspected did not settle it. | Not recorded by the method used for this area |
What is each capability evidenced doing?
The mode records that a named subject performs an operation. It does not record what kind of performer that subject is, and several rows disclaim an agentic mechanism in their own limitation.
| Capability | How far it goes | What it does | Human work still needed | What this does not tell you |
|---|---|---|---|---|
Bullhorn Amplify Digital Workers — Present, Match and Screen skillsC-001 | prepares the work, stops before it counts | A submission packet, and an automatic mutation of a submission status field: "Submission screening status fields now automatically update to 'Invited' when candidates receive screening engagements through Bullhorn Automation's Send Engagement step." | Not stated in the retrieved artifacts. No passage establishes who accepts, rejects or converts the submission into an engagement. | Establishes autonomous machine action on submissions. Does NOT establish action on any object the contract ruled consequential at the entitlement grade, and does NOT establish that any right-to-represent or candidate-ownership state is recorded. Autonomy was not the test. |
Workday Illuminate — Contingent Sourcing AgentC-002 | prepares the work, stops before it counts | Identified candidates and streamlined screening. No output object named. | Not stated. | Establishes an announced agent acting on sourcing and screening. Does NOT establish action on any consequential object, and the artifact itself places availability after the announcement: "will be available to early adopters by the end of 2025, with general availability planned for early 2026." |
Workday Illuminate — Document Intelligence for Contingent Labor AgentC-003 | the sources do not settle whether it acts or only prepares | "Accelerates SOW creation, tracks obligations, and promotes alignment across contracts to help drive savings and mitigate risk." | Not stated. The artifact does not say whether a person authors, edits or approves the SOW the agent accelerates. | Establishes an announced agent placed on a consequential object. Does NOT establish that it changes that object's state, and does NOT establish availability at the cutoff — the artifact states "New Illuminate agents will be available in 2026." |
SAP Fieldglass Services Procurement — AI deliverables generationC-004 | the sources do not settle whether it acts or only prepares | "Procurement specialists can accelerate the development of their statements of work using the deliverables feature in SAP Fieldglass Services Procurement." The feature "analyzes project scope and automatically generates precise deliverables". | Not stated. The subject of the sentence is the procurement specialist, but the generation is described as automatic. | The only retrieved artifact is dated 2026-04-14, after the frozen cutoff. It establishes nothing about the capability at 2025-12-31. The efficiency figures it quotes are vendor claims and are not carried into any register. |
Deel Contractor of RecordC-005 | performs the operation itself | Deel becomes the hiring entity and "assess[es] each contractor's classification and become[s] their agent of record, taking on the liability for employers." Existing contractors can be moved into that state in bulk: "Bulk-upgrade contractors to Contractor of Record in minutes". | Not established. The Contractor tier is described as having "an AI-powered classification tool"; the artifacts do not state whether a Contractor-of-Record classification decision is machine-determined or expert-reviewed. | Establishes that the offering changes who legally engages a contractor and produces a classification determination, on artifacts dated before the cutoff. Does NOT establish that the classification decision is machine-made, does NOT establish any volume or usage, and does NOT establish that the determination binds any tax or labour authority. |
Magnit VMS Market RatesC-006 | advises only | "organizations can utilize real-time insights including hiring intelligence and cost savings estimates to make more strategic hiring decisions" | All of it. No retrieved passage has the capability writing a value to a rate card, a requisition or a work order. | Excluded on mode, not on object. Rate cards ARE consequential in this area; this capability is not evidenced as changing one. A future artifact showing the tool writing a rate would change the outcome. |
Beeline AIC-007 | prepares the work, stops before it counts | "Save hours with streamlined requisitions, candidate insights, interview prep, and SOW creation." Also "Enriching job descriptions to enable a skills-first approach". | Not stated. | The dates rendered on the Beeline AI product page (2025-06-03, 2025-08-04, 2025-08-05) belong to linked resources, not to the capability text, and are not treated as the page's date. |
SAP Fieldglass GLA agent (general ledger account / cost centre agent)C-008 | performs the operation itself | "When the GLA agent applies cost center changes to a worker and the Capture effective dates for cost center on contingent workers configuration is enabled, cost center start and end dates are revised" | None described for the cost-centre revision itself; the agent is the acting subject. | Excluded on object, not on mode. This is the area's clearest evidenced case of a machine agent autonomously mutating a live worker record, and it is excluded because a cost centre does not change what anyone is entitled to do or be paid. Recording it prevents the population from being read as 'no autonomous agents were found'. |
Whose systems does this area run on?
What part each system plays was decided by what it does to the area's records, never by what kind of company runs it. Where the sources leave that open the entry says so, because an open question is not a kind of system.
| System | Who runs it | What part it plays | What it does to the official record |
|---|---|---|---|
SAP Fieldglass — contingent workforce work order, worker record and time sheetC-009 | SAP SE | authoritative-transaction-rail | creates the work order in SAP Fieldglass; holds the work order in SAP Fieldglass; mutates the work order in SAP Fieldglass via revision; accepts-or-rejects the work order revision — acceptance is performed by the supplier within SAP Fieldglass; creates the worker record in SAP Fieldglass on work-order activation |
Workday VNDLY vendor management systemC-010 | Workday, Inc. | hybrid | holds the contingent engagement record — requisition, rate card and statement of work — in Workday VNDLY; creates-for and submits-to Workday HCM the worker onboarding and provisioning record |
Off-payroll working (IR35) regime and the Check Employment Status for Tax (CEST) serviceC-011 | HM Revenue & Customs (United Kingdom) | authoritative-transaction-rail | defines the permissible forms of the employment-status determination, in HMRC's off-payroll working rules; creates the determination result within CEST, operated by HMRC; accepts-or-rejects the determination as valid — "HMRC will stand by all results given by the tool"; observes the status determination statement, which is issued by the client, not by HMRC |
Beeline Extended Workforce PlatformC-012 | Beeline | unresolved | none-established |
Bullhorn VMS SyncC-013 | Bullhorn, Inc. | transaction-enablement-layer | creates the submission record in the Bullhorn applicant-tracking system; mutates the submission status in the Bullhorn applicant-tracking system; submits-to the buyer's vendor management system (named in the artifact as Fieldglass, Beeline, Pixid, Healthtrust or SimpleVMS); constructs-for the buyer's vendor management system the submission it does not hold |
Deel Contractor-of-Record engaging-entity systemC-014 | Deel, Inc. | authoritative-transaction-rail | creates the contractor engagement in Deel's own entity, which becomes the hiring party; holds the contractor engagement in Deel's entity system; creates the classification determination within Deel, with Deel bearing its consequences |
What may be said from this area, and what may not?
Each one carries how far it is backed and, where it was recorded, the exact stronger sentence that may never be written from it.
Of the twelve admitted events, the four that changed a rule binding on parties other than the publisher were all published by a tax authority: the US Department of Labor and HM Revenue & Customs.
The strongest thing against it EV-05 and EV-06. Deel, a commercial party, changed the engaging counterparty for contractors and took on misclassification liability by contract. That is a binding change — but it binds only the parties who contract for it, which is why it is recorded here as a contrast rather than as a refutation.
What may not be said from this Never: 'regulators drive change in contingent workforce procurement', 'platforms are not driving change', or any claim about frequency, share or trend.
No admitted event evidences a machine agent changing the state of a work order, a rate card, a timesheet approval state or an engagement status. Every agent placement in the event set falls on a candidate submission or a statement of work.
The strongest thing against it C-008, the SAP Fieldglass GLA agent, autonomously mutates a live worker record — but on a cost centre, which is not an entitlement object. It is the closest thing found to a counterexample and it does not reach one.
What may not be said from this Never: 'AI agents cannot change binding objects', 'no vendor has automated the work order', or any claim that the boundary is technical rather than evidentiary.
In SAP Fieldglass, the work order is the instrument at which a contingent engagement becomes valid: it must be accepted by the supplier, its activation is what registers the job seeker as a worker, and it carries the field that determines when the worker may begin submitting time sheets.
The strongest thing against it None was found. No retrieved passage places the binding act anywhere other than supplier acceptance of the work order.
What may not be said from this Never: 'the work order is the binding object in contingent workforce procurement', or any generalisation of one platform's document model to the area.
The single participant offering established at the frozen cutoff qualified by becoming the engaging party and taking on classification liability, not by automating a workflow.
The strongest thing against it None in the participant register. C-008 executes autonomously and does not qualify; C-001 acts autonomously and does not qualify.
What may not be said from this Never: 'automation does not qualify', 'the employer-of-record model is winning', or any comparison of business models.
Across this pilot's evidence, machine capability is forming on the objects that carry the weakest entitlement, while the objects that bind are changed by contract or by statute.
The strongest thing against it EV-07 and EV-11 place agents on the statement of work, which IS a binding object. Both are recorded as unresolved between construction and mutation, so the pattern survives only because neither is established — and either could break it.
What may not be said from this Never: 'AI stops at the boundary of authority', 'agents are confined to low-value work', or any framing that reads as a law rather than a reading of eleven months of collected artifacts.
In the UK off-payroll case, the party that defines the permissible engagement grammar and the party whose system makes a determination valid are the same — HMRC — while a third party, the client, composes and issues the determination.
The strongest thing against it None was found for this object. For a different object — the contractor engagement at C-014 — a single commercial party holds composition and binding together, which is the opposite configuration.
What may not be said from this Never: 'regulators define the grammar of contingent work', or any extension beyond the UK off-payroll object.
No capability recorded in either register is established as being in production use by any buyer.
The strongest thing against it None. No retrieved artifact names a buyer using any capability recorded here.
What may not be said from this Never state or imply deployment, adoption, usage or customer counts.
No retrieved artifact links any of the four institutional events to any change in any platform's behaviour.
The strongest thing against it None was found.
What may not be said from this Never: 'regulation is driving platform change', 'platforms responded to the umbrella rules', or any causal or responsive framing.
Three of the four units this pilot judged structurally significant on current evidence — SAP Fieldglass, Workday VNDLY and Bullhorn VMS Sync — cannot be placed at the frozen cutoff, because the artifacts establishing what they hold carry no page-visible date.
The strongest thing against it C-011 and C-014 are both datable at the cutoff — the first from a change-history entry on a government page, the second from a dated vendor blog. Datability is therefore a property of the estate, not of the area.
What may not be said from this Never: 'these platforms did not hold these objects at the cutoff'. Unresolved is not negative.
Two dated vendor announcements were rejected from the event set because neither named an record in scope for the area being acted on, leaving the area's largest platform operator by footprint contributing zero admitted events.
The strongest thing against it None — both artifacts were retrieved and inspected in full and neither names a requisition, work order, rate card, statement of work, timesheet, engagement status or payment eligibility.
What may not be said from this Never: 'Beeline has no agentic capability', or any inference from a rejected artifact to an absent capability.
Workday VNDLY is not a mirror of the buyer's HR system for the engagement objects: it is named as the system of record for the contingent workforce and holds the requisition, rate card and statement of work, while the worker's provisioning and access record is created in Workday HCM.
The strongest thing against it The same artifacts confirm the mirror reading for a different object: VNDLY onboards workers into HCM, where the provisioning record is created and held. One unit, two opposite relationships, which is why the role is hybrid rather than transaction infrastructure.
What may not be said from this Never: 'VMSs hold the authoritative engagement record'. One vendor, and only for three named objects.
A transaction-enablement layer exists in this area: Bullhorn VMS Sync creates and mutates a submission in the supplier's own system and transmits it into a buyer's vendor management system that it does not hold.
The strongest thing against it None was found. The artifact names the receiving systems explicitly, which is what makes the non-holding relationship checkable rather than inferred.
What may not be said from this Never: 'intermediaries are compressing', 'enablement layers are proliferating', or any claim about number, direction or trend.
What dated acts touch this area's records?
A list, in date order. It is not a timeline and carries no rate: the collection capped each publisher, so this is a floor on what was retrievable rather than a count of what occurred.
| Date | Kind of act | Consequence recorded | Source |
|---|---|---|---|
2024-01-10 day precision | institutional accommodation | The test by which a worker is classified is replaced, changing the rule against which any engagement's status is assessed. | source |
2025-04-30 day precision | institutional accommodation | The authority's own determination service was changed while the authority's commitment to stand by its results remained stated on the same page. | source |
2025-05-19 day precision | named deployment | none stated. | source |
2025-05-28 day precision | named deployment | none stated. | source |
2025-08-07 day precision | workflow expansion | none stated in this artifact. | source |
2025-09-03 day precision | commercial-model change | Misclassification liability transfers from the buying organisation to the provider, by contract. | source |
2025-09-16 day precision | named deployment | none stated. | source |
2025-09-17 day precision | institutional accommodation | Liability for a third party's payroll default moves up the labour supply chain to the party closest to the buyer. | source |
2025-11-26 day precision | institutional accommodation | The statutory measure implementing the reassignment of PAYE responsibility is published with a commencement date. | source |
2025-12 month precision | workflow expansion | none stated. | source |
2026-04-14 day precision | workflow expansion | none stated. | source |
2026-05-28 day precision | named deployment | none stated. | source |