ChatDiagram
workflow · document control

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.

Type Réseau de PetriNorme Murata 1989 + ISO/IEC 15909-1Moteur schematex-petriMis à jour 24/09/2026
Document review cycle
Drawing preview
La demande

“Create a Petri net for a document review cycle with a draft submitted for review, then either approved or returned for revisions before resubmission.”

Essayez ensuiteAdd a legal review before approval.Add a token for two documents awaiting review.
Ce que contient ce dessin

Comprenez les décisions qui le sous-tendent.

01Starting token

The draft place holds the initial token.

02Review branch

Approval and revision are alternative outcomes from review.

03Feedback loop

Revisions return the token to a new draft.

04End state

Approval leaves the token in a completed place.

Use this small net to explain a review loop before adding roles, deadlines, or parallel approvals.

Voir tous les modèles de réseau de Petri →

FAQ

Questions fréquentes

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.