Speak naturally
Describe your process in plain language. No BPMN expertise needed.
Describe how work gets done in your own words. We’ll ask what matters, turn it into a clear BPMN 2.0 process, and give you a diagram you can edit, improve, and share.
From process descriptions or SOP text to BPMN 2.0 — in minutes.
The employee submits a leave request. Their manager reviews it and lets them know the decision.
Plain-language descriptionChoose your modeling style and describe your process or paste your SOP text. Answer clarifying questions, confirm the scenario, then refine your diagram and prepare a process manual. You stay in control at every step.
Choose Simple workflow or Standard BPMN 2.0, then describe the process or paste your SOP text.
Answer focused questions about roles, activities, decisions, and exceptions.
Review the proposed scenario and assumptions, make corrections, and confirm it before we draw.
Generate an editable diagram, then adjust its activities, connections, and layout.
Export your diagram, or create an editable process manual and download it in Word.
Enough structure to be useful. Simple enough to start with what you know.
Describe your process in plain language. No BPMN expertise needed.
The AI asks clarifying questions instead of inventing missing details.
Make standard BPMN 2.0 diagrams you can edit and reuse.
Work in either language, with RTL support for Arabic process content.
Export BPMN, PDF, PNG, or SVG.
Review and refine activities, roles, and decisions in the manual editor.
BPMN exports can be opened in tools such as Camunda · Signavio · Bizagi · ARIS. Compatibility may vary by tool and diagram; no affiliation or endorsement is implied.
Five examples: two simple, two medium, and one long process. Each flowchart shows the complete process described, including decisions, correction loops, and parallel work. Switch between English and Arabic.
An employee submits the requested leave dates to their manager. The manager checks team coverage and approves or rejects the request. The employee is notified of the decision, and the request is closed.
1. Submit leave request → 2. Review coverage and decide → 3. Notify employee and close
An employee sends a document to the administrator. The administrator registers it with a reference number, saves it in the shared archive, and sends the employee an acknowledgement. The process ends when the acknowledgement is sent.
1. Receive document → 2. Register and archive → 3. Send acknowledgement
A supplier submits an invoice to Finance. Finance checks the required information and matches the invoice to the purchase order and goods receipt. Missing information or a mismatch sends the invoice back to the supplier for correction and resubmission. A matching invoice above the approval threshold is reviewed by the department manager; a rejected invoice returns for correction. Once all required approvals are complete, Finance schedules payment, sends confirmation to the supplier, and archives the invoice.
1. Receive invoice → 2. Check completeness → 3. Match order and receipt → 4. Return discrepancies for correction → 5. Obtain approval when required → 6. Schedule payment → 7. Notify supplier → 8. Archive invoice
After a candidate accepts an offer, HR collects the employee documents and confirms the start date. Missing documents are returned to the employee for completion. HR then starts two activities in parallel: IT creates the account and prepares the laptop, while Facilities prepares the workspace and access badge. If either preparation fails, the responsible team resolves the issue and repeats its readiness check. Once both teams confirm readiness, the manager holds an orientation, HR checks that all onboarding items are complete, and the employee record is activated.
1. Confirm start date → 2. Collect and verify documents → 3. Complete missing information → 4. Prepare IT access and workspace in parallel → 5. Resolve readiness issues → 6. Join both ready branches → 7. Hold orientation → 8. Activate employee record
An employee submits a purchase request with a business justification, item specifications, estimated cost, and required delivery date. Procurement checks completeness; incomplete requests return to the employee for correction and resubmission. The budget owner checks available funds. If funds are unavailable, the employee revises the scope and resubmits or cancels the request. For a funded request, Procurement obtains supplier quotations, compares price, quality, and delivery time, and recommends a supplier. The department manager reviews the recommendation. Purchases above the approval threshold also require Finance approval; rejected recommendations return to supplier selection. After all approvals, Procurement issues a purchase order and the supplier confirms availability and a delivery date. If the delivery date is unacceptable, Procurement negotiates a new date or returns to supplier selection. The warehouse receives the delivery and checks quantity and quality. Missing or damaged goods trigger a replacement request and repeat inspection until the goods are accepted. Finance receives the invoice and matches it to the purchase order and accepted goods receipt. Discrepancies return to the supplier for correction and resubmission. Once the invoice matches, Finance pays the supplier and sends payment confirmation. Procurement archives the order, receipt, invoice, and confirmation, then closes the request.
1. Submit purchase request → 2. Validate and correct → 3. Confirm budget or revise/cancel → 4. Obtain quotations → 5. Compare suppliers → 6. Review recommendation → 7. Obtain required approvals → 8. Issue purchase order → 9. Confirm delivery or renegotiate → 10. Receive goods → 11. Inspect and resolve defects → 12. Receive invoice → 13. Match and correct discrepancies → 14. Pay and notify supplier → 15. Archive and close
From plain words to a process you can actually use.
Try it without an account, or sign up free to keep working.
For getting the process out of your head.
No sign-up needed to try 2 diagrams in total.
Yes. Describe your process in everyday language. The studio helps clarify the details and creates a BPMN 2.0 diagram you can inspect and edit.
Yes. The studio supports Arabic and English, including right-to-left Arabic process content.
File upload is not available. You can paste the relevant SOP or process description as text.
Not currently. Describe the process in text instead. Photo upload is not supported.
You can export BPMN, PDF, PNG, and SVG. There is no SOP document export.
Yes. Use the manual editor to review and refine your diagram after generation.
The BPMN 2.0 file is intended for compatible modeling tools such as Camunda, Signavio, Bizagi, and ARIS. Import behavior varies by tool and diagram; these names do not imply endorsement.
Your process description and answers are sent to AI services to generate and clarify your diagram. We cannot make a blanket claim about provider training practices here. Avoid entering sensitive or confidential information; review the Privacy draft before relying on it for policy details.
Start with the words you already have.