Cycles Blog
Things 3 vs a Rotation Planner for Recurring Work
Things 3 handles fixed-cadence repeats beautifully, but recurring work that needs fairness, weighting, or sharing breaks down. Here is how to choose.
Things 3 recurring tasks vs a rotation planner: which one fits?
Things 3 has earned its standing as the gold standard for Apple productivity, and its repeat handling has had roughly a decade to mature. Yet the same pattern keeps showing up for people who lean on it for recurring work: missed repeats do not get rebalanced, they stack into an ever-growing overdue list. By the time you notice, the Today view is full of tasks you never meant to track that closely.
The real question is not whether Things 3 is good. It is. The question is whether due-date-driven repeats fit work that needs balancing across people, priorities, and available time.
This guide covers where Things 3 recurring tasks excel, where the repeat model breaks down, a side-by-side checklist, and three worked scenarios, then gives verdicts by situation. It stays useful whichever tool you choose, because the point is to surface the decision your tool is already making for you.
Where Things 3 recurring tasks excel
A comparison earns trust by conceding the incumbent's strengths first, and Things 3 has real ones.
The Apple ecosystem experience is best in class. Things 3 runs natively on iPhone, iPad, Mac, and Apple Watch, and the handoff between devices is among the smoothest you can get on Apple platforms. Repeat entry is nearly frictionless: type something like "every week on Monday" and the repeat is set, with no dialogs to fight through.
The workflow is clean GTD. Repeats slot naturally into projects and areas, surface in the Today view when their date arrives, and stay out of the way until then. Capturing and completing them on the go works through Apple Reminders and Siri integration, which matters more than it sounds when your hands are full.
Behind all of that sits a decade of design polish and reliability, which is exactly what you would expect from a mature app. For solo, fixed-cadence, strictly date-shaped work, Things 3 repeats genuinely excel, and nothing in this article disputes that.
The clone problem: date-based repeats aren't balanced work
In Things 3, a repeat is a cloned to-do. The same task reappears on the same cadence, and the app makes no further decisions for you. It keeps no memory of who completed it last, holds no sense of how important it is relative to your other recurring work, and has no idea how much work your week can absorb.
When life intervenes, due-date thinking converts recurring work into overdue debt rather than rebalancing it. The list does not ask what deserves attention; it asks what is late, and everything late accrues until you clear it.
Rotation planning reframes the problem. Recurring work is not a stream of deadlines; it is work to be balanced across people, priorities, and available capacity. Cycles, a local-first rotation planner for recurring work, describes its job as helping you "decide what deserves attention next, build a realistic plan around available capacity, and keep strict, weighted, or shuffled rotations moving without turning recurring work into an overdue list." That is a different question from the one a due-date list asks, and for work that needs balancing, it is the right one.
If the category is new to you, start with a primer on what a rotation planner is and when it helps.
Strict, weighted, or shuffled: what a rotation schedule app adds
Rotation planners give recurring work three modes, and the vocabulary is worth knowing even if you never leave Things 3.
Strict rotations fix the order: do A, then B, then C, then back to A. This is the habit-like mode for sequences where consistency is the point, and it is the one mode Things 3's date-based repeats can approximate. Give each step its own repeat at the same cadence and you have something close.
Weighted rotations make higher-priority recurring work surface more often than lower-priority work. Important upkeep comes up nearly every cycle; low-stakes checks come up occasionally. There is no native Things 3 equivalent. You can fake it with different repeat intervals, but the app never knows one task matters more than another; it only knows two dates.
Shuffled rotations deliberately vary the mix. Instead of the same order every time, the planner draws a varied, fair sequence. There is no native equivalent here either.
This is a feature-level gap, not a matter of taste, and you can verify it against your own setup. Try to make one recurring task appear twice as often as another because it matters more, or to vary the order of a practice list on purpose. You will find workarounds, not features.
A useful audit while you are in there: list your recurring work and sort every item into needs fixed order, needs weighting, or needs shuffle. If nearly everything lands in the first pile, Things 3 fits you. If fairness and priority mix show up, keep reading.
Where Things 3 repeats break down: fairness, weighting, sharing, capacity
Four specific gaps follow from the clone model. They shape the checklist and the verdicts later, so they are worth walking through carefully.
- Fairness between people. Things 3 has no turn-taking. It keeps no memory of who cleaned the kitchen last or whose turn comes next, so a fair split between two people depends on memory and negotiation outside the app.
- Task weighting. There is no native way for important recurring work to surface more often than low-stakes work. Every repeat fires at whatever cadence you typed, regardless of consequence.
- Household sharing. A shared rotation between partners or family simply is not a Things 3 concept. A repeat lives in one person's database, with no native way for two people to share one rotation and its history.
- Capacity awareness. Things 3 does not know how much recurring work fits your week. Add repeats faster than you complete them and the overdue list is the inevitable result. If your pile-up feels structural rather than personal, a breakdown of six reasons recurring tasks pile up covers the mechanics.
Each gap maps to the rotation-first answer: a planner that decides what deserves attention next, builds a realistic plan around the capacity you actually have, and keeps the rotation moving instead of letting it convert into debt.
Things 3 vs a rotation planner: the comparison checklist
Recurring-work criterion | Things 3 | A rotation planner (Cycles) |
|---|---|---|
Repeat entry friction | Excellent: type "every week on Monday" | Set the rotation once, with mode, order, and participants |
Strict, fixed-order repeats | Approximated by date-based repeats | Native strict mode |
Weighted rotations | Not available | Native weighted mode |
Shuffled rotations | Not available | Native shuffled mode |
Fairness and turn-taking | No memory of who did what | Tracks whose turn it is |
Shared household rotation | Not a Things 3 concept | Rotations shared between people |
Overdue handling | Debt accrues until cleared | Rebalances instead of accruing |
Read honestly, the table is not one-sided. Things 3 wins on entry friction and ecosystem polish, and those wins matter daily. The rotation planner wins on fairness, weighting, household sharing, and capacity, which are exactly the four places recurring work tends to break down.
Privacy-conscious Apple users get one more deciding factor. Things 3 relies on its Things Cloud sync subscription to keep devices in step, which means planning data takes a server round-trip. Cycles is local-first: every rotation decision happens on your device, with no server involved. For people who care where their household data lives, that difference is not cosmetic.
The cheapest way to decide is empirical. Pick one real rotation, run it side by side in both tools for two weeks, and watch which one you actually open during the busy week. Feature tables persuade; two weeks of real use decides.
Worked scenarios: a chore wheel, a creative practice, and home maintenance
Abstractions are easier to judge with real tasks. Here are three recurring domains, each walked through both tools.
A chore wheel for two
In Things 3, one partner creates "clean the kitchen" with a weekly repeat. The other partner either duplicates it in their own database or trusts the first person's list. Either way, the app cannot say whose turn it is, so fairness rests on memory and goodwill, which is exactly where it erodes.
A rotation-first setup treats the chore as shared from the start. The planner tracks whose turn it is, and the split stays even when schedules slip. If one of you works rotating shifts, the harder version of this problem is covered in keeping a fair home rotation when your work schedule rotates.
A creative practice
Say your practice spans writing, music, and sketching. Date-cloned repeats give you "write" on Tuesday and "practice guitar" on Thursday, in the same order forever, and skipped sessions become red debt. The order cannot vary, because a repeat has no order to vary.
A shuffled rotation holds a pool of creative sessions and draws a varied next pick each cycle. Deliberate variety is one of the levers for sustaining a creative practice and avoiding burnout, and shuffling is the mode built for it.
A home maintenance spread
A house runs on many small recurring jobs, from smoke alarm tests to filter changes, and they are not equally important. In Things 3 each job gets its own repeat at its own cadence, and nothing relates the critical ones to the trivial ones or to the hours you actually have.
Weighting fixes the first half: critical upkeep surfaces more often than low-stakes checks. Capacity awareness fixes the second: maintenance spreads across the weeks you can absorb, so it stops converting into overdue debt. A workable template is to rank each job by consequence, weight the ones that bite, and let capacity place the rest.
Verdict by use case: picking the best app for recurring work
There is no single winner here, only fit by situation.
Stay in Things 3 if your recurring work is solo, fixed-cadence, strictly ordered, and Apple-only. You genuinely lose nothing, and you keep one of the best-designed apps on any platform.
Go hybrid if you like Things 3 for deadlines and projects but recurring work keeps sliding. Keep one-off and deadline-driven work where it is, and move only the recurring domains to a rotation planner. This is the pragmatic middle path: each tool does the work its philosophy actually supports.
Move your recurring work entirely when fairness between people, weighting, shared household work, or capacity awareness keeps breaking down in your current setup. If you have rebuilt your repeats more than once and the overdue list keeps winning, the bottleneck is the tool's philosophy, not your discipline.
For privacy-conscious users, local-first planning with no server round-trips can decide the question on its own.
Before committing either way, See how Cycles works.
Due dates for deadlines, rotations for recurring work
The dividing line is clean. Things 3 excels at date-shaped, deadline-driven work; rotation thinking fits work that needs balancing across people, priorities, and capacity. Your recurring work only becomes an overdue list if your tool's philosophy allows it, and that choice gets made the day you set up the app, long before you miss anything.
The next step is small: pick one recurring domain, whether home, health, creative, or admin, and run it as a rotation for a month. If the rotation holds and the overdue list shrinks, you have your answer. If the fixed weekly rhythm was never the problem, then Things 3 was never wrong for you, and now you know why.