Productivity & Workflows
Ellie Planner Review: Timeboxing, Brain Dumps, and Subscription Options
Evaluate Ellie with a completed interrupted-day plan and seven-day paper fit record. Compare collection, timeboxing, calendar side effects and monthly, annual or Lifetime commitments without assuming a trial passed.
Ellie Planner is worth evaluating if you want a simple sequence: capture loose tasks, choose what fits today, then place selected work into timeboxes. Its value depends on whether you keep collection separate from commitments when the day changes. A full calendar is not evidence of completed work, and Lifetime pricing should follow a demonstrated fit rather than precede it.
This LandOffer.ai review uses current official documentation and personally inspected public pricing on October 27, 2026. The interrupted workday and seven-day fit record are authored planning exercises. Offline checks verify interval and cost arithmetic only. No Ellie account, trial, task, calendar connection, event, reminder, export, payment or cancellation was created or tested.

Brain Dump is a collection space, not today's promise
Ellie's Brain Dump guide describes a place to collect tasks as they arise and review them deliberately. That is useful when your current list mixes obligations, ideas and requests you have not accepted. Capturing a thought gives it somewhere to wait; it does not establish that it belongs in today's schedule.
Identify the next action before assigning it a block. “Scanner guide” might mean draft instructions, confirm a disputed step or ask for a review. Each has a different duration and dependency. When the action is still unclear, keep the clarification visible rather than filling the calendar with a confident but meaningless estimate.
The same distinction protects other people's commitments. A request in your Brain Dump has not necessarily been accepted by you, your manager or a reviewer. Identify who can change its timing and what must be delivered before turning it into a planned block. An attractive daily board cannot supply missing authority.
Timeboxing can stay separate from external calendars
The Timebox guide describes dragging tasks onto a calendar without requiring an external calendar connection. It also documents a week view and moving a timeboxed task back to Kanban on web and desktop while retaining the task. These are product descriptions, not evidence that an interrupted day's work will automatically fit.
That separation is a useful evaluation boundary. You can first decide whether the method matches your work using synthetic inputs and the documented internal planner. Connecting an employer's calendar is a further decision about data and event side effects. A personal planning requirement does not itself authorize that connection.
Preserve a meaningful estimate and an explicit stopping point for each block. A 90-minute drafting session might produce a reviewable first version rather than finish an entire guide. If a task takes longer, record the remaining work. Stretching its rectangle until the day looks orderly can hide the trade-off that someone needs to approve.
A completed day before and after an interruption
The fictional Finch warehouse team needs a reviewed scanner-training checklist by Tuesday, November 3, 2026 at 16:00 UTC. Anouk owns the checklist. Keir owns its technical review, and operations lead Celia owns any change to the required scope or delivery date. The required output is a six-step checklist with a confirmed exception route.
The planning exercise uses Ellie Web on a managed Mac and an iPhone for consultation, without connecting a calendar. Both devices and the chosen workflow are scenario requirements, not tested installations. Existing meetings, lunch and administrative work are entered as planning constraints. Their inclusion does not claim that Ellie imported or reserved them.
Anouk's Monday, November 2 workday runs from 09:00 to 17:00 UTC. The initial plan contains 285 minutes of selected task work, 60 minutes of planning, shutdown and administration, 60 minutes of meetings, 45 minutes of lunch and 30 minutes of buffer. The resulting 480 minutes account for the whole day, including the reviewer conversation Anouk must attend.
At 10:45, a clarification request arrives about a conflicting scanner instruction. Celia accepts it as a 45-minute priority for that day. Anouk uses the first 15 minutes to identify the disputed step, pauses for the existing meeting and lunch, then completes the remaining 30 minutes after lunch. The request is invented; no actual workplace incident or hardware test occurred.
The filled revision is:
| Work or constraint | Baseline | Revised decision |
|---|---|---|
| Choose today's work | 09:00–09:15 | Retained |
| Draft six checklist steps | 09:15–10:45 | Retained; first version ready for later validation |
| Morning buffer | 10:45–11:00 | Used for the first 15 minutes of the priority clarification |
| Existing meeting and lunch | 11:00–12:00 and 12:00–12:45 | Retained; nobody else's meeting is moved |
| Validate the six steps | 12:45–13:45 | Moved to 13:15–14:15 after the remaining clarification work at 12:45–13:15 |
| Keir's technical review | 13:45–14:15 | Moved to 14:15–14:45 with Keir's explicit fictional agreement |
| Apply review comments | 14:15–15:00 | Moved to 14:45–15:30 |
| Optional illustrated cover | 15:00–15:30 | Returned to the unscheduled collection; outside the required six-step scope |
| Package the checklist | 15:30–16:00 | Retained |
| Administration, buffer and shutdown | 16:00–16:30, 16:30–16:45, 16:45–17:00 | Retained |
The new 45-minute priority uses the original 15-minute morning buffer plus the 30 minutes freed by deferring the optional cover. No extra capacity is invented. The later 15-minute buffer remains. The revised calendar still accounts for 480 minutes, and the selected work now totals 300 minutes, including the priority request but excluding the cover.
This is a completed time-allocation design. The local Python interval check found no overlap among the revised blocks and confirmed continuous coverage from 09:00 to 17:00. It did not perform a drag operation in Ellie. Keir's agreement and every work result are authored facts within the example. If the reviewer cannot accept the new slot in a real situation, this revision is not feasible and a different scope or timing decision is needed.
Close the day without calling rollover completion
In the fictional closeout, Anouk finishes the clarification, six-step validation, review changes and packaging. Keir accepts the checklist content, while a separate optional illustration request remains unscheduled. The authoritative document records the reviewed version; a planner checkmark is not used as the only evidence of acceptance.
Ellie's current Calendar Kanban guide describes eligible incomplete tasks rolling to the next day after local midnight when rollover is enabled. Brain Dump items do not roll over, and tasks more than 14 days overdue remain where they are. It also describes a separate recurring-task rollover switch on web and desktop that is off by default.
Those details change how to interpret a tidy next-day board. A moved task may still be unfinished, while an unscheduled thought may remain in Brain Dump. Review both places before assuming tomorrow contains every unresolved item. Neither state should be mistaken for acceptance, dismissal or completed work. For Finch, the optional cover remains a deliberately deferred item with a named reason, not something assumed to have rolled or vanished.
The recurring-task guide separately describes editing one instance versus updating all incomplete instances. A routine planning block should not accidentally rewrite every future instance because today's interruption required an exception. No recurrence or rollover setting was changed for this review.
Calendar integrations have different write boundaries
The Google Calendar guide distinguishes overlaying events from adding Ellie tasks as calendar events. It documents overlay as the default linked behavior, optional two-way task/event synchronization and a Busy-title option. It also says changing the default destination affects future timeboxes rather than moving previously timeboxed tasks.
That is more specific than “calendar integration included.” Before connecting, identify whether you only need context or intend to create and modify external events. Check the actual destination and recipient visibility in an authorized synthetic evaluation. A Busy title is not proof that every underlying detail is hidden from every authorized account or administrator.
The Apple guide describes a different setup on iOS and web/desktop, and says linking Ellie tasks to Apple events with Google-style two-way synchronization is not supported. Its documented ability to move or delete Apple events is another reason not to treat an overlay interface as inherently read-only.
The Outlook guide describes overlay and optional task/event synchronization separately as well. None of these paths was connected or tested here. Finch's current decision remains internal planning with manually recorded constraints; any integration requires its own approval and acceptance evidence. The current pricing FAQ says there is no Android app; an Android-only requirement would therefore stop this device-fit proposal.

