monday has no approvals feature. These are the honest answers to the questions that follow — the native way first, in full, and then exactly where it stops.
One board, one status column, and one automation per transition — plus the label everybody forgets, and the three things columns cannot do.
Why a status column cannot represent “two of the three have agreed”, the native workaround and what it costs, and when to stop working around it.
What guests actually cost, when a shareable board is the right answer, and how to get a signature from somebody who will never have a login.
What monday’s activity log does and does not record, why a status column is not evidence, and the four things worth keeping whatever tool you use.
Rounds without a status per round, why replacing a file breaks an approval that already happened, and when you should buy a proofing suite instead.
Five columns, seven labels and four automations, written out — for when you have decided to build it natively and want the structural decisions made for you.
Routing by amount so the person spending the money does not choose who signs it off, self-approval, and what a status column can prove about an authorised spend.
The date column people forget, why a reminder on a schedule becomes furniture within a fortnight, and what to chase instead of what is overdue.
What to do in the next twenty minutes when a file was replaced after sign-off, how to work out what each approver actually saw, and the habits that stop it recurring.
What a dashboard widget genuinely solves, why a cross-board view quietly stops matching some boards, and the half of the problem a list of items cannot cover.
The form, the board and the two automations that work — and the three things monday will not do for you: balances, clashes and cover.
Why the person who received the goods should approve before the budget holder, what to attach so it can be checked, and where a board stops being accounts payable.
The difference between approving a contract and signing one, surviving four rounds of redlines, and why every new version invalidates the last approval.
Why no app can live on a subitem card, what a status column on the subitem board does and does not do, and how to get a sign-off recorded against one anyway.
What a dashboard Table widget does, why cross-board views quietly miss boards, and the naming drift underneath all of it.
Why workload views need an estimate column nobody fills in, what to count instead, and the two rules that keep the answer honest.
Duplication, board templates, the hidden board subitems really live on, and why a template that only sets names saves almost nothing.