03 The hard part
Why do approval systems get bypassed?
Because of one unanswered question, and it is never the technology.
- The question: what happens when the approver is unavailable? Not in theory, but on the Friday before a long weekend with a dispatch waiting.
- The wrong answer: nothing happens and the request waits. Two of those and the team goes back to WhatsApp, which is where the audit trail disappears.
- The other wrong answer: it auto-approves. That converts a delay problem into a control problem, and the first bad approval switches the whole system off.
- What works: a named delegate per approver, set in advance, activated by the leave record or by the approver, with the delegation written into the trail, plus escalation up the hierarchy after a stated time.
The record it leaves behind
04 Delivery
How we build one
Five steps, and the first three are conversations rather than configuration. The elapsed time goes into agreeing the rule, not implementing it.
Step 1: Time the current path
Request to action at your Bhiwandi office, measured rather than estimated, and where it waits.
2 to 3 daysStep 2: Write the rule in a sentence
By value, category, cost centre, margin or vendor, with thresholds as numbers. A rule that cannot be written in a sentence should probably not be one.
2 to 3 daysStep 3: Answer the absence question
Delegates, escalation timings and what may never auto-approve. This decides whether the system gets used or bypassed.
1 to 2 daysStep 4: Build escalation and fallback first
Reminders, escalation, a manual path and an alert to a named owner, before the happy path is wired at all.
1 to 2 weeksStep 5: Hand over the rule editor
An administrator on your side is trained to change thresholds and approvers without us.
1 day
05 Reference
Terms used on this page
- Escalation matrix
- The rule for what happens when an approval is not actioned in time: who receives it next, after how long, and whether it may auto-approve.
- Delegation of authority
- Approval rights passing to another person during absence, recorded so the trail shows who actually approved.
- Maker-checker
- A control requiring that whoever creates a transaction is not whoever approves it.
- Straight-through processing
- Written STP: a request meeting every rule, released with no human action.
- Service level
- Written SLA: the time within which an approval is expected to be actioned, and against which a breach is measured.
- Approval trail
- The unedited record of actor, timestamp, value and routing rule for every action taken on a request.
- Data Protection Board of India
- The adjudicating body under the Digital Personal Data Protection Act, 2023. The Schedule to that Act sets fixed rupee ceilings rather than a share of turnover: up to ₹250 crore for failing to take reasonable security safeguards against a personal data breach, up to ₹200 crore for failing to notify the Board and the people affected, and up to ₹50 crore for a breach of any other provision. That is why consent, retention and access control are build decisions here rather than paperwork.
06 Questions
Workflow automation in Bhiwandi: FAQs
Next step
Tell us the approval that holds things up most.
We will come back with the routing rules, the escalation matrix, the delegation design and a fixed quote. The first map is free.
Read by Dhanush Prabha, our CTO, not a form queue. Reply usually within one working day, in your time zone.

