ISO ARTICLES DIGITAL ISO SYSTEMS & WORKFLOW AUTOMATION ARTICLE 126

Designing Digital Approval Paths With Clear Accountability

Create authorization pathways that preserve decision rights, independent review, delegation and evidence—even when workflows cross functions and locations.

ISO Toolkits Editorial Team Digital management systems & controlled workflows

A digital form moves swiftly from request to green Approved status. Yet the organization cannot explain whether the person who approved it had the authority to accept the risk, whether technical evidence was reviewed or who can reverse a mistaken authorization. Speed does not resolve accountability. A trustworthy digital approval route distinguishes preparing information, recommending a decision, authorizing a release, verifying its effectiveness and escalating an exception. Those actions may require different roles and evidence.

Photo pending: Operations and compliance managers reviewing who is authorized to approve high-risk process changes

Q1Which decision does the approval actually authorize?

State what is being authorized and the consequence if the decision is wrong. Approval of a noncritical training announcement may require a line manager. Approval of an environmental permit exception or product deviation may require legally defined or specialized authority. The route should reflect the actual control objective, not the software default.

Document the decision’s prerequisites: current document version, completed analysis, competent reviewer, acceptance limits and stakeholder notification. Avoid a generic Approval field that means “seen” for one group and “authorized to operate” for another.

Create a stable approval definition in the process documentation and user guidance. Where a standard requires controlled documented information, the organization still determines suitable responsibilities and controls; the standard does not automatically prescribe one universal electronic signature sequence.

Technical context: ISO 9001:2026 — Quality management systems — Requirements is one verified source for the concepts discussed here.

Q2How do recommendation and authorization differ?

A process owner may prepare a risk treatment and recommend it for acceptance. A more senior risk owner may be responsible for accepting residual exposure. An independent quality reviewer may verify evidence. Those distinctions should be evident in workflow status and record history.

Implement segregation where self-approval would undermine credibility or violate a binding requirement. Define exceptions for small teams with compensating checks rather than forcing an impossible organizational structure. Record both the authority and the reason for any approved variance.

Avoid cascading identical approvals merely for reassurance. Each signer should contribute a different judgment. A supervisor acknowledgement does not replace technical assessment, and a quality verification does not transfer the operational decision from the accountable manager.

At each control transition, describe what authority does not mean. A department head may approve funding for a corrective action without verifying technical adequacy; a process engineer may confirm a proposed solution without accepting contractual exposure. The digital system should show those separate decisions through their labels, permissions and retained evidence. When a signer sees only “Approve,” ask whether the specific question being answered is evident from the record without reconstructing the entire email discussion.

Consider the use of group approvals carefully. A shared mailbox or generic department role may help route work, but it should not obscure which person exercised a binding decision. The record should identify the human or controlled system event and the authority applied. Where a committee makes a decision, preserve the agreed decision rule and evidence of the outcome. Do not substitute a service account’s successful API call for the substantive approval of a competent person.

Q3How should temporary delegation be governed?

Delegation needs a defined source, start date, expiry, scope and evidence of authorization. During leave, an acting manager may approve certain documents but not contractual price deviations or safety-critical exceptions. A copied role without boundaries can create unauthorized powers.

Connect identity management and business roles carefully. HR job title alone often does not reflect site qualification, temporary assignment or organizational separation. Use an approved authority matrix and limit privileges to the task. Review permissions when an employee moves, leaves or changes responsibility.

ISO/IEC 27001 and ISO/IEC 27002 provide information security management requirements and relevant control guidance. A digital approval route must also reflect its own risk assessment, applicable law and customer obligations rather than treating access-control guidance as an automatic signature-law solution.

Approval history should preserve the proposal as it existed at the time of decision. When a requestor edits supporting evidence after an approval, the system may need to reopen authorization rather than allowing the old signature to float onto new content. Define which field changes are material and who can make that determination. For sensitive concessions, a new review may be necessary even if the headline request title remains unchanged.

Q4What happens after rejection or urgent escalation?

Not every approval is a straight line. A reviewer may reject evidence, request revision, ask for more analysis or refer the decision to another authority. Distinguish these statuses so a request does not appear approved simply because it left an inbox.

For urgent work, establish what can proceed, which interim controls apply, who authorizes the exception and when it must be reviewed. Do not let a timer grant approval automatically unless the specific obligation genuinely permits deemed consent. Silence is often an inadequate basis for significant risk acceptance.

Record the original request and each returned version. A resubmitted item should identify which evidence changed, allowing the approver to review the new decision rather than accidentally endorsing an older attachment.

Photo pending: Site supervisor verifying documented sign-off and delegated authority for a safety-relevant corrective action

Q5Which approval evidence can be reconstructed?

