What happens today
Shared file, agency-side exposure.
A candidate accepts and the client confirms a start date, often only days away. A recruitment consultant, a compliance coordinator, and an administrator now share responsibility for a document file that has to be complete before the first shift. Because the agency is the employer of record for the temporary worker, the exposure sits with the agency rather than with the client.
No two placements need the same documents.
The required set is the intersection of jurisdiction, role type, sector, client contract, and worker classification, so it shifts from one placement to the next. For example, a US placement turns on Form I-9 and E-Verify, with strict day-one and three-day deadlines; a UK placement on a right to work check completed before the first shift; a German placement on the AÜG designation and its eighteen month assignment ceiling. Each is a different rule set, and each carries its own deadline.
Credentials and client demands stack on top.
Layered on top of that are role credentials such as professional registration, licenses, training certificates, vaccination records, references, and background screening. Layered on top again are client-specific items such as site induction, the client NDA, mandated training modules, insurance evidence, and the badge request, frequently submitted through the client portal in the client format.
It lives in memory, not a system.
This requirement list is rarely written down as a rule set. It lives in a spreadsheet, a template email, and the coordinator's memory. The work itself is deciding which list applies, sending the request, chasing it repeatedly, opening every returned file and reading it for document type, name match, expiry, issuing body, legibility, and completeness, typing the extracted values into the applicant tracking system, setting a reminder for the expiry date, and escalating whatever fails.
The failure points are predictable.
What goes wrong is specific and it repeats. A candidate photographs one page of a two page certificate. A credential arrives already expired. The name on the certificate does not match the placement record after a marriage or a transliteration. Right to work evidence lands after the start date, so the worker begins uncovered. An expiry reminder is missed and someone is on a client site with a lapsed credential.
How the architecture runs it
A candidate accepts, the client confirms a start date days away, and because the agency is the employer of record the exposure sits with the agency. The FLOW derives the exact document set for the placement, reads every returned file against the rules that apply, and has verified evidence in place before the first shift — with a compliance specialist deciding only the genuine exceptions.
The compliance team maintains this in plain text — it sets the required document set for the placement.
Every step, in order, under which policy, by which person or agent, on what evidence.
What the FLOW does
Start on placement.
A confirmed placement in the ATS starts the FLOW through Connect.
Resolve the requirements.
Business Context derives the document set from the intersection of jurisdiction, role, sector, contract, and worker classification — the Form I-9 and E-Verify path in the United States, the right-to-work check in the United Kingdom, the Arbeitnehmerüberlassung terms in Germany — rather than a laminated checklist.
Request and read the documents.
A Digital Task Agent requests the documents in the candidate’s language and reads each returned file for type, name match, expiry, issuing body, and completeness, even from a photograph or a partial scan.
Validate against the policy.
The FLOW tests each document against the resolved set and maps any defect to the rule and the value that failed; a genuine exception goes to a compliance specialist in the Enterprise Workplace with the field, the file, and the failed rule attached.
Route the outcome.
A Digital Supervisor classifies the case as complete, chase, or exception — the chasing runs on schedule on its own, and only the real exceptions reach a person.
Clear for day one.
Connect writes the verified status and the document links back to the ATS to clear the worker for the first shift, and logs each expiry so a reverification is raised before a credential lapses.
What it's worth
Different decision-makers weigh different things.
Here is what this FLOW returns to each.
Coordinator hours come back, and missed-deadline write-offs — I-9, right to work — stop becoming fines or lost time-to-bill. Valid placements clear without manual chasing.
More placements cleared per coordinator, with a predictable time-to-first-shift instead of a scramble in the final days.
No worker starts on a client site with a lapsed or missing credential, and every decision is defensible straight from the execution record.
Runs above your ATS with no migration, and the tool bounds stay IT-owned even as the policy changes.
Compliant onboarding at scale — the team works exceptions, not inboxes, and candidates are contacted in their own language.
Coexistence
How this connects to what you already run.
NEWWORK Connect reads from and writes to the systems that hold your records, including applicant tracking, HR, finance, and procurement platforms. Those systems remain your Systems of Record. NEWWORK runs above and between them, which is why a FLOW of this kind can go into production without a migration program standing in front of it.
You can begin with one of these FLOWs, with a Digital Employee owning a single recurring role, with an Enterprise Workplace for one team, or with a complete Business Solution. Any starting point. Any combination. Your way.
Start above your existing systems. Replace selectively when it creates value.
Governed autonomy
Why the record matters as much as the work.
Every FLOW produces one execution record: what happened, in what order, under which policy, by which human or which Digital Task Agent, on what evidence, and with what outcome.
Governed autonomy means the FLOW acts inside limits you set, escalates what it should not decide alone, and leaves a trace of both. The same record answers the compliance request, the invoice dispute, and the audit question, because it is the record of the work itself rather than a report written about it afterwards.
That is what makes work of this kind safe to give to an AI system in a regulated, client-audited business. The capability is what makes the pilot worth running. The record is what makes it defensible.
AI-native by architecture. Agentic in execution. Autonomous where governed.
