Break a job into four drawings, or three deliverables, or a line per supplier, and each one needs its own yes. Then you go looking for where to put the approval and find that a subitem card has Updates, Files, and nowhere to put anything else.
The constraint
Which is why every approvals app gets told it does not do subitems.
On an ordinary item you can press + at the end of the tabs and add an app view. Open a subitem and that is not there. The card offers Updates, Files and the subitem’s own columns, and monday does not extend app views to it.
So this is a platform limit rather than a gap somebody forgot to fill — worth knowing before you go looking for an app that solves it, because the ones that claim to are solving it somewhere other than the card.
Natively
It works, and here is exactly what it does not do.
Subitems have their own board and their own columns, so a Status column and a subitem automation will do the mechanical part:
What you do not get, and will want by the second month:
The other two workarounds
Both are common and both cost something worth naming.
Promote each subitem to an item. Everything works again — and you have lost the grouping that made the subitems worth having, so the board is now four hundred rows where it was forty.
Approve the parent instead. Fine when the parent is what is being agreed to. Dishonest when it is not: one approval covering four drawings cannot say which drawing the objection was about, and the person who signed it has no way to agree with three and not the fourth.
Questions
No. A subitem card offers Updates, Files and its columns — there is no place to add an app view the way you can on an item. This is a platform constraint, not something a particular app has neglected, and it is why approvals apps are so often told in reviews that subitems are not supported.
With a status column on the subitem board and an automation on it. Subitem automations exist and work; what you lose is everything a status column cannot hold — several approvers, a reason, and any record of what was attached at the time.
On whatever is actually being agreed to. If four drawings each need their own sign-off, four approvals on four subitems is the honest shape, and rolling them into one approval on the parent hides which drawing somebody objected to.
Only by being sent something. There is no seat, no guest access and no card they can be pointed at, so it has to be a link — which is also the only way that works for the person who does not use monday at all.
What we built
Since the card cannot hold a panel, the panel goes to it.
The parent item lists its subitems with what is happening to each — not sent, with whom, approved, declined. Open one and the whole panel scopes to it: choose the approvers, attach what they should look at, and send.
The approval belongs to the subitem, not to the parent. It appears in the list of everything waiting across every board, carrying the parent’s name so that rev C is readable as a thing, and it can be sent to somebody outside the company as a link with no seat and no login.
One difference worth stating: the option to move a status column when the decision lands is not offered on a subitem, because a subitem sits on its own board with its own columns and writing the parent’s column there would move nothing while appearing to work.
Keep reading
One board, one status column, and one automation per transition.
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.
Three approvals a month, free, every feature on — including the subitems the card will not hold.