What this is
What is an approval workflow record?
What is an approval workflow record?
It is a standalone engine that captures a multi-signature decision as a sequence of steps rather than a single sign-off box on the record being approved. Each step names the role required, the person who filled it, their decision and the date. It exists so approval sequencing is defined once and reused, instead of being redrawn inside every template that needs staged sign off.
What does approver independence mean here?
It means the person approving did not do the work being approved and does not report to the person who did. The record asks this directly for every step because a supervisor rubber-stamping their own team's output is a signature, but not a check. Independence is what turns a signature into evidence.
What is delegated authority, and why is it tracked separately from the decision?
Delegated authority is when someone signs on behalf of the named approver because that person is unavailable — a deputy manager approving in the manager's absence, for example. The decision field records what was decided; the delegation fields record whether that authority was actually granted and documented, because an undocumented delegation is functionally the same as an unauthorised signature.
Scope
When is an approval workflow record required?
This is a routing engine, not a decision record in its own right. It exists to sit behind other templates and hold their approval sequence; using it to record the substance of a decision, rather than who signed off on one, produces records nobody can report against.
Use this template when
- A record — a change, a waiver, a purchase, a plan — needs more than one signature before it takes effect
- The order signatures are collected in actually matters, because a later approver can still stop what an earlier one accepted
- You need to prove an approver was independent of the work, or that a delegation was properly authorised
- A linked template declares that it needs staged approval and expects this engine to hold the routing
- You are consolidating scattered ad-hoc sign-off boxes from several templates into one reusable, auditable pattern
Do not use it for
- Waiver and Concession Record, which records a decision to accept a deviation, not the signatures that authorised it.
- Management Review Record, which is a scheduled governance meeting output, not a staged sign-off chain.
- Escalation Record, which routes a stalled or overdue item upward rather than sequencing planned approvals.
- Corrective and Preventive Action, which is the action record itself; approval of its closure belongs here, not inside it.
- Any single-signature acknowledgement — a read-and-understood confirmation does not need a routed, multi-step engine.
Compliance mapping
Which ISO 9001 cl.7.5 requirements does this satisfy?
ISO 9001's documented information clause is the anchor, but the record also draws on how the standard assigns authority — a review sequence is only as sound as the roles behind it.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.7.5.3 | Documented information must be approved for adequacy prior to issue | Header |
| ISO 9001 cl.5.3 | Roles, responsibilities and authorities must be assigned and understood | Approvals |
| ISO 9001 cl.5.3 | Authority delegated in an approver's absence must be recorded, not assumed | Approvals |
| ISO 9001 cl.7.5.3 | Documented information must be identifiable and retrievable, including its predecessor record | Header |
| ISO 9001 cl.9.1.3 | Data on process performance — here, time to complete approval — must be analysed | Outcome |
| ISO 9001 cl.10.2 | Where a decision points to a nonconformity or gap, corrective action must be raised and tracked to closure | Outcome |
What it does not cover
- Steps Taken In Order marked No, which means the sequence was defeated regardless of how many valid signatures exist.
- Approver Independent Of The Work marked No with no compensating step, which turns the signature into self-certification rather than review.
- Delegated Authority Used marked Yes with Delegation Recorded left blank or No, which is an unauthorised signature wearing an authorised one's name.
- Work Started Before Approval marked Yes, which means the approval documents a decision already made in practice, not one still open to being stopped.
- Final Status left as Complete with All Steps Complete marked Partly, which closes the record before the routing it was built to enforce has actually finished.
Global
Approval Workflow Record requirements by country
ISO 9001 sets the approval principle everywhere it is adopted, but three regimes shape how strictly a staged sign-off has to be evidenced in practice.
ISO 9001:2015 cl.7.5.3 and cl.5.3
Certification bodies expect approval evidence to show adequacy review before issue and traceable authority, not just a name in a box.
An auditor sampling this engine will ask for the sequence and the independence answer, not just the final signature.
FDA 21 CFR Part 11 — electronic records and electronic signatures
Where the approved record feeds a regulated process, each electronic signature step needs its own authenticated, time-stamped, non-repudiable entry.
A shared login or a signature entered after the fact for a regulated approval is a Part 11 finding, not just a housekeeping gap.
UKAS-accredited ISO 9001 certification
UKAS auditors treat delegated authority the same way ISO 9001 does internationally, but commonly probe named-deputy arrangements specifically during site visits.
An undocumented deputy signing routinely, rather than occasionally and on record, is a recurring UK audit finding.
How to complete it
How to complete an approval workflow record, step by step
Filling in the fields is mechanical. Deciding whether the resulting approval actually means something takes judgement in four places.
Approval Route offers single, two-stage, three-stage or committee. Adding stages for their own sake slows every record down without adding a check; the honest question is whether a later approver could plausibly overturn an earlier one's decision, not how senior the topic feels.
Small sites sometimes have no genuinely independent approver available. That is a real constraint, not a reason to mark Yes anyway — record No, note why, and route the decision one level higher instead of pretending the check happened.
One documented delegation during genuine absence is unremarkable. The same deputy signing every time the named approver is nominally on leave is a sign the role, not the person, needs re-assigning.
Marking this Yes should not be treated as a formality to tidy up later. It means the approval step, wherever it sits in the route, no longer has the power to stop anything — so the judgement call is whether the record should still proceed to Approved, or whether it needs to be reopened as a concession instead.
What auditors find
Most common approval workflow record findings
The same six gaps account for most of the findings raised against this engine, usually surfaced when a spot-check compares the approval record against the timeline of the work it covers.
| Finding | Clause | What fixes it |
|---|---|---|
| All signatures dated the same day, on the day the underlying work was completed | ISO 9001 cl.7.5.3 | Route the record before the work starts and require each Decision Date to reflect when that step's reviewer actually looked at it. |
| Approver Independent Of The Work answered Yes for someone named elsewhere on the record as having done the work | ISO 9001 cl.5.3 | Cross-check the approver against the record's own author or actioning fields before accepting the independence answer; reroute if they match. |
| Delegated Authority Used marked Yes with no corresponding entry anywhere for who authorised the delegation | ISO 9001 cl.5.3 | Require a reference to the delegation authorisation — a role description, a standing instruction, or a dated note — before Delegation Recorded can be marked Yes. |
| Step Number sequence has gaps or repeats across approvers on the same route | ISO 9001 cl.7.5.3 | Renumber steps consecutively from one and block a second entry at the same step number for the same route. |
| Final Status set to Approved with conditions but no condition text or follow-up action anywhere on the record | ISO 9001 cl.10.2 | Require Action Required to be answered whenever Final Status is Approved with conditions, and reject Complete until it resolves. |
| Days To Complete left blank on records that took months to route | ISO 9001 cl.9.1.3 | Calculate the field automatically from the first and last Decision Date rather than relying on manual entry. |
Case in point
Case in point: the deputy who never stopped deputising
A change request needed manager sign-off, then site manager sign-off. The manager was on long-term leave, so their deputy signed every request for four months. Each individual record showed Delegation Recorded as Yes, correctly, because a genuine handover note existed at the start of the leave.
What the individual records did not show, because nothing forced the comparison, was that the same deputy had effectively become the permanent first-stage approver — including for changes affecting their own team. Reviewing the approval records as a set, not one at a time, is what surfaced it; the fix was a role reassignment, not a training reminder.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- FDN-028
- Archetype
- Engine
- Record ID
- APPR-2026-000
- Scoring
- Approvals complete
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 9001 cl.7.5
- Links
- Used by any template needing staged approval
- Tags
- Engine, Approval
- Sections
- 4
- Fields
- 34
- Follow up fields
- 3
- Repeating sections
- 1
- Links out
- 3
Header
10 fieldsApproval ID*
Auto sequence. Format APPR-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Order Matters
Approvals collected out of order let somebody sign off work that a later approver would have stopped. This engine records the sequence as well as the signatures.
Record Being Approved*
Record ID*
Immediate predecessor record
Approval Route*
Approvals
Repeats9 fieldsStep Number*
Role Required*
Approver*
Decision*
Decision Date*
Comment
Approver Independent Of The Work*
- Yes3 pts
- No0 pts
Delegated Authority Used
- No3 pts
- Yes1 pt
Delegation Recorded
- Yes3 pts
- No0 pts
Related records
1 fieldEscalation ID
Where an approval stalled and was escalated.
Links to FDN-029 Escalation ID
Outcome
14 fieldsAll Steps Complete*
- Yes3 pts
- Partly1 pt
- No0 pts
Steps Taken In Order*
- Yes3 pts
- No0 pts
Any Step Skipped*
- No3 pts
- Yes0 pts
Final Status*
- Approved3 pts
- Approved with conditions2 pts
- Declined0 pts
- Withdrawn1 pt
Days To Complete
Work Started Before Approval*
- No3 pts
- Yes0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Requester*
Signature*
Final Approver*
Second Signature*
FDN-028 · record IDs look like APPR-2026-000 · Used by any template needing staged approval
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The form is the easy part. Keeping the route current, chasing the next approver and holding the evidence together is the work that actually slips.
Watches open approval routes, nudges the next approver in sequence rather than everyone at once, and flags any record where a step was signed out of order.
Rolls approval sequencing and delegation evidence into the wider governance picture, so a repeated deputy pattern shows up at portfolio level, not just on one record.
Ties approval records back to the documents and changes they authorise, keeping the adequacy-before-issue check visible alongside the document control trail.
Surfaces routes stuck at a stage past their expected time, so a stalled approval gets escalated before it quietly becomes a work-started-before-approval finding.
This template lives in General — control tower. The orchestration layer. Registries and engines every other workspace reads from.
Meet General→Glossary
Approval Workflow Record definitions and key terms
- Approval route
- The declared sequence of stages — single, two-stage, three-stage or committee — a given record must pass through before it is considered approved.
- Staged sign-off
- An approval built from more than one sequential decision point, where a later approver can still stop what an earlier one accepted.
- Approver independence
- The condition that the person approving did not perform, and does not manage the person who performed, the work under review.
- Delegated authority
- Sign-off given by a documented deputy standing in for the named approver, distinct from that approver acting directly.
- Sequence integrity
- The property that approval steps were both completed and completed in their declared order, tracked here as a field separate from completion alone.
FAQ
Frequently asked questions about approval workflow record
Does every record in the library need its own approval routing?+
No. Most single-signature acknowledgements do not need this engine at all. It exists for the smaller set of decisions — changes, waivers, high-value purchases — where more than one person genuinely needs to check the decision before it stands.
What happens if an approver declines partway through the route?+
The step is recorded as Declined with its own comment, and the route stops there rather than continuing to later stages. Final Status should reflect Declined or Withdrawn; it should not show Approved with a declined step buried earlier in the sequence.
Can the same person appear at two stages of one route?+
The form does not block it structurally, but it usually defeats the purpose of a multi-stage route, and the independence question should catch it — the same person cannot honestly be independent of their own earlier decision.
Why does the engine track escalations separately rather than as another approval step?+
An escalation happens because the route stalled, not because a new approver was always intended to be part of it. Keeping it as a linked Escalation Record rather than an approval step keeps the routing logic clean and the delay visible.
Is a verbal approval acceptable if it is written up afterwards?+
It can be recorded, but Escalated In Writing-style honesty matters here too: note that the decision was given verbally and documented after the fact, rather than backdating it to look like a contemporaneous written approval.
Does completing every step guarantee the record passes an audit?+
No. An auditor sampling this engine checks the sequence, the independence answers and whether work started early, not just whether every box has a name in it.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Management System Governance
Legal and Other Requirements Register
Lists every law, regulation, permit and commitment that applies to your operation
Compliance Obligation Assessment
Assesses how each legal requirement applies to you and what you do to meet it
Compliance Evaluation Record
Records the periodic evaluation of whether you actually comply with each obligation
Regulatory Change Record
Records a change in law or regulation and what it means for you
Regulatory Inspection Record
Records a visit by a regulator, including what was inspected, what was said and any orders issued
Management Review Record
Records the periodic review of the management system by senior leadership, covering performance, risks, resources and improvement
More in Engines
Risk Assessment
The single risk assessment used across the whole business
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 cl.7.5.3 — Control of documented information
- ISO 9001:2015 cl.5.3 — Organizational roles, responsibilities and authorities
- ISO 9001:2015 cl.10.2 — Nonconformity and corrective action
- FDA 21 CFR Part 11 — Electronic records; electronic signatures
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.