Amplenote Explained 10: A system for managing tasks, part 1
Based on Amplenote's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Daily jots function as the system’s capture inbox, where ideas and to-dos are quickly converted into tasks using Command Enter or Control Enter twice.
Briefing
A minimalist task system in Amplenote hinges on a simple loop: capture everything quickly, review it to sort and enrich tasks, then plan what happens next. The core idea is to keep daily jots as the reliable “inbox” for ideas and to-dos, then use Tasks mode to organize those items into the right notes and schedules—without forcing a rigid folder structure from day one. That approach matters because it reduces the friction of capturing thoughts and turns a messy stream of tasks into a system that can grow naturally as a person’s real-life priorities become clearer.
Capture starts with daily jots. Whenever an idea, reminder, or to-do pops up, it gets typed into the current daily jot and converted into a task using Command Enter or Control Enter twice. If the thought arrives while taking notes, the workflow stays lightweight: create a task immediately, then use the /move command to relocate it—such as moving it to “today,” which routes it back to the daily jot inbox. A quick task menu in the bottom-right corner also supports fast capture via a plus icon. The emphasis is on reliability and speed: the system’s first job is getting tasks out of the head and into a place that can be processed later.
Review is the organizing phase. In Tasks mode, the system filters by daily jots to pull together every task captured into the inbox. Each item then gets a single guiding question: where does it belong? Instead of completing tasks right away, the process focuses on categorization and task enrichment. As tasks get sorted, patterns emerge—tasks cluster around hobbies, career, family and social life, shopping, habits, and long-term goals. This “build as you go” method avoids deep upfront structure; the system develops based on what actually gets captured.
Moving tasks is a frequent action during review. Shopping-related items get moved into an existing groceries note. Habit-like tasks get recurrence rules set—such as daily schedules with a start time (e.g., 10 p.m.) and a duration (e.g., 15 minutes). Other habits can use flexible recurrence, like watering plants three days after the last watering. Tasks tied to long-term personal goals get grouped into a goals note so they’re easier to find when making weekly plans.
Task score and deadlines help prioritize. Tasks with clear deadlines—like renewing a passport before it expires—can be filed into goals once the deadline is already set. Tasks without a near-term deadline can still be elevated by marking them important, which increases task score and helps them rise relative to other items. Urgent tasks can be flagged with /urgent, and important can be combined with urgency for items like regular backups. Even tasks that are neither important nor urgent can be left unmarked and still moved into the goals note.
Planning finishes the loop. Switching back to Tasks mode in agenda view groups tasks by start date, making it easy to draft the next day or week. Tasks can be scheduled by setting a start date with /start, dragging and dropping into the right section, or hidden for a few days until they become more relevant. Recurring obligations like habits and chores remain visible as planning continues. The result is a functional system where daily jots capture quickly, Tasks mode processes and organizes, and agenda view turns that organization into a realistic plan—while keeping complexity optional rather than mandatory.
Cornell Notes
The system uses a three-step loop in Amplenote: capture, review, and plan. Daily jots act as the inbox where ideas and to-dos are quickly converted into tasks (via Command Enter or Control Enter twice). In Tasks mode, filtering by daily jots creates a list of captured tasks that get sorted by asking “where does this belong?”—moving items into notes like groceries, habits, and goals. During review, tasks are enriched with recurrence, start times, durations, deadlines, and priority signals using task score, /urgent, and “important.” Finally, agenda view groups tasks by start date so scheduling, hiding, and drafting next-day or next-week plans becomes straightforward.
How does the system capture tasks without disrupting note-taking or workflow?
What does “review” mean in this workflow, and why doesn’t it complete tasks immediately?
How does the system decide where tasks should live as it grows over time?
What tools are used to turn a raw task into a scheduled obligation?
How do deadlines and task score influence prioritization?
What does the planning step do differently from review?
Review Questions
- When reviewing tasks from the daily jots inbox, what single question guides the decision of where each task should go?
- How do recurrence and start times differ from task score and priority flags like /urgent?
- In agenda view, what are two ways to schedule or defer tasks before committing to a plan?
Key Points
- 1
Daily jots function as the system’s capture inbox, where ideas and to-dos are quickly converted into tasks using Command Enter or Control Enter twice.
- 2
Use /move during capture to relocate tasks without breaking focus—such as sending them back to “today” (the daily jot inbox).
- 3
Review in Tasks mode starts by filtering by daily jots, then sorting tasks by asking where each task belongs rather than completing it immediately.
- 4
Let the system grow bottom-up: move tasks into notes like groceries, habits, and goals based on recurring categories that emerge from real captures.
- 5
Enrich tasks during review with recurrence (including flexible patterns), start times, durations, and deadlines when available.
- 6
Prioritize using task score by marking tasks as important, and use /urgent to flag time-sensitive items even when no fixed deadline exists.
- 7
Plan in agenda view by scheduling with /start or drag-and-drop, and hide tasks for a few days when a plausible plan isn’t ready yet.