Remember The Milk / Forums / Tips & Tricks

Reply to Tired of unrealistic to-do lists? I wrote an open-source MilkScript that turns RTM into a personal Agile Coach ⏱️🌡️

mordimer86 (Pro) says:

What you've built is genuinely impressive.

I keep an eye on what gets posted here, and yours stopped me, it looks like something I would have built myself a few years ago. Not just the fact that it's thousands of lines of MilkScript in an environment that was never meant to carry this kind of weight — but because behind all of it there's clearly someone who has felt the planning problem in their bones and tried to engineer their way out of it. The schedule simulation, the capacity modeling, the weighted triage, the historical correction — none of that comes from reading about productivity. It comes from getting burned.

So this isn't a view perspective from the outside. It's more like running into someone on the same road I spent years walking.

My own version was building steadily more sophisticated planning systems inside my task manager. The pattern was always the same: over-optimistic capacity, bad duration estimates, and a generous helping of ADHD procrastination on top. And because every failure looked like a forecasting error, the fix always seemed obvious — a better forecasting engine. Tighter estimates. Smarter correction factors. More math.

What actually changed things for me wasn't a better engine. It was realizing I had been doing something subtly wrong the whole time: I was planning *time* inside a tool built to manage *tasks*.

Once I named it that way, a lot fell into place. I moved time planning into the calendar, where time actually lives, and let the task manager do what it's good at — holding commitments, not schedules. The setup became GTD-flavored and context-driven: recurring vs. current, PC vs. non-PC, what's actionable right now given where I am. The calendar owns time; the list owns commitments. The moment I stopped trying to schedule my entire life inside the task list, the whole thing got resilient. A new job, shifted responsibilities, a blown-up routine — those stopped being reasons to rebuild the machinery and became just... a new context.

Which is the question your project quietly put in front of me, and I mean it as an architecture question, not a verdict:

Have you built an extraordinarily sophisticated task manager — or have you built a calendar, with a real scheduling engine inside it, and then placed that calendar inside a task manager? Because a lot of what I see — fixed working hours, day boundaries, minute-level simulation — is the kind of thing time-and-calendar tools exist to own. When that logic lives inside the task list instead, every change in your life has to be re-encoded by hand, rather than just absorbed.

A couple of smaller things pointed in the same direction for me.

One was the historical efficiency correction. That's a sound instinct — averaging over a longer window is more robust to day-to-day noise, and I'd lean the same way. But it made me wonder what happens the week after you're sick, or back from a holiday, or right after one of those rare weeks where you finally clear a mountain of backlog. A rolling average can't tell the difference between "the world changed" and "this was just a noisy week," so it keeps quietly pricing in a reality that's no longer true. That's not a tuning problem. It's a question of whether the system can recognize a change in regime at all — and that's a hard thing to express in fixed rules.

The other was the relationship to data structure. If a malformed tag can stop the system and ask the user to repair things, then some of the upkeep has quietly moved onto the person. Keeping the data clean has become *their* job. And that's the part that struck me most, because that kind of work — tolerating mess, inferring intent, keeping order without bothering you about it — is exactly the kind of thing that can now happen quietly in the background instead of surfacing as an error you have to go fix. A parser stops and demands repairs. Something that understands intent just keeps going.

And that's really what I kept circling back to — the word *coach*.

A coach doesn't just count. A coach notices the pattern you didn't encode. A coach says the uncomfortable thing — "this task has been postponed three hundred times; I don't think the problem is capacity." A coach tells avoidance apart from overload, and changes tactics when the current one clearly isn't working. An engine, however good, computes. It doesn't do any of that — not because it's badly built, but because that's not what engines are.

So I found myself wondering whether you've built a remarkable planning *engine* and then hung the word "coach" on it.

To be fair, that might be exactly what you want. Some people genuinely prefer a deterministic system they can trust to behave the same way every time, and there's nothing wrong with that. What works for me isn't automatically right for you.