An audit trail should record the person or service identity, authorized role, object and version, action, timestamp, reason and required evidence. For sensitive decisions, ensure logs are protected against unauthorized alteration and can be retrieved by independent reviewers.

Differentiate a human decision from an automated rule execution. A system can check completeness or apply an approved threshold, but where professional judgment is required the record should identify who exercised it. Logging that “the system approved” may be inadequate to explain delegated accountability.

Check the evidentiary status of electronic signatures under applicable laws and contracts. Do not assume that clicking a button automatically satisfies a jurisdiction-specific statutory signature or identity-verification duty.

Q6How are multi-site and unusual cases tested?

Create test cases for a retired approver, an incorrect role, two simultaneous revisions, a withdrawn request and a site-specific local approval. Attempt to authorize an item without the required evidence and confirm that the application blocks or flags the action as designed.

In a multi-site management system, central approval and local release may be separate events. A global procedure may be approved centrally while each site confirms training and version availability. Show this distinction in status rather than hiding local deployment after a corporate green badge.

Include access logging, record export and fallback when identity services are temporarily unavailable. Test both denied and successful transactions, and inspect the actual evidence produced for each.

Segregation review should cover the technical paths available to administrators, connectors and delegated users as well as the everyday approval screen. A user might be unable to approve their own request in the interface yet trigger an API transition using a broad service credential. Verify the denial, logging and exception handling through direct tests. These checks demonstrate whether accountability survives the actual architecture rather than existing only in the delegation policy.

Decision domainOwner or objectiveObservable evidence
Decision typeProcess ownerAuthority and acceptance rule
SegregationQuality and complianceReviewer/approver separation
DelegationPeople and identity governanceScope, effective period and expiry
Audit trailRecords stewardIdentity, version, decision and reason

Q7What demonstrates decision quality after launch?

Approval cycle time is a useful workload indicator, but not a full measure of effectiveness. Track misrouted cases, unauthorized overrides, repeated resubmissions, late escalations and post-approval failures attributable to missing review. Analyze cause instead of rewarding teams for clicking faster.

Assign an owner to review exceptional delegations and role conflicts. A platform administrator should not unilaterally expand business authority through technical configuration. Changes to approval logic should follow governance, testing and version control.

If repeated exceptions reveal ambiguous decision rights, update the authority matrix and relevant process rather than adding another reminder. The finished workflow should make decisions understandable to the next manager who needs to rely on them.

Temporary emergency authorization is particularly sensitive in distributed organizations. Define who may invoke it, which obligations cannot be bypassed, which conditions must be logged and when a retrospective review is mandatory. For example, urgent replacement of a critical component may need an independent technical acceptance and notification to the customer even if an ordinary manager is unavailable. A fast digital override must not make those protections disappear merely because the workflow deadline expired.

Review the evidence after a normal operational cycle: were approvals routed to the right people, did delegated powers terminate, did rejected cases remain blocked, and were decisions based on current versions? A high approval rate is not proof of effective governance. Sample actions that were withdrawn, reopened or escalated, since those reveal whether the system can preserve accountability when conditions differ from the original expectation.

Treat a change to approval authority as a management-system change even when it is technically simple. The approving business owner should confirm its scope, any affected customer or legal requirements and the impact on pending cases. Test whether old transactions remain historically intelligible after the role change. For emergency administration, retain the reason and independent review of privileged action. These precautions prevent later auditors or managers from confusing historical authorization with powers granted to a role at the time they inspect the system.

Practical Review Questions

  • Could the requestor approve their own high-risk exception?
  • Does delegated authority expire and follow employment changes?
  • Does rejection retain its original evidence and reason?
  • Can an independent reviewer reconstruct an approval after two years?

Build an authorization-control test suite

Choose one approval route with financial, customer or safety implications. Draw its distinct recommendation, authorization and verification stages, then build a test record for role changes, rejection, expired delegation and urgent exceptions.

Have the accountable business owner and information security reviewer approve acceptance evidence. Test the outcome on the configured platform and retain a clear record of who can change the authorization rules after go-live.

Closing Perspective

Digital approvals should leave a clear answer to three questions: who decided, on which evidence, and under which authority?

References & Further Reading

Official ISO publications and NIST guidance informing the relevant management-system, security, software-quality and records-governance methods. Requirements and guidance are distinct; applicability depends on business scope and risk.

  1. ISO 9001:2026 — Quality management systems — Requirements
  2. ISO/IEC 27001:2022 — Information security management systems — Requirements
  3. ISO/IEC 27002:2022 — Information security controls — Guidance
  4. ISO 15489-1:2016 — Records management — Concepts and principles
  5. NIST SP 800-53 Revision 5 — Security and privacy controls