How To Master Subitems in Monday.com Easily 2026

On a task row — here, "Updata APK V2" inside a sprint backlog — click the expand arrow to reveal the subitem area, then choose Add subitem. A new blank row appears with a text field ready for a name, sitting inside its own mini table beneath the parent. Typing a name and pressing enter locks it in as a subitem, nested visually and structurally under the task it belongs to.

The subitem table isn't limited to whatever columns the parent board uses — it has its own header row, which in this example includes Subitem, Owner, monday Doc, Status, and Date. You can add more independently, such as People, Files, or Timeline, without those columns appearing anywhere on the parent task's row. This separation is what makes subitems useful for genuinely different tracking needs — a parent task might track sprint dates while its subitems track individual completion status.

Click the Owner cell on a subitem row to assign a person, the same way you would on any board — clicking the avatar surfaces a contact card confirming who's assigned before you commit. Setting the Status column to Done marks that individual piece of work complete without touching the parent task's own Status column, which might still read "Ready to start" or "In Progress" depending on what else is outstanding underneath it.

A subitem living in its own nested table is useful, but a parent row that reflects what's happening below it is more useful still. From the subitem column's settings, you can mirror fields like total cost, hours, or completion percentage directly onto the parent item row, so scanning the top-level board tells you the state of the work without expanding every task. This is the same mechanism that powers subitem rollups — mirrored columns and summary columns both pull live data up from subitems to parents.

Because subitem status is a trackable field, it can trigger automations the same way any column change can. A common recipe changes a parent task's own status to Done the moment every subitem underneath it reaches Done — useful for a task like "Updata APK V2" where the real work happens across several subitems and nobody wants to manually flip the parent status once the last one wraps up. Build this from the Automate menu, choosing a "when all subitems are marked Done" trigger and a "change status to" action on the parent.

Once several tasks have subitems attached, collapsing them back down keeps the board scannable — the count badge next to a task name still tells you subitems exist, without their rows taking up vertical space. Expand only the tasks you're actively reviewing, and lean on filters to surface just the subitems matching a particular owner or status when you need a cross-task view rather than paging through every parent one at a time.