Approved, not sent, is the most wasteful state in the product.
So it is called out rather than buried. An offer above your threshold genuinely cannot be sent without approval, and joining is the event the money waits for.
Real product screens. Figures shown in them are seed data from a demo workspace, not customer results.
A ceiling can never catch a zero.
An approval gate fires on amounts above a threshold, so it structurally cannot stop a ₹0 offer. That is why a floor was added underneath it. Without one, a zero-value offer could reach a candidate on the public response link.
Not "the button is hidden". Genuinely cannot, by any route.
Added because the ceiling fires on "above", so zero slipped underneath it.
The approval threshold defaults to effectively unlimited, which means no offer is gated by value until somebody sets it. Set it deliberately rather than assuming the gate is on.
Six of them, and only one releases money.
One chase task. Not one a day.
An offer quiet for five days raises exactly one chase task, and it closes itself when the candidate responds. A queue that re-raises the same item every morning trains everyone to stop reading it, and then the queue is worse than nothing.
Anything your configuration gates lands in one place.
Offers over threshold, agency connection requests, requisitions needing sign-off. And anything consequential the system wants to do automatically becomes a one-tap confirmation rather than a silent action.
