Free tool
Where does your approval process actually break?
Six questions, and a named list of what's open — in the order they cost you. Not a benchmark against anyone else: just your own answers against the mechanisms that decide whether a stalled round costs you or not.
About a minute. No sign-up, and nothing is sent to a server.
Optional — how many projects are in review at once, on a normal week?
Nothing here is open.
Every mechanism these six questions check is already in place. What's left is whatever they don't ask about — this is a checklist, not an audit, and a short one.
Also open
Already solid
Where this comes from
Six mechanisms, not six opinions.
Every question maps to something concrete, not a vibe.
Something that ends a round nobody has replied to. One named person whose sign-off is the one that counts. A yes you can trace back to the version it was given on. Feedback that all lands in the same place. A record of what was approved and when. And an agreed number of rounds that both sides are counting.
Three of those six are things yeses does — it tracks the versions a decision was given on, keeps the feedback on the work itself, and records who approved what and when.
Two of them are a clause, not a feature. A response deadline and a named approver are things you agree in a proposal, which is what the deadline generator writes.
And the sixth is neither. Nothing here counts your rounds for you. An agreed round count is a line in a proposal and a number somebody watches, which is why that answer points at the calculator rather than at the product. Saying so is cheaper than being found out: a checklist that turns out to be a feature list is worth nothing to the person filling it in.
The other two
Both of these close a gap on that list.
Free, no sign-up, and nothing sent to a server — the same as this one.
Questions
About this checklist.
Is this scored against other teams?
No. There's no survey behind it — each question scores your own answer against a mechanism, not against anyone else's numbers.
What do the six questions actually check?
Whether a quiet round has anything that ends it, whose sign-off actually closes one, whether a yes can be traced to the version it was given on, whether all the feedback lands in one place, whether there's a record of what was approved and when, and whether anyone is counting the rounds.
Why does it lead with one gap instead of the score?
Because the score can't tell you much on its own. There's nothing to compare it against — deliberately, since no survey backs this — so a number out of twelve is a grade with no scale. Which mechanism is missing is the part you can act on, so that leads and the score sits underneath it.
What if a question doesn't apply to us?
Two of them have a way out. A team of three has no need to name an approver, and a retainer has no round count to run past. Taking either exit drops that question out of the total rather than scoring it zero, so the result reads out of ten instead of twelve.
Is my input stored anywhere?
No. The answers live in the page and in the link you copy. Nothing is sent to a server, and there is no account to make.
The checklist is free. Closing the gaps isn't your job to remember.
Deadlines that send themselves, approvals tied to a version, one named sign-off — running in the background instead of on a checklist.