Why processes · AI and processes

AI needs guardrails. Guardrails need transparent processes.

AI processes unstructured information at speed, but has no sense of responsibilities, compliance limits or the bigger picture. A process model describes exactly that. This page makes the case in six steps: why AI alone is not enough, why BPMN has two readers, its new role, the missing prerequisite, where this leads, and how patchley closes the gap.

01 — The starting point

AI alone is not enough. BPMN alone is not either.

Classic BPMN is rigid and rule-based. AI on its own is probabilistic and hard to control. Together they become regulated flexibility: the AI acts dynamically inside limits that were defined before it started.

Classic BPMN aloneAI aloneAI + BPMN
Way of workingRigid and rule-based, inflexible with exceptions.Probabilistic, a black box.Regulated flexibility: the AI acts dynamically inside defined guardrails.
GovernanceDefinable and auditable in advance.Hard to control, risk of hallucinations.Hard limits, for example a four-eyes approval, that an AI cannot skip.
Creation and upkeepLaborious, manual, time-consuming.Quick drafts, but without reliable structure.The AI drafts the model from the conversation, the person checks and decides.

02 — One language, two readers

The notation may look old. As a language for AI it is more current than ever.

Many see BPMN as yesterday's cumbersome modelling language. But it is precise, standardised and machine-readable, which is exactly what AI agents need to complete tasks reliably.

SalesManagementAI agentAI AGENTyesnoRequest receivedCheck requestCRMRequestReconcile dataCRM · ERPCustomer record×Approval needed?CONTROLApprove offerSend offerE-mailOffer sent
Fictional example model: lanes, a gateway, data objects, systems and a control step. The same file for both readers: the diagram for people, the structure behind it for the AI agent.

For people: the diagram Reader 1 · human

  • Who does what, in which order
  • Bottlenecks and hand-overs at a glance
  • The basis for agreement and sign-off

For the AI: the workflow behind it Reader 2 · AI agent

  • Responsibilities (lanes), decisions (gateways), data and systems per step
  • Controls and approvals that must not be skipped
  • The goal: which result has to stand at the end
In one sentence

The visualisation is for people. The structure behind it is for the AI, so that it does not merely act but reaches the right result.

03 — The new role of BPMN

From the handbook on the intranet to the operating system for AI agents.

BPMN does not die because of AI. It moves from a tiresome documentation duty to the control layer for intelligent workflows. Four roles it takes on:

1

Guardrail for AI agents

The model defines when an agent works, which data it gets and when a person steps in (human in the loop).

2

Traceability and audit

When AI makes business-critical decisions, it must be visible where it was active. Rules for high-risk AI applications, such as the EU AI Act, ask for exactly this kind of traceability.

3

Check the effect before you automate

Whoever speeds up one step without knowing the process only moves the backlog to the next manual hand-over.

4

Process knowledge that answers

Staff do not need to read the diagram. They ask "Who approves this offer?", and the answer comes from the stored process.

04 — The prerequisite is missing

All of this only works with transparent processes. That is exactly where it fails.

AI can only automate what it knows. In most organisations the actual sequence of work is not cleanly described anywhere, and smaller and mid-sized companies feel this most.

The consequence

AI automates what it sees. What is not described, it does not see.

Symptom 1

Documented, but outdated

The process handbook describes the state at the last certification, not everyday work today.

Symptom 2

Only in people's heads

How it really runs is known to a few experienced colleagues. When the knowledge leaves, the process leaves with it.

Symptom 3

No staff department for it

In a mid-sized company the management itself has to do this. Modelling projects lasting weeks are simply not an option.

05 — Where this leads

Every jump in AI came from better context.

From a single prompt to rules, knowledge and actions: each step gave the AI more context. The next step is structure, the process graph. After that, the model does not describe the work any more; it runs it.

01WordsThe prompt
02RulesThe system prompt
03KnowledgeDocuments and retrieval
04ActionsTools and agent chains
05StructureThe process graph: machine-readable process maps, BPMN 2.0 with lanes, systems, data and controls, created in the workshop.patchley today
06ExecutionThe process runs: process models that are executed, AI agents per step, people where judgement is needed.The vision · Executions pilot
Today and next

Today the model describes the work. Next, it runs it. That second step is the Executions pilot, in preparation with a small group of pilot organisations, not a released feature.

06 — How patchley closes the gap

From the conversation to a process that people and AI understand.

patchley collects process knowledge where it lives: in people's heads and in the conversation. No modelling project, no staff department, just your own words.

1CaptureSpeak in the workshop, upload a document or a recording, or let patchley join the meeting.
2ModelBPMN 2.0 from the conversation: lanes, systems, control steps. Editable straight away.
3AnalysePain points, controls, compliance and figures per step, or your own template.
4DesignThe To-Be process, including the steps an AI agent takes over, as its own diagram with the As-Is one switch away.
Pilot · in preparationRunThe released model becomes the workflow for people, systems and AI agents.Join pilot

STANDARD FORMATS · NO LOCK-IN: BPMN 2.0 XML OPENS IN SIGNAVIO, ADONIS AND CAMUNDA MODELER · AI MODELS FROM A EUROPEAN PROVIDER, HOSTED IN THE EU

The argument as a document: "AI and processes"PDF · 8 pages. Request it by email.
Request by email
More on why processes:Process capture without recording anyone's screen.The workshop ends with the diagram.

Bring one real process to a 30-minute call. Leave with the diagram.

We model it live with you, in your language. Pick a time and the Microsoft Teams invitation is in your calendar straight away.

info@patchley.com

Book a 30-minute demo

We model it live with you, in your language. Pick a time and the Microsoft Teams invitation is in your calendar straight away.

Download request

Request a document

Enter your email address and we send you the document by email.

Requested document

Fields marked * are required.

See patchley in 19 clicks

Executions · pilot

Join the Executions pilot

Tell us a little about your organisation and the process you would run first.

Fields marked * are required.