CAPABILITY · REQUESTS & APPROVALS

Decisions, approvals and delegated authority, built into the work.

A useful approval should answer what changed, what is being requested, what happens if it is approved and who has authority to decide. Voyager assembles that context for spending, access, resources, exceptions and operating decisions, then carries an approved choice into the work it affects.

How it works

A request arrives with its context, is routed by policy and carries through when approved.

The approver sees what changed and the consequence of each choice. Thresholds, delegation and escalation decide who answers. The approved change reaches every system it affects. Illustrative.

01 · Arrives with context

Request · spending$1,900

Purchase 60 fittings from Harbor MetalsRaised by Voyager for procurement

What changed: Kestrel shipment moved to Oct 15
Why now: Northgate install Oct 12
If approved: Install on the contract date
If declined: Penalty clause applies
Evidence: PO, contract, stock, quote

02 · Routed by policy

Up to $500Team lead$500 to $5,000Finance leadOver $5,000Finance director

Finance lead away until FriDelegated to deputy controllerApproval
No answer in 4 hoursEscalates to finance directorApproval

Approved by Ana Lopes · 09:26Deputy controller, delegated authority

03 · Carried through

09:26Purchase order sentProcurement
09:26Install date heldSchedule
09:27Customer confirmedOutlook
09:27Decision and reason recordedAudit

01DECIDE WITH CONTEXT

An approval that explains itself.

A request shows what changed, why it matters now, the consequence of each choice and the evidence behind it, so the approver does not have to reconstruct the situation from messages.

Decisions and exceptions
Spending and purchase approvals
Access and resource requests

02POLICY

Thresholds, delegation and escalation you configure.

Approval policies can depend on amount, role, team, system and counterparty. Delegation and escalation keep decisions moving when people are away, and an authority matrix shows who can approve what.

03FOLLOW-THROUGH

Approved means done, not re-typed elsewhere.

Once a request is approved, Voyager carries the change into the schedules, records, communications and systems it affects, and records who approved it and why.

PRACTICAL ANSWERS

Common questions about this capability.

Can Voyager require approval before acting?: Yes. Supported actions can each be set to be handled automatically, stopped for approval, or reserved for people.
Can approval rules differ by amount or team?: Yes. Thresholds, delegation and escalation can vary by amount, role, team, system and counterparty.
Is there an audit trail?: Yes. Decisions record who made them, when, why and on what evidence.

Get started

Choose an approval that currently gets decided in messages or spreadsheets.

Map an approval path Request access Explore capabilities

We will map the evidence an approver needs, the thresholds and delegation rules, and what Voyager should update automatically after the decision.