Zoikorum™
APPROVAL WORKFLOWS · MULTI-LEVEL APPROVALS

Get every governed decision to the right authority.

ROUTE GOVERNED DECISIONS TO AUTHORIZED APPROVERS.

Route professional-services decisions through explicit approval paths connected to policy, contracts, milestones, changes and supported payment states. Approvers get the context they need; the engagement keeps a clear record of who decided what, when, and under which authority.

Approval Workflows
Procurement Lead
Procurement LeadApproved · 10:42
Budget Owner
Legal
Budget Owner + Legal1 of 2 · In review
Execution readinessSystem state · upcoming

Stage 2 · Budget Owner + Legal — Required · parallel · all required. Budget Owner approved; Legal pending.

1 of 2
DECISION REQUEST · CONTRACT APPROVAL

External Finance Advisory

ILLUSTRATIVE
OBJECTContract v4 + SOW v2
WHY REQUIREDPolicy Profile “Regulated Advisory” - commercial threshold
Stage 2 · 1 of 2 complete
BUDGET OWNERAPPROVED · 11:06
LEGALPENDING · DUE OCT 2
Changed since prior version:Fee capLiability clauseDelivery date

Explicit authority

Know which role or authority is required for the decision.

Context attached

Approvers see the object, version, trigger and evidence.

Version-aware

Approval stays connected to the exact version decided.

Decision evidence

Decisions and material routing events create a durable record.

Controlled exceptions

Explicit authority and evidence; no hidden bypass.

APPROVAL CHAIN STATES

Five states, always labelled in words.

Shared across Contracts & Controls. A state describes the scope of an authoritative workflow decision — nothing more.

Not required
Not required

No approval is required for this decision under the current configuration.

Pending
Pending

A required approver decision has not yet been recorded.

Approved
Approved

Required approvals are recorded for this exact version.

Rejected or returned
Rejected or returned

The decision was rejected or returned for changes; history is kept.

EXCEPTION
EXCEPTION

Handled through an explicit, permissioned and recorded exception path.

WHY APPROVALS FAIL

Approvals scattered across email create uncertainty.

Authority implied by job titleA title isn't proof of decision authority.
No link to the version decidedA changed contract can quietly inherit a stale approval.
Context lives somewhere elseApprovers reconstruct what changed from threads and attachments.
Silence becomes a decisionTimers and reminders turn into unofficial bypasses.
Approvals scattered across email
WHERE APPROVAL WORKFLOWS APPLIES

Governed decisions, where configured.

Representative decision points across the engagement. Not every engagement requires every approval.

Contract execution
CONTRACT EXECUTION

“Is this exact contract/SOW version approved for signature?”

DOWNSTREAM EFFECT

May unlock execution readiness when all required conditions are satisfied.

APPROVAL PLAN

The resolved route for one decision.

An Approval Plan is derived from authorized rules and context, then frozen for the request unless a governed re-plan event occurs. Select a stage.

Approval Plan · Plan version 3

Recommended implementation · illustrative
In progress · Stage 2
TRIGGERContract v4 submitted for execution readiness
POLICY INPUTSRegulated Advisory v6 · Spend Control v2
FALLBACKAuthorized delegate where active
ESCALATIONReminder → approved escalation contact · no auto-approval
REAPPROVALMaterial contract fields changed → new request, prior approval superseded
STAGE 2

Budget Owner + Legal

ROUTING MODEPARALLEL · ALL REQUIRED
REQUIRED AUTHORITYCOMMERCIAL AUTHORITY + LEGAL REVIEW ROLE
COMPLETIONBOTH MUST APPROVE
STATUS1 OF 2
EVERY PLAN RECORDS

Decision request ID

Stable, with no sensitive meaning encoded.

Subject + version

The exact authoritative object reference.

Trigger

Rule/version or explicit manual authority.

Plan version

Immutable; changes create a re-plan event.

Steps

Order, mode, authority, completion condition.

Current state

Pending, in review, completed, blocked...

Evidence refs

Pointers — not cloned sensitive content.

Downstream action

What may proceed after completion.

HOW IT WORKS

Trigger. Route. Decide. Resolve. Record.

Select a step to see what the system is responsible for.

DECISION PACKET · APPROVER WORKSPACE

Everything needed to decide — in one place.

Try a decision. Returns and rejections need a reason, and a newer version blocks decisions on stale context.

Contract approval · Contract v4 + SOW v2In reviewILLUSTRATIVE
CONTEXT
ENGAGEMENT + OBJECTExternal Finance AdvisoryContract v4 + SOW v2 · owner: Requester
PROFESSIONAL / FIRMExample Advisory LLC (demo)
COMMERCIAL CONTEXT - AUTHORIZED[Amount] · cost center [ID]
JURISDICTION / SERVICERegulated advisory - [jurisdiction]
DECISION
WHY APPROVAL IS REQUIRED

Policy Profile “Regulated Advisory” v6 requires legal review for this service category · commercial threshold crossed.

MATERIAL CHANGES · V3 → V4
FEE CAP{PRIOR CAP}{NEW CAP}
LIABILITYCLAUSE 9 (PRIOR)CLAUSE 9 (REVISED)
DELIVERY{PRIOR DATE}{NEW DATE}
DECISION IMPACT

If approved, Legal’s step completes and execution readiness is signaled to Contracts. Signature remains a Contracts action.

AI-generated summary. Review the source contract, policy explanation and evidence before deciding.
ROUTE
1 · Procurement LeadApproved
2a · Budget OwnerApproved
2b · Legal (you)In review
3 · Execution readinessUpcoming
AUTHORITY BASISOrganization approval policy · legal review role
DEADLINE / ESCALATIONDue Oct 2 · reminder, then approved escalation contact. Never auto-approves.
AUDIT PREVIEWDecision, actor, authority basis, version, timestamp
Multi-level routing models

