Amplenote Explained 1: Your first week in Amplenote
Based on Amplenote's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Amplenote’s first-week workflow follows a capture → review → plan loop to turn raw ideas into scheduled work.
Briefing
Amplenote’s first-week setup centers on a simple loop—capture, review, plan—designed to get users productive quickly without getting lost in feature details. The core idea is that tasks should always have a “home” inside notes, and that weekly review should turn a messy stream of captured ideas into a structured system of notes, tags, and scheduled work.
For getting started, Amplenote offers imports from Evernote or any markdown-exporting note app, including attachments. But the guidance here is to delay importing and instead start fresh for a week. That approach accelerates learning of Amplenote’s note-and-task workflow, and it also reveals which existing items are actually revisited versus what can be left behind—useful “spring cleaning” for people who tend to dump most collected items into folders and never open them again.
The capture step begins with daily jots: automatically created notes that appear each day and serve as a default destination for new ideas. On web or desktop, users can type an idea into today’s daily jot and convert it into a task using hotkeys—Command+Enter on macOS or Control+Enter on Windows. Typing again turns the bullet into a task, making it ready for later processing. On mobile, quick add performs the same function, routing the task into today’s daily jot by default. Desktop clients also support a custom keyboard shortcut to capture from anywhere.
Because tasks must live inside notes, Amplenote forces a destination at capture time. Daily jots are recommended because they’re easy to access and are typically the default. Daily jots are ordinary notes under the hood, viewable in “jots mode” or editable in “notes mode,” but they’re created and tagged automatically.
The review step uses “tasks mode” to consolidate tasks from across all notes into a single list. A key move is creating an “inbox” shortcut by filtering tasks to the daily jots tag, then saving that filtered view to shortcuts so it opens automatically. Reviewing the inbox means deciding where each captured item belongs—those decisions shape the eventual structure of the user’s Amplenote workspace.
Examples show how tasks get reorganized: “buy milk” moves into a new note called “grocery list,” which is then added to shortcuts for quick access. A home-office chair task moves into a “renovate home office” note and gets tagged as a project, with tag colors used to visually separate projects from other to-dos. A “water plants once a week” item is converted into a repeating habit using an “every 7 days” command (with repetition occurring 7 days after completion), then moved into a “chores” note and tagged as “habits,” colored differently.
If the inbox is empty, the review phase is complete. The final step—planning—happens in calendar mode. Users customize the calendar to show the tags they created (habits and projects), then drag and drop tasks onto the schedule, adjusting durations as needed. Habit tasks appear in a distinct color based on tag settings, making responsibilities easier to distinguish at a glance. After a week of iterating through this loop, the system evolves into a personalized set of notes, tags, and categories built from real usage rather than imported assumptions.
Cornell Notes
Amplenote’s first-week workflow is built around three steps: capture, review, and plan. New ideas get captured as tasks inside daily jots (automatically created notes), using hotkeys on desktop or quick add on mobile. During review, tasks mode consolidates tasks into an “inbox” filtered to the daily jots tag, and each item is moved into the right note, tagged, and—when appropriate—converted into repeating habits. Planning happens in calendar mode, where users customize the calendar to display specific tags (like habits and projects) and drag tasks onto the schedule. This matters because it turns scattered captures into a structured system where tasks always have a note “home.”
Why does the setup recommend starting fresh instead of importing old notes right away?
How does Amplenote ensure tasks don’t float around without context?
What is the “inbox” in this workflow, and how is it created?
How do tasks get transformed during review—especially for habits and projects?
How does calendar mode use tags to make planning clearer?
Review Questions
- What are the three steps in the Amplenote first-week system, and what does each step accomplish?
- During review, how does a task move from daily jots into a more permanent note structure?
- In calendar mode, how do tag colors and tag filters affect what appears on the schedule and how tasks are visually distinguished?
Key Points
- 1
Amplenote’s first-week workflow follows a capture → review → plan loop to turn raw ideas into scheduled work.
- 2
Delay importing old notes for a week to learn the daily jots workflow and identify what you actually revisit.
- 3
Capture new ideas into daily jots, then convert text into tasks using Command+Enter (macOS) or Control+Enter (Windows), or quick add on mobile.
- 4
Use tasks mode to create an “inbox” filtered to the daily jots tag, then save it to shortcuts for automatic access.
- 5
During review, move each task into the note where it belongs and use tags (like projects and habits) plus tag colors for clarity.
- 6
Convert repeating items into habits using an “every” command (e.g., every 7 days repeats 7 days after completion).
- 7
Plan in calendar mode by customizing the calendar to show specific tags and dragging tasks onto the schedule with durations as needed.