But if I were carrying this work forward, I'd be tempted in a different direction. The expertise it takes to design something like this is the same expertise it takes to design an *assistant* rather than a *tool*. RTM Pro already exposes MCP access — the hook that lets AI assistants like Claude connect to it directly. The deterministic parts — the math, the scoring, the forecasting — can stay deterministic, where determinism is a virtue. But the judgment, the grooming, the pattern-spotting, the honest conversations — those never sit comfortably inside hardcoded logic, no matter how many lines you give them.

One thing I've learned, partly from doing requirements analysis for a living, is that it usually deletes more than it adds. If a chunk of a system disappears because a better architecture made it unnecessary, that isn't lost work — it's the abstraction getting sharper. The instruction can describe *what* to achieve and leave the *how* adaptive, which is the one thing rigid logic can never do.

So I'll leave it as the question I couldn't put down after reading your post: picture this system five years from now. Is it an even more capable deterministic engine — or has it grown into something that behaves more like a collaborator than a calculator?

Either way, real respect for what you've made. If you ever want to compare notes — how the context-driven setup works in practice, or where I think the deterministic / judgment line falls — I'm genuinely happy to share. I have a strong feeling that with your engineering instincts pointed at the design problem rather than the implementation, you'd build something well past anything I've managed.

(Full disclosure: I'm wired pretty technically myself, so I ran these thoughts through an AI to make them readable — the intent is mine, the phrasing had help. Felt only fair to say, given the topic.)

P.S. — small practical thing, unrelated to any of the above: a few bits in the English setup section still have the original Chinese in them (the `rtm.args` parameter labels). An English-only user copying the steps would hit a wall there. Easy fix, just easy to miss.

Tired of unrealistic to-do lists? I wrote an open-source MilkScript that turns RTM into a personal Agile Coach ⏱️🌡️

grant.yi (Pro) says:

Hey fellow productivity nerds,

We’ve all been there: piling 50 hours of tasks into a 40-hour workweek, only to feel completely burnt out and defeated by Thursday. Remember The Milk is fantastic for capturing what needs to be done, but it doesn't inherently tell you if you actually have the time to do it.

I got tired of constantly overflowing my schedule, so I spent some time leveraging MilkScript (RTM's automation engine) to build something I’m calling the RTM Agile Coach.

It’s completely free and open-source. Basically, it transforms RTM from a passive checklist into an active, capacity-aware project manager.

Here is what it actually does behind the scenes:

⏳ Precision Scheduling Engine: You tell it your working hours (e.g., 9 AM - 6 PM, Mon-Fri). It simulates your task list minute-by-minute. If a task hits 6 PM, it automatically carries the remaining hours over to the next working day.

📅 **实时战略排期推演 (Schedule)**
• 预计完工: 2026-06-06 10:06:15 星期六
*（注：排期表展示的预计完工是“最坏情况”（Worst Case）：如果你白天完全没时间做这个任务，晚上要搞到几点。）*
🟢 [06-02(二) 10:29 - 10:39] 检查****回复-0.33🍅 (10m)
🟢 [06-02(二) 10:39 - 11:39] 查询****材料？-1.00🍅 (30m)
🟢 [06-02(二) 11:39 - 13:40] 2.2.5-如何****-2.00🍅 (60m)
🟢 [06-02(二) 13:40 - 15:40] 3-2-1-在****更新****-2.00🍅 (60m)
🟢 [06-03(三) 09:00 - 09:05] 3.****验证-0.17🍅 (5m)
🟢 [06-03(三) 09:05 - 09:35] 弄清楚****是什么-1.00🍅 (30m)
🟢 [06-03(三) 09:35 - 09:40] 3.****验证-0.17🍅 (5m)
🟢 [06-03(三) 09:40 - 11:40] 准备****材料-2.00🍅 (60m)
🟢 [06-04(四) 09:00 - 09:05] 3.****验证-0.17🍅 (5m)
🟢 [06-05(五) 09:00 - 09:05] 3.****验证-0.17🍅 (5m)
➖➖➖➖➖➖ 🧨 标准容量耗尽 (转入加班推演) ➖➖➖➖➖➖
🧨 [06-06(六) 10:00 - 10:06] 3.****验证-0.17🍅 (5m) (加班)
↳ 📉 **阻塞瓶颈**: 高顺位任务占据加班通道，后续2任务被迫顺延。
🧨 [06-06(六) 10:06 - 10:06] 4.发放**** (0m) (加班)
🧨 [06-06(六) 10:06 - 10:06] 4.发放**** (0m) (加班)
• 目标死线: 2026-06-06 23:59:59 星期六

🌡️ Visual Workload Heatmaps: It generates a literal heatmap inside an RTM note. At a glance, you can see which days are 🟩 (idle/comfortable), 🟧 (saturated), or 🟥 (dangerously overloaded).

🌡️ **每日实时战略负载热力 (Load Heatmap)**
🟨 06-02(二): 69% [ 5.2/ 7.5h] 🟢空闲2.3h
🟩 06-03(三): 35% [ 3.2/ 9.0h] 🔒含日程📅(0.5h) 🟢空闲5.8h
🟩 06-04(四): 1% [ 0.1/ 9.0h] 🟢空闲8.9h
🟩 06-05(五): 1% [ 0.1/ 9.0h] 🟢空闲8.9h
🧨 06-06(六): N/A [ 0.1/ 0.0h] 🧨加班0.1h

✂️ Smart Triage & Pruning: If you overbook yourself, the script doesn't just warn you—it gives you solutions. It uses a weighted algorithm (Objective Priority + Task Priority + Urgency) to recommend exactly which tasks you should drop, delay, or move to an empty slot.

🚀 ** 行动指南(Action Plan) **
------------------------------------------------------------
⚠️【高压预警】需加班 (预测拥挤度 25%)

🤔👉 **系统研判**: 任务堆积在休息/下班时段，导致局部加班 (全局其实有盈余)。
--------------------------------------------------
💡 **诊断与建议**: 宏观总容量充裕 (仍有约 12.9h 盈余)。当前警报纯粹是因为**死线太紧**或**任务被锁定在休息日**。
👉 **建议行动：无需删除任务。只需推迟死线，或将休息日任务平移至工作日，警报即可解除。**
------------------------------------------------------------
📊 ** 核心指标速览 **:
• 排期拥挤度: 24.9%
• 预测总耗时: 8.6 h(🔒0.5h) | 可用 34.5 h
* (注: 预测耗时 = 任务加权工时 + 日程📅)*

🔋 Fatigue-Aware Overtime Advice: Thinking of pulling an all-nighter? The script calculates the "cognitive cost" (e.g., 1 hour of overtime ≈ 0.8 hours of real output). If you try to schedule work past 9 PM, it triggers a "circuit breaker" and bluntly tells you to cut your scope instead.

🧠 Adaptive Efficiency Tracking: It looks at your historical data (past 7/30/180 days) to figure out your actual completion rate, adjusting its predictions so you stop falling for the Planning Fallacy.

📊 **实时战略容量分析 (Capacity)**
• 实际📍需求: 8.1h (原始 4.6h +77%)
↳ 算式: ∑ (预估 × 效率) / 60
↳ 详情:
• 1.5-📌-****: 1.50h × 2.00🌐 = 3.00h
• 1.5-📌-1.将****准备好-7: 1.00h × 2.01🎯 = 2.01h
• 1.10-🎉-3.更新****: 1.00h × 2.00🌐 = 2.00h
• 1.4-⛳-1.****步骤-4: 1.08h × 1.00🎯 = 1.08h
• 日程📅占用: 🔒0.5h
• 可用🟢容量: 34.5h (截止 2026-06-06)

Who is this for?
If you are an RTM Pro user who uses MilkScript and loves the GTD/Agile methodology, this is for you. It does require setting up some specific tags (like 1.1-🔭 for objectives), but it is highly customizable.

Where to get it:
I’ve open-sourced the entire script and documentation on GitHub here: [ https://github.com/yxxyle/thex ]

I would absolutely love for this community to try it out, tear it apart, and tell me what you think. Let me know if you have any questions or need help setting it up!

Happy organizing! 🎯

After 17 years I cancelled RTM — the MCP brought me back

tomkenobi (Pro) says:

After 15 years of RTM Pro I cancelled my subscription. The MCP brought me back the same day.

For the last while I had been building a personal knowledge system in Obsidian, with Claude Code as my main interface — Obsidian basically as the IDE, Claude Code as the brain. (Claude Code does not require Obsidian, by the way — any plain folder of Markdown works.) Over time the system needed task management. I tried doing it inside Obsidian with the Tasks plugin — checkboxes living inside the notes themselves. It worked, technically. But it never felt like real task management.

I had been going back and forth on this for weeks. The RTM Android app was actually one of the reasons I kept hesitating — nothing else feels that solid on mobile. Eventually I cancelled anyway.

Then — moments after the cancellation, I'm not exaggerating — I noticed the MCP banner in the footer of rememberthemilk.com. I plugged it into Claude Code that same day. Suddenly my notes-system and my task list were having a conversation. "Capture this", "what's in the Homelab list", "mark this done with a note about what worked" — all in the same terminal where I'm already working.

I'd played with the RTM API before, but it always meant writing and maintaining a wrapper. The MCP makes Claude itself the wrapper — no scripts, no middleware, no syntax to remember.

My setup today:

- One list per area of life — Homelab, Work, Music, Personal, Projects.
- Projects don't get their own lists — they live in one shared "Projects" list with tags like #server-rebuild or #book-research. A Smart List per area uses a filter like list:Homelab OR tag:homelab; a Smart List per project uses list:Projects AND tag:server-rebuild. Same pattern, two layers.
- Every time I complete a task, I add a short note — what I did, what I learned. After a few weeks, my completed tasks have turned into a personal log.

Daily flow: in the morning, Claude reads my RTM Inbox plus tasks due within three days into a snapshot. In the evening, I review and shift things in conversation. Capturing during the day is just "remember to X" — Claude routes it to the right list and tag automatically. On the go, a small Telegram bot drops anything I send it straight into the RTM Inbox — no priority, sorted at the next pass.

The MCP is the moment RTM stopped being "a separate app I need to remember to open" and became part of how I actually work.

Reply to milk-mcp: Give Claude Code a Memory with Remember The Milk

mordimer86 (Pro) says:

I'm hoping that you understand the scale of what you did here.
#huge #gem #pureGold #HolyGrail

I'm thinking of forking this into a Claude.ai/desktop control app. Free tier in Claude limits number of project to 5, which is a significant bottleneck about instructions and memory management, especially if you have a lot of things open. And that might go away with this.
That's like $250 in annualy savings.

milk-mcp: Give Claude Code a Memory with Remember The Milk

donkitchen (Pro) says:

Hey RTM community! I've been a longtime user, and I just open-sourced something I'm genuinely excited about: milk-mcp — a TypeScript MCP server that uses RTM as persistent memory and task management for Claude Code sessions.
👉 https://github.com/donkitchen/milk-mcp

## The problem it solves ##

Claude Code sessions are ephemeral. Close a session, and all that context — what you were building, what decisions you made, what bugs you spotted — is gone. You end up re-explaining your project every single time. milk-mcp fixes this by anchoring Claude's memory to your RTM account.

## How it works ##

For each project, milk-mcp automatically creates 5 dedicated RTM lists:
✅ TODO — active tasks for the current session
📋 Backlog — deferred and future work
🐛 Bugs — logged with reproduction steps
🏛️ Decisions — architectural choices recorded with rationale
🔁 Context — session handoff notes so Claude picks up right where you left off

Starting a session is as simple as "Let's work on MyProject" — Claude calls rtm_session_start, loads your open TODOs and latest context, and you're off. At the end, "Let's wrap up" triggers rtm_session_end and saves everything for next time.

## Why RTM? ##

Honestly? Because it's the best task manager ever made and I've used it for years 😄 But also because the API is clean, the free tier works great, and now my RTM account does double duty as both my personal task list and my AI's external brain.
Setup takes about 5 minutes — Node.js 18+, your RTM API credentials, one auth script, and one claude mcp add command.

Would love stars, feedback, and contributors. Let's keep building the RTM + AI future! 🥛✨

Reply to RTM MCP - I can talk to RTM in plain English

donkitchen (Pro) says:

This is awesome — love seeing RTM get some AI love! Big props for publishing the first open-source RTM MCP and sharing your daily planning + evening reflection workflow. That pattern detection ("you've been postponing this for 3 days") is exactly the kind of thing that makes AI assistants actually useful rather than just cool demos.

Your post actually inspired me to build my own take: milk-mcp (https://github.com/donkitchen/milk-mcp). Same DNA — TypeScript, RTM, Claude Code — but I took it in a different direction. Where your setup shines for personal productivity and conversational task management, I focused specifically on the developer workflow problem: Claude Code sessions are ephemeral, and losing context between sessions is brutal. milk-mcp turns RTM into a persistent memory layer so Claude picks up exactly where it left off.

It creates 5 structured lists per project (TODOs, Backlog, Bugs, Decisions, and a Context/handoff list) and has dedicated tools for session_start and session_end so the handoff is explicit and reliable. The Decisions list is my personal favorite — architectural choices get logged with rationale, so Claude never asks "why did we do it this way?" again.

Two different tools solving related problems — would love to see the community build on both! 🚀

Reply to RTM MCP - I can talk to RTM in plain English

raymond.bergmark (Pro) says:

Wow, great implementation!
Well worth a Tuesday winner!

RTM MCP - I can talk to RTM in plain English

ljadach (Pro) says:

Hi,

I have built an MCP server for RTM (available as open source to all: https://github.com/ljadach/rtm-mcp) and integrated it with my personal AI assistant on Claude Code. Now together with the Assistant we do the daily planning and day closing and it has full access to my ToDo list from RTM, so I can, in conversational style, discuss my priorities ("what are the top tasks for today"), ask it to make adjustments ("change the due date of all tasks that ....) and create the task automatically resulting from my discussion with AI assistant or from meeting notes processed by AI.

In the evenings, thanks to the MCP integration the Assistant can identify patterns ("you have been postponing this task for 3 days now"), praise me ("you have completed x tasks and I am proud of you for completing x"). It can also maintain the activity log and check if I am progressing against my long term goals and objectives.

I think this is only the beginning. The possibilities of integrating AI with RTM are endless!

Be productive everywhere: A simple hack for grouping tasks by "Location"

splahitk (Pro) says:

Like most users of RTM, I am a bit obsessed with getting things done in the most efficient way possible. Few things are more frustrating to me than realizing I forgot to stop by the grocery store while I was already running errands; or not realizing I could complete a few tasks on my phone while stuck waiting in line; or forgetting to tackle something at home before heading out for the day.

I struggled at first with how to solve this problem. I tried a few solutions that involved a lot of complex tagging (e.g. anything tagged with "chore" or "clean" or "pet" or "yard" would show on my "Home" smart list, and anything tagged with "errand" or "buy" would show on my "Errands" smart list, etc.). Inevitably, tasks slipped through the cracks because I would forget to apply a required tag.

I considered the Location feature, but it required a specific address. While that worked for tasks to be completed at Home, it did not work for Errands or Online tasks. I was forced to specify a single address for each Errand (tedious and not all that valuable to me), and it would not allow me to specify "The Internet" as a location... or would it?

That was my "Aha!" moment. I already knew what general locations I wanted to use for my tasks, and I could simply enter my Home address for each--who would care? Instead of trying to remember any number of valid tags, I could simply enter a single Location for every task:

🏠 I have to be Home to do this task.
🚙 I have to be away from Home to do this task.
📱 I can do this task from anywhere as long as I have internet.
🕳️ It doesn't really matter where I do this task; used rarely, these are more reminders than true tasks (like: "Think about cool new ways to use RTM").

I have a smart list for each Location, and it's organized by due date and priority. Before taking my daughter to practice, I check the "Home" list to see what I can accomplish before it's time to leave. While I wait for my daughter at practice, I complete "Online" tasks on my phone/laptop. Before I drive home from practice, I check the "Errands" list to see if I need to stop anywhere on the way.

I even have a smart list that tells me if I have missed setting the Location field on any tasks--so nothing slips through the cracks!

Reply to android app: clicking on URL opens it in some kind of "sub" browser

scottf51 says:

You have put this in the "tips and tricks" section, you are more likely to get a response in the "help" section. Not being an android user I am afraid I cannot help, but others may be able to

android app: clicking on URL opens it in some kind of "sub" browser

sdfoakes says:

Please can anyone help me figure out why this is happening? In the android app, when I tap on the URL assigned to a task (blue writing), the app opens the URL inside a copy of my usual browser (Lemur) as opposed to letting the phone's usual handler handle it (and opening in the main browser). Any suggestions?

Reply to Using Evernote + RTM for Powerful Checklist Management

emily (Remember The Milk) says:

Hi Gustavo, this is an excellent tip! You're this week's Tips & Tricks Tuesday winner, so we've added a free year of Pro to your Remember The Milk account. :)

Reply to Daily Task Refresh

janvanderploeg (Pro) says:

Nice script!

Reply to Daily Task Refresh

irminger.elise (Pro) says:

I have been on the computer for hours today looking for exactly this type of thing! Please tell me where I can learn this magic. I will, of course, be studying this code to try to see if I can bend it to my will.

Daily Task Refresh

shalgrim (Pro) says:

I don't complete all my tasks that are due every day. (I know that's a bad practice that may trigger you, but let's leave it aside for now.) As a result, I spend the first part of my day updating my list, which mostly involves postponing tasks. That's a lot of selecting and postponing.

To make it a bit more complex, I also don't want to postpone every task. Some tasks are daily reminders that, if I didn't get to them that day, don't really need to be pushed into the next day. For example, "meditate," or "practice gratitude" don't make sense to double up on.

So I've made a MilkScript that cleans up my list for me. Any task in my Now list due before today that is incomplete gets postponed, unless it has the tag "zskip," in which case it gets completed. Finally, if I have a high priority task from yesterday that didn't get completed, I don't want to automate the postponing or completion of that task...I want human input on something like that, so I just leave those alone so they're visible.

Finally, I've also set up a Zap on Zapier so every day at 6 AM my MilkScript gets run automatically

Here's my Script:

const nowList = rtm.getSmartLists().find(smartList => smartList.getName() === 'Now');
const incompleteNowTasksDueToday = nowList.getTasks('status:incomplete AND dueBefore:today')
console.info(`Your "Now" list has ${incompleteNowTasksDueToday.length} items in it due before today`);
const tagsByTaskIdMap = new Map(
incompleteNowTasksDueToday.map(task => {
const id = task.getId();
const tagNames = task.getTags().map(tag => tag.getName());
return [id, tagNames];
})
);
incompleteNowTasksDueToday.forEach(task => {
const name = task.getName();
const priority = task.getPriority();
const tagNames = tagsByTaskIdMap.get(task.getId()) || [];
if (priority.toString() === rtm.Priority.High.toString()) {
// I don't want to postpone or complete High priority tasks; requires human evaluation
console.info(`skipping high priority task ${name}`);
} else if (tagNames.includes('zskip')) {
console.info(`Completing zskip task ${name}`);
task.complete();
} else {
console.info(`Postponing ${name}`);
task.postpone();
}
});

Reply to Bangbang, he shot me down

agt.paper says:

This post needs a like button.

Bangbang, he shot me down

sagansjagger (Pro) says:

I have a tag, bangbang, on any task that I can:
1. handle by myself,
2. with materials that I already have or can acquire quickly, and
3. in about 15-20 minutes.

I also label each task name with a location, such as "Living Room," (@home, in my living room) "General," (for tasks that don't have a specific location) "Out," (for errands) or "Online" (for anything that can be done on a @computer, @phone, or @online [comptuer or phone]).

When combined with locations, name labels, and/or lists in the smart search, I can pull up and then print targeted task lists based on location.

The intent is to tackle the house or errands by "banging" out several tasks in an hour or so of focused work. Bangbang!

For example:
- tag: bangbang AND list: "Cleaning & Yard Work" = all cleaning and yard work tasks that I can bang out quickly
- tag: bangbang AND (name: "Living Room" OR name: "Kitchen" OR "Dining Room") = bang tasks located on the middle floor of my house
- tag: bangbang AND location: computer = bang tasks that require a laptop - no more doom scrolling, wondering what I need to do!

Hope this helps!
- Cass

Tip!

keithhen (Pro) says:

This is a simple tip but anyone can use it. One of the best ways I’ve kept my workday calm is by relying on start dates and a single Smart List that acts like a runway. My role involves juggling projects that don’t all start at the same time, and before I began using start dates in Remember The Milk, I constantly had a “too big” Today list. Now, I give every task a realistic start date so it stays hidden until I can actually begin it. To pull it all together, I built a Smart List I call “Runway” that shows me anything starting soon or due in the next 48 hours:

(startBefore:tomorrow OR dueWithin:"2 days of today")

This view keeps me focused on what’s actionable without overwhelming me with everything I’ll eventually need to do. It’s also flexible. I can quickly scan what’s coming up, spot dependencies, and adjust before things get urgent. With this one Smart List and the discipline of using start dates, I’ve found my workload much easier to manage and my stress level way lower.

Using Evernote + RTM for Powerful Checklist Management

gustavo.marins (Pro) says:

I use Remember The Milk together with Evernote to manage various types of checklists — from movies to watch, gift ideas, wishlists, and books to read. Here's how I make the most of this integration:

1. First things first – In RTM, click on “Integrations” at the bottom right corner of the screen. Then search for the Evernote integration and connect your account.

2. Create each checklist as a separate note in Evernote – I use Evernote's checkbox feature to build structured lists. Each note represents a different checklist, such as:

- 🎬 Movies to Watch
- 🎁 Gift Ideas
- 📚 Books to Read
- 💭 Wishlist
- 💡 Creative Ideas

3. Link the note to a task in RTM automatically – I use Evernote’s reminder feature, which is the small bell icon located at the bottom of the note. When I click the bell and set a reminder — no need to choose a specific date or time — a task is automatically created in RTM with the same title. In RTM, this task will show a small elephant icon in the “Linked with” field, indicating it's connected to the Evernote note. This makes it easy to jump back to the full checklist when needed.

4. Organize checklist tasks in a dedicated project – I place all these tasks in a project called "🗂️ Checklists". The emoji helps visually distinguish it from other lists. I also mark this project as a favorite in RTM so it stays easily accessible and stands out in my sidebar.

5. Versatile and free! – This setup can be used for countless purposes! And best of all, you don’t need to be a Pro user — it showcases the versatility of RTM’s free version.

Reply to Use priorities to plan your time within a single list

emily (Remember The Milk) says:

Hi jansona, this is a great tip and a fantastic way to use priorities. We've shared your tip on our blog as this week's Tips & Tricks Tuesday winner. We've added a free year of Pro to your account. :)