Deep Dive

Apple Reminders Sucks at Subtasks: A 2026 Update

By Vyshakh Nair, Founder, Ultra Reminders · Updated May 5, 2026 · 8 min read
Part of the master guide: The Definitive Guide to Apple Reminders in 2026

Apple Reminders subtasks problems include single-level nesting, recurring sub-reminders that never reset, drag-to-indent failures, and sub-tasks that vanish when promoted to top level. Apple has not addressed any of these as of macOS 26.1 in May 2026.

If you've spent more than ten minutes in any subreddit about Apple productivity in the last year, you've seen the complaint. "Why are subtasks so bad?" "Why don't recurring subtasks reset?" "Why did my subtask disappear when I tried to promote it?" The pattern is so consistent that it's almost a meme.

This is not a hate post. Apple Reminders is genuinely useful. But the subtasks implementation has been a known pain point since iOS 13 (2019) and Apple has shipped exactly zero meaningful improvements in the seven major iOS versions since. Power users have given up. Newer users discover the limits and quietly leave for Things 3, Todoist, OmniFocus, or Ultra Reminders.

This guide walks through the specific complaints, why they keep happening, and what actually works.

This is part of The Definitive Guide to Apple Reminders in 2026.

The pattern

Search Reddit for "apple reminders subtasks" and the same five complaints come up over and over. We pulled the top 50 threads from r/macapps, r/iOS, r/productivity, and r/Things between January 2025 and April 2026. The complaint pattern:

"I spent 20 minutes building out a project with 3 levels of subtasks. Saved. Came back the next day, the third level was just gone. iCloud sync ate it."
paraphrased from r/macapps, January 2026

"Why can subtasks not have their own subtasks? It's 2026. This is a basic feature. Even Microsoft To Do does this."
paraphrased from r/iOS, March 2026

"My recurring subtask never resets. I check it off, the parent recurs the next week, the subtask stays checked. Pointless."
paraphrased from r/productivity, February 2026

"Tried to promote a subtask to top-level by dragging it. The subtask disappeared. No undo. Lost the task."
paraphrased from r/macapps, April 2026

"Subtasks don't show up in Smart Lists if you filter by tag. Only the parent does. So the smart list is incomplete."
paraphrased from r/Things, December 2025

Five complaints, five different mechanisms, all rooted in the same architectural decision: Apple treats subtasks as a presentation feature, not a first-class data type. Subtasks are second-class citizens in the Reminders data model and the bugs flow from that.

Why people feel this way

The complaints are loud because subtasks are exactly where you commit to using a task manager seriously. You're past the "buy milk" phase. You're trying to plan a project. A trip. A house move. A product launch. The moment the structure breaks, the system breaks.

For a project with 30 to 80 atomic tasks, you need at least 2 levels of nesting (project > phase > task) and ideally 3 (project > phase > sub-phase > task). Reminders gives you one level. So your phases either bloat into giant lists, or you lose the project context entirely and end up with 80 flat tasks across 5 lists.

The recurring sub-reminder bug is even more visceral. You set up a weekly review with 6 subtasks (review inbox, review waiting list, review someday list, etc.). The parent recurs every Sunday. The subtasks check off once and stay checked off. The next Sunday, you have a parent reminder with 6 ghost subtasks. You can't reset them without deleting and rebuilding. Every. Week.

This isn't a corner case. This is the second-most common reason people abandon Reminders for paid alternatives, behind notification reliability.

For the broader limits picture, see 13 Apple Reminders Limitations Power Users Hit and Why Power Users Quit Apple Reminders.

What works

Within the constraints of Apple Reminders, here are the workarounds that actually hold.

Workaround 1: Use lists for what should be sub-projects

Instead of trying to nest subtasks 3 levels deep, treat each major project as a list. Then use sections within the list for phases, and use subtasks (1 level) for the smallest atomic units.

  • List: "Q4 Launch"
    • Section: "Pre-launch"
      • Task: "Finalize landing page" (with 4 subtasks)
      • Task: "Write launch email" (with 3 subtasks)
    • Section: "Launch week"
      • Task: "Schedule social posts" (with 5 subtasks)

This gives you effectively 3 levels of structure (list > section > task > subtask) without fighting the Reminders model. The trade-off: lists feel heavier than nested folders. Most people get used to it within a week.

For the kanban view of this same pattern, see How to Build a Kanban Board Inside Apple Reminders.

Workaround 2: Use templates for recurring projects with subtasks

Apple Reminders templates (long-press a list, save as template) preserve the subtask structure. So instead of fighting recurring subtasks, save the whole list as a template and re-instantiate it weekly.

The flow:

  1. Build your weekly review list once with all the subtasks you want.
  2. Save as template.
  3. Each Sunday, create a new list from the template. All subtasks reset to unchecked because they're new.

The cost: an extra list per week. The benefit: actually-reset subtasks. Most people who do weekly reviews find this acceptable. Templates were a real upgrade Apple shipped (iOS 16) and they partially solve the recurring subtask pain.

Workaround 3: Avoid drag-to-promote

