Approval Workflows

Stop Asking Whose Desk It Is On

Chains set by request type and value, a live pipeline the requester can read, escalation when something sits too long, and a trail that answers an auditor without a search through mailboxes.

Start Free Trial
  • Rules by value
  • Live pipeline
  • Escalation built in
  • The rule decides

    Value sets the chain, so the route never varies.

  • No more chasing

    The requester can see the stage without asking.

  • Nothing stalls on leave

    Escalation and delegation, both on the record.

  • Audit as retrieval

    Who agreed to what, and when, permanently.

Most approvals are not refused. They are just waited on.

Three gaps account for most of the delay in a decision, and none of them is a judgement problem.

Invisible

Nobody knows whose desk it is on

The requester chases the last person they emailed, who forwarded it on a week ago to someone else.

Inconsistent

Who signs depends on who is asked

Without a rule tied to value, the same decision takes one signature or three depending on the route it took.

Stalled

It has been in an inbox for a fortnight

An approver on leave stops everything behind them, because nothing moves a request on but that person.

Neome closes all three by letting the rule choose the route, showing the stage, and moving what has stalled.

Chains

The value decides who has to sign

Approval chains are configured per request type and value band, so a small purchase takes one signature and a capital one takes two. Because the rule decides, the same decision follows the same route every time rather than depending on who was asked first.

  • Per request type
  • Value-banded levels
  • Multi-level chains

Visibility

The requester can see whose desk it is on

A live pipeline shows every request, the stage it has reached and who it is waiting on, with the requester told at each step. That removes the chasing, which is usually more expensive in time than the approval itself.

  • Live pipeline
  • Current stage visible
  • Requester told at each step

Escalation and delegation

One person on leave should not stop everything

A request unanswered past its threshold escalates to the next approver rather than sitting still. Approvers can delegate while away, with the delegation recorded on every request they act on, so cover is arranged rather than improvised.

  • Escalation on overdue
  • Delegation while away
  • Both recorded on the request

Audit

Who agreed to what, and when, permanently

Every request keeps its full history: who raised it, what it said, who approved, when, and anything they added. An auditor asking why something was bought is answered by retrieving a record rather than by reconstructing a thread from mailboxes that may no longer exist.

  • Complete request history
  • Approver and timestamp
  • Retrievable, not reconstructed

Reporting

Find the bottleneck by name

Set a date range and every figure below it is bounded by those dates.

Pending approvals

What is waiting?

Everything currently awaiting a decision, by approver and by age, so a bottleneck is a name rather than a feeling.

Turnaround time

How long do we take?

Cycle time from request to decision by type and value band, which is the number that tells you whether the process is helping or just existing.

Escalation frequency

Where does it stick?

How often requests escalate and past whom, which usually points at a workload problem rather than an attitude one.

All the features, done right

Approval chains

Per request type and value.

Multi-level

One signature or three, by rule.

Live pipeline

Every request and its stage.

Approver alerts

On arrival, not on a reminder.

Escalation

Overdue requests move up.

Delegation

Cover arranged, and recorded.

Approver comments

The reason travels with the decision.

Rejection reasons

A no that explains itself.

Full audit trail

Who, what, when, permanently.

Turnaround reporting

Cycle time by type.

Role-based access

Requester, approver, admin.

Mobile apps

Approve from anywhere.

Before you move your approvals across

The questions teams ask before the first request is routed through Neome.

Ready to implement this service?

Talk to our team and get a rollout plan aligned to your business process.