A filled seven-day fit record without an invented trial
The second asset uses the same Finch requirement. Anouk considers a seven-day evaluation from November 2 through November 8. The following is a completed documentation-and-paper review record, not a log from an Ellie trial. “Supported” means the reviewed documentation describes a route; actual account behavior remains untested.
| Day and question | Filled finding from the planning exercise | Fit decision and remaining test |
|---|---|---|
| Monday: can an interruption fit? | Priority work takes 45 minutes; buffer and an optional cover supply that time | Planning method is coherent; actual drag, duration and saving behavior untested |
| Tuesday: is delivery separate from scheduling? | Checklist acceptance and the 16:00 cutoff remain in the source record | Keep planner as preparation aid; no delivery or acknowledgment was actually sent |
| Wednesday: what remains in collection? | Optional cover and a possible second checklist wait unscheduled | Brain Dump fits collection conceptually; capture and retrieval untested |
| Thursday: what happens to unfinished work? | Rollover rules are documented separately from Brain Dump | Check saved settings and one synthetic incomplete task before relying on them |
| Friday: do calendar events need writeback? | Current requirement only needs existing commitments as context | No connection approved; if overlay is later required, verify the chosen provider route |
| Saturday: which devices matter? | Web and iPhone fit the stated device requirement; Android is not required | Actual interface and synchronization still need evaluation |
| Sunday: which payment commitment is justified? | Method fits on paper, but repeated daily use and account behavior are unknown | Prefer a limited monthly evaluation after an approved trial; hold annual and Lifetime |
The record finishes the provisional buying decision while keeping the trial itself unperformed. It also supplies stop conditions: inability to preserve a task when unboxing it, unexpected external event writes, or missing required device behavior would hold purchase. A successful arithmetic exercise cannot override any of those product failures.
Compare subscriptions and Lifetime after fit
The personally inspected pricing page showed $9.99 monthly. Selecting Yearly changed the card and post-trial text to $99.99 per year. Lifetime was $299.99 once. The current FAQ states seven-day trials for monthly and yearly subscriptions and explicitly says Ellie has no free plan. An earlier retrieved layout described Free; the loaded current page and a fresh re-opened body agreed on the trial model.
These are displayed dollar prices, not a verified currency selection, tax-inclusive checkout or employer reimbursement. The page describes Lifetime as the same current Pro features without a recurring bill. That does not establish unlimited service longevity, future feature promises or a tested export-and-restore route.
Twelve monthly payments total $119.88 at the displayed rate. Annual prepayment is $19.89 less. Three annual payments total $299.97, two cents below the one-time Lifetime price; 30 monthly payments total $299.70, also slightly below it. These are simple price comparisons, not a forecast that the product will remain suitable or available for those periods.
Anouk's completed recommendation is therefore an approved seven-day trial first, followed by monthly only if the missing product checks pass. Annual remains a later option if repeated use supports a longer commitment. Lifetime is deferred. No trial was started, billing cancellation deadline observed or payment committed by this article.
Ellie offers a documented collection-to-timebox workflow; evaluate it against a disrupted day and explicit account-side checks. Preserve the deferred work, required output and external commitments before evaluating convenience. LandOffer.ai publishes this review; actual synchronization, reminder delivery, daily adherence and time savings remain unmeasured.
Sources and Further Reading
- Ellie pricing — Public Monthly and Yearly selections inspected October 27, 2026.
- The Brain Dump
- The Timebox
- Calendar Kanban and rollover
- Recurring tasks
- Google Calendar integration
- Apple Calendar integration
- Outlook Calendar integration


