Image
Workflow
Back office

Onboarding paperwork and checklist coordination

The checklist exists and so does the policy behind it, but both live in somebody’s memory of the last joiner. This is how an agent runs them as written and determines nothing about employment.

The checklist is a copy of the last one with the name changed

Today

What it requires depends on who last remembered

  • The joiner spends their first week being asked for the same three documents.
  • The checklist is a copy of the last one with the name changed, so what it actually requires depends on who last remembered.
  • An item arrives and looks complete, and it is missing the date that makes it count.
  • And the question about what your policy really requires gets asked of whoever answers first.
With agents

Your checklist and policy run as written, stopping at every question that belongs to a person

  • The joiner is asked once.
  • An item that looks complete without being complete becomes visible.
  • The question that needs a person reaches one.

How an agent runs it

The checklist and the policy behind it already exist. This workflow runs them as written, one joiner at a time, and stops at every question that belongs to a person.

01

Opens

Starts the checklist your own policy defines for this kind of joiner, with the accountable owner named on it from the first day.
02

Checks

Tests each item that arrives against its checklist rule, including whether the fields and dates the rule requires are actually there.
03

Names

Says what is missing, what is expiring, and what no rule in your checklist covers, so a gap in the policy reads as a gap.
04

Requests

Asks for the outstanding items through a channel you authorize, once, with what is needed stated plainly.
05

Human gate

Every identity or eligibility item, and every question about what your policy or the law requires, goes to the accountable owner. The workflow determines nothing about employment, eligibility or the law, it decides no joiner complete, and the checklist can be worked by hand at any point without the agent because the policy and the records are yours.
06

Reports

Shows where each joiner stands and who each one is waiting on, so chasing is a report rather than a memory.
07

Records

Keeps completion against the checklist, so the file is assembled as you go rather than reconstructed later.

Results

What changes when the checklist runs as written

The joiner is asked once

The checklist tracks what arrived against what the rule requires, so each request names only what is still outstanding.

Complete-looking items surface

Every item is tested against its own rule, including the fields and dates that rule requires.

The question reaches a person

Identity, eligibility and policy questions are held for the accountable owner rather than answered.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one process end to end, from the checklist your policy defines to a file a person signs off. Eligibility, employment terms and policy interpretation belong to a person, and nothing the workflow produces is an HR or legal determination. The executive assistant layer is the possible next step rather than a promised state once this kind of coordination sits with one seat; How It Works shows how the holds are built.

Tier 1 / Prove
How It Works

Questions, answered

No. It checks items against your checklist rule and holds every identity, eligibility and policy question for the accountable owner. It makes no employment, eligibility, tax or legal determination and gives no advice, the gate is closed by default, and the policy and the records live in your systems, so the checklist can be worked by hand at any point without the agent.

AI Opportunity Audit

See which items your own rules could have tracked without chasing

Bring your onboarding checklist and the last joiner's file, and see which items your own rules could have tracked without anybody chasing them.