Task by Task · Free illustrative practice
Ask AI to draft a process diagram you can check
Example output
An editable process diagram
Illustrative purchase-request procedure. The branches retain the £500 boundary and rejection routes.
Staff draft requestR1
Details complete?R2
No → return to staffR2
Amount at most £500?R4 / R5
Yes → manager reviewAmount ≤ £500
No → budget-owner reviewAmount > £500
Approved → recordR6
Rejected → notify requesterR3 / R5 / R7
Source rule: each reviewer may approve or reject. Review is not automatic approval.
Read the complete example prompt
Create an editable purchase-request flowchart from the fictional rules below.
Return Mermaid source in a .mmd file, an SVG preview and a plain-language path list.
Use readable labels and show the source rule ID on each relevant branch.
Preserve the £500 equality boundary, missing-detail return and rejection routes.
Review is not automatic approval. Keep any sequencing that the rules do not
establish as an explicit question; do not invent an extra policy or authority.
FICTIONAL SOURCE RULES
R1: Staff draft a request.
R2: Missing detail returns to staff.
R3: The manager can reject a request.
R4: The manager may approve an amount of £500 or less.
R5: Above £500 the budget owner reviews and may approve or reject.
R6: An approved request is recorded.
R7: A rejection is communicated to the requester.
CHECK THE ACTUAL FILE
Trace missing details, £500 exactly, £501, and a manager rejecting a £400 request.
Compare each path with the relevant supplied rule. Do not certify the process
or implement an approval workflow. Keep the diagram words and nodes editable.Check the AI technique
Check AI’s diagram against the actual rules
Compare source-bound and faulty drafts using independently stated boundary cases.
Read the check or repair request
Create an editable purchase-request flowchart from the fictional rules below.
Return Mermaid source in a .mmd file, an SVG preview and a plain-language path list.
Use readable labels and show the source rule ID on each relevant branch.
Preserve the £500 equality boundary, missing-detail return and rejection routes.
Review is not automatic approval. Keep any sequencing that the rules do not
establish as an explicit question; do not invent an extra policy or authority.
FICTIONAL SOURCE RULES
R1: Staff draft a request.
R2: Missing detail returns to staff.
R3: The manager can reject a request.
R4: The manager may approve an amount of £500 or less.
R5: Above £500 the budget owner reviews and may approve or reject.
R6: An approved request is recorded.
R7: A rejection is communicated to the requester.
CHECK THE ACTUAL FILE
Trace missing details, £500 exactly, £501, and a manager rejecting a £400 request.
Compare each path with the relevant supplied rule. Do not certify the process
or implement an approval workflow. Keep the diagram words and nodes editable.