For the operations manager who still coordinates by hand

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.

Classify my process See the specimen first

133: step patterns
66: systems, SAP to clipboard
10: findings it can raise, mapped to 41 licensed controls

Two dispatch office staff at a desk with parcels on the shelves behind them, both smiling — Every step a person still moves by hand, named before someone asks which ones an agent could take.

Specimen, 5 of 32 steps

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

Run the whole specimen below to see all 32, the findings and the controls.

Your process, one step per line

Numbered lists, bullets, who | does what | in which system, a table with a header row, or plain sentences. Mixed is fine. A line that matches nothing comes back unclear with four questions, never a guess.

Parsing and classification run in your browser. Nothing is sent anywhere until you choose to save.

01 PASTE

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.

02 CLASSIFY

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.

03 PROPOSE

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.

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.

The dictionary of step patterns is ours and is published in full: every pattern it recognises, with the verdict, what you lose and the first move for each. Nothing is generated on the fly.