Productivity & Workflows
TickTick Premium Review for Work: Calendar Views, Filters, and Collaboration Boundaries
Evaluate TickTick Premium through a completed monthly work plan and known filter results. Separate personal calendar benefits, recurring routines, fixed commitments, shared-list permissions and current upgrade limits.
TickTick Premium is worth evaluating when you need richer calendar planning, task durations or saved filters across your own work. Recurring tasks and basic organization are available without making those needs alone an upgrade case. Shared lists can support bounded collaboration, including member permissions, but a filtered personal view is not an access boundary or a substitute for your team's approval system.
This LandOffer.ai review checks official sources and personally inspected public pricing on October 27, 2026. The monthly plan, filter results and purchasing decision below are authored examples. Offline arithmetic checks their dates, workload and selected task IDs; no TickTick account, calendar, recurrence, filter, reminder, invitation, permission or subscription was changed or tested.

Start with the requirement that actually needs Premium
The current English upgrade page displayed US$49.99 per year. Its comparison includes recurring tasks in Free, while Duration and Filter are Premium features. Calendar View is described as Basic versus Unlimited, so “Free has no calendar” would overstate the distinction. The displayed annual equivalent is not an independently verified monthly purchase option or final tax-inclusive checkout.
The same page lists nine versus 299 lists and 99 versus 999 tasks or notes per list. That can matter for a large inventory, but capacity is not the only upgrade reason. A person with four modest lists might still need duration-based planning and a reusable focus view. Someone with a simple recurring checklist may remain satisfied with Free.
Paying for Premium does not create work capacity. A task occupying a calendar interval does not confirm the owner has that time available. A shared assignment does not establish that a colleague agreed to deliver it. Keep the actual commitment, named reviewer and work capacity in the planning record, even when a calendar makes those details easier to see.
A completed month with routines and a fixed commitment
In the fictional Cedar workshop, Ellis prepares a monthly equipment-care bulletin. The bulletin must reach operations lead Farah by November 20, 2026 at 15:00 UTC. Its required scope is three equipment entries and their reviewed care instructions. Ellis owns preparation; reviewer Tomas owns technical comments; Farah owns any change to the delivery commitment.
Ellis intends to use TickTick Web on a managed Windows 11 laptop and consult an Android phone. Those are scenario devices, not tested installations. The source bulletin and final acceptance remain in the workshop's approved document system. TickTick is a candidate personal planner and a small shared review list, not the authoritative record for changing an equipment procedure.
Here is the filled planning specification. Dates and duration entries are intended configuration choices, not strings proven to parse or synchronize in an account.
| Work item | Chosen date or recurrence | Completed planning decision |
|---|---|---|
| Review the equipment-care queue, Ellis | Monthly on the 5th; calendar-based routine | November review planned November 5; December routine remains December 5 |
| Confirm three source entries, Ellis | November 10, 45 minutes | Required input check; no extra entries added without a scope decision |
| Draft the three entries, Ellis | November 12, 90 minutes | One preparation block after confirmation |
| Technical comments, Tomas | November 16, 45 minutes | Agreed fictional reviewer slot; not counted as Ellis's capacity |
| Apply comments, Ellis | November 17, 45 minutes | Changes depend on the completed review |
| Package the reviewed bulletin, Ellis | November 19, 30 minutes | Requires accepted content and the approved destination |
| Deliver bulletin, Ellis | November 20, 15 minutes, before 15:00 UTC | One-time commitment recorded in the task description and source document |
| Clear the temporary reference shelf, Ellis | Every 14 days by completion date | Spacing after actual cleanup, unrelated to the bulletin's delivery cutoff |
Ellis has four hours available for the five one-time preparation and delivery items. They total 225 minutes, leaving 15 minutes of unallocated capacity. Tomas's 45-minute review is additional work by a different person; it must have its own confirmed allocation. Routine queue review and shelf cleanup have separate allocations; they have not disappeared into the four-hour bulletin budget.
The complete fictional change record begins when source confirmation slips from November 10 to November 11. Ellis retains the November 12 draft block because the input still precedes it. No extra task is added, and Farah's November 20 cutoff remains unchanged. The calendar is revised to reflect an internal dependency, rather than silently moving the commitment.
Choose recurrence by what the routine means
The current recurrence guide distinguishes repetition by due date, completion date and specific dates. Completion-based repetition calculates the next reminder from completion. The guide also describes changing a calendar occurrence with “Only this Recurrence.” Those documented choices deserve checking against the saved result before real adoption.
For Cedar, the monthly queue review stays tied to the fifth. In the authored record Ellis completes the November 5 review late, on November 7, without intentionally changing its calendar pattern. The planning expectation is still December 5. Shelf cleanup instead completes November 7 under a 14-day completion-based rule, making November 21 the intended next date.
Those are expectations based on the chosen meanings, supported by offline date arithmetic. They are not observed TickTick recurrence results. A live evaluation should inspect both the saved rule and the generated next occurrence, especially after an exception or changed date. Do not transfer another app's recurrence syntax into TickTick and assume it means the same thing.
The bulletin's November 20 cutoff is one-time. It is not the repeat end date for queue review or shelf cleanup. In this plan, the cutoff is explicit text linked to the authoritative work record; no separate immutable deadline field, automatic escalation or enforcement is assumed. A later cleanup occurrence says nothing about whether the bulletin was delivered.
Calendar views reveal a plan, not guaranteed availability
Calendar View Options describes choosing displayed lists, coloring tasks by list, tag or priority, and displaying future recurring cycles. These controls change what a planner sees. Excluding the shelf list from a view does not eliminate its work, and showing future repeats does not establish that those occurrences were completed.
The freshly inspected guide also limits its described batch calendar operations to Windows and Web, noting that drag-and-drop is not yet supported on macOS in that section. Cedar's Web planning fits the documented route; an organization evaluating a different client should inspect its actual controls. This review did not test bulk postponement, dragging or Android parity.
Ellis's completed personal-view decision is to show the Bulletin and Care Queue lists in the weekly planning view, while consulting Shelf separately during routine review. Tomas's assigned review remains visible as a dependency, without being counted as Ellis's own work. Farah's fixed cutoff is checked against the source record each time a preparation block moves.
A color can help locate a task, but it should not carry the only copy of its meaning. Record “source confirmation,” “review pending” or the delivery cutoff in readable task text. That makes the plan intelligible to someone viewing a different layout or a printed task list.
A saved filter needs a known inclusion set
The filter guide describes normal filters by attributes and content, plus advanced combinations using AND and OR. It also describes previewing the result. Use that preview to challenge a filter with known examples, including a task it should exclude and a task on the final included day. A clean screen is a poor success measure if it has quietly hidden the task that matters.
For a second completed asset, Ellis defines “My bulletin preparation, November 10–19 inclusive.” The intended logic is: Bulletin list AND assigned to Ellis AND date in that closed range. This is a plain-language specification, not tested TickTick query syntax. The seven-row authored reference set is:
| ID and task | List, owner and date | Intended result and reason |
|---|---|---|
| B1 Confirm sources | Bulletin; Ellis; November 11 | Include: matches all three conditions |
| B2 Draft entries | Bulletin; Ellis; November 12 | Include |
| B3 Technical comments | Bulletin; Tomas; November 16 | Exclude: different owner, though still a dependency |
| B4 Apply comments | Bulletin; Ellis; November 17 | Include |
| B5 Package bulletin | Bulletin; Ellis; November 19 | Include |
| B6 Deliver bulletin | Bulletin; Ellis; November 20 | Exclude from this preparation range; delivery remains separately monitored |
| S1 Shelf cleanup | Shelf; Ellis; November 21 | Exclude: different list and outside the range |
The correct inclusion set is B1, B2, B4 and B5. Their estimated effort totals 210 minutes. Adding B6's 15-minute delivery recovers the complete 225-minute one-time budget. The local offline selection check reproduced those IDs and totals only. It evaluated authored row attributes in Python, without connecting to TickTick or executing its filter engine.
The completed review finds an important limitation: this filter intentionally omits the delivery task and Tomas's review. Ellis therefore pairs it with an unfiltered Bulletin list review before changing dates or reporting readiness. The four returned tasks can all look orderly while a dependency or final cutoff is still at risk. Document exclusions alongside the returned tasks.
Collaboration has a list boundary and a subscription boundary
The current team collaboration guide documents assigning tasks, comments and list-member edit, comment or read-only permissions. It says only the shared list's content is exposed by sharing that list, and only its owner needs Premium for the expanded sharing arrangement. Non-Premium collaborators do not acquire Premium features through membership.
For Cedar, Ellis is the proposed Premium owner of a Bulletin Review list. Tomas is a proposed editor; Farah is a proposed commenter. Private preparation and shelf tasks stay outside that list. The shared content would contain the three review entries and source-document links permitted for those colleagues. Source-document access would require its own approval; adding a link does not grant it.
This is a completed access design, not an invitation receipt or verified permission configuration. Farah's comment role would not make her task comments an automatic formal approval. Likewise, Ellis's personal filter cannot hide a sensitive task from someone who already has access to the shared list. Use the actual list boundary and authorized member settings, then verify the recipient view when an evaluation is approved.
The upgrade table labels member counts as two and 29, while the general FAQ describes one added member for Free and up to 29 added members for Premium. Confirm owner-versus-member counting before buying at the limit. Cedar's two proposed collaborators do not depend on resolving the upper boundary, but the discrepancy should not be turned into an invented team-wide entitlement.

