Every organisation has one. The manpower requisition, the purchase approval, the contract file that left one desk in perfectly good order — and then simply stopped moving. Nobody rejected it. Nobody questioned it. It just sat, for three weeks, while the work it was meant to release stood still.
When someone finally asks, the reconstruction begins: who has the file, since when, whether they ever saw it at all. The answer is usually mundane. The approver was on site, or travelling, or buried under other work, and the file waited in an inbox that nobody was watching.
The cost of that quiet wait is real. A position stays unfilled, a purchase stays undelivered, a project stays paused — all for a signature that would have taken thirty seconds to give, if only the file had been in front of the right person at the right moment.
Nobody said no — nobody said anything
A requisition that needs four signatures rarely fails because somebody said no. A no is at least an answer; the process can respond to it, argue with it, revise and resubmit. What kills timelines is the non-answer — the approval that is neither given nor refused, just pending.
Pending has no owner. The requester assumes the approver is considering the file. The approver, if they registered it at all, assumes it can wait a day — and the day multiplies quietly into weeks. Everyone in the chain behaves reasonably, and the file still does not move.
That is the honest diagnosis. Approval delays are almost never a decision problem; the decisions, once actually made, take minutes. They are a visibility and follow-up problem wearing a decision problem's clothes.
Why chasing fails as a job
The traditional remedy is a person — a coordinator or an assistant whose unofficial duty is to chase signatures. It fails for a predictable human reason. Chasing means nagging, and nagging a senior manager is a risk nobody junior wants to take twice.
So the chasing happens softly, or late, or not at all. A coordinator sends one gentle reminder and then waits, because the second reminder feels like an accusation. The hierarchy that gives the approval its authority is the same hierarchy that makes it unchaseable from below.
There is a scale problem underneath the social one. One person can track a handful of files by memory and goodwill. An organisation raising requisitions across departments, projects and locations generates far more pending approvals than any individual can hold in their head.
And chasing produces nothing. Every hour spent asking where a file is adds no value to the file. It is pure friction — work created entirely by the absence of visibility, performed by people who have better things to do.
Your hierarchy is not the problem
One popular answer is to blame the hierarchy itself — too many signatures, too much control, cut the chain and the files will fly. Occasionally that is true. Mostly it is not. The signatures exist because money, headcount and commitments deserve senior eyes before they leave the building.
A four-signature chain that clears in days is not bureaucracy; it is governance working. The same chain taking three weeks is not extra control. It is the same decision plus weeks of nothing — and the nothing is the part worth removing.
So the goal is not fewer approvals. It is approvals that move: the same chain, the same authority, the same policy — minus the sitting. That reframing matters, because it means the fix does not require anyone to give up control.
Reminders are the system's job
When approvals run through a system that knows your hierarchy, chasing stops being anyone's job. The system knows which file is with which approver and for how long. The reminder goes out automatically — polite, factual, addressed to exactly the person holding the file.
That single change removes the social friction that made chasing fail. Nobody has to weigh whether it is their place to nudge a director. The nudge does not come from a subordinate; it comes from the process itself, and it reads as information rather than impertinence.
This is exactly how manpower requisitions work in the recruitment platform we built for Vensar. Files route through the company's own approval chain with automatic reminders, so nothing sits on a desk. The approvers lost no authority. They lost only the ability to become an accidental bottleneck without anyone noticing.
A reminder from the system is information; a reminder from a junior colleague is a confrontation.
Escalations that follow your rules, not a template
Off-the-shelf approval tools impose their own idea of a workflow — a generic chain, a fixed reminder cadence, an escalation policy that someone designing for every company in the world thought was sensible. Your organisation's rules are more specific than that, and they exist for reasons.
Who approves what depends on amount, department and designation, sometimes on the project itself. Who is informed when a file stalls is a question of your culture, not a default setting. An escalation that jumps levels the wrong way can cause more damage than the delay it was meant to cure.
So we start every build by mapping the hierarchy as it really operates — who approves what, in which order, with which exceptions — and we encode that. The reminders and escalations then follow rules your organisation already recognises as its own, which is precisely why they get respected instead of ignored.
Every step visible, every decision human
Once approvals move through a system, something else changes: visibility. At any moment, anyone with the right access can see where a file stands, how long it has been there and what happens next. The three-week mystery becomes a status line that answers itself.
Visibility changes behaviour on its own. When everyone can see where a file is waiting, files wait less. Not because anyone is punished, but because the quiet inbox is no longer quiet — the delay has a name, a timestamp and an audience.
None of this automates the decision itself. Approvers still read, question, reject and approve; that is the entire point of having them. What disappears is the dead time between decisions and the awkward machinery of humans chasing humans.
The busywork runs itself. Your people stay in control of the decisions — and no file sits on a desk for three weeks because nobody wanted to send the second reminder.