You find out a request is stuck when someone complains about it.
Stop chasing approvals. Start running the process.
You own a process that lives in inboxes, spreadsheets and corridor reminders. Koldheim gives it a shape everyone follows, and shows you where every request is.
What it looks like now
The approval rules live in a policy document nobody opens.
Month-end reporting means rebuilding what happened from email threads.

What you get, and where it shows up
A live view of every request
Each stage is its own page. See what is waiting, who it is waiting on, and how long decisions take.
More on thisThe rules are part of the process
Value thresholds and second signatures are built in, so requests reach the right person first time.
More on thisThe history writes itself
Every step and decision is recorded as it happens. Nothing to reconstruct at month end.
More on thisWhere you work in it
Spending routed by your own approval limits, with the budget checked before anyone approves.
Asset RequisitionsOperationsSupplies priced from live stock and routed by value, with the storeroom told of a shortfall first.
ProjectsProject managementThe work that follows, in columns, with who moved each card on the trail.
Where to next
The rule the service runs, in your browser. No form, no call.
Your process map, running.Branches, thresholds, checks against live records and a designed rejection path. If you can map it, we author it with you as configuration, and Koldheim runs it without a development project in between.
No spend without the right signature.Requests arrive priced from stock, with the department budget in front of the approver. Over your threshold, a second signature is required before anything moves.
Know what you own, and what it is about to need.Tag, serial, warranty, condition, who holds it and where it is, on one register. Servicing raises its own task before it is due, and the work that follows sits on a board.