WORKFLOW
Document review cycle Petri net
A document review cycle Petri net shows the states a document passes through and the events that move it forward. A token starts in Draft ready. Submitting the document moves it into review. From there, the reviewer can approve it, placing the token in Approved, or request changes. The revision path returns the token to the draft so the author can resubmit it.
Make this diagram your own.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
CASE ANALYSIS
Scenario
A team needs to show that a reviewer can approve a document or return it for revision.
Key decisions
- Starting token: The draft place holds the initial token.
- Review branch: Approval and revision are alternative outcomes from review.
- Feedback loop: Revisions return the token to a new draft.
- End state: Approval leaves the token in a completed place.
When to reuse this
Use this small net to explain a review loop before adding roles, deadlines, or parallel approvals.
FAQ
Frequently asked questions
What does the token represent?
It represents one document moving through the review process.
Why does the revision path return to Draft?
After changes are made, the document is ready to be submitted and reviewed again.
Can this show several reviewers?
Yes. Add places and transitions for each review stage or parallel review path.
RELATED EXAMPLES
More workflow examples
MAKE YOUR OWN
Try the diagram makers.
Open this example in the editor →
Tweak it with chat, export PNG/SVG, or fork it for your own use case.
petri-document-review-cycle