Paste the steps of a process. See which ones an AI layer would take first, and what you lose when it does.
Write the steps the way you would for a new hire. Every one comes back as re-keying, a decision, an approval or an exception, with a verdict, hand over or keep, and for every hand-over the control that disappears when nobody sees the value before it lands. The first 12 steps classify free with no account, and the specimen runs in full; nothing you paste leaves your browser until you save it.
- 133
- step patterns
- 66
- systems, SAP to clipboard
- 10
- findings it can raise, mapped to 41 controls
- 01Every morning at 8 the inbound clerk downloads the supplier ASNs from the email inbox and keys them into the WMShand over
- 03If the quantity does not match the delivery note, raise a discrepancy with the supplierkeep
- 09Any invoice over 10,000 has to be approved by the finance managerkeep
- 24Dispatch re-keys every order into the DHL and StarTrack portalshand over
- 28Sort out the Friday stuff for the big accountunclear
Use business process model and notation (BPMN)
Every process you paste also comes back as a BPMN 2.0 process model: a .bpmn file with its diagram, one lane per owner, keep steps as user tasks and hand-over candidates as service tasks, drawn as-is and as a to-be draft after the hand-overs, and downloadable as .bpmn, SVG or PNG. Every release checks the files against the OMG BPMN 2.0 schema and opens them in the bpmn-js viewer. On Solo and Team you can also import a .bpmn file your team already has and classify its tasks.
How the BPMN output works · Download the specimen as-is .bpmn · the specimen to-be .bpmn · See both diagrams on the specimen
Allow the creation of business rule logic: write the rule a decision step follows as a table, check and test it, and export it as BPMN gateway conditions and a DMN 1.3 decision table.
Write the process as you would for a new hire
One step per line, in the order it happens. A numbered list, bullets, who | does what | in which system, a table with a header row, or plain sentences such as "Export the day's orders from the WMS and re-key them into the carrier portal". Mixed shapes in one paste are fine. Free text is the common case; no structure is required.
Every step gets a kind and a verdict
Each line is matched against 133 step patterns and 66 systems. Kinds: re-keying, decision, approval, exception. Verdicts: hand over for re-keying and decisions with a rule a system holds; keep for approvals, judgement calls with no written rule and exceptions that reach a customer or supplier; unclear with four questions when nothing matched. For every hand-over: what you lose sight of, and the first thing to log so it is visible again.
Take the delegation map and the findings to your manager
The register lists the hand-over candidates in the order a resolution layer should take them, and what a person keeps. The findings name the unclear steps, the re-keying into a system of record with no check after it, the approvals with no threshold, the exceptions nobody owns and the hand-overs nothing downstream would see. Each finding is mapped to the ISO 9001 and ISO/IEC 42001 clauses it is evidence for, quoted, with the artefacts an auditor accepts. Export it, save it, re-upload it after the pilot and see what changed.
Use business process model and notation (BPMN)
The same register as a BPMN 2.0 process model with its diagram: as-is and a to-be draft side by side, exported as .bpmn, SVG or PNG, and a .bpmn file from your team read back in and classified on Solo and Team. What is in the BPMN file.
BPMN 2.0 out, and in
Every register is also a BPMN 2.0 process model with its diagram, for the automation team, the implementation partner or the process library that reads BPMN.
- As-is and to-be, side by side. The process as written, and a draft after the hand-overs: each hand-over moved to an automation lane, a review added only where the register found nothing checks it.
- One lane per owner you named, each step a task in your order. Keep steps are user tasks, hand-over candidates are service tasks, unclear steps are plain tasks, re-keyed data is flagged, and an exclusive gateway appears only where a step states a condition.
- The reason travels with the task. Kind, verdict, what you lose, first move, systems and findings in each task's documentation and extension elements.
- Valid BPMN 2.0. Checked against the OMG BPMN 2.0 schema and opened in the bpmn-js viewer in every release. Download .bpmn, SVG or PNG.
- Import a .bpmn file your team already has: its tasks are read in flow order, lanes as owners, and classified.
Why a register and not a workflow tool
The tools that promise to run your operations want the process modelled first, and the modelling is the work nobody has time for. Your process already exists, in the head of the person who does it, and they can write it down in ten minutes. What the written version lacks is the column that says which steps are a person acting as a cable between two systems, which are judgement, and which of the cable steps carry a control that only exists because a person looks at the value on its way through. That is the column this builds, from the lines you already have, with no connector, no model and no account.
Handoff Register: the questions buyers ask
What is Handoff Register?
Handoff Register takes the steps of a process written the way you would for a new hire and shows which ones an AI layer would take first, and what you lose when it does. It is for the operations manager who still coordinates by hand.
How do I write the process in?
One step per line, in the order it happens. A numbered list, bullets, `who | does what | in which system`, a table with a header row, or plain sentences are all fine, and mixed shapes in one paste are fine too.
How many steps are free?
The first 12 steps classify free with no account, and the specimen runs in full. Nothing you paste leaves your browser until you save it.
What does each step come back as?
Every step is classified as re-keying, a decision, an approval or an exception, with a verdict of hand over or keep. A step that matches nothing comes back unclear, with four questions.
What decides hand over or keep?
Hand over is for re-keying and for decisions with a rule a system holds. Keep is for approvals, judgement calls with no written rule, and exceptions that reach a customer or supplier.
What do I learn about each hand-over?
For every hand-over it says what you lose sight of, and the first thing to log so it is visible again. That is the control that disappears when nobody sees the value before it lands.
What is each step matched against?
Each line is matched against 133 step patterns and 66 systems. The dictionary of step patterns is published in full at /steps/, with the verdict, what you lose and the first move for each.
What findings does it raise?
It raises findings such as the unclear steps, the re-keying into a system of record with no check after it, the approvals with no threshold, the exceptions nobody owns, and the hand-overs nothing downstream would see. They are mapped to the ISO 9001 and ISO/IEC 42001 clauses they are evidence for, quoted, with the artefacts an auditor accepts.
Does it produce a BPMN model?
Yes. Every process comes back as a BPMN 2.0 process model with its diagram, one lane per owner, keep steps as user tasks and hand-over candidates as service tasks, drawn as-is and as a to-be draft after the hand-overs, and downloadable as .bpmn, SVG or PNG.
How do I know the BPMN file is valid?
Every release checks the files against the OMG BPMN 2.0 schema and opens them in the bpmn-js viewer. The reason travels with each task: kind, verdict, what you lose, first move, systems and findings in its documentation and extension elements.
Can I import a BPMN file my team already has?
On Solo and Team you can import a .bpmn file your team already has: its tasks are read in flow order, lanes as owners, and classified.
What about a decision step that follows a rule?
You can write the rule a decision step follows as a table, check and test it, and export it as BPMN gateway conditions and a DMN 1.3 decision table. Export the register, save it, re-upload it after the pilot and see what changed.