AI draws a process: a neat diagram can lose the way out
Review an AI process diagram against specific cases. Check conditions, branches, waiting and different endings, not just its appearance.
Article language: English

In this article
Every arrow in the diagram leads to “Equipment issued.” A customer might fail to provide measurements, cancel or change the date, but the diagram allows none of that. The company on the page serves only decisive, fully prepared and punctual people. Convenient customers, if only they always came through the door.
At Doba, a fictional equipment rental business, AI turns a description of a reservation into a diagram. The team wants to use it to discuss the process before automating anything. Acceptance means comparing the drawing with agreed conditions and walking specific cases through it. This is not formal model certification and does not require one particular notation. An attractive graphic should help people notice decisions, not make those decisions for them.
First preserve the conditions that are easy to shorten
Separate activities, conditions, events and endings in the input. “An employee checks that the information is complete” is an activity. “If a measurement is missing, the employee asks for it” describes a condition for the next path. “The customer cancels” is an event that can change the course. “Reservation closed after cancellation” is a different ending from issuing the equipment. Do not reduce everything to a row of rectangles.
For Doba, write down the example's working rules. Preparing a reservation requires a date, the selected equipment set and the required measurement. Missing information leads to a request for completion. Cancellation requires preparation to stop and the case to be marked. Issuing the set requires confirmation that this action occurred. These are assumptions for a fictional workflow; in a real company the process owner must confirm them.
Mark gaps too. If the description does not say what happens when a customer does not reply, do not let AI independently decide on three reminders and closure after a week. Ask it to mark the unresolved rule. The model may prepare an option for discussion, but it should be visible as a proposal. Otherwise the generator's decision can hide in the drawing under the appearance of documentation of current work.
Associate every important condition with a source passage and a person who confirms it. A short identifier is enough: the reservation description, an instruction version or an agreement from the owner. Do not copy all company correspondence into the diagram. The next person should be able to reconstruct why one event permits issuing equipment while another stops the process.
If the description comes from discussions among several teams, check for contradictions before generation. One person may speak of a preliminary reservation and another of a confirmed one. Those words should not accidentally describe the same field. A service map helps reveal different perspectives, as described in the article on mapping customer contact and back-office work (in Polish). When accepting the diagram, check whether agreed distinctions survived the simplification into a drawing.
Also mark whether the drawing describes current work or a proposed change. Doba may now confirm cancellations manually but want preparation stopped automatically in future. Each version needs its own name and date. If the model combines them without explanation, the team might mistake a planned function for one already operating. Each difference in the review should lead to a question about the present state or an intentional design decision.
Set the process model's boundary. It might start with receiving an enquiry and end with confirmation that equipment was issued, deliberately leaving its return out of scope. Label that boundary. An omitted return is not an error if it was consciously excluded. A missing cancellation path within the reservation process is different and needs explanation.
Walk through cases that do not have the same ending
Before examining the appearance, prepare a few small case cards. Each contains the starting information, subsequent events and the agreed result. In this example choose four:
- The customer provides complete information, the set is available, and an employee confirms preparation and issue. The case should reach confirmed issue.
- A measurement is missing. The customer supplies it after the employee asks. The case returns to assessment of the information instead of automatically jumping to issue.
- The customer cancels before the set is prepared. The team stops further work and records the appropriate ending without confirming issue.
- The date changes after a preliminary availability check. Before the next step, availability must be assessed again for the new date.
This is a test design using fictional data, not a report of an implementation. For each card, follow the visible connections and record where the case stops or takes an unauthorized shortcut. Do not draw in a missing arrow with a gesture because “everyone knows you can go back.” A future diagram user will not always have its author beside them with a pen.
At a branch, ask who chooses the next path and on what basis. “Yes” and “no” make sense only with an unambiguous question. “Is the information correct?” could mean completeness, agreement with the offer or employee approval. If these checks lead to different actions, separate them. An extra step in the drawing can be clearer than three meanings hidden in one diamond.
In formal BPMN, a notation for describing processes with defined elements, branching symbols have specific meanings. The OMG BPMN 2.0.2 specification distinguishes, among other things, choosing one alternative path from starting parallel paths. If a team uses that notation, accidentally changing a symbol can change the model's meaning. A simple custom diagram also needs to explain its connections clearly.
For availability, include the state “not yet checked.” It is neither confirmation that the set is free nor confirmation that it is unavailable. The diagram should show the action that resolves the question. If information comes from another system, no response should retain its own state. The team must decide how to handle it rather than let the generator pick a convenient branch for an unknown value.
Doba may prepare the set and inform the customer separately. If both actions are required, the diagram should explain when it is permissible to proceed. Do not join two branches simply because it looks tidier. Establish whether the next step needs both confirmations, one of them or another condition. The label “join” does not answer that question.

For every wait, check the event that ends it. “Waiting for information” requires a way to recognize a response and link it to the correct case. If the waiting-time rule has not been agreed, leave the question open. Do not simply send the case to success to remove a loose arrow. A neat line ending does not confirm that the work is complete.
Distinguish sending work from its acceptance. A task passed to another department may still need confirmation of responsibility and the necessary context. The handoff between AI agents raises a similar question about context; the article on handoffs between AI agents (in Polish) examines it. A line connecting two boxes does not prove that the second party received enough information to act.
At an exception handoff, identify the next action and responsible role. An automation exception queue does not complete a case merely by receiving a record. The next responsible step is discussed in the article on automation exception queues (in Polish). If the diagram routes cases with missing data there, its user should find a rule for return or closure. The entire rule need not fit on one image, but the reference to the further description should be clear and accessible.
Check the ending as well. Sending a collection request does not yet mean the equipment was issued. Closing after cancellation does not mean successful fulfillment. If all paths end with “done,” the team may later confuse the fate of the case with completion of a particular action. Name endings according to what they confirm and identify the basis for confirmation.
An open file does not prove an accurate account of the work
A diagram may be an image or a file with elements that can be edited further. Agree what the team needs to receive. If it plans to change conditions and connections, an image needs a different maintenance approach from an agreed editable model. Check the actual material and whether the required change can be made, not just the file extension.
The bpmn-js documentation describes importing and saving a BPMN XML diagram. Import can return an error or warnings; it is not a separate check of the diagram against every rule. Opening the file successfully in an editor does not prove that it includes every case agreed by the company. Check that separately against the source material and case cards.
Likewise, a valid JSON structure from AI does not determine the meaning of data, a distinction explored in the article on JSON structure and meaning in AI output (in Polish). Do not dismiss the technical check; it can detect its own errors. Record the import result, conformity of the elements used and the case-walkthrough result separately. Name each result in the report instead of combining them under “checked.”
Also check the export that people discussing the process will see. A small condition label may disappear or become unreadable. Two crossing lines may look like a connection that is absent from the model. Ask someone who did not create it to walk through one card using that material. Their question can reveal ambiguity without guessing whether the cause is the description, file or layout.
Do not assume that a model intended for discussion is a ready-made automation configuration. Execution needs further decisions about data, permissions, confirmations and error handling. Such an operating workflow is the subject of the business process automation audit guide (in Polish). Acceptance of the drawing provides a basis for the next work; it does not substitute for its result.
A correction to one path should preserve the others
Adding cancellation may change the rules for preparation, notifications and case closure. After the change, walk through the cancellation case again and the earlier cards whose paths changed. Do not limit the check to looking at the new box. Some work may already have happened when the event occurred, and its subsequent fate needs a separate agreement.
Add a late-message case. After cancellation, an earlier preparation confirmation might arrive. Without a rule, the diagram should not return the case to the issue path simply because that message appeared later. The distinction between arrival order and the meaning for the current state is explored in the article on late automation status messages (in Polish).
Check the model when the case is handed to another authorized person. Can they identify the current state and the role responsible for the next step from the drawing and referenced instructions? The author's name in a comment is no substitute for a cover arrangement. If one person's absence prevents the model being understood, improve the record and access to explanations. This tests the documentation's usability without confirming technical execution of the automation.
When there is a discrepancy, decide whether to correct the drawing, the source description or the way work is done. Two people may understand the same condition differently. A new diagram does not settle that disagreement. Record the question, the decision maker and the effect of leaving it unresolved. Incorporate the rule in the next version only after it is confirmed.
Keep the previous model, the scope of the correction and its connection to the source. When AI redraws the whole diagram, compare apparently unchanged paths too. Correcting one exception does not authorize removal of a condition elsewhere. A list of differences helps the reviewer focus on actual changes.
For an overview of AI use reviews and agreeing the scope, see Aeneia Audit. At Doba, a useful diagram shows not only equipment issue but also waiting, reassessment and closure after cancellation. The diagram can then support a discussion about work that can really happen, rather than politely directing every customer to the same arrow of success.