The completed Free-to-Premium decision
Ellis's requirement record contains four lists with fewer than 99 tasks each, two proposed review collaborators, monthly and completion-based routines, explicit durations and a saved personal preparation filter. List capacity and recurrence alone do not make the upgrade case. Duration, richer calendar planning and the reusable filter do.
The decision is to evaluate one Premium subscription at the currently displayed US$49.99 annual rate, keeping Tomas and Farah as collaborators rather than buying three subscriptions automatically. If all three independently need Premium planning tools, the same displayed rate would imply US$149.97 annually. These are arithmetic assumptions before tax or platform-specific offers, not an employer purchase or a guaranteed account entitlement.
Attachment-heavy work needs a separate check: the current upgrade comparison says 199 attachments per day, while the general FAQ still says 99 for Premium. Cedar keeps source documents in its approved system and does not use either figure to justify purchase. Resolve the applicable account limit before migrating an attachment-heavy workflow.
The upgrade FAQ says data remains after Premium expires but paid features become unavailable. Retained tasks therefore do not guarantee an unchanged working view or continued access to the same paid-only controls. Before relying on a downgrade route, preserve readable commitments, recurrence meanings and an accessible source record outside a paid-only filter.
TickTick Premium is a reasonable candidate for this bounded personal-planning requirement. Continue with an authorized client evaluation of the saved durations, recurrence exceptions, known filter results and recipient permissions. Keep the delivery commitment and source approval separate. LandOffer.ai publishes this review; actual reminder delivery, synchronization, permissions and productivity outcomes remain unmeasured.
Sources and Further Reading
- TickTick English upgrade page — Native public pricing and comparison inspected October 27, 2026.
- Set Up Recurring Tasks
- Calendar View Options
- Filters: Choose What You Want to See
- How Teams Can Collaborate
- TickTick general FAQ


