Which Metrics to Track for an Approval Process

Choosing metrics for an approval process means separating volume from behaviour. Counting requests tells you how busy the process is; timing tells you whether it works.

What volume alone hides

A count of approvals says nothing about the experience of waiting for one.

Requests approved quickly and slowly, averaged into one figure
No indication of which approver is the constraint
Rejections invisible, so the control cannot be evaluated
Committed spend unknown until the entries post

The metrics worth tracking

Metric	What it reveals
Pending requests	Current load waiting on a decision
Time in approval phase	Where requests actually wait
Rejection rate	Whether the control catches anything
Approved value per cost centre	Committed spend before closing
Upcoming due dates	Approved payments coming due

How to capture them in Jestor

Enable log metrics on the phase field in Jestor so approval dwell time is recorded.
Add indicators for pending, approved, and rejected volume.
Add a panel showing approved value grouped by cost center.
Add a due-date view so approved payments are not forgotten.
Apply conditional colour so a phase exceeding its target stands out.

Why Jestor is the best complement to Omie for approval reporting

The integration is native, with no middleware — so the approved value shown on the dashboard is the same figure that reached accounts payable, with no reconciliation between them.

Because timing is recorded automatically as cards move, the approval metric that matters most requires no additional instrumentation.

Frequently Asked Questions

Why track rejection rate?

A control that never rejects anything may be theoretical. See jestor.com.

Is timing recorded automatically?

Yes, once log metrics are enabled on the phase field.

Can I see committed spend before closing?

Yes, as approved value per cost centre.

Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

Get to know Jestor

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,