A deadline, and something that happens when it passes
A request can carry a date. When that date passes with no answer, two different messages go out: one to the person whose turn it is, and one to whoever asked for the approval — carrying the name of the person holding it up. Chasing only the person who is already ignoring the request is noise; the message that unblocks it is the one that reaches the person who is waiting.
Created by asking for it
Through a Sidekick skill, say “ask Ana, Tom and Priya to sign off on this, one at a time” and the request is built: approvers resolved by name, order preserved. No form to fill in.
The order is visible before you commit
When approvers decide one at a time, they are numbered as you pick them, so you can review the order before the request exists. It is the one thing you cannot correct afterwards without starting over.
It does not touch your board until you say where
Mirroring the approval state into a status column is opt-in, and you pick the column. With no column chosen, the app writes nothing to your board.
Approve and Reject only for whoever’s turn it is
Everyone else sees the current state and who is holding it up. Nobody approves out of order, and nobody wonders whether their click counted.