Don't promote subtasks via drag. Use the right-click menu (Mac) or long-press menu (iOS) and choose "Move to..." instead. The drag UI has the worst sync race conditions. The menu-driven move is more reliable.

If you do drag and a subtask vanishes, check Notification Center for an undo prompt. Sometimes there's a 5-second window. Often not.

Workaround 4: Use tags to flag parent + subtask groups

Since Smart Lists don't always include subtasks when filtering by tag, tag both the parent AND each subtask with the same project tag. So a subtask of "Q4 Launch" gets tagged #q4-launch, and so does the parent. The Smart List for #q4-launch then catches everything.

It's redundant typing. It's the price of the subtask filter limitation. Templates can include tags so once set up, it's not too painful.

For more tag patterns, see How to Use Tags in Apple Reminders (Complete System).

Workaround 5: Pin the parent reminder for visibility

Subtasks are visually buried under their parent. If the parent is collapsed, you don't see the subtasks at all. Pin or flag the parent so you can find it fast. Use the Today smart list to surface anything due, including buried subtasks.

For related sub-reminder bug detail, see How to Create Subtasks and Sublists in Apple Reminders and Why Your Reminder Marks Itself Incomplete.

What does not work

Trying to recreate Things 3 hierarchy in Reminders. You can't. Stop trying. The data model literally doesn't support it.

Relying on iCloud to preserve 3-level structures during sync. Ghost subtasks, vanishing tasks, and reset states are all reproducible. iCloud's conflict resolution does not handle subtasks well.

Using Shortcuts to "fix" recurring subtasks. People build Shortcuts that uncheck all subtasks of a parent on a schedule. Brittle. Unreliable across devices. Most abandon after 3 weeks.

Hoping the next iOS version will fix it. It hasn't in iOS 13, 14, 15, 16, 17, 18, or 26. Plan around the limit, not around hope.

"I rebuild my weekly review subtasks manually every Sunday because the recurring rule on subtasks doesn't reset. It takes 4 minutes. I've accepted it. Switched to Things last month and got the time back."
paraphrased from r/macapps, March 2026

How Ultra Reminders solves it

Ultra Reminders supports unlimited subtask nesting, deterministic recurring sub-reminder reset, drag-to-promote with safe sync (no race condition), and full subtask inclusion in Smart Lists.

The architecture difference. Ultra Reminders treats subtasks as first-class entities with their own IDs, parent pointers, and recurrence rules. The data model doesn't degrade as you nest. Recurrence rules are stored per-task (parent or sub) and execute independently.

What this means in practice:

  • Build a project 5 levels deep. Saved. Synced. Stays put.
  • Recurring weekly review with 8 subtasks: each subtask resets to unchecked when the parent recurs.
  • Promote a subtask to top-level via drag: no race condition, the subtask appears at top-level intact.
  • Smart Lists filtered by tag include subtasks at any depth.

Ultra Reminders syncs back to Apple Reminders via iCloud, so your iPhone and Watch still see the data. The catch: nested levels beyond 1 collapse to flat tasks on iPhone (because Apple's data model can't store them). On Mac via Ultra, the structure is intact. On iPhone via Apple Reminders, you see a flat list.

For most people this trade is worth it: full structure on the device where you do project work (Mac), simple list on the device where you triage (iPhone).

For the broader workflow comparison, see 10 Things Apple Reminders Cannot Do.

FAQ

Q: Is there any way to nest subtasks more than 1 level in Apple Reminders?

A: Not in the official UI. There are AppleScript and Shortcut hacks that can create the appearance of nesting, but the data model only stores 1 level. When you sync to iCloud or open on another device, anything beyond level 1 collapses or disappears. Apple has not added true multi-level subtasks as of macOS 26.1 in May 2026.

Q: Why don't recurring subtasks reset when the parent recurs?

A: Because Apple Reminders' recurrence model only attaches to the top-level reminder. Subtasks are bound to the parent's lifecycle but don't have their own state machine. When the parent recurs, a "new" parent is created, but the existing subtasks (still attached to the old parent) keep their checked state. This has been the documented behavior since subtasks were introduced and Apple hasn't changed it.

Q: Will my subtasks be lost if I switch to Ultra Reminders?

A: No. Ultra Reminders reads from Apple Reminders via EventKit on first launch. Existing subtasks (level 1) are preserved. You can then add additional nesting in Ultra. If you uninstall Ultra later, your Apple Reminders data is unchanged.

Q: Do subtasks show up in iOS Notification Center?

A: Subtask notifications fire if the subtask has its own due date set. They appear as separate notifications with the subtask title. The parent's title is not included, so subtask notifications can be confusing if you don't recognize the title.

Q: How does Things 3 handle subtasks differently?

A: Things 3 supports projects (which are essentially top-level containers) and checklists within projects. It's not "infinite nesting" but it gets you 2 to 3 effective levels of structure. Recurring projects work cleanly. The trade-off is Things is $50 one-time on Mac, with separate purchases for iOS and iPad.

Ultra Reminders solves subtasks that nest, recur, and sync without losing themselves. Free 14-day trial at ultrareminders.com.