Set the Parent Status Automatically from Subitem Statuses in monday.com (2026)

Direct answer: monday.com can set the parent status natively when all subitems reach a status, via the built-in recipe “When all subitems’ statuses are something, change parent status.” If all-or-nothing is enough, use it and you’re done. It can’t handle partial thresholds, mixed statuses, or majority logic. For rules like “80% done → Ready for review,” write the parent status with a rollup rule: ALL_DONE, MOST_COMMON, or THRESHOLD_STATUS.

What can the native automation do?

monday.com ships a recipe for exactly the most common case:

1. Open your board → Automate.
2. Search “subitem” and pick the all-subitems-status recipe (“When all subitems’ statuses are something, change parent status”).
3. Set the subitem status to watch for and the parent status to apply.

When the last subitem flips to Done, the parent flips too. It’s free and reliable. If it covers your workflow, don’t install anything.

When do you need more than all-or-nothing?

The native recipe has one trigger shape: every subitem at one status. Real boards outgrow that quickly:

• Partial thresholds: QA wants the parent at “Ready for review” once 80% of subtasks are done. The native recipe fires at nothing less than all of them.
• Mixed statuses: seven subitems spread across four labels. Which one should the parent show? All-or-nothing has no answer. What you want is the dominant status.
• Any-status mirroring: the parent should reflect whatever unanimous state subitems are in — all “Blocked” should read Blocked, all “Approved” should read Approved. The native recipe watches one status only.
• Scope control: some subitems (say, “Nice to have” tasks) shouldn’t influence the parent status at all.

SubItems Pro handles these with three Status rollup functions. Each is a Rollup Sync rule (source subitem Status column → function → parent Status column), kept current by webhooks, with Sync now for on-demand recalculation. Setup is the same for all three: add the Rollup Sync board view, authorize once, create the rule with auto-sync on. The free plan includes every function on one board with one rule. Full steps are in the user guide.

How do you mirror a unanimous status (ALL_DONE)?

Rule: subitem Status → ALL_DONE → parent Status column.

When every subitem shares the same label, the parent status is set to that label (any label, not only Done). Five subitems all “Approved” makes the parent “Approved”, and all “Stuck” makes it “Stuck”. While statuses are mixed, the rule deliberately leaves the parent alone, so whatever you or another automation set stays in place.

Use it when the parent should be a faithful mirror of a settled state, in any direction. It’s a superset of the native recipe’s done-only behavior.

How do you show the dominant status (MOST_COMMON)?

Rule: subitem Status → MOST_COMMON → parent Status column.

The parent always displays whichever label occurs most often. Seven subitems (four “In progress”, two “Done”, one “Stuck”) put the parent at “In progress”. As work completes and Done becomes the majority, the parent follows automatically.

This is the right fit for portfolio-style boards where managers scan parent rows and just want each parent to summarize the bulk state of its subtasks, without anyone curating it.

How do you flip the parent at a threshold (“80% done → Ready for review”)?

Rule: subitem Status → THRESHOLD_STATUS → parent Status column, with four settings:

• Labels that count: e.g. “Done” (add “Skipped” if that counts as complete).
• Threshold: e.g. 80%.
• Status to set when the threshold is met: “Ready for review”.
• Fallback status otherwise: “In progress”.

With 10 subtasks, the parent reads “In progress” through the seventh Done. The eighth (80%) flips it to “Ready for review” within moments. If work is reopened and the ratio drops back below 80%, the parent returns to the fallback. It never goes stale.

Set the threshold to 100% and it becomes the native recipe with two upgrades: you choose what the parent says before completion, and you can add a subitem filter (paid plans) so only in-scope subtasks count. Pair it with a visible counter or percentage from counting done subitems on the parent so people can see why the status flipped.

Which approach fits your board?

Approach	Parent changes when…	Limits
Native recipe	ALL subitems reach one status	All-or-nothing; one status watched; nothing before 100%
ALL_DONE	Every subitem shares the same label (any label)	Mixed statuses leave the parent unchanged
MOST_COMMON	The majority label changes	Parent tracks the bulk, not completion
THRESHOLD_STATUS	≥ N% match your chosen labels	Needs a fallback label; filters require a paid plan

The native recipe covers the plain “everything done → parent done” case well. The three rollup functions exist for the boards it can’t express. For progress bars, percentages, and counts, see showing subitem progress on the parent item and the complete subitem rollup guide.