Intake to Onboarding with nothing missing
New clients, patients, members or suppliers are taken from first request to onboarding: the request extracted, what is missing listed, the pack prepared, and tasks opened only after approval.
The problem it answers
New clients, patients, members or suppliers wait while staff chase missing items, and iSystematic's Intake to Onboarding solution turns each request into a list of what is missing and a prepared onboarding pack.
What it does
It extracts the request, lists what is missing, prepares the onboarding pack, and opens tasks once a person approves them.
It works from the list of what is missing, not from the documents: identity documents, health records and financial records never enter it.
A missing critical value is asked for, never guessed. An unsigned or disputed scope stops onboarding until a person resolves it, and the terms agreed with the client are never changed by the workflow.
Built from
It is built from two catalogue workflows and three catalogue patterns.
| Id | Name | What it brings |
|---|---|---|
| W11 | Lead Intake and Next-Step Draft | Summarises the request, lists missing facts and drafts an acknowledgement for review; fit is judged on the service, never on personal attributes |
| W12 | Client Onboarding | Checklist, welcome draft and missing-items review, then tasks once approved |
| P02 | Extract, Validate, Propose | Fields extracted and validated; missing critical values are never inferred |
| P04 | Approval Before Commitment | Tasks and records are created only after approval |
| P07 | Deduplicate Before Acting | An identifier check before any outside action, so a request is not processed twice |
What it is built on
Three parts of the framework corpus decide how intake runs, and each leaves a record the client keeps.
| Framework | In this solution | Client keeps |
|---|---|---|
| Activity-on-Vertex Workflow Graph (AP-2) | Extract, list what is missing, prepare the pack, open tasks: each step a vertex with declared dependencies | The workflow graph |
| Capability Contract (AP-5) and Tiered Human-in-the-Loop (AP-4) | Tasks and records are created only after approval, through declared operations | Approval records |
| AI Data Governance Framework™ | Identity documents, health or financial records never enter; intake works from what is missing, not from the documents | Classification record; G1 record |
Five parts apply to every build and are not repeated here: decision rights, the five gate records, a BOE Declaration per control, a vendor assessment for every vendor, and incident response. How we build sets out all of them.
The evidence it leaves behind
Every intake leaves records the client keeps.
- An intake record and an onboarding checklist
- The workflow graph
- Approval records
- A classification record and the G1 record
- The five gate records and a BOE Declaration per control, as for every build
Typical buyer
The typical buyer is an operations or client-services team.
Status
Proposed, as of 9 October 2026. A solution becomes Piloting or Released only after a documented pilot, and no result is shown for it before then.
How to start
Most organisations start with the Automation Assessment, which scores intake beside nine other candidate tasks. When intake is already the clear first task, a six-week Pilot runs it for one team, with the baseline measured first.
Where to go next
Operations leaders
For COOs: iSystematic's two-week Automation Assessment scores ten candidate tasks, recommends three solutions and sets a baseline before anything is built.
Front Door Agent
The Front Door Agent gives an organisation one front door across email, web chat, WhatsApp and forms, built on ARIA by Simplification.io, with people approving.
Meeting-to-Action Operations
Meeting-to-Action Operations turns consented recordings or notes into decisions, owners and dates, and creates tasks only after a person approves them.
Receivables Assistant
The Receivables Assistant prepares reminders only for invoices confirmed unpaid, with exact amounts, and blocks paid or disputed items before anything is sent.
How we build
How iSystematic builds: every solution uses the same deposited frameworks. See what each part decides, what the client keeps, and each specification's DOI.
Conformance is self-declared; no regulator endorses this work.
Start with the Automation Assessment
Two weeks, a fixed fee shared on a short call, ten candidate tasks scored and three solutions recommended.