Five ways a decisioncan travel.

Recommended routing patterns. They appear in the product only where implemented and approved.

PARALLEL — ALL REQUIRED
Recommended
Request
Approver AAPPROVED
Approver BPENDING
Approver CAPPROVED
2 of 3ALL REQUIRED
Completion ruleALL REQUIRED APPROVERS IN THE STEP MUST APPROVE.
UX requirementSHOW X OF Y DECISIONS; IDENTIFY PENDING ROLES WITHOUT UNNECESSARY PERSONAL DATA.
Authority type

Role or authority scope — not a free-form job title.

Decision set

Approve, reject, return for changes; optionally request context.

Due handling

Due date, reminders and escalation. No auto-approval by timeout.

Conflict rule

Optional separation-of-duties check — never silently waived.

CONTRACTS, SOWS & CHANGE CONTROL

Approve the exact version — and know when it changes.

Explore Contracts
Draft ready for review
A decision request can be created that references the exact contract/SOW version.
Approved version
Decision evidence points to that version; Contracts controls execution readiness.
Material edit after approval
Contracts signals the change; configured reapproval rules can supersede the stale approval.
Change order
The new change object receives its own approval path when required.
Signature
Signature belongs to Contracts. Approval completion is not itself a signature.
Executed agreement
Historical approvals stay immutable; amendments create new governed decisions.
Approve exact version
EXAMPLE WARNING

Contract v5 was created after Legal’s review of v4. The v4 approval is preserved in history; v5 needs its own decision.

MILESTONES, ACCEPTANCE & PAYMENT

A decision, not money movement.

Payment Protection

Milestone acceptance

APPROVAL WORKFLOWS

Routes acceptance authority, shows evidence, records the decision.

OWNING DOMAIN

Milestone and engagement state updates acceptance.

Payment release prerequisite

APPROVAL WORKFLOWS

Records required business approval where configured.

OWNING DOMAIN

Payment Protection validates conditions and executes or blocks release.

Active dispute

APPROVAL WORKFLOWS

Shows that a decision may be blocked or routed differently.

OWNING DOMAIN

Dispute / Payment Protection own hold and resolution.

Refund / cancellation

APPROVAL WORKFLOWS

May route a required authority decision if configured.

OWNING DOMAIN

Refund & Cancellation applies policy and financial action.

DELEGATION & ESCALATION

Availability handled — without authority leakage.

Delegation and escalation

Delegation is time-bounded, scoped and recorded

EligibilityThe delegate must already satisfy the required authority scope.
Effective windowStart and end time; optional immediate revocation.
ScopeSpecific approval types, units, amount bands or categories.
EvidenceOriginal authority, delegate, delegation reference, timestamp.
VisibilityRequester sees the route is active; professionals see only safe status.
Failure stateNo eligible delegate? The request stays pending and escalates.
DEADLINES, REMINDERS & ESCALATION
Overdue state shown; re-notify, and notify the requester if appropriate.
Inaction never becomes an approval.
ENTERPRISE OPERATING MODEL

Configure routes. Keep authority where it belongs.

Request Enterprise Demo

Organization governance

Define which units, spend bands, service categories and risks require approval.

Authority administration

Maintain approver roles and scopes, budget ownership and acceptance authority.

Workflow configuration

Reusable route templates and escalation — without granting decision authority to admins.

Engagement execution

Create decision requests from real engagement objects; surface progress.

Evidence & review

Retain decision evidence; route cross-engagement reporting to Audit & Reporting.

Continuous improvement

Privacy-safe aggregate analytics to reduce unnecessary approvals while keeping required controls.

REQUESTER, APPROVER & PROFESSIONAL

Fast for every side — safe for each one.

Requester, Approver & Professional

For approvers

A queue ordered by actionability and due state, not notification noise.
A decision packet with version, changes, reason, evidence, authority and impact.
Approve, reject, return, request context or delegate — only as permitted.
Stale requests are blocked or superseded, so old approvals are never guessed at.
Responsible AI

AI summarizes. Accountable people decide.

AI Transparency
Responsible AI

AI may assist with

  • Summarizing the decision packet with source links.
  • Highlighting material changes between versions.
  • Drafting a rationale for the approver to edit or accept.
  • Prioritizing the queue using transparent operational factors.
  • Suggesting missing context before review.

AI must never silently

  • Submit an approval, rejection, exception or payment decision as the accountable actor.
  • Invent policy reasons, authority or evidence.
  • Conceal uncertainty or omit contradictory sources.
  • Rank decisions using sensitive traits or opaque criteria.
  • Override separation-of-duties, delegation or authority constraints.
Disclosure: “AI-generated summary. Review the source contract, policy explanation and evidence before deciding.” The final action is attributed to the authenticated accountable actor.
Right authority
Right authority
Exact version
Exact version
Durable record
Durable record
QUESTIONS

Approval Workflows, answered.

Approval Workflows FAQ
Talk to Sales
GET STARTED

Every decision, to the right authority.

See how approval plans, decision packets and durable evidence fit your organization.

Every decision to the right authority

Routing patterns, delegation and escalation shown here are recommended designs and appear in the product only where implemented and approved. Approval Workflows records business decisions; it does not move money or sign agreements. Approval status represents the scope of an authoritative workflow decision; it does not replace legal, regulatory, procurement or professional judgment and does not by itself execute payment or milestone acceptance.