Document approval workflow decision tree template
A document approval workflow decision tree: editorial or substantive change, mandatory reviewers by document type, second approver, and training on release.
How it works
Rename the lanes to your real decision rights
The four lanes name who answers each question: Author, Document owner, Reviewers and Approver. Replace them with your own roles, named by role rather than by person so the chart survives leavers and reorganisations. If your quality manager is both the document owner and the approver, merge those lanes rather than pretending the decision is split. If technical and regulatory review are answered by different people, split the Reviewers lane in two.
Write the editorial test in one sentence
The 'Editorial or substantive change?' decision is the one people abuse, because it is the only route that skips review and approval. Write a test anyone can apply: if a reader would do anything differently as a result of the change, it is substantive. Then list the accepted editorial cases explicitly, for example typographical fixes, formatting, a renamed department and corrected cross-references, and state that the document owner, not the author, decides.
Fix the mandatory reviewer set per document type
Turn 'Regulated document type?' into a short table your document register can answer from a field rather than from memory. For each type, name the reviewers who must sign and the ones who are optional. Regulated typically means the document sits inside the scope of a management system, a licence or a safety case; if you cannot decide a document's type from its register entry, the decision will be made inconsistently.
Set the trigger for a second approver
Second approvals should be triggered by a property of the document, not by nervousness. Common triggers are a regulated document type, a legal or safety commitment, and a document outside the first approver's delegated authority. Record the trigger next to the decision and name the role that provides the second approval, so the chart tells people who to send it to rather than only that someone else is needed.
Decide when rework ends the cycle
The 'Can the author resolve now?' decision keeps drafts out of an unbounded review loop. Agree what can be closed in the current round, typically wording, clarification and formatting, and what cannot, typically anything needing new content, new data or a decision the author is not authorised to make. Anything in the second group returns to the author as rework and re-enters at intake rather than looping.
Set the read-and-understood rule and store the evidence
Require read-and-understood where the change alters what someone must actually do in a safety-critical, regulated or customer-facing step, and not for formatting or wording. Decide before release where the acknowledgement is stored and how long it is retained, because that record, not the approval itself, is what demonstrates that people are working to the current revision.
Frequently asked questions
What is a document approval workflow?
It is the routing a draft follows between being written and being released: classifying the change, selecting the reviewers who must see it, resolving their comments, obtaining approval, and deciding what release obliges other people to do. It is a decision structure rather than a task list, because the interesting part is not that a review happens but which review happens and who is entitled to decide. A workflow that always applies the same route to every document is not a workflow; it is a queue.
How is this different from a document control process flowchart?
Scope and shape. The document control process flowchart is a cross-functional process map covering the full lifecycle, including version numbering, issue to a controlled location, withdrawal of superseded copies and scheduled periodic review, and it answers what happens next and who does it. This page is the decision tree for the review-and-approve segment only, and it answers which route a document takes and who decides. If you are writing a procedure, you probably want both: the process map for the lifecycle, and this chart as the routing rules inside its approval stage.
When can a change be approved as editorial and skip full review?
Only when the meaning does not change. Typographical fixes, formatting, a renamed department and corrected cross-references qualify; anything that changes what a person must do, in what order, with what limits or against what acceptance criteria does not, however small the edit looks. Two guards keep the route honest: only a revision to an existing document can be classified as editorial, and the document owner makes the call rather than the author. Record the classification, because it is the first thing an auditor will test.
Do we need two approvers on a document?
No standard requires two approvers as a general rule. ISO 9001:2015 clause 7.5.2 requires documented information to be reviewed and approved for suitability and adequacy before issue, but it does not say by how many people. Sector rules are stricter in specific cases, for example pharmaceutical manufacturing requires the quality unit to approve production and process control procedures. The practical rule is to trigger a second or regulatory approver by document property, such as a regulated type, a legal or safety commitment, or a document outside the first approver's delegated authority.
Does an electronic approval count as a signature?
In most commercial contexts, an auditable approval record naming the approver, the version and the date is sufficient. In FDA-regulated contexts, 21 CFR Part 11 sets specific conditions: a signed electronic record has to show the printed name of the signer, the date and time of signing and the meaning of the signature, such as review or approval, and the signature must be linked to its record so it cannot be excised, copied or transferred. Confirm which regime applies before you assume a click-through approval is enough.