Zum Inhalt springen

SolutionsApprovals

Project approval workflows with a person on the hook

An approval is a name, a version, and a timestamp. Sigmaviu routes documents, submittals, RFIs, change orders, policies, and work orders to a person, role, or department and keeps the chain.

PMO, document control, and operations leads who route decisions.

Approvals · chain

Live
Four approval stations, with the ball in court on the reviewer.

Approval chain

Ball in court · Reviewer

Author

Complete

Discipline

Complete

3

Reviewer

Waiting

4

Approved

Queued

Escalation armed · 48h SLA · No self-approval
Four approval stations, with the ball in court on the reviewer.

What changes

  1. 01

    The right route for the risk

    Document paths follow risk class. Submittals and RFIs use an ordered chain with revise-and-resubmit.

  2. 02

    No self-approval

    Authors can be blocked from approving their own document, policy, or submitted daily report.

  3. 03

    A nudge when it stalls

    Automations can escalate on your rules, and in-app notifications go to the people you named.

Snapshot

Ball-in-court board

Who is on the hook right now

Sample
ItemStepHolderSLA
SUB-214ReviewerM. Okonkwo18h left
DOC-091DisciplineStructural2d left
RFI-044AuthorField engOverdue
CHG-012ApprovedClosed—

Distribution

On SLA61%
Due soon24%
Overdue15%

How Sigmaviu handles this

Pick a destination

Route to a person, role, or department with a searchable picker. You do not paste an ID.

Ball in court

Submittals and RFIs show who owes the next action and which revision is current.

Timed follow-up

Escalation jobs can remind or move a stalled item. You define the chain. It does not invent one.

One-off routes

A custom path can run once without creating a permanent template named after that matrix.

A working sequence

  1. 1

    Choose the object

    Document, submittal, change, policy, or work order.

  2. 2

    Name the approvers

    Order the people, roles, or departments.

  3. 3

    Decide

    Approve, reject, or send it back. The log keeps the note.

  4. 4

    Move the work

    Approved changes can update cost and schedule. Approved files become the current revision.

Scope

These are the approval paths Sigmaviu already runs for its own records. They are not a general BPM designer for every corporate process outside the product.

Questions buyers ask

Can we test a rule before it runs?

Automation conditions are written in plain language and include a test harness so you can see what would match.

Do approvers get email only?

Routed people get in-app notifications. Scheduled touchpoints use the same in-app pattern, with a reminder per due date.

What if the author is also the manager?

Where separation of duties is on, that person cannot approve their own record unless an admin explicitly allows a documented exception, such as daily-report self-approval.