Everything waits for the owner's answer
Discounts, change orders and purchases all queue behind one calendar — and the queue is longest when you're busiest.
What's the leak?
Discounts, change orders and purchases all queue behind one calendar — and the queue is longest when you're busiest.
What it looks like
A rep needs a small discount approved. A crew lead needs a part ordered. An office manager needs a credit applied. All three text the owner, who is on a roof. Three customers wait a day for decisions worth less than the delay.
Why it happens
No delegated thresholds exist, so a routine decision escalates at exactly the same priority as a genuine exception. Approving everything looks like control; it functions as a throughput cap.
What it costs
Company throughput is limited by one person's availability, and the backlog grows fastest during the periods where speed matters most.
How URBLD closes the leak
Approval limits are set by role, routine decisions clear at the level they belong to, and only items above the threshold escalate. Every approval is recorded, so delegation stays auditable.
Leak diagnosis
- Observed symptom
- Discounts, change orders, purchases and exceptions all wait for one person's answer.
- Inferred root failure
- No delegated approval thresholds, so routine decisions escalate at the same priority as real exceptions.
- Lifecycle stage
- Cross-stage
- Financial or capacity consequence
- Throughput is capped by one calendar, and the queue grows fastest exactly when the business is busiest.
Measure it yourself
Median hours items spend waiting for approval, and the share of approvals below a value that could be delegated.
Practical diagnostic
Log every approval request for one week with its value and its wait time, then find the threshold that covers most of them.
Recommended operating response
Set delegated limits by role, escalate only above the threshold, and record every approval so delegation stays auditable.
Deeper explanation: The owner dependency bottleneck
Related Features
Related Workflows
Other leaks worth checking
See how URBLD closes every leak
One connected workflow from the first lead to the